INTL 3:770/1 3:770/3   
   REPLYADDR tnp@invalid.invalid   
   REPLYTO 3:770/3.0 UUCP   
   MSGID:  54380e7b   
   REPLY:  ce35af16   
   PID: SoupGate-Win32 v1.05   
   On 01/02/2024 19:36, 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.   
   >   
   >   
   So it is possible?   
   I found something called bridge-utils that implies it can be done, but   
   the Pi is now bricked since I did an upgrade on it.   
      
   --   
   Microsoft : the best reason to go to Linux that ever existed.   
      
   --- 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