Ah. Shoulda figured out that by myself.Normally each interface is in a different network. Configure eth0 to be 192.168.2.1
I tried that. That is, I specified eth0 as 192.168.2.14, and the gateway as 192.168.1.1, which would be on the same network as the other interface, wlan0. Unfortunately the wizard complained that "Your gateway 192.168.1.1 is not on this network." Since as you say, each computer needs only one gateway, it appears the wizard is in error assuming the gateway must be on any particular network. In fact it looks like the wizard is assuming a gateway is on a per-network (per-interface) basis, which does in fact jive with the fact that gateways are specified on interface configurations, not computer-wide configurations. Your claim that gateways are a per-computer thing makes more sense to me, but something is off here...
BTW, a per-computer gateway would seem to imply that the wizard must include checks that the gateway on all interfaces is the same.
Maybe the network wizard is not really up to handling complex requirements. If I'm building a server, I should simply not use it.
Yeah, I'm trying to make something like a proxy server including a NAT firewall and other such frills. I am a total newbie on networks so I don't even know if these things are possible. So your questions are mostly answered by "huh?" Guess I need to do a lot more reading. As to DHCP server, I tend to like things simple, don't like extraneous services and daemons running. Since these are small, static networks, it looks like DHCP should not be needed. I also don't see why it should have any connection at all to DNS, but then again, I don't know anything.It's not clear what you want to achieve with eth0. If you want to attach other machines to it and have traffic pass through your Puppy machine to the internet, then you are trying to make your Puppy machine a router and there are quite a few more considerations. How do you intend to pass on the DNS addresses and you eth0 address as their gateway, (will you run a dhcp server on your Puppy machine). How is the upstream router 192.168.1.1 going to know about the network that is beyond your Puppy machine, (will you run a NAT firewall on your Puppy machine).
I'm thinking of making my server an OpenBSD rather than a Puppy one, since there seems to be a lot of know-how about this sort of application on the internet.