On Thu, 1 Sep 2005 01:01:08 -0400, Bill wrote: >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 > >
I'm sure that you know what you mean but what you have stated about the networks and host is ambiguous. Let's see if I guess correctly in phrasing it a little differently. If not you have a better chance to correct the impression. There are 2 private networks: 192.168.0.0/24 10.3.0.0/8 <- maybe you use a /24 but /8 is the "natural" for a 10. network You have 3 hosts: A router with 2 NICs, 192.168.0.4 and 10.3.0.1 One with a NIC = 192.168.0.2 (connected to the router on its 192.168.0.4 NIC) It also has another NIC that connects to the internet (somehow) One with a NIC = 10.3.50.1 (connected to the router NIC 10.3.0.1) So far so good? Well really you have 2 routers there. The one you called a router plus the 192.168.0.2 host. The latter will need to have forwarding on as well as the one you called Router in your post. Your first router will need to have its default gateway set to 192.168.0.2 for traffic from the 10. network to get to the 'net. Looking at nststat -rnf inet on your Openbsd boxes might be enlightening and should be posted as a part of your question. The Linux box only needs netstat -rn as it defaults to the inet family. Forget the term segments. It is confusing where you have no segmentation. Make sure ALL machines on your 10. network have a netmask of 255.0.0.0 for "purity" because you need at least 255.255.192.0 (math done in head at end of day - please check!) to get that third octet (50) covered. Let's see where that gets you..... >From the land "down under": Australia. Do we look <umop apisdn> from up over? Do NOT CC me - I am subscribed to the list. Replies to the sender address will fail except from the list-server.
