XPost: comp.os.linux.misc   
   From: tnp@invalid.invalid   
      
   If you recall I was after a configuration that would allow a Pi 4 or 5   
   to act in addition to its generic operation as a server on the network,   
   to also act as a wifi access point.   
      
   I have *sort of* succeeded.   
      
   The general process is to down the wifi and Ethernet interfaces, create   
   a bridge interface as master and slave the two other interfaces (Thernet   
   and wifi) to it   
      
   The bridge interface has all the IP stuff attached to it.   
      
   The Wifi interface has instructions to be an access point and have an   
   SSID, securitry and so on.   
      
      
   Ultimately I discovered that all this does is create and edit files in   
      
   /etc/NetworkManager/system-connections and frankly this is probably the   
   easiest way to do it   
      
   Here are the three files I created via nmcli   
      
   # more br0.nmconnection   
   [connection]   
   id=br0   
   uuid=db3fc586-63b4-43f6-9cf3-efd207086553   
   type=bridge   
   interface-name=nm-bridge   
   timestamp=1768417618   
      
   [ethernet]   
      
   [bridge]   
   stp=false   
      
   [ipv4]   
   address1=192.168.0.101/24,192.168.0.254   
   dns=192.168.0.101;   
   method=manual   
      
   [ipv6]   
   addr-gen-mode=default   
   method=disabled   
      
   [proxy]   
      
      
   -----------------------------------   
      
   # more Garden.nmconnection   
   [connection]   
   id=Garden   
   uuid=f977bba8-bda3-404b-89c3-57c959c8b1fd   
   type=wifi   
   interface-name=wlan0   
   master=db3fc586-63b4-43f6-9cf3-efd207086553   
   slave-type=bridge   
   timestamp=1768410601   
      
   [wifi]   
   band=bg   
   channel=9   
   mode=ap   
   powersave=2   
   ssid=MyGarden   
      
   [wifi-security]   
   key-mgmt=wpa-psk   
   psk=rottenRatz   
      
   [bridge-port]   
   --------------------------------------------------------------------   
      
   # more Ethernet.nmconnection   
   [connection]   
   id=Ethernet   
   uuid=4a8b7eb6-678a-47e2-b5b2-416cc800438f   
   type=ethernet   
   interface-name=eth0   
   master=db3fc586-63b4-43f6-9cf3-efd207086553   
   slave-type=bridge   
   timestamp=1768409686   
      
   [ethernet]   
      
   [bridge-port]   
      
   ---------------------------------------------------------------------------   
   Now for the problems:   
      
   First of all I cant get the Pi4B to do more than 72Mbps. I *think* this   
   is a hardware limit   
      
   More importantly if  any connected wifi clients try to use the   
   *internet*, response is flaky as fuck. 50%+  packet loss   
      
   But wifi clients connected via the Pi WiFi  can access the *LAN*   
   smoothly. No packet loss.   
      
   Wifi clients attached via any other access point can access the internet   
   smoothly.   
      
   Just not *wifi clients attached via the pi*....   
      
   I am struggling to understand how a device can access the LAN perfectly   
   but not the Internet.   
      
   Any ideas?   
      
   --   
   Future generations will wonder in bemused amazement that the early   
   twenty-first century’s developed world went into hysterical panic over a   
   globally average temperature increase of a few tenths of a degree, and,   
   on the basis of gross exaggerations of highly uncertain computer   
   projections combined into implausible chains of inference, proceeded to   
   contemplate a rollback of the industrial age.   
      
   Richard Lindzen   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)