Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Raspberry Pi WiFi to ethernet bridge

willhaley.com

Post reply on HN
Print view View original

41–50 of 67 posts

Re: Raspberry Pi WiFi to ethernet bridge

#41

Post by icedchai »

rkeene2 wrote: post #39
icedchai wrote: post #36

Earlier quoted context omitted.

No tunnel is needed. Just use a bridge interface.

Since not all IEEE 802.1 Ethernet frames can be converted to IEEE 802.11 frames using the Linux bridging infrastructure isn't sufficient (even though it can do fancy things like bridge non-Ethernet and Ethernet interfaces; Like bridging PPP interfaces and IEEE 802.1 Interfaces). You genuinely need a tunnel if you want support all Ethernet functionality.

I'm highly skeptical that bridging is insufficient for most use cases. After all, most Linux-based access points are using standard bridging.

Re: Raspberry Pi WiFi to ethernet bridge

#42

Post by livueta »

godelski wrote: post #24
vorpalhex wrote: post #23

Earlier quoted context omitted.

Make sure nothing is changing your DNS. You may need to set your router to push the pihole as your DNS and tell any programs to use system DNS.

I've checked that my router continues to point to the pihole (no fallbacks, though I've tried with fallbacks and no difference). I also setup the pihole with cloudflare. I'm just always confused because it seems like some people have absolutely no problem and there's others in my camp and the former just stop after "just follow the directions." I even remember the LTT video mentioned this specific problem.

I went down a similar rabbit hole recently with unbound as a caching resolver, where it appeared to work on my real computers but didn't on phones. I took a pcap and found that my Android 10+ devices were refusing to use the good-old port 53 DNS my unbound jail was serving because it wasn't DoT. Once I set up unbound with real certs _and_ set it as each device's "Private DNS", it worked as expected.

Your issue might be different but I suggest taking a pcap to make sure your assumptions about what is answering a given DNS query are true.

Re: Raspberry Pi WiFi to ethernet bridge

#43

Post by OJFord »

puzzlingcaptcha wrote: post #11

Ah yes, network configuration by way of executing a random bash script from a blog. With tasty morsels like: ># I have to admit, I do not understand ARP and IP forwarding enough to explain exactly what is happening here.

Yeah, I don't like the style of this 'first, download this script; then, execute it'.. and it creates/overwrites files.

Why not tell me to create the necessary files, with some article content around what we're doing and why?

As an article this doesn't seem to offer anything more than a suggestively named GitHub repository with a small readme.

Re: Raspberry Pi WiFi to ethernet bridge

#44

Post by tomjakubowski »

geerlingguy wrote: post #14
puzzlingcaptcha wrote: post #11

Ah yes, network configuration by way of executing a random bash script from a blog. With tasty morsels like: ># I have to admit, I do not understand ARP and IP forwarding enough to explain exactly what is happening here.

I mean, the number of people on this site who could intelligently explain ARP and IP forwarding in detail is probably 10x higher than in the general population—and that percentage here is probably in the low single digits.

I think you mean the proportion is higher here, unless you mean that >90% of people who could intelligently explain ARP and IP forwarding are HN posters.

Re: Raspberry Pi WiFi to ethernet bridge

#46

Post by sosodev »

I was using my Raspberry Pi 4 as a WiFi bridge for a "temporary" networking solution after I moved house. I ended up running it that way for over a year and it worked pretty flawlessly. Only problem was that it didn't get anywhere near my full WiFi speed.

Re: Raspberry Pi WiFi to ethernet bridge

#48

Post by rkeene2 »

icedchai wrote: post #41
rkeene2 wrote: post #39

Earlier quoted context omitted.

Since not all IEEE 802.1 Ethernet frames can be converted to IEEE 802.11 frames using the Linux bridging infrastructure isn't sufficient (even though it can do fancy things like bridge non-Ethernet and Ethernet interfaces; Like bridging PPP interfaces and IEEE 802.1 Interfaces). You genuinely need a tunnel if you want support all Ethernet functionality.

I'm highly skeptical that bridging is insufficient for most use cases. After all, most Linux-based access points are using standard bridging.

Indeed that is true that for most cases WiFi can do the things users want. My note was that not everything you can do with Ethernet frames can be converted to WiFi frames.

One such example is Ethernet multicast.

Re: Raspberry Pi WiFi to ethernet bridge

#49

Post by vel0city »

vxNsr wrote: post #29

I’m trying to understand why this is better than a usb WiFi dongle, and coming up empty. Anyone have an idea?

Wireless bridges can be useful when you're trying to connect several devices through a single wireless link. Think about potentially having a whole room of devices all with a perfectly placed antenna instead of half a dozen antennas placed in compromised locations.
Post reply on HN