C. R. Oldham wrote:
> Greetings,
> 
> I'm not a newbie with Debian or with networking, so this problem has been
> extremely frustrating to me.
> 
> I have an old ThinkPad 760e with an Ositech Jack of Diamonds combo
> enet/modem card and an Lucent Orinoco gold card.  I want to use the unit
> as a wireless "access point"--basically a router from the wireless
> ethernet onto my home network and from there out my DSL line to the
> Internet.
> 
> I have successfully installed Debian unstable onto it and upgraded the
> kernel to 2.4.9.  The ethernet adapter and the 802.11b adapter both work
> fine.  The 802.11b adapter is in ad-hoc (aka "peer-to-peer") mode.
> 
> This is the way my network is setup:
> 
> DSL ------- Linux box --switch-- TP 760e --wireless-- Dell Latitude (w2k)
> Internet    eth0: dsl            eth1, ethernet:      802.11b: 192.168.2.2
>                                   192.168.1.151
>             eth1: 192.168.1.1    eth0, 802.11b: 
>                                   192.168.2.1
> 
> The Thinkpad can ping the Linux box at 192.168.1.1 and it can ping the
> Latitude at 192.168.2.2.  It can also reach the general Internet.
> The Latitude can ping the Thinkpad at both 192.168.2.1 and 192.168.1.151.
> It *cannot* however, ping the Linux box at 192.168.1.1 or reach the
> general Internet.
> 
> IP forwarding is turned on.
> 
> For various reasons I don't want to use masquerading--I would rather just
> route.  However I was under the impression that this should "just work"
> without any setup other than ip_forwarding.
> 
> Here's the routing table on the Thinkpad:
> 
> Kernel IP routing table
> Destination    Gateway      Genmask       Flags    Metric Ref Use Iface
> 192.168.2.0    *            255.255.255.0 U          0     0   0  eth0
> 192.168.1.0    *            255.255.255.0 U          0     0   0  eth1
> default        192.168.1.1  0.0.0.0       UG         0     0   0  eth1
> 
> What am I missing?  I know it's something stupid.
> 
> Thanks in advance!
> 
> --cro
> [EMAIL PROTECTED]
> 

You need to add a route on the Linux box to tell it how to reach the 
192.168.2.0 network otherwise it will try to go through its default 
gateway which isn't right. Without masqerading on the IBM, packets 
coming from the Latitude still have their real source address which is 
on a different network than the Linux box and the Linux box doesn't know 
how to reach that network by default.
I think this should work

route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.1.151



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to