OBSD 3.7 - new install

I am building a router.  And I am having a routing problem.  I am not
doing any packet filtering, NAT or anything... its all strictly private
address space nets I also most definately have ip forwarding set in
sysctl

Right now I have the router installed with two active interfaces...

Segment A (192.168.0.4) interface on the router 
Segment B (10.3.0.1) interface on the router

Now I have a machine on each segment also:

192.168.0.2 (Segment A)
10.3.50.1 (Segment B)

Segment B has the default gateway set to 192.168.0.2
(192.168.0.2 then passes out to the internet )

>From 10.3.50.1 my default gateway on is the 10.3.0.1 (router nic).  I
can ping any of the other interface cards on the router (there are a
few) including the 192.168.0.4 interface on the router.  But I cannot
ping the 192.168.0.2 machine.

* WAIT * I know what you are going to say... but I DO have the ip
forwarding set

# sysctl -a | grep forward 
net.inet.ip.forwarding=1

I checked many times since.

Now, if I go to the 192.168.0.2 machine, I added a route so it knows
where the 10.3.0.0 network is, and I can ping the 10.3.50.1 machine no
problem.  I can also ping all the other nic's on the router.  So the
router is forwarding packets.  

So if the pings can get from 192.168.0.2 to 10.3.50.1, the ping
responses from 10.3.50.1 should be able to be returned from the
192.168.0.2 box back no problem.

I am not sure where the pings are being lost... if the machine on
segment A knows how to reach segment B and can ping it... doesn't that
mean the segment B machine essentially can get pings back if it sends
them to Segment A?  Segment A is its default route.

Confused...

Any help would be greatly appreciated

All the boxes are obsd 3.7 except for the 10.3.50.1 box which is linux






-- 

Bill Chmura
Director of Internet Technology
Explosivo ITG
Wolcott, CT

p: 860.621.8693
e: [EMAIL PROTECTED]
w. http://www.explosivo.com

Reply via email to