Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.sys.raspberry-pi    |    Raspberry Pi computers & related hardwar    |    26,127 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 26,061 of 26,127    |
|    The Natural Philosopher to All    |
|    Re: More on the search for the mafic spe    |
|    16 Jan 26 14:44:22    |
      XPost: comp.os.linux.misc       From: tnp@invalid.invalid              On 16/01/2026 12:11, mm0fmf wrote:       > On 14/01/2026 21:00, The Natural Philosopher wrote:       >>       >> 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.       >       > Have you read this? (Probably you have)       >       > https://wiki.debian.org/BridgeNetworkConnections       >       It applies to a debian configuration that is not what I have. I have no       brctl for example.       And it says *how* to set up a bridge,m but that I have already done.              It has no info on using network manager for example,              I am chasing a performance issue now - and a strange one at that.              Unless you can conclusively state that the bridge set up by brctl is       markedly different from the one set up by Network manager, that 'how to'       is not relevant, sadly.              The 'magic spell' I ended up using is pretty much this one              https://gist.github.com/plembo/f7abd2d9b6f76e7afdece02dae7e5097              What is happening is that the bridge seems perfectly stable from       Ethernet to the bridge host machine, but is very variable on the Wi-Fi       interface, and that gets worse if       - the incoming packet is via the inbound router from the internet...       - inbound traffic to the host is heavy.              I get between 48% and 988% packet loss to external machines on the       Internet. Mostly OK access to the rest of the LAN using the Wi-Fi interface.              Somewhere the bridge is dropping stuff and I don't know why. After       struggling with journalctl there is nothing relevant in the logs that I       found.              neither CPU nor ram on the Pi are especially overloaded.              In short according to the logs etc. everything is working as it should,       but packets are being mangled somewhere.              I included my network manager files in case someone with a pi 4 or 5       might care to try and duplicate the setup and see if its shit for them       as well...                     --       I was brought up to believe that you should never give offence if you       can avoid it; the new culture tells us you should always take offence if       you can. There are now experts in the art of taking offence, indeed       whole academic subjects, such as 'gender studies', devoted to it.              Sir Roger Scruton              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca