On Wednesday, 5. June 2002 16:07, Carlos Manuel Duclos Vergara wrote:
Hi,
Hi,
Hi Carlos,
route -n tells
Destination Gateway Genmask Flags Metric Ref Use Iface 62.245.134.128 0.0.0.0 255.255.255.240 U 0 0 0 eth1 62.245.134.144 0.0.0.0 255.255.255.240 U 0 0 0 eth0 0.0.0.0 62.245.134.129 0.0.0.0 UG 0 0 0 eth1
if this is a cross cable connection (or am i wrong?), you need to setup 62.245.134.145 62.245.134.144 255.255.255.255 eth0 (maybe
Can you explain why you need a netmask of 255.255.255.255 when using a cross cable?
you should check your masks, if you're trying to protect a network why using a cross cable?)
The web server is connected directy to the firewall with a cross cable. The only alternative would be a straight cable and a hub, or am I wrong? What's the advantage?
The web servers NIC is configured as eth0 62.245.134.145 netmask 255.255.255.240
and the routing table looks like this: Destination Gateway Genmask Flags Metric Ref Use Iface 62.245.134.144 0.0.0.0 255.255.255.240 U 0 0 0 eth0 62.245.134.144 0.0.0.0 255.255.255.240 U 0 0 0 eth0 0.0.0.0 62.245.134.146 0.0.0.0 UG 0 0 0 eth0
the default route must be 0.0.0.0 62.245.134.144 not 0.0.0.0 62.245.134.146
I have set it like this, but I get a "network unreachable" error when the system sets the route at boot time. Wrong netmask?
bye
by, Robert -- Where do you want to be tomorrow? Entracom. Building Linux systems. http://www.entracom.de