<snip> > In addition to the 192.168 machines on the LAN, I also have a machine > video.bsd.uchicago.edu with a valid IP 128.135.97.144 behind the > firewall (ie, it connects to eth1). This is my bastion host, and will > run the http server, mail server and that kind of stuff. From the > bastion host I can talk to my router and vice versa. > > My question is: how do I get the outside world to see this machine.
Hmmm, and now we move into routing... :) I think the better way to go here, it to just keep video.bsd.uchicago.edu on your private network, 192.168.1.x/24 and use NAT on the firewall to map only the ports you need public. This will, of course, mean that your firewall will have to be "routing" that 128.135.97.x/netmask network. > My fundamental question is: how does the outside world know that it > has to come through my router to get to video.bsd.uchicago.edu? Is > video broadcasting and my router forwards that broadcast? Okay, this is handled by the router that is delegating that 128.135.97.0/? network to you. But, we are probably going to need a little bit more information here. What do you have that is under your control? Did the administrator just hand you the whole 128.135.97.0/24 as a class C, tell you that it was called bsd.uchicago.edu, point to a drop in the wall and leave you alone? Cheers, sach -- /* Sach Jobb [EMAIL PROTECTED] %s/windows/linux/g */ "As far as i'm concerned the two biggest hassles in the world revolve around DNS and girlfriends." -- (name undisclosed to protect the innocent)
