Yeah, i agree with Eric completely. I think the best route is to install 'plug' (or a suitable alternative) on the firewall box (assuming is opensource friendly) and use NAT (Network Address Translation) to map the appropriate ports on your firewall to the private address of video.
You may have to either alias 128.135.97.144 on eth0 of your firewall box, or get the DNS administrator to change the address of video.bsd.uchicago.edu from 128.135.97.144 to that of your firewall's public address in the appropriate DNS tables. Cheers, sach > > So in the current config, the router interacts with the internet on > > eth0 and the LAN on eth1, with the IP addresses of those cards given > > in the diagram. > > > > I want to be able to access 128.135.97.144 from the internet. > > > This isn't going to work like you have it here. The router will be > confused thinking that 128.135.x.x is one both eth0 and eht1. This is a > no-no. You would have to set the router up as a bridge and doing that > would break all the 192.168 stuff. > > What you can do is give the 128.135.97.144 machine a 192.168.x.x address > and have the router statically map 128.135.97.144 to 192.168.x.x. Sorta > like an inbound NAT kinda thing. > > How you would do this would depend on your hardware. > > -e > > -- /* 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)
