19:42 <Guest88> Hello, I am having issues getting networking to work correctly on my board. I followed this page (https://ofitselfso.com/BeagleNotes/HowToConnectPocketBeagleToTheInternetViaUSB.php) to set up networking via usb, with some google DNS's. I then manually set the system time. Pinging google.com results in no packet loss, pinging beagleboard.org results

19:42 <Guest88> in 100% loss. I then tried running 'sudo apt update' and all the debian connections timed out, though pinging one of the servers results in no loss. I tried following this BeagleBoard page on upgrading (https://beagleboard.org/upgrade), but under 'update the boot-scripts' it says to 'cd /opt/scripts/' however there is no 'scripts' folder or file on

19:42 <Guest88> my board there. Any ideas on what the issue is?

19:46 <zmatt> you don't have /opt/scripts ? that sounds very odd, what image do you have flashed onto it? also, what board do you have?

19:47 <Guest88> AI-64, bbai64-debian-11.3-xfce-arm64-2022-06-14-10gb.img.xz

19:47 <zmatt> ah ok, ai64

19:49 <zmatt> can't you just connect it to your network via ethernet?

19:50 <zmatt> or if your computer has internet via wifi and has an ethernet port, use internet sharing to ethernet and connect the beaglebone to that. this requires no network setup other than enabling internet sharing

19:52 <Guest88> I'll give that a shot

19:52 <zmatt> what this guide is doing is a bad idea since it's bypassing the system's network manager... though at least the debian 11 images use systemd-networkd which is less prone to fight you if you work behind its back than connman on debian 10 did

19:52 <Guest88> Interestingly pip works just fine- not sure why only some networks are fine

19:52 <zmatt> what exactly is the error you're getting?

19:54 <zmatt> oh btw that guide has you messing with /etc/resolv.conf ... that file should actually be a symlink to /run/systemd/resolve/stub-resolv.conf to get the nameservers configured automatically based on dhcp

19:55 <zmatt> (I think systemd-resolved has fallback to google's nameservers anyway, so even in the dhcpless situation you wouldn't need to configure that manually I think)

19:56 <Guest88> when running 'sudo apt update', various version of "could not connect to debian.beagleboard.org", "cannot initiate the connection to deb.debian.org (Network is unreachable)", "connection timed out"

19:57 <Guest88> how could I symlink resolv.conf to stub-resolv.conf?

19:59 <zmatt> is it not already/still a symlink? I'm not sure what happens if you try to edit a file that's a symlink with nano, whether it'll replace the symlink with a file or whether it'll edit the pointed-to file

20:00 <Guest88> Not sure, when I opened it in nano there was a comment "No DNS servers known" and a single line 'search .'

20:02 <Guest88> I tried changing it back just now and it no longer recognizes google.com

20:03 <zmatt> that sounds like you edited the pointed-to file (which is bad since that's an auto-generated file you shouldn't be editing)

20:04 <zmatt> but it also sounds like it's a symlink to the wrong file

20:04 <zmatt> what does ls -ld /etc/resolv.conf show?

20:04 <zmatt> I suspect it's a symlink to /run/systemd/resolve/resolv.conf

20:04 <zmatt> which would be wrong, it should point to /run/systemd/resolve/stub-resolv.conf

20:04 <Guest88> lrwxrwxrwx 1 root root 32 Jun 14  2022 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf

20:04 <zmatt> yep that's definitely wrong

20:05 <zmatt> ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

20:07 <Guest88> ok I ran that, then ran ls -ld /etc/resolv.conf to check and it gave me

20:07 <Guest88> lrwxrwxrwx 1 root root 37 Mar 14 20:05 /etc/resolv.conf -> /run/systemd/resolve/stub-resolv.conf

20:07 <Guest88> again

20:08 <zmatt> that looks correct

20:08 <zmatt> what do you mean "again" ? it now points to stub-resolv.conf rather than resolv.conf

20:08 <Guest88> i misread it my bad

20:09 <Guest88> pinging google.com results in "temporary failure in name resolution"

20:09 <zmatt> can you share the output of "ip addr" and "ip route" using e.g. pastebin? (don't paste directly into chat)

20:09 <Guest88> sure

20:10 <zmatt> hmm maybe I'm wrong about fallback dns being configured by default

20:10 <zmatt> yeah it seems I am

20:11 <Guest88> https://pastebin.com/A84G8CUJ

20:11 <zmatt> you can configure FallbackDNS=8.8.8.8 in /etc/systemd/resolved.conf

20:13 <zmatt> though, maybe it would be better to just configure it specifically for the usb interface if you're still going with that, it's not really needed in any other circumstance

20:14 <Guest88> alright then I'll go try the ethernet cable and see if that works

20:14 <zmatt> that's certainly what I'd recommend, it also avoids the risk of losing connection to your beaglebone as a result of messing with the usb networking (on the beaglebone side and/or your computer)

20:15 <zmatt> but if you want to go for usb, the proper way to add the default route and set the dns would be by setting Gateway=192.168.7.1 and DNS=8.8.8.8 in the [Network] section of /etc/systemd/network/usb0.network and then do "sudo networkctl reload"

20:16 <zmatt> oh

20:17 <zmatt> hold on, I see that usb now uses /24 as mask instead of /30, so there's nothing guaranteeing your PC will be 192.168.7.1

20:17 <Guest88> so far 192.168.7.1 has worked

20:18 <zmatt> sure, since it's the first ip in the range, but it doesn't feel great to rely on that

20:18 <zmatt> anyway, this bizarre setup of the PC being the dhcp client but also the gateway is kinda gross anyway

20:20 <zmatt> normally when using internet sharing the PC would be the dhcp server and the beaglebone the DHCP client, which is how it will work by default via ethernet, but reconfiguring usb like that is a bit riskier since it risks connectivity (in theory you should be able to ssh to "beaglebone.local" regardless of network config thanks to link-local IPv6, except OSes love to randomly break that under some ...

20:20 <zmatt> ...circumstances)

20:21 <zmatt> Windows is particularly obnoxious about that... it may decide to classify the usb network interface as a "public network" and in that case it refuses to resolve .local names on it

20:27 <Guest88> stole an ethernet from another computer and just hooked the board up to a monitor, worked easily. I'll just stick to this setup then since it works. Thank you for all your help zmatt