On Thursday 17 April 2008 07:15:19 am Paul Mc Auley wrote:
> | There is a dhcpd server running on A,
> | serving the ethernet LAN (192.168.2.0).
> | There is also a firewall (shorewall) running on A,
> | allowing packets on the ethernet LAN through to the internet.
> | There is also a dhcpd server running on B,
> | serving the WiFi LAN (192.168.3.0).
>> Am I the only one who thinks the correct solution is to remove at least
> one interlocking dependency by shelling out a few quid on an access point
> and put it on a common subnet with both the wired and wireless ethernet?
I'm afraid I didn't tell the full story.
I do actually have exactly what you recommend -
the 192.168.2.0 LAN does in fact support WiFi as well as ethernet.
But NetworkManager on my laptop for some reason I haven't been able to fathom
sometimes does not see this AP (even when it is 5 cms away),
but does see the ancient PCI WiFi card inside an ancient computer.
So I was trying to use it, largely as an exercise,
and found it was more difficult than I expected.
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!