On Aug 10, 2001 at 05:56, S. Krishnan wrote:
ISP ________ ________ side | | | | --------|WinBox |-----|LinuxBox|----- To private |________| |________| network
Enable IP fwdg on Win
No. And there's a lot of confusion about the network topology I have here, which I should have specified clearly in my original post:
WinboxNIC | DSL -- USBWinboxNIC -- Hub -- NICLinbox | NICWinbox
If he does not enable IP forwarding on the Windows machine, how is he going to connect the Linux box to the outside world so that outside people have access
Point.
to it? Remember, he wanted people to have web and POP3 access, so that obviously he needs the Linux
Correct.
suggestion, since you suggest two NIC's, one for the WAN and one for the internal LAN, and not to enable IP forwarding on Linux. You do not seem to have read my
I don't want IP forwarding on Linux. If that were the case, things would be very easy!
post correctly, since I had suggested that he enable IP forwarding on the gateway machine, which in fact is the Windows machine, and not on the Linux box.
Which I've already done. Now how to access the Linbox from outside?
Granted, I forgot to add that he needed an additional LAN card to provide routing services for a public IP address for the Linux box.
Hm hm hm?
using Windows forwarding services - but that will mean an additional network card on the Windows gateway.
The configuration shown above will do it, eh?
have no idea if it will support multipoint forwarding services, with one being NAT'ed and one with full access. Windows Proxy Server ought to work, however.
That's what I want, I think.
configure it that causes all the problems. Remember, you cannot access the outside world through a firewall unless it allows IP packets to be forwarded, whether it is on Windows or Linux or FreeBSD or whatever. That is what iptables, ipchains, ipfilter, ipfw, etc.
I get the general idea, but I need specifics. How do I address my Linux box from the outside now?
On Aug 10, 2001 at 20:21, premstud@vsnl.com wrote:
|--------| ______|__ |--------|ISP | 1 | | | --------|WinBox | |LinuxBox| |__ ___2_| |________| | |----- To private network
A static route is added from the NIC 1 to the linux box with
How to do that in Windows?
NIC 1 as the gateway for packets destined to the linux box.
And how to do that?
The lan connects to the windows gateway through the 2nd NIC, and is seprated from the external network.
In our case, there is one NIC for the internal network. All packets should go to it, and those meant for the Linbox will be picked up by it. How to translate external packets coming to 65.1.1.1 (e.g.) to 192.168.0.127 (e.g.)? And translate only those packets meant for the Winbox. NAT?
On Aug 10, 2001 at 02:32, S. Krishnan wrote:
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
::nodnodnod::
IP on this LAN. What you could do however is to add a second NIC to the Linux box, give it an external
Nonono.
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.
Yes, but looks like this is the only way to go. What security issues? (Besides the obvious ones of having a box on the net.)
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?
Existing legacy Windows network being invaded by the Linbox (say hello to gort, everyone).