problem with my routing I believe

[Hyperblaze]

I?m in the process of trying to setup a freebsd box to act as a gateway. This box contains 3 network cards. Here is how it is divided.

1) Network card 1 goes to the modem for internet access.

2) Network card 2 has a network class of 192.168.1.0 and plugs in directory to another computer 192.168.1.5 (both gateway network card and other computer have static ips)

3) Network card 3 has a network class of 192.168.2.0 and has dhcp running on it, giving out dynamic ips to several other computers (not including the one discussed above)

All netmasks are 255.255.255.0

As you can see, I?m trying to run two networks and give them both access to the internet.

Any of the computers which are running under dhcp can access anything just fine.

Computer under the class of 192.168.1.0 cannot ping anyone. On the gateway, I can ping the computer with the static IP, but it is VERY slow.

Anyone ever encountered this before? Any possible solutions?

Routing tables

Internet:
Destination Gateway Flags Refs Use Netif Expire
default 74.104.225.1 UGS 1 9762 dc0
192.168.1 255.255.255.255 UGS 0 0 dc0 (I added
this one myself to see if that helped)
192.168.1/24 link#3 UC 0 0 rl1
192.168.1.5 00:b00:1d:7a:a3 UHLW 1 85 rl1 1012
74.104.225/25 link#1 UC 0 0 dc0
74.104.225.1 00:12:43:a9:ae:ac UHLW 2 0 dc0 1188
127.0.0.1 127.0.0.1 UH 0 48 lo0
192.168.2 link#2 UC 0 0 rl0
192.168.2.5 00:50:ba:e8:cf:93 UHLW 1 133 rl0 908
192.168.2.6 00:50:ba:2a:e5:be UHLW 1 327 rl0 1119
192.168.2.7 00:16:b68:2f:cd UHLW 1 1 rl0 64

Internet6:
Destination Gateway Flags Netif Expire
::1 ::1 UHL lo0
fe80::%lo0/64 fe80::1%lo0 U lo0
fe80::1%lo0 link#5 UHL lo0
ff01:5::/32 fe80::1%lo0 UC lo0
ff02::%lo0/32 fe80::1%lo0 UC lo0
$

 

[n0cmonkey]

1. Remove the one you added.
2. Check Rate/duplex and make sure they match. Is there a hub or switch between the computers on 192.168.1/24?
3. Can 192.168.1.5 ping its gateway (you mention the reverse)?

 

[Hyperblaze]

Originally posted by: n0cmonkey
1. Remove the one you added.
2. Check Rate/duplex and make sure they match. Is there a hub or switch between the computers on 192.168.1/24?
3. Can 192.168.1.5 ping its gateway (you mention the reverse)?

2. There is only one computer on the 192.168.1/24 network. This computer is directly connected to the gateway without any switch/hub support. It is also using cross-over cable.
3. Last night's test showed 192.168.1.5 cannot ping anyone (it should only be able to ping the gateway). I'll have to check again if it's either not pinging or just really damn slow pinging. From the gateway, pinging 192.168.1.5, it didn't show pings for at least 5-10 seconds.

 

[n0cmonkey]

Originally posted by: Hyperblaze

Originally posted by: n0cmonkey
1. Remove the one you added.
2. Check Rate/duplex and make sure they match. Is there a hub or switch between the computers on 192.168.1/24?
3. Can 192.168.1.5 ping its gateway (you mention the reverse)?

2. There is only one computer on the 192.168.1/24 network. This computer is directly connected to the gateway without any switch/hub support. It is also using cross-over cable.
3. Last night's test showed 192.168.1.5 cannot ping anyone (it should only be able to ping the gateway). I'll have to check again if it's either not pinging or just really damn slow pinging. From the gateway, pinging 192.168.1.5, it didn't show pings for at least 5-10 seconds.

Sounds fishy. Have you done the usual crap? Like try a different cable, double check for duplex mismatch, etc?

 

[skreet]

Yeah, you say they're directly connected? Crossover cable, or switch? That seems very strange..

 

[her209]

Could it be that only one of the networks is being natted/patted?