--- Satya satyap@satya.virtualave.net wrote:
Here's the situation:
Net DSL Windowsbox LAN(dhcp) Linuxbox
The LAN, naturally, has a 192.168.0.0 range of IPs (I think it's a class C). The DSL modem is connected to the Winbox on USB and the LAN is a 5-port hub supporting a windows network, with my Linux box (say hello to gort, folks) creeping in using dhcpd.
The Linux box, and any box on the LAN, can access everything. I think the Net cannot access anything but the Windows box on the DSL modem (see http://gort.cjb.net/. That's the Winbox.).
Now I need POP3 (and HTTP et al, if possible) access to the Linux box from the outside world. IP forwarding is enabled on the Winbox.
What do I do now?
PS: Can I get a static IP on the internal network with minimal changes to the other boxen?
First, since you're using a 192.168.x.x address, you cannot afford to connect this LAN to the outside world, since this address range is a private RFC 1918 assigned one. The Linux box is a part of this subnet, and so there would be no point in giving it a static IP on this LAN. What you could do however is to add a second NIC to the Linux box, give it an external static IP address (a public address, of course), and connect it to the outside world, after properly firewalling it.
If your DSL connection works anything like a sync serial PPP link, what you need to do is to ask your ISP to give you two static IP's, with one being for your Windows box on which you enable IP forwarding. Your ISP would actually assign you a (say) 4 address IP subnet, of which of course one address would go for the network address, one for broadcast and you would then have two addresses left. One address of these would be used for your Windows box and one for the Linux box. This is of course just my guess, that you can set DSL up the same way that you do a serial link - but I think it can be done. You would have to enable IP forwarding on your Windows box for this to work.
Another option is to use Network Address Translation (NAT), to rewrite IP packets coming in to access a particular service on a a private machine within the network. I do not really recommend this though, as the security issues can cause you a good deal of grief.
BTW, I find it rather curious that you're running a Windows box as a public host, when you have a far better (Linux) alternative. Why, why, why?
HTH,
Krishnan
__________________________________________________ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/