INTL 3:770/1 3:770/3   
   REPLYADDR theom+news@chiark.greenend.org.uk   
   REPLYTO 3:770/3.0 UUCP   
   MSGID:  17a217d2   
   REPLY:  ce35af16   
   PID: SoupGate-Win32 v1.05   
   mm0fmf  wrote:   
   > On 01/02/2024 18:55, The Natural Philosopher wrote:   
   > >   
   > > Ok, I've looked up loads of stuff on the interwebbery, and all the   
   > > solutions to make a pi into a wifi *bridge* are actually making it into   
   > > a router, with its own DHCP etc   
   > >   
   > > Not the same as the average wifi access works in a WAP at all.   
   > >   
   > > Can this actually be done at all?   
   > >   
   > > I basically want a pi on the network to be connected to by wifi clients,   
   > > and forward the packets over its ethernet to the main LAN. And let the   
   > > main DHCP server do the business.   
   > >   
   > >   
   > >   
   > You set it up as an AP and enable ip4 forwarding so so stuff received on   
   > the wifi goes to the ethernet and back.  I've got this on an old Pi but   
   > it's not handy or I'd look at the config.   
      
   That's routing not bridging.  With bridging you create a bridge device and   
   attach two network devices to it - packets received on one device are sent   
   to another.  It's as if the wifi and LAN are one network.  Most consumer   
   routers bridge their wifi and LAN ports.   
      
   If you want to go ethernet->wifi->ethernet there are some issues with the Pi   
   0W/3 hardware not having the right features in the wifi chip:   
   https://raspberrypi.stackexchange.com/questions/51057/raspberry-   
   i-3-model-b-wireless-bridge-to-ethernet   
   Not sure if the same applies to the 4 and 5 or if they fixed it in the   
   hardware.   
      
   (I previously had a better source than that, which I can't find now)   
      
   If bridging doesn't work then you can still route, ie put wifi and LAN on   
   different subnets and have forwarding rules to pass packets between.  Which   
   is probably why most of the guides out there are discussing that not   
   bridging.   
      
   You can also use proxy ARP to make IPv4 routing look like bridging:   
   https://raspberrypi.stackexchange.com/questions/88954/workaround   
   for-a-wifi-bridge-on-a-raspberry-pi-with-proxy-arp   
   and for IPv6 there's Proxy NDP.   
      
   I've done Proxy ARP on other machines long ago but not a Pi.   
      
   Theo   
      
   --- SoupGate-Win32 v1.05   
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)   
   SEEN-BY: 10/0 1 15/0 90/1 103/705 105/81 106/201 128/260 129/305 135/225   
   SEEN-BY: 153/757 7715 218/0 1 601 700 840 870 930 220/70 221/1 6 226/17   
   SEEN-BY: 226/30 100 227/114 229/110 112 113 200 206 307 317 400 426   
   SEEN-BY: 229/428 470 550 616 664 700 240/1120 266/512 267/800 282/1038   
   SEEN-BY: 291/111 292/854 301/1 113 812 310/31 320/219 322/757 335/364   
   SEEN-BY: 341/66 342/200 396/45 460/58 633/280 712/848 770/1 3 100   
   SEEN-BY: 770/330 340 772/210 220 230 5020/400 1042 5058/104 5075/35   
   PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426