Stardate 20011201.2057 (Crew, this is the Captain): It looks like I can do what I need to but I am going to have to stay with the primary interface connected to the universe, because Apache is wired to only talk on that interface. So right now my server thinks you are all on my LAN (on the primary interface), and my laptop is the Internet (on the secondary interface). That's because this was really designed to be a server for a small company, and its web capability was intended for internal use. So DHCP and Apache are on the same interface and I don't want to have to dive into Linux itself to see if I can change that.
However, I have Spica connected to the secondary interface and I've hardwired a 192.168 IP on it, and it can get out to the world. Regulus also supports NAT and it's turned on right now, and oddly enough that's working the way I've got it wired. Just to prove it, I connected the other (old) laptop up and had them both working at the same time.
Hard wiring the IPs is actually more attractive than DHCP, because it means I can give the machines their names and set up hard routing entries for them for interconnection. So the only thing remaining to work out is if the wireless hub will have any trouble with this -- mostly because of the question of whether it's possible to nest NATting. After all, the wireless hub itself will try to be a NAT to the computers talking to it over the air. So I'm going to hit the manual for it. (I presume it will work.) In the mean time, I appreciate the help and advice people have been giving me. (discuss)
