on Tue, Dec 04, 2001 at 04:18:13AM -0800, Karsten M. Self (kmself@ix.netcom.com) wrote:
> I'm trying to configure a system as a LAN <=> wireless gateway. From
> everything I can see, everything's set up right, except that the gateway
> isn't gatewaying.
Well, I figured out the problem. It wasn't my ego after all. It was
the interpreter of dreams. Well, I feel a bit better, my friend hadn't
figured it out either.
> I've set up two networks (introspec: 192.168.0.0, wireless:
> 192.168.1.0).
...and that's the initial clue.
> I can ping from the gateway to either network, establish connections
> to/from the gateway and hosts on either network. I can't connect across
> the gateway from the wireless side to the LAN. If I add a route entry
> for hosts on the LAN, I can ping the gateway on its wireless network
> interface.
On a hunch, I started playing with adding routes on other hosts back to
the 192.168.1.0 network, and then pinging these hosts. I'd done this on
navel and fritz, and found to my surprise I could ping them. But not
jung. Think...hmm...maybe the packets need to get back to me, eh?
Remember:
> Network consists of:
>
> - jung: internet gateway (via modem) / firewall, OpenBSD box.
> 192.168.0.1 (introspect)
> - navel: desktop and DNS server.
> 192.168.0.32 (introspect)
> - ego: laptop, intended LAN/802.11b gateway.
> 192.168.0.64 (eth0, introspect)
> 192.168.1.1 (eth1, wireless)
> - id: laptop, 802.11b remote link
> 192.168.1.2 (eth0, wireless)
>
> For the graphically inclined:
>
>
> { Internet } -- jung (oBSD/Gateway)
> |
> [ hub ] (wireless link)
> / \
> navel (DNS) ego (laptop) · · · · · · id (laptop)
> Configuration:
(on ego)
> route:
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 127.0.0.0 0.0.0.0 255.255.255.255 UH 0 0 0 lo
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
> 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
> 0.0.0.0 192.168.0.1 0.0.0.0 UG 1 0 0 eth0
Note that last entry. It's my default gateway. Which is jung. Except
that jung had no idea how to reach 192.168.1.0. All it knows are its
internal interface (192.168.0.0) and whatever IP my ISP's tossed at its
external interface. 192.168.1.0 is nonrouteable (though my firewall
rules don't block it, so I'm passing the packets off to my ISP whose
going "Karsten, you dumb shit, can't you keep your nonroutables inside
your own netowrk?").
> Behavior:
>
> I can ping both ways between any one node and ego. Hell, at the
> moment, I've got sessions open on ego to id, navel, jung, and fritz [1].
>
> I added the following route entry on navel and can ping ego's
> 192.168.1.1 IP from navel:
>
> $ route add 192.168.1.0 gw ego
I'd not tried pinging navel at this point, found I could.
Solution: add a route to the network from my network's default gateway.
All is solved.
...and I learned something about networks and routing.
Peace.
--
Karsten M. Self <kmself@ix.netcom.com> http://kmself.home.netcom.com/
What part of "Gestalt" don't you understand? Home of the brave
http://gestalt-system.sourceforge.net/ Land of the free
Free Dmitry! Boycott Adobe! Repeal the DMCA! http://www.freesklyarov.org
Geek for Hire http://kmself.home.netcom.com/resume.html
Attachment:
pgpd0fAho58T1.pgp
Description: PGP signature