------- Comment #3 from gordonr-bugzilla@gormand.com.au 2006-05-23 00:47 -------
(In reply to comment #2)
> I admit that I don't really get this local network stuff, BUT the fact remains
> that when I added a 3rd NIC (wireless adapter)
That was the missing part of the bug report
I read this as you adding a
wireless gateway on your LAN, not a third NIC (and I suspect Charlie did too).
> and added a new local network to
> serve the wireless clients, I couldn't get connected to SME server if I added
> 192.168.100.1 as router for the new local network 192.168.200.0
That would be correct. The correct router is 192.168.200.1 (assuming your third
NIC is 192.168.200.1). They are all local interfaces, but they will have separate
rules applied to them - in particular the anti-spoofing rules, which drop packets
coming in on the "wrong" interface.
> Moreover, changing manually the router in /home/e-smith/db/networks
Please don't - use the 'db' command to modify the databases - see the
Developer's Guide linked at
http://wiki.contribs.org/development/> from
> 192.168.100.1 to 192.168.200.1, I could connect with a client to the new
> created local network.
> Is my setup wrong or am I missing something here?
No, you are correct. The problem here is that we don't have any support for a
third NIC, and so you will have to manually modify the networks db. Since we
don't have the support for the third NIC under the covers, we don't support it
in the server manager.
This is really a New Feature Request, and so I am marking it as such. Note that
if third NIC support were to be added, it would almost certainly want its own
firewalling rules.
Adjusting summary
WAS: Unable to attribute right router IP for new local network
IS: Add support for three NIC configuration(BTW: I'm not sure that a wireless NIC is the way to go. The MAC filtering,
security profiles and similar of the wireless access points are probably not
worth reinventing.)