We figured it out.  It was ICS messing up the routing on the 192.168.0.0
subnet the whole time.  Let me state again that I HATE ICS.  Thanks for
teh help guys.

--------------<<<((((((0))))))>>>--------------
Leo Clark
[EMAIL PROTECTED]


On Tue, 9 Oct 2001, Jacob Meuser wrote:

> On Tue, Oct 09, 2001 at 01:38:10PM -0700, Leo Clark wrote:
> 
> > We each have our own DSL lines and nat gateways to share the connection
> > between the various boxes on our networks.
> 
> > We are useing three subnets.  One for my house, one for the wireless
> > network, and one for my friend's house.  
> 
> 
> A little diagram, for my own clarity  
> 
>                 ISP------NET------ISP
>                  |                 |
>            net0-nat0              nat1-net1
>             |                           | 
>          wigate0--------winet--------wigate1
>          
> 
> net0 - 10.0.0.0/24
> net1 - 192.168.1.0/24
> # hypothetical
> winet - 172.16.0.0/24
> wigate0 - 10.0.0.101/32 && 172.16.0.1/32
> wigate1 - 192.168.1.101/32 && 172.16.0.2/32
> 
> 
> > We got all his routes set properly and his OpenBSD wireless gateway seamed
> > great too.  Until we tried to route packets through it.  It refuses to
> > pass anything though it.  I have it sitting on both networks and talking
> > on them fine.  It can see and talk with the other wireless gateway box,
> > and it can talk through that one to get to my network.  It can also use
> > the wired nic to get to anything on my friends network.  The wireless
> > laptop also talks just fine with it.  But no one can use it as a gateway,
> > if I set the laptop to use it as it's default route I can't see
> > anything.  If I try to access 192.168.0/24 (my friends subnet) from my
> > subnet (10.0.0/24) my packets get stuck in his wireless gateway.  If one
> > of his boxes try to ping my wireless gateway, or even a wireless laptop in
> > range, the packets get stoped at the wireless gateway box.
> 
> You see packets arriving at wigate1 with tcpdump, but no forwarding,
> correct? 
> 
> > I checked sysctl.conf and use the sysctl command to set
> > net.inet.ip.forwarding=1 but still not avail.  It can talk on both
> > networks just fine.  I don't have IPF running nor do I want it to right
> > now.  I would like to just get it up before playing with security and
> > breaking it again.
> 
> I assume no NAT either?
> 
> > The routing tables are correct, and everything looks right.  Is there
> > something I missed?  Is there something else in OpenBSD (i'm running 2.9
> > release BTW) that could stop this from working?  I have a fairly plain
> > install.  Basicly all I did from first boot was to add the extra routes,
> > add some users, modify sysctl.conf, and fix up the hosts file.
> 
> should just need net.inet.ip.forwarding=1 and the routes
>  
> > I can't understand what I did diffrent on my box that makes it work that
> > could be diffrent then his.  I'm really at a loss here.  I would aprechate
> > any ideas.  Thanks!
> 
> Perhaps something with /etc/mygate in wigate1?  That's just a wild
> guess.  Have you actually tried diffing /etc on the machines to see if
> perhaps you made some kind of typo (since all you'll see is what you've
> changed)?
> 
> -- 
> <[EMAIL PROTECTED]>
> <[EMAIL PROTECTED]>
> <[EMAIL PROTECTED]>
> 

Reply via email to