**** BEGIN LOGGING AT Sat Dec 05 02:59:57 2020 Dec 05 03:00:24 some fellas from ##networking helped me fix it Dec 05 03:00:53 but i dont really understand all the ins and outs Dec 05 03:01:04 i figured i should submit my findings to the mailing list Dec 05 03:01:35 where did that route even come from? it's not on my beaglebone running the 2020-04-06 image Dec 05 03:03:21 this is the bb ai, i'm using the default image Dec 05 03:03:26 but i upgraded everything in /opt/scripts Dec 05 03:03:34 i have no idea where that configuration came from Dec 05 03:03:39 but i restarted and it present on boot Dec 05 03:04:11 are you using usb networking or just ethernet/wifi ? Dec 05 03:04:24 i mean in that example, only wifi Dec 05 03:04:31 i checked all of them Dec 05 03:04:40 all of what? Dec 05 03:05:26 i mean, i made sure i could all of the network interfaces it enumerated Dec 05 03:05:34 usb0, 1, wlan0, soft ap, eth0 Dec 05 03:05:41 not blue tooth, had no idea how to do that Dec 05 03:05:49 i could use all* Dec 05 03:09:29 on my own beagle I normally don't use bb.org's obscure boot setup scripts for usb stuff Dec 05 03:09:50 and I'm not super familiar with how they work Dec 05 03:10:02 lemme see what I get on my bbai Dec 05 03:17:37 lol i got the demo running Dec 05 03:17:44 it wasn't hard tbh after the update Dec 05 03:17:46 it just runs Dec 05 03:17:50 the mpeg streamer is pretty cool Dec 05 03:18:03 my current bbai system definitely doesn't add a default route to usb0 Dec 05 03:18:32 interesting Dec 05 03:18:38 i mean i couldn't find where mine was being added tbh Dec 05 03:19:13 but it's running the 2019-08-03 image Dec 05 03:19:42 I'm looking at a git diff between its /opt/scripts and origin/master Dec 05 03:19:48 i mean everything else seems to be fine Dec 05 03:19:56 actually i dont think this happened until i ran the updates Dec 05 03:20:08 the usb stuff has definitely been made more configurable Dec 05 03:20:09 ok Dec 05 03:20:18 alright now i'm gonna pull the fan off and see how long until this thing crashes Dec 05 03:20:19 update packages or update /opt/scripts ? Dec 05 03:20:25 both Dec 05 03:20:29 pulled scripts, ran update kernel Dec 05 03:20:34 and updated packages Dec 05 03:20:35 restarted after Dec 05 03:21:40 oh jeez this is still a debian stretch system.. ok maybe I should first just reflash this bbai Dec 05 03:22:20 huh thats what i have Dec 05 03:22:26 and 4.14.108-ti-4137 Dec 05 03:23:34 so you're using an old system but with a few random thing updated to create a nice mix of ancient and new stuff? :) Dec 05 03:23:51 i mean whats next dist-upgrade? Dec 05 03:24:33 I mean that's a pretty desperate act and not one I'd look forward on a beaglebone unless it's a very lean system with few packages installed Dec 05 03:25:03 and it's still no substitute for flashing an uptodate image due to things like /boot/uEnv.txt and defaults in /etc/ Dec 05 03:25:51 what does /etc/dogtag say? Dec 05 03:26:36 hmm big question is, do I have a spare sd card Dec 05 03:27:06 lol my network is faling apart Dec 05 03:27:14 we're at 60 degrees and counting Dec 05 03:27:20 object recognition was pretty hokey Dec 05 03:27:30 2019-08-03 for dogtag Dec 05 03:28:36 lol i just streamed for 6 hours straight Dec 05 03:31:58 it might actually be stabalizing even with the demo running Dec 05 03:32:31 ok so that's probably why I still haven't reflashed my bbai, I don't seem to have a spare card of adequate size Dec 05 03:32:57 temp is still climbing slowly :-( Dec 05 03:33:34 anyway, if you're not using usb networking you could disable it entirely using /etc/default/bb-boot Dec 05 03:33:49 i took a look there Dec 05 03:33:55 running the command to delete the default worked Dec 05 03:34:02 i might add it to a script Dec 05 03:34:52 for clarify, could you share the output of "ip route" after boot? Dec 05 03:35:11 im pretty sure the one i gave you was after boot but yes after this little experiment is done Dec 05 03:35:14 (like I said, the output of the deprecated legacy "route" tool isn't super helpful) Dec 05 03:35:18 i just want to see how how it gets without fan Dec 05 03:35:22 oh okay yeah ip route not route Dec 05 03:35:24 sure Dec 05 03:35:28 how hot* Dec 05 03:35:44 this image classification script is crazy Dec 05 03:35:48 it keeps on calling my head a beer glass Dec 05 03:36:45 lol Dec 05 03:38:58 so will it shut down at 80? Dec 05 03:41:31 like its getting above 70 very slowly Dec 05 03:41:46 i think i need to run it overnight to see it go over threshhold Dec 05 03:42:24 I've pulled /opt/scripts on my bbai and updated bb-customizations and bb-bbai-firmware (which pulled in bb-usb-gadgets as dependency) .. let's see if that has any impact Dec 05 03:42:49 it definitely does Dec 05 03:43:03 oh? Dec 05 03:43:21 though I'm confused why this results in no default route on ethernet Dec 05 03:43:33 im not sure what it results in at all Dec 05 03:44:47 like, usb0 isn't managed by connman, eth0 is and it's up and should have a default route Dec 05 03:45:01 you're connected via default route? Dec 05 03:45:10 ? Dec 05 03:45:24 it's on my lan, default route doesn't matter except for internet access Dec 05 03:45:27 sorry i might be losing my mind Dec 05 03:45:39 so one of the issues was that ipv4 and ipv6 were using different routes Dec 05 03:45:44 since usb0 doesn't have ipv6 Dec 05 03:45:50 ???!? Dec 05 03:45:52 so ping google worked cause that resolves to ipv6 Dec 05 03:46:02 but ping github didn't cause that resolves to ipv4 Dec 05 03:46:15 and since the default route (usb0) doesn't have ipv6, it would switch to using the correct route Dec 05 03:46:19 oh wtf you're right, why doesn't it have ipv6 Dec 05 03:46:38 but also again, where the fuck is the default route on eth0 Dec 05 03:46:56 i mean if you delete the default route entirely it seems to just fall back to some intelligent logic Dec 05 03:47:26 no it doesn't, that's probably just connman trying to fight you Dec 05 03:47:54 if you remove all default routes there's no default route, unless something subsequently adds a default route Dec 05 03:48:00 yeah something does Dec 05 03:49:01 its that plume.lan thing https://paste.ofcode.org/U7g4ZQbS5TfD7SnrEUiKzh Dec 05 03:49:02 which itself is weird, but not as weird as the fact that the default route to eth0 is missing to begin with Dec 05 03:49:33 "it" ? Dec 05 03:49:52 the new default route that was added after i deleted the only default route Dec 05 03:50:00 gateway as "plume.lan" Dec 05 03:50:02 in the paste Dec 05 03:50:10 no clue what it is Dec 05 03:50:13 yeah so presumably connman is doing that for some reaosn Dec 05 03:50:20 ehm, it's evidently your gateway on wlan0 Dec 05 03:50:52 yeah i guess Dec 05 03:50:59 i'm really out of my area here Dec 05 03:51:07 the ppl over at #networking were like SCREAMING at me Dec 05 03:51:17 "You're STUPID! GO BACK TO KINDERGARTEN" Dec 05 03:51:25 i had to copy paste the link to the freenode code of conduct lol Dec 05 03:51:44 or at least one person was anyway Dec 05 03:51:50 but again, that connman reacts to manual meddling and overwrites config isn't that weird, it is a network manager after all, the weird part is that the default route to eth0 is missing to begin with Dec 05 03:51:53 this is IRC tho so Dec 05 03:52:02 sometimes people get angry Dec 05 03:52:02 I mean, I can understand #networking not being very useful Dec 05 03:52:06 no they were Dec 05 03:52:13 they helped Dec 05 03:52:16 inbetween the insults LOL Dec 05 03:52:38 i mean people really shouldn't be so mean Dec 05 03:52:43 because not everyone is going to stand up like i did Dec 05 03:52:46 and it pushes people away Dec 05 03:52:46 since your networking setup consists of an obscure network manager (connman) whose behaviour they're probably unfamiliar with, and a bunch of obscure beaglebonespecific setup scripts Dec 05 03:52:55 Yea...not naming any names. @zmatt! Dec 05 03:52:58 well yeah there is that Dec 05 03:53:17 Ha. Dec 05 03:53:45 connman is so weird Dec 05 03:53:54 ayjay_t: and I wouldn't call your current solution a solution... it's more like a random poke that inexplicably triggers a reconfiguration that happens to result in a working result Dec 05 03:54:11 yes I don't really understand why connman in the first place Dec 05 03:54:25 well yeah i mean Dec 05 03:54:34 i deleted the default and it established a default default that works Dec 05 03:54:41 systemd-networkd is included with systemd, more flexible, easier to configure, and more well-behaved Dec 05 03:54:45 right, that's the inexplicable behaviour Dec 05 03:54:51 i'm assuming it was like "hmm, this interface is UP, lets use that as default" Dec 05 03:54:56 no Dec 05 03:54:56 which i think is GENIUS Dec 05 03:55:37 who knows man Dec 05 03:55:56 i mean i barely understand how networks are supposed to work let alone how linux implements them Dec 05 03:57:05 this isn't anything linux, this is connman and a pile of ad-hoc shell scripts Dec 05 03:57:40 did you find the offending line by the way? Dec 05 03:57:44 you have the diff on those files you updated right Dec 05 03:58:14 ok, disconnecting and reconnecting ethernet doesn't help, so either the default route to ethernet is being overwritten each time, or its presence somehow keeps connman from adding the correct default route which is completely bonkers Dec 05 03:58:26 haven't found it yet no Dec 05 03:59:52 oh for fuck's sake Dec 05 04:00:20 I forgot the network configuration is spread across connman AND a bunch of shell scripts AND ifupdown Dec 05 04:00:36 because why have two network configuration mechanisms when you can have three Dec 05 04:00:54 and it's right there, /etc/network/interfaces Dec 05 04:00:59 well i guess if you're going to have like 6 network interfaces Dec 05 04:01:11 then you want all 6 managed by the same network manager Dec 05 04:01:16 haha not us Dec 05 04:01:29 it's not educational if there's no pain Dec 05 04:01:46 anyway, the bogus route is coming from /etc/network/interfaces Dec 05 04:01:51 is it really tho???? Dec 05 04:01:56 i looked there i didnt' see anything... OH Dec 05 04:02:04 i mean id idn't see anything conspicuous Dec 05 04:02:14 unless this is just on my local system? Dec 05 04:02:21 i mean i saw the usb0 lines Dec 05 04:02:21 due to trying to replicate someone's setup Dec 05 04:02:43 like, installing updates shouldn't touch /etc/network/interfaces Dec 05 04:03:06 i don't necessarily recall that it did Dec 05 04:03:21 and it didn't, file last modified in 2019 Dec 05 04:03:36 so I have this garbage on my system locally presumably because I was trying to replicate someone's broken setup Dec 05 04:03:41 possibly yours? :P dunno Dec 05 04:03:44 yah same here Dec 05 04:03:53 i mean this is a new board from me Dec 05 04:03:56 i did not add this Dec 05 04:04:05 either that or it was actually in the 2019-08-03 image by accident Dec 05 04:04:07 i mean whats the offending line in your file? Dec 05 04:04:20 mine is iface usb0 inet static, address netmask network and gateway Dec 05 04:04:27 but if it wasn't touch why did things break after the setup Dec 05 04:04:28 all of which are offending Dec 05 04:04:29 it can't be this Dec 05 04:04:37 are they? its not setting it up as default tho is it? Dec 05 04:04:41 it's just giving itself an IP Dec 05 04:04:48 "gateway" = default route Dec 05 04:05:15 it needs to give itself an IP to have dnsasq run dhcp on that interface tho AFAIK Dec 05 04:05:17 and ip configuration doesn't belong here, and it doesn't actually come from here normally on the bbb Dec 05 04:05:20 so would you just remove the gateway line? Dec 05 04:05:38 but why did this only matter after we updated :-( :-( :-( Dec 05 04:05:45 note how usb1 doesn't have config in /etc/network/interfaces but does have a network config Dec 05 04:05:49 because the scripts changed Dec 05 04:05:57 and now somehow for some reason involve ifupdown Dec 05 04:06:00 and previously didn't Dec 05 04:06:40 though honestly I don't even know what scripts are involved, there is a zoo of scripts and I can't really make heads or tails of it Dec 05 04:07:02 but /etc/default/bb-boot seems to be the primary place they pull config from Dec 05 04:07:42 yeah i looked through the scripts but it was messy Dec 05 04:08:09 so i mean we should probably tell rcn tho? he is the maintainer Dec 05 04:08:49 I really need to make a guide on how to replace all this mess with just systemd-networkd (+ a "g_ether" line in /etc/modules if you want usb networking) Dec 05 04:09:14 but this seems like a significant bug Dec 05 04:09:23 since anyone who tries the ai for the first time is going to go through the update thing Dec 05 04:09:28 and then immediately lose access to github Dec 05 04:10:40 so it breaks the udpate process during the update process since the bbb.io instructions rely on github Dec 05 04:10:42 yeah if this bogus config is indeed in /etc/network/interfaces on the factory bbai image then this is a problem Dec 05 04:12:07 but at the same time it doesn't bother until you start running the updates Dec 05 04:12:12 so the updates need to account for it Dec 05 04:12:31 and i guess more importantly, can account for it Dec 05 04:12:39 like i dont think the user needs to notice Dec 05 04:13:18 anyway, that at least fixed the issue: https://pastebin.com/raw/2knWZhmy Dec 05 04:13:41 of course the second question is what the fuck is connman thinking Dec 05 04:13:48 why is it the way it is Dec 05 04:14:09 connman just seems obtuse and terrible Dec 05 04:14:17 well, its a con, man Dec 05 04:19:13 man that was a beagle adventure tonight Dec 05 05:22:59 ayjay_t: first draft version on how to switch a beaglebone to use systemd-networkd ... I need a better solution for the MAC address of usb gadgets, and this draft doesn't include wifi yet (just ethernet and rndis): https://pastebin.com/3tjj3v3R Dec 05 05:23:37 lines 61 and 67 are scary yet satisfying ;) Dec 05 05:27:30 this thing is at 82 C and still kicking Dec 05 18:08:59 tbh i like dnsmasq Dec 05 18:17:04 Hello everyone. I wonder why my BBBW doesn't have a wireless interface. WiFi and BT leds are off, there is no wlan0 and no wireless network created. I updated the image with a sd but still no success. Any ideas? Dec 05 18:28:28 check dmesg for anything relevant? Dec 05 18:28:43 My other BBBW worked out of the box, creating a beaglebone network. Dec 05 18:29:15 
: PHY 4a101000.mdio:00 not found[ 20.370149] net eth0: phy "4a101000.mdio:00" not found on slave 0, err -19 Dec 05 18:30:44 ip addr returns: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever2: can0: mtu 16 Dec 05 18:30:44 qdisc noop state DOWN group default qlen 10 link/can3: can1: mtu 16 qdisc noop state DOWN group default qlen 10 link/can4: eth0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether f4:5e:ab:51:e9:95 brd ff:ff:ff:ff:ff:ff5: usb0: mtu 1500 Dec 05 18:30:45 qdisc pfifo_fast state UP group default qlen 1000 link/ether f4:5e:ab:51:e9:97 brd ff:ff:ff:ff:ff:ff inet 192.168.7.2/24 brd 192.168.7.255 scope global usb0 valid_lft forever preferred_lft forever inet6 fe80::f65e:abff:fe51:e997/64 scope link valid_lft forever preferred_lft forever6: usb1: mtu Dec 05 18:30:45 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether f4:5e:ab:51:e9:9b brd ff:ff:ff:ff:ff:ff inet 192.168.6.2/24 brd 192.168.6.255 scope global usb1 valid_lft forever preferred_lft forever inet6 fe80::f65e:abff:fe51:e99b/64 scope link valid_lft forever preferred_lft forever Dec 05 18:30:53 woh no don't post a lot like that Dec 05 18:31:03 use a paste bin Dec 05 18:31:05 sorry Dec 05 18:31:15 like paste.ofcode.org or something Dec 05 18:31:47 so you have two boards, one works, the other doesn't, the one that doesn't, you tried to update the image on, it still doesn't work? Dec 05 18:32:31 yes, both has the same image now Dec 05 18:32:45 I used the same sd card to flash both cards Dec 05 18:32:59 yeah and one works and one doesn't Dec 05 18:33:04 yep Dec 05 18:33:05 there's no wlan0 appearing Dec 05 18:33:12 nope Dec 05 18:33:24 systemctl list-units --failed Dec 05 18:33:56 0 loaded units listed Dec 05 18:35:08 if i list all I see wlan0.service disablesd Dec 05 18:36:11 i wonder what kind of error you'd get if you enabled and started it? Dec 05 18:36:26 journalctl -eu wlan0.service Dec 05 18:36:29 Hi guys, I am new to beaglebone black. I am trying to install the Ethtool package in my BBB but getting error as "unable to locate package ethtool". Kindly help me up Dec 05 18:37:22 sorry Huyston i assumed you already knew systemctl enable wlan0.service; systemctl start wlan0.service; Dec 05 18:37:36 but tbf Huyston i'm surprised you're not seeing any errors as certainly boot scripts expect working wifi Dec 05 18:37:52 and if it's not just a matter of turning it on (which.... would be weird), i'd inpsect the board for damage Dec 05 18:38:03 that's how much help i'd be, there are people here who have more knowledge Dec 05 18:39:00 Maman make sure you run `apt-get update` first Dec 05 18:39:02 or apt update Dec 05 18:39:12 i enable it and journal says it was successfull, but no wifi still. I'll try to reboot and check Dec 05 18:39:24 Yes. I did the apt-get update first. Its not working Dec 05 18:39:33 showing the same error Dec 05 18:39:38 But thanks for helping, those commands will help me debug a little more Dec 05 18:39:57 Maman: what's not working, apt update or apt install? Dec 05 18:40:33 apt install Dec 05 18:40:52 sudo apt-get update Dec 05 18:40:55 and then Dec 05 18:40:56 try `apt-cache search ethtool` Dec 05 18:41:17 that's right, i think he said he already ran update, but you definitely have to run update first Dec 05 18:41:38 Its saying unable to locate package ethtool Dec 05 18:42:12 Maman, run these commands: `sudo apt-get update; sudo apt-cache search ethtool; sudo apt-get install ethtool` Dec 05 18:42:22 and then copy and paste them and the output to paste.ofcode.org and post the link here Dec 05 18:42:33 Sure Dec 05 18:45:35 https://paste.ofcode.org/Jcq22g6hfrcWjgjsbLyzTe Dec 05 18:45:46 Can you check the code now? Dec 05 18:46:15 sure yeah i'm reading it Dec 05 18:46:19 your update isn't working, it's failling Dec 05 18:46:24 does `ping google.com` work? Dec 05 18:47:10 what does `ip route` say? Dec 05 18:47:15 (use another pase) Dec 05 18:47:17 paste* Dec 05 18:47:37 Maman: ^^ Dec 05 18:47:37 Its giving temporary failure in name resolution Dec 05 18:47:43 ping google.com is? Dec 05 18:47:50 ip route Dec 05 18:48:09 that's not making sense to me, ip route just tries to list things Dec 05 18:48:10 Its giving temporary failure in name resolution Dec 05 18:48:21 This error is for ping google Dec 05 18:48:37 169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.104.72 Dec 05 18:48:53 This is what ip route give Dec 05 18:48:57 is that all it gives? Dec 05 18:49:04 Yes Dec 05 18:49:18 okay well basically your beaglebone isn't properly connected to the internet Dec 05 18:49:36 are you sure the ethernet connection really goes to the world wide web? Dec 05 18:49:36 default dev eth0 scope link Dec 05 18:49:40 This is all it gives Dec 05 18:50:10 I am using debian linux OS using putty Dec 05 18:50:38 I am sorry I am a power engineer PhD student, trying to run this beagle for the first time. Dec 05 18:50:48 but is the beagle actually connected to the internet? Dec 05 18:50:57 How to know this? Dec 05 18:51:08 I have connected the ethernet cable with my laptop Dec 05 18:51:19 and my laptop has internet connection Dec 05 18:51:25 if you connect the cable directly to your laptop, the laptop doesn't automatically give it the internet Dec 05 18:51:33 ok Dec 05 18:51:37 it's easier to connect it directly to a router or network switch, but you can also "bridge" the connection Dec 05 18:51:48 Then what do I have to do to connect with with internet Dec 05 18:51:57 i forget the exact commands you have to run on your laptop Dec 05 18:52:04 I do have a router as well. Dec 05 18:52:06 google "bridge wifi to ethernet" Dec 05 18:52:14 you can connect the beaglebone directly the router, and it will work immediately Dec 05 18:52:22 and then you can log into your router and you can find it's IP address that way Dec 05 18:52:27 and you can ssh into it that way, it will have internet Dec 05 18:52:41 Should I connect that router with the laptop also or directly to the internet connection Dec 05 18:52:43 or you can keep it attached to your laptop, and you can google "bridge wifi to ethernet" and follow the steps on your laptop Dec 05 18:52:56 your router is connected to the router via wifi? Dec 05 18:53:03 sorry, your laptop is connected to the router via wifi? Dec 05 18:53:47 No via ethernet cable Dec 05 18:54:02 well i guess you have two ethernet ports on your laptop? Dec 05 18:54:08 It is basically a switch Dec 05 18:54:14 here is the basics: anything connected to router, wifi or ethernet, gets internet automatically Dec 05 18:54:27 No. i have not connected my router yet but it is still with me Dec 05 18:54:28 if there is something inbetween, you need to look up how to bridge Dec 05 18:54:39 oh the router is not connected to the internet? Dec 05 18:54:50 ritenow I have connected my beagle direclty with the laptop RJ45 connector Dec 05 18:54:55 NO. Dec 05 18:55:12 lol okay its just a random router Dec 05 18:55:18 i mean the actual router you are using Dec 05 18:55:21 to connect to the internet Dec 05 18:55:33 yes its a spare router which I will be using to connect more than 1 BBB. Dec 05 18:55:45 that's not going give it the internet unless the router has internet though Dec 05 18:55:55 Maman, we are looking for a router that has an internet connection Dec 05 18:56:00 the issue is that the beaglebone doesn't have internet Dec 05 18:56:20 if I connect my router with the laptop using ethernet cable and then connect my BBB with the router. Will it work? Dec 05 18:56:44 if the router isn't connected to the internet, it will not work Dec 05 18:56:47 As my laptop will have internet via lab wifi Dec 05 18:56:53 no it wont work Dec 05 18:56:57 so you need to do Option B) Dec 05 18:57:01 "bridge wifi to ethernet" Dec 05 18:57:10 options like? :( Dec 05 18:57:16 huh? Dec 05 18:57:18 alrighty. Dec 05 18:57:19 no i mean you need to do plan b Dec 05 18:57:25 Sorry read your message late Dec 05 18:57:29 Mamn, once you learn to do the bridge Dec 05 18:57:51 bridge wifi to ethernet- So I have to search how to do this? Dec 05 18:58:08 yeah it is common but i don't need to do it so i don't know the steps Dec 05 18:58:22 And with this- I can just connect my BBB with the laptop using ethernet cable and the ethtool will work Dec 05 18:58:53 you cannot install any software on the BBB until it has an internet connection Dec 05 18:59:02 Can you give me any link for bridge wifi to ethernet please Dec 05 18:59:14 Yes, I got it now that I need internet connection in my BBB Dec 05 18:59:44 no please take this information and try to solve the problem for a while Dec 05 18:59:50 if you cannot figure it out with this you should come back Dec 05 19:00:37 Alrighty. Thanks a million bud. Dec 05 19:00:55 I will search it. Thank you very much. :) Dec 05 19:14:13 Maman: it would make sense to ask your IT department to provide a physical network switch for you in the lab Dec 05 19:14:32 that would be more professional Dec 05 19:15:01 but you still need a way to figure out the IP address of the beaglebone once it is connected Dec 05 19:17:20 The wifi simply doesn't work, even after I enable and start it. It says its enabled but not interface shows up, nor the led turns on or anything else. Will try to flash another kernel and pray not to be a defect board. Dec 05 19:17:54 yeah it's strange Huyston, someone else might be aware of some problems like these Dec 05 19:17:57 where did you buy the board from? Dec 05 19:18:30 out of curiousity, which image are you using? Dec 05 19:19:20 I'm not sure, maybe its from digikey. I didn't buy it. Dec 05 19:19:37 :-/ Dec 05 19:19:51 not knowing who to return it to :'( Dec 05 19:20:28 A client bought it. The problem is the project deadline... Dec 05 19:20:53 the problem is always the project deadline Dec 05 19:21:08 better a good product released late than a bad product released early Dec 05 19:21:50 the image I used was bone-debian-10.3-iot-armhf-2020-04-06-4gb.img Dec 05 19:22:51 okay, good luck Dec 05 19:23:36 thanks! Dec 05 19:30:58 Huyston: does "ip link" show an eth0 interface? Dec 05 19:31:10 there has been a batch of BBBW devices programmed with wrong board identification in EEPROM Dec 05 19:32:42 yeah, bingo, I see eth0 in the ip addr output you pasted into chat (which, as ayjay_t said, please don't ever do that again, use a paste service like pastebin.com ) Dec 05 19:32:51 Huyston: this is fixable Dec 05 19:33:37 it requires a bit of care, but fixing the board id is something you can do yourself Dec 05 19:37:23 (it requires using a wire to override the EEPROM's write protection, and then overwriting the first 16 bytes of EEPROM with the correct board identification. after verifying very carefully that EEPROM now has correct contents), you can then reboot and eth0 should be gone and wlan0 be in its place Dec 05 19:37:28 ) Dec 05 19:42:36 zmatt-test: test Dec 05 19:43:16 okay so the webchat sorta but not really draws attention if your name is mentioned Dec 05 19:43:33 I was curious about that Dec 05 19:44:19 zmatt-test: test Dec 05 19:46:37 using the freenode webchat directly (instead of in an iframe) is much, much better... the tab gets a special icon, the tab title aggressively tries to draw your attention (with an "*" in front of the page title blinking at 1 Hz), and it offers to enable desktop notifications when you open the chat Dec 05 19:49:09 jkridner[m]: may I suggest replacing the (annoyingly small) iframe embedding the webchat in https://beagleboard.org/chat by a big button directly linking to it? (instead of a tiny link below the embedded webchat) .. I'm pretty sure that will result in a much better experience both for users of the webchat and anyone trying to interact with them Dec 05 20:20:50 zmatt, yes it does Dec 05 20:21:51 try: head -c 16 /sys/bus/i2c/devices/0-0050/eeprom | hexdump -C Dec 05 20:22:08 the BBBW is A335BNLTBWA5, the BBB is A335BNLT00C0 Dec 05 20:22:44 im prowering the board, one sec Dec 05 20:23:28 the command to fix it would be: echo -ne '\xaa\x55\x33\xeeA335BNLTBWA5' >/sys/bus/i2c/devices/0-0050/eeprom Dec 05 20:23:37 but that needs to be done while the EEPROM's write protection is overridden Dec 05 20:25:45 output of that command is 
.U3.A335BNLTEW00 Dec 05 20:27:39 which is not a valid identification of any board: https://github.com/beagleboard/image-builder#eeprom-database Dec 05 20:28:24 though I think it might also be different from the misprogrammed BBBWs I've previously seen Dec 05 20:29:00 can you use "head -c 32" instead of "head -c 16" and show the second line? (I'm curious what its production date is) Dec 05 20:29:32 0858 Dec 05 20:29:48 if that means something Dec 05 20:29:49 ? Dec 05 20:30:20 I used head -c 32 Dec 05 20:30:34 head -c 32 /sys/bus/i2c/devices/0-0050/eeprom | hexdump -C Dec 05 20:30:53 the first line is .U3.A335BNLTEW00 Dec 05 20:30:54 so the second line would normally be something like Dec 05 20:30:55 00000010 31 36 35 30 42 42 57 47 34 36 33 39 ff ff ff ff |1650BBWG4639....| Dec 05 20:31:04 and the second is 0858............ Dec 05 20:31:13 oooookay then Dec 05 20:31:22 30 38 35 38 00 00 00 00 00 00 00 00 ff ff ff ff |0858............| Dec 05 20:32:06 no serial number, produced in week 58 of 2008 (8 years before the BBBW was designed) ... right, sure Dec 05 20:32:32 lol Dec 05 20:32:54 week 58 is always a busy week of the year for manufacturing Dec 05 20:34:21 so, you should _definitely_ contact the supplier to let them know they shipped you a board whose EEPROM has been programmed with complete and utter trash Dec 05 20:34:37 hahah, after hours work Dec 05 20:35:04 will do that Dec 05 20:35:29 whether you want to make them swap it out on principle or just fix the board identification in EEPROM yourself is up to you Dec 05 20:36:11 to disable EEPROM write protection you need to connect TP1 (highlighted in red) to ground (some options highlighted in green): https://liktaanjeneus.nl/bbbw-tp1.jpg Dec 05 20:36:38 then use the command I gave earlier to overwrite its first 16 bytes Dec 05 20:36:54 dump eeprom again to double-check its board identification is now actually correct Dec 05 20:38:35 if you screw up in any way you can try again, though if you corrupt any of the first 12 bytes you'll want to make sure they're fixed before you reboot or power off the board, otherwise you'll have a bigger problem :P Dec 05 20:42:13 if it messes the eeprom or doesn't work after that, the supplier will accept the board for a replacement? Dec 05 20:42:30 you'd have to ask the supplier, not me Dec 05 20:43:09 I mean, not the supplier, but beagleboard. Because its a fabrication error, right? Dec 05 20:43:45 Will think about it. I took note of the instructions. Dec 05 20:44:06 getting them back to the manufacturer (which isn't beagleboard.org either) is up to the distributor Dec 05 20:44:29 you bought the board from the distributor, they're the ones who need to fix this Dec 05 20:45:41 and it would be in their best interest to allow you to try fixing the EEPROM yourself (without refusing the RMA if it doesn't) since it will probably save them an RMA, but that's still up to them Dec 05 20:47:21 zmatt should we notify someone somewhere of the /etc/network/interfaces issue Dec 05 20:47:23 yea. Thanks very much for you very useful and detailed explanation Dec 05 20:49:14 ayjay_t: https://github.com/beagleboard/Latest-Images/issues would be the place to do that Dec 05 20:49:42 ill submit something Dec 05 21:00:34 I kinda half-butted this report but it should be good enough and I'll boot the device back up later Dec 05 21:00:38 https://github.com/beagleboard/Latest-Images/issues/78 Dec 06 00:12:04 I am trying to see if a friend can ssh to my board. I gave him the ip4 and ip6 address, but when they open the terminal it doesn't connect or nothing pops up. I'm not sure what I'm doing wrong Dec 06 00:13:01 eh, what's the networking situation? bbb and friend are both on your lan? Dec 06 00:14:59 My board is connected to the internet via ethernet. I made a friend download putty and wanted to see if he could access it via ssh Dec 06 00:15:12 We're not on the same lan Dec 06 00:15:18 This is just a personal thing, I wanted to test Dec 06 00:16:52 for ipv4 that requires setting up port forwarding in your router. ipv4 addresses in the ranges 10.0.0.0 - 10.255.255.255, 172.16.0.0 - 172.31.255.255, and 192.168.0.0 - 192.168.255.255 are private network ranges and not internet-accessible Dec 06 00:18:13 for ipv6 that requires that you actually have ipv6 internet access (BBB has a proper IPv6 address in addition to the link-local address that starts with fe80::) and usually requires opening up internet access to your beaglebone in your router Dec 06 00:18:54 access from the internet I mean Dec 06 00:19:23 Ah okay hmm, I tried giving him both the ipv4 and ipv6. Neither worked, but now it makes sense that I would need to port foward the ipv4 address. How would I open internet access through the ipv6? Dec 06 00:19:26 it would be a huge security problem if anyone on the internet could just (attempt to) connect computers and devices on your local network Dec 06 00:19:44 *connect to Dec 06 00:21:09 in both cases you need to configure it in your router... or, if this feature is enabled in your router, the beaglebone may itself be able to ask for a port mapping in the router, and there's probably some util for that (I'd look to look it up) Dec 06 00:21:34 in case of IPv4 you'd set up a mapping from some external port (_very VERY strongly recommended to not be port 22) to port 22 of your beaglebone Dec 06 00:22:47 same for IPv6 except it normally doesn't use port mapping, you'd just open up port 22 (which is not a huge security issue with IPv6 because the range of IPv6 addresses is so huge you can't really practically guess or scan for them) Dec 06 00:25:10 I found a utility, lemme see if it works Dec 06 00:26:15 Hmm okay, I'll try it out. It makes sense Dec 06 00:26:25 So I wouldn't want to open up port 22, got it Dec 06 00:27:22 yeah, using a random external port in case of IPv4, to make sure attackers won't easily find it Dec 06 00:30:18 Hmm makes sense Dec 06 00:30:25 I'll look up a guide to port foward then Dec 06 00:30:38 I found a utility, I'm checking if it works Dec 06 00:31:56 Thank you zmatt Dec 06 00:43:30 sudo apt install miniupnpc Dec 06 00:43:35 upnpc -r 22 $((10000+RANDOM)) tcp Dec 06 00:44:26 if your router supports IGD:2 and has it enabled then that will create the port mapping and display the result, e.g. "external *****:18801 TCP is redirected to internal 192.168.178.38:22 (duration=0)" (where ***** is your external IP address) Dec 06 00:47:10 to remove it use "upnpc -N 18801 18801 tcp" (the port number is repeated twice because it's start and end of a range) Dec 06 00:47:25 this utility is spammy and could definitely be way, way more user friendly Dec 06 00:53:51 Hmm okay, so if I input that it should work? That's for ipv4 right? Dec 06 00:55:13 yes that's for ipv4 Dec 06 00:56:41 Okay I'll try it out and read about the util in a bit so I can really understand this stuff. Thank you very much zmatt Dec 06 00:59:58 It says it failed, it gave me error code 402, is it okay for me to post the log? It contains IPs, so I would probably not want to Dec 06 01:01:24 just replace your external IP by **** or whatever Dec 06 01:01:44 or make your pastebin "unlisted" and send me the link by private message Dec 06 01:07:50 I sent it to you Dec 06 01:08:29 okay that upnp device clearly isn't your router Dec 06 01:08:35 so upnp is probably disabled in your router Dec 06 01:09:06 so you'll need to dig into your router settings to manually add a port mapping Dec 06 01:09:50 Hmm okay, I'll try that then Dec 06 01:10:24 (or enable upnp, but beware that some time ago a whole bunch of routers were discovered to have security holes in their UPnP implementation, so either verify your router isn't on that list or verify it's running uptodate firmware) Dec 06 01:17:26 ! Dec 06 01:18:02 I remember that idea. Router security...big deal. It is a big deal. Dec 06 01:23:09 I portfowarded it Dec 06 01:23:15 However, it says TCP/UDP: 22 Dec 06 01:23:22 And It wouldn't give me a choice for another port Dec 06 01:23:38 that sucks, hope you configured a decent password on your bbb Dec 06 01:26:58 Hmm I'll see if I can do something else to let me pick a different port Dec 06 01:27:12 when I do ifconfig. It's inet right? That's the ipv4 Dec 06 01:27:45 of what? Dec 06 01:29:10 "inet" in the output of "ip addr" (and presumably the obsolete "ifconfig") means IPv4 yes Dec 06 01:31:26 Ah okay I didn't know ip addr existed Dec 06 01:31:36 Do I have to restart my board? Dec 06 01:33:31 no Dec 06 01:34:01 that doesn't even make any sense... you didn't change anything on the bbb Dec 06 01:35:14 eh, just to be sure: obviously your friend needs to connect to your external ip Dec 06 01:36:41 (and trying this yourself, while on your local network, may or may not work depending on the router and whether it supports "hairpin NAT") Dec 06 01:41:21 Hmm okay that's good to know Dec 06 01:41:41 My external ip meaning the one on my board when I type ip addr Dec 06 01:41:50 ?* Dec 06 01:41:57 no Dec 06 01:42:45 The one on my router then Dec 06 01:43:24 the beaglebone doesn't know anything about the address translation or port mapping the router is doing... well, unless it can ask the router via upnp but it can't in your case Dec 06 01:44:50 So then which Ip would I give my friend? Dec 06 01:45:23 (the router gets exactly one IPv4 address from your ISP, so it needs to do magic to make all devices on your network seem like 1 device on the internet, which is also why incoming connections can't work unless the router it told for which device a connection to a specific port is intended) Dec 06 01:46:10 that one IP address you got from your ISP, which the router knows. there are also websites you can use to find your IP address (since it's the IP address you have from the perspective of anyone on the internet) Dec 06 01:46:23 just google "my ip address" or something Dec 06 01:46:41 Okay trying it now Dec 06 01:54:03 It worked thank you very much zmatt Dec 06 01:54:21 I'll still have to figure out how to change that it's on port 22, but I understand this better now. Thanks Dec 06 01:56:35 if your router doesn't give separate options for source and destination port then you can't Dec 06 02:14:38 (again, highly recommended to configure a decent password instead of the default "temppwd") Dec 06 02:15:07 (like, you should have done that before exposing it to the internet on port 22 ) Dec 06 02:19:00 Aceplosion: actually, a relatively easy workaround is making sshd on the beaglebone list on a secondary port (in addition to 22), and then add a port mapping in the router for that secondary port instead of for port 22 Dec 06 02:19:30 That sounds like a good idea, how would I do that? And yeah I made a different password and took down the port foward after confirming it works Dec 06 02:21:15 in /etc/ssh/sshd_config uncomment the "Port 22" directive and add a "Port 12345" (for example) line below it Dec 06 02:21:26 then "sudo systemctl reload ssh" Dec 06 02:25:09 Okay I added the secondary port and ran the reload Dec 06 02:25:24 just have it start a second sshd with a different config Dec 06 02:25:33 ds2: why on earth would you do that Dec 06 02:25:45 it can listen on two ports just fine Dec 06 02:25:57 zmatt: that's if you want to use 1 common config Dec 06 02:26:02 Aceplosion: you can specify the port number when connecting using the -p option Dec 06 02:26:28 if it is exposed to the internet, passwords are undesireable Dec 06 02:26:48 outside instance is keys only, inside is whatever you feel like Dec 06 02:27:21 depending on your confidence level, outside instance may disable port redirection Dec 06 02:27:56 that's of no security benefit if it allows login Dec 06 02:28:11 and this still doesn't require a separate sshd instance, you can just do something like: https://pastebin.com/WhzhZBBt Dec 06 02:29:20 it comes down to your level of comfort Dec 06 02:29:46 having memory isolation can help Dec 06 02:30:03 anyway, afk Dec 06 02:30:14 *nod* that's a differnet debate Dec 06 02:30:23 I don't think I see the secondary port under my list of options of devices to forward Dec 06 02:48:44 I got it to work on a different port **** ENDING LOGGING AT Sun Dec 06 02:59:56 2020