[12:02] join /php [16:07] Hello, (It might not be related to this topic. It is more network based problem.) I have a raspberry pi which is connected to the router wirelessly, and I have a vpn client configured on it. My router is very old, and I cannot install a new firmware on it. I just wanted to know that if it could be possible to route all the chromecast traffic through raspberry pi? (Through VPN?) I can connect Chromcast to the raspberry pi, using a LAN cable. [16:12] bindi: probably too late but if you're around here's a package of scripts that automate building and testing RAID-1 + LUKS + LVM in a virtual machine http://iam.tj/projects/ubuntu/raid1-luks-lvm-test.tar.gz [17:23] I have just deployed an Ubuntu machine, it shows '9 packages can be updated. 7 updates are security updates.' but when I run sudo apt-ge t update; sudo apt-get upgrade, nothing happens. Do you know what should I do? [17:23] When I log back in again, it shows me the same messages. [17:24] I have asked the same question in #ubuntu, but no I have received no response back. [17:29] TJ- respond me back in #Ubuntu. Thanks again. [17:29] fleabeard: place your details here fleabeard [17:32] hiya lotuspsychje: my issue is my Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network Connection (rev 02) [17:32] is only running in 100 Mbps mode instead of 1000 Mbps mode. I'm currently using Ubuntu Server 18.04 LTS. [17:32] system up to date fleabeard ? [17:32] fleabeard: show us "lspci -nnk -d::0200" [17:33] TJ-, https://pastebin.ubuntu.com/p/8KpRSVK67x/ [17:33] lotuspsychje, yes, updated this morning (fresh install) [17:33] allright tnx fleabeard [17:34] fleabeard: and check what the link is advertising with "sudo ethtool " [17:35] Compare the advertised, supported, and actual "Speed:" [17:36] TJ-, https://pastebin.ubuntu.com/p/vZYHN33qyR/ [17:37] fleabeard: it has auto-negotiated with the switch, so either a poor connection somewhere (Gigabit needs all 8 cores working) or the switch doesn't agree :) [17:37] TJ-, thanks, I'm trying to confirm with the router I'm using (TP-Link Archer C9) that the ports are gigabit. [17:40] fleabeard: "4 10/100/1000Mbps LAN Ports," [17:41] TJ-, thank you! my goodness I was having so much trouble verifying this for some reason! So I'm guessing all 4 ports support gigabit? [17:44] yes, and the WAN port, according to https://www.tp-link.com/us/products/details/cat-5506_Archer-C9.html#specifications [17:45] fleabeard: I'm finding a lot of reports from several years ago about this same symptom with that chipset, and its predecessor, affecting Windows, but I'd have thought it was resolved by now [17:46] one person says, "unplug and replug after initial negotiation (of 100Mbps) sometimes fixes it" [17:49] fleabeard: what kind cable and how long? [17:50] TJ-, I'll give that a try then. [17:50] cryptodan_mobile, it's a hand-made cat6 cable about 5' long [17:51] I've reinstalled libssl1.0.0 and libssl-dev, but I'm still getting errors about "error while loading shared libraries: libssl.so.1.1: cannot open shared object file: no such file or directory" [17:51] what's the process to fix this? [17:52] fleabeard: if ya can go buy a premade 10foot one to see if it's your cable [17:52] TJ-, the unplug/re-plug trick didn't do the trick :( [17:52] cryptodan_mobile, I tried a purchased cat5e cable and had the same issue (which is why I created the cat6 cable last night) :) [17:53] Wow [19:57] Greetingws [19:57] Greetings, rather. [20:00] I've got a 14.04 LTS server that's been up and doing its job for 4 years now.. looking at rebuilding. I've seen that there seem to be a number of changes to networking in 18.04.1... And that some folks are having headaches with it... [20:01] is 18.04.1 stable enough to put in and expect to behave itself ? [20:01] Annoyed: the issues are generally around converting ifupdown to netplan/systemd-networkd configs [20:02] Annoyed: so really it's mostly more about the learning curve [20:02] Annoyed: plus of course, for 14.04>18.04 the init system changes from upstart to systemd [20:04] That's one of my concerns. I've been using this thing as a router; 2 interfaces, configured in /etc/network/interfaces. In my setup, the inside interface doesn't need gateway or DNS info, it's the uplink for the inside network. But looking at setting up the file in /etc/netplan, everything I've read says you have to set a DG & DNS in that file... [20:04] I don't want to set amachine 2nd DG for this [20:05] err... I don't want to set a 2nd default gateway for this machine. [20:05] netplan is junk, stick with ifupdown [20:05] Can you still use the old way ? [20:06] Or maybe just 16.04.5 instead? [20:07] yes you can still do it the old way and maintain your /etc/network/interfaces file [20:08] I've set up VM's for both and I really don't like the look of netplan either.. Is there a howto or docs someplace on using 18.04 with the old setup? [20:08] Annoyed: netplan interfaces don't need a default gateway setting [20:10] T3- So I can try to just set it up w/out that info in the yaml file? [20:17] The more I read on this, the more I think I'm better off installing 16.04.5 and wait for the dust to settle on this new crap.. I don't want to spend a lot of time figuring out netplan if it's a problem child. [20:26] Annoyed: recall that netplan is designed to *generate a run-time config* - if the config is static then netplan isn't needed, you can directly create a systemd-networkd config [20:26] Annoyed: the point of netplan was to support 'cloud' containerised devices via cloud-init but it seems to have leaked back to bare-metal/long-running 'traditional' servers [20:27] Outside interface is DHCP, but inside is static. [20:27] Netplan should only be on the cloud instance then [20:28] So how do I configure the inside interface? [20:29] Annoyed: if you want to see a systemd-networkd config for a server with 2 logical interfaces (1 x VLAN, 1 x LACP bond) see http://iam.tj/projects/ubuntu/systemd-networkd-bonding.txt [20:31] Annoyed: for your needs you'd only need 2 basic .network descriptions, 1 for static, and 1 for DHCP [20:31] I gather I can leave whatever the installer sets up for the outside interface, cause it seems to work, at least on the VM, but how do I set up the inside static? [20:33] \ /etc/systemd/network seems to be empty on my VM of 18.04 [20:33] Annoyed: look at my "/etc/systemd/network/LAN_Aggregate.network" you'd just alter the "Name=bond0" to be the name of the LAN NIC [20:33] Annoyed: yes, it will be, that is where the sysadmin puts the static config [20:34] Annoyed: if a runtime config is being generated (by netplan) it'll be in /run/systemd/network/ [20:34] Annoyed: and you can directly copy a file from there to /etc/systemd/network/ and remove the netplan config so netplan no longer generates a boot-time config under /run/ [20:35] Oh, so I create a devicename.network file in /etc/systemd/network, and treat that as /etc/network/interfaces? [20:35] Annoyed: :D yup [20:35] Ok, that makes sense [20:36] Annoyed: and remove any /etc/network/interfaces entries/file(s) so that the sysv ifupdown compatibility systemd units don't try to create an additional config! [20:36] This is gonna be a clean install [20:36] so there shouldn't be any [20:37] Hmmm is one, but it's all comments [20:37] Right; with you mentioning the 14.04 I just wanted to be clear - we've seen people caught out by systemd playing nice with the existing ifupdown config and the sysadm also creating a systemd config, and the 2 clashing [20:38] Ok, thanks [20:40] That makes sense [20:43] Thanks for the help. Much appreciated [21:48] TJ-: currently rocking Debian on the machine :D [21:49] bindi: I've been updating the scripts, and you can now see an ascii-cast of it at work: http://iam.tj/projects/raid-vm/ [21:50] bindi: I've been playing with it in the VM, detaching disks etc. It boots perfectly degraded without me even realising :D [21:51] nice [22:05] I integrated the LUKS unlocking into the initrd.img so the passphrase only needs typing once, for GRUB