**** BEGIN LOGGING AT Fri Dec 22 03:00:01 2017 Dec 22 07:57:44 Hi. I got a problem with eth0 on BBB. Can somebody help with fixing it or understanding it deeper? Dec 22 09:00:49 help Dec 22 09:02:01 I wonder that the pinout of beaglebone black between the webpage and manual guide are different? Dec 22 09:04:19 Why the pinout name of beaglebone black between webpage and manual pdf are different? Dec 22 09:06:01 For example, pin number P8_21 shows on website is GPIO_62, but in the manual guide shows GPIO1_30 ??? Dec 22 09:07:49 hohum, really? Dec 22 09:08:19 ah that might just be *yet* another numbering scheme Dec 22 09:08:58 What do you mean by another numbering schematic? Dec 22 09:10:57 This link for manual guide "https://cdn.sparkfun.com/datasheets/Dev/Beagle/e14%20BBB_SRM_rev%200.9.pdf" Dec 22 09:11:13 and this link for website "http://beagleboard.org/support/bone101" Dec 22 09:11:39 Why GPIO pins name are different between 2 sources? Dec 22 09:13:53 There are 3 naming conventions at play, at least: P(8|9_XY; GPIOx_y; GPIO_zzz Dec 22 09:15:09 I suspect the first one to be physical naming on the layout, the second one naming based on the SoC internal banking and logic (see TRM?), while the last one is probably some Linux kernel thing. Just guessing. Dec 22 09:19:05 Thank you, it's very helpful. Dec 22 10:13:00 Paul_: 1*32+30 = 62 Dec 22 10:13:45 the first numbering scheme uses "pin 30 of GPIO controller 1", the second numbering scheme numbers all gpios sequentially Dec 22 10:17:01 and what tbr said is correct too, the sequential numbering is what the linux kernel uses Dec 22 10:17:41 I got it, thank you Dec 22 10:18:55 (though actually it doesn't guarantee stable numbering at all, technically you're supposed to look up the base gpio number of a gpio controller via udev or sysfs, not assume it's 32 * gpio controller number) Dec 22 10:21:49 If I want to use the name in my schematic, which sources should I reference? Dec 22 10:22:08 GPIO1_30 Dec 22 10:22:16 OK Dec 22 14:11:17 Hi guys, just received my new awesome PocketBeagle. Dec 22 14:12:07 I´ve been trying to share my Wifi connection from my laptop (running linux) via USB to the little PocketBeagle. Dec 22 14:12:08 I thought you were just happy to see me! Dec 22 14:12:26 Oh, bridging interfaces is never fun. Dec 22 14:13:03 Haha! Gaaaargh, I've been finding that out the last couple hours Dec 22 14:13:29 it's not that hard Dec 22 14:13:44 one possible complication is that your DHCP server might not want to hand out a second lease to your laptop Dec 22 14:13:55 my home network is happy with that, my work network not so much Dec 22 14:14:08 if you're actually bridging, the dhcp server doesn't see it as a second request from your laptop Dec 22 14:14:23 I think work only allows a single IP per port or something weird, 802.1x makes things tricky Dec 22 14:14:35 Hmmm... I've googled around for solutions (http://robotic-controls.com/learn/beaglebone/beaglebone-black-ubuntu mainly) Dec 22 14:14:58 myself: that's possible, but not really related to dhcp Dec 22 14:15:16 pinging the target from the laptop and wise-versa works good but 8.8.8.8 not so much... Dec 22 14:15:33 ooh, so you have an IP, just not routing? Dec 22 14:16:34 yup, I'm able to ssh into the Pocket and ping the host, no troubles Dec 22 14:16:37 did you do the "echo 1 > /proc/sys/net/ipv4/ip_forward" on the laptop? Dec 22 14:16:41 yup Dec 22 14:16:49 over my head, then :) Dec 22 14:16:55 horigome: not really much into about networking on that page though... also, it's really old (2013) and I see some obviously bad suggestions there Dec 22 14:17:11 ip_forward isn't relevant for bridging afaik? Dec 22 14:18:54 ah you're probably setting up NAT routing rather than bridging Dec 22 14:19:37 I am a total noob when it comes to networking. What I am trying to do is to somehow "share" the wireless network connection with the Beagle. Dec 22 14:20:38 This pdf gives a very similar step-by-step procedure (https://www.cs.sfu.ca/CourseCentral/433/bfraser/other/Networking.pdf) Dec 22 14:23:03 I would think that a prof from SImon Fraser Univeristy would provide reliable material to his students (and other googlers). Dec 22 14:23:27 lemme do a quick test Dec 22 14:33:33 https://pastebin.com/raw/0pKZ4PBZ Dec 22 14:43:52 ok, I guess you didn't care Dec 22 14:48:35 ouch, my connection went down. Thank you for the pastbin link, going to reboot and check it out Dec 22 14:48:39 ok :) Dec 22 14:49:11 I'm assuming there that both sides already have an ip address (like they would in the default config) Dec 22 14:49:21 hence I Dec 22 14:49:50 hence I'm just setting up NAT on the host and add a route on the beaglebone Dec 22 14:49:58 that seems to suffice for me Dec 22 14:50:24 to be able to resolve names the beaglebone will of course also need a suitable /etc/resolv.conf Dec 22 14:52:23 the host setup should be one-time (at least until you reboot), the route on the pocketbeagle needs to be done every time (fixing it to be persistent is possible of course, but more effort) Dec 22 14:56:40 Alright, would "nameserver 8.8.8.8" be enough for a MVP /etc/resolv.conf? Dec 22 14:58:08 sure Dec 22 15:05:22 Hmm.. still stalls on ping -n 8.8.8.8 Dec 22 15:05:39 try picking your local router instead Dec 22 15:05:42 *pinging Dec 22 15:06:32 I got the impression I'm not always getting a response from 8.8.8.8 either Dec 22 15:06:48 I'm not sure it's guaranteed that it'll respond to pings :P Dec 22 15:07:55 haha weird, theres no response from my local router Dec 22 15:08:18 maybe your laptop has a firewall? check iptables -L Dec 22 15:08:47 also, can you show the output of ip -4 addr on both laptop and beaglebone, and output of ip route on your beaglebone? Dec 22 15:08:51 *pocketbeagle Dec 22 15:11:28 https://pastebin.com/3Zu3VgdX Dec 22 15:12:39 ok, you clearly do have non-trivial firewall config Dec 22 15:14:41 can you show iptables -L -v and iptables -t nat -L -v Dec 22 15:15:59 https://pastebin.com/GLBSjcar - voila Dec 22 15:18:00 so, evidently you have some funky config related to docker Dec 22 15:19:10 a lame but simple workaround would probably be: iptables -P FORWARD ACCEPT Dec 22 15:19:27 to change the policy (default rule) of the FORWARD chain from DROP to ACCEPT Dec 22 15:21:55 uhm, so that would mean that instead of dropping connections that are being forwarded they are instead routed onwards? Dec 22 15:22:14 this did the job Dec 22 15:23:03 it means that when deciding what to do with packets that need forwarding (i.e. are not locally delivered nor locally originated), when none of the rules match, the packet will be accepted (i.e. forwarded) instead of being dropped Dec 22 15:25:05 all right, got it. So my laptop could now become a part of a nice bot network if I'm not careful? Dec 22 15:25:18 no Dec 22 15:26:04 Hi, Little off-topic : how can I send a single line http command (rpinotifier) via cli ?? Dec 22 15:26:17 wget doesn't work Dec 22 15:26:47 good to know, thank you very much for you kind help. Happy holidays! Dec 22 15:27:20 horigome: this only concerns whether your laptop will forward packets when they are being delivered to your laptop (due to the routing table of a host on your local network) and your laptop determines the correct destination is elsewhere Dec 22 15:27:33 fred_tv: wget. Dec 22 15:28:13 horigome: if you google you can find lots of images that show the flow of packets through the linux networking stack, and the various chains where iptables can influence things Dec 22 15:28:36 both simplified diagrams like https://danielmiessler.com/images/DM_NF.PNG and highly detailed diagrams like http://inai.de/images/nf-packet-flow.png Dec 22 15:29:07 wget doesn't work Dec 22 15:29:27 Interesting Dec 22 15:30:24 fred_tv: "I'm trying to do something. It doesn't work. What do I do?" ... wget is the obvious way to do a http request from the commandline, so if it "doesn't work" you're going to have to be a lot more specific Dec 22 15:33:26 Sorry, the goal is to send a blind http://blablabla/blabla string (do yu perhaps know rpinotifier?) , from a pc browser it works , with wget it tries to save back something with no results Dec 22 15:33:59 wget has lots of options, including for output control Dec 22 15:34:24 horigome: and the hot new thing to simplify the whole thing is 'nftables' Dec 22 15:34:51 which is intended to replace iptables, ip6tables, arptables, ebtables Dec 22 16:05:09 I'll take a look.... Dec 23 01:25:08 I'm looking for bb with ethernet and sd card on one side Dec 23 01:25:19 give me an advice please Dec 23 01:40:11 what? **** ENDING LOGGING AT Sat Dec 23 03:00:02 2017