Check your routing table with 'route -n'.
Do you have a route on the Linux router machine that looks like this? --
Destination Gateway GenmaskIface
200.189.192.144 0.0.0.0 255.255.255.248eth1
I guess the problem is on the ipmasq rules.
I'll put three
Hello debian users.
I am having the following ip masquerading issue:
1) I have four networks in my office
200.189.194.144 (netmask 255.255.255.248) - internet servers
10.0.0.x (netmask 255.255.255.0) - internal network
10.0.1.x (netmask 255.255.255.0) - other internal network
200.217.207.129
Guilherme Barile [EMAIL PROTECTED] writes:
Hello debian users.
I am having the following ip masquerading issue:
1) I have four networks in my office
200.189.194.144 (netmask 255.255.255.248) - internet servers
10.0.0.x (netmask 255.255.255.0) - internal network
10.0.1.x (netmask
Guilherme Barile wrote:
From a computer in the 10.0.0.x network I can ping the internet (via ADSL)
and any computer on the 10.0.1.x network (vice versa for the computers on
the 10.0.1.x net) BUT, i cannot access the servers connected to NIC2 (eth1)
directly I need some special rule for
4 matches
Mail list logo