Timeline for Question on L3 'pseudo-bridge' implementation for Raspberry Pi 4B
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 6, 2020 at 8:39 | comment | added | Ingo | @user8585939 I think the AMS 7131-AC-T (don't know it) is working as real OSI layer 2 bridge. That is a complete different configuration than proxy arp and explains the differences. It seems I'm a bit confused with the word "device" you are using. So far I have meant that a device only have a wired port and is connected to the RasPi that has eth0 and wlan0. And yes, with the static configuration you have to reboot the RasPi to discover interface changes. That is what static mean and is by definition as explained in the prefix. | |
| Feb 6, 2020 at 5:20 | comment | added | Big Owls | The length of the Ethernet cable doesn't matter to me, perhaps I emphasized that poorly. This could happen on a 5 foot Ethernet cable. I more meant the behavior. | |
| Feb 6, 2020 at 5:14 | comment | added | Big Owls | When we couldn't get this working reliably on the Pi, we bought that AMS 7131-AC-T, and sure enough, their engineers say it does not offer WLAN/LAN redundancy to the side before the bridge. Wireless bridging works great until we attempt to plug an Ethernet cable directly from the primary hotspot LAN to the bridged network. I don't think that's unreasonable because after all, it doesn't know what interface to physially use at that point! However it never just "picks" one. At that point, when the Ethernet cable is plugged in, we experience complete failure. | |
| Feb 6, 2020 at 5:07 | comment | added | Big Owls | ... in order to tell it to start "listening" on the physical port instead of wirelessly over the USB/WIFI adapter. We must reboot the Pi to get it to ignore wireless. On a side note, when I buy a "industrial wireless bridge" such as an Antaira AMS 7131-AC-T, I can ping the (static ip) device without the primary hotspot being up and the WiFi on the bridge being completely disconnected. Perhaps this is due to some of the options we choose or how they are configured out of the box (I suspect this may be the difference between a "multi-client bridge" and a "fully transparent bridge." | |
| Feb 6, 2020 at 5:05 | comment | added | Big Owls | Ingo, thank you for taking the time to answer this question and set up a test. I am very appreciative of that level of assistance. Also, please bear with me on my follow-up to this, as network engineering is NOT my forte. Regarding the ethernet cable; what I meant to communicate was that we are physically patching the primary hotspot to the device, so merely just instead attempting to communicate via the physical ethernet port (eth0) instead of through our WiFi USB adapter. This will be a common practice when we can't get signal in the field. The device hates this, and has no redundancy... | |
| Feb 6, 2020 at 0:25 | history | answered | Ingo | CC BY-SA 4.0 |