Re: [Aironet] Compiling the latest Drivers on RH6.2

[Steve R. <sr...@ad...>]

Bob,
I wanted to thank you again for your advice and update you on my progress.
I finally solved my problem by starting ROUTED on my LINUX box. That fixed
up the routing and things are working great.

I am running V1.1 w/Ben Reed's suggested bypass for the 800 status codes.

Thanks again for all your assistance to me but all the correspondents in
this list.

Steve
P.S. I'm sitting here, watching the Olympics and composing this message
while connected to the network.

----- Original Message -----
From: "Bob Edwards" <Rob...@an...>
To: "Steve Robertson" <r73...@pa...>
Cc: <ai...@en...>
Sent: Wednesday, August 30, 2000 11:35 PM
Subject: Re: [Aironet] Compiling the latest Drivers on RH6.2


> Steve Robertson wrote:
> >
> > Bob,
> > Thank you very much for your note ...
> > I added the #include but didn't need the "hack" in airo.h. I'm using a
> > "virgin" RH6.2 kernel.
> >
> > After fumbling around I finally got the module loaded with insmod, a
route
> > added and the card configured. Now when I ping the PCI card(Linux) from
a
> > Win98 client ... I get the following message on the console for the root
user:
> >
> >     "Airo: Got  weird status 800"
> >
> > The other issue I'm having is routing packets from the wirless subnet
onto my
> > normal subnet. The wirless stuff is 192.168.4.1(Linux-eth1) and
> > 192.168.4.2(Win98). The normal net is 192.168.30.8(Linux-eth0) and
several
> > others. Another Linux box with a firewall is running at 192.168.30.1.
How do I
> > set up the routing so packets flow from the wireless segment to normal
and
> > vice versa?
> >
>
> Because you are using "private" subnets, I am not sure if the kernel will
> route between them or not. I do it with the same subnets on both sides of
> the router and use a couple of tricks with sub-subnet masks and proxy-ARP.
>
> However, to do it in your environment, I would do this:
>
> on your linux wireless router:
>  route add -net default gw 192.168.30.1 # add a default route to the fw
>
> on the firewall:
>  route add -net 192.168.4.0 netmask 255.255.255.0 gw 192.168.30.8
>
> on the wireless windoze box:
>  set the default route to 192.168.4.1
>
> If the firewall is happy, you should be able to ping 192.168.4.1 (eth1 on
> your wireless router) and, if the wireless stuff is working you should be
> able to ping 192.168.4.2.
>
> In my set up, I have something like this:
>
> On public subnet x.y.z.0 I have my first wireless router with the same
> IP number on both interfaces (eth0 is wired, eth1 is wireless):
>  ifconfig eth0 x.y.z.88 netmask 255.255.255.0 up
>  ifconfig eth1 x.y.z.88 netmask 255.255.255.255 up
> and I have routes set up:
>  route add -net default gw x.y.z.1
>  route add -host x.y.z.71 dev eth1
>  route add -net x.y.z.64 gw x.y.z.71
> turn on forwarding:
>  echo 1 > /proc/sys/net/ipv4/ip_forward
>
> and I have proxy (static) ARP entries:
>  arp -i eth0 -Ds x.y.z.65 eth0 pub
>  ...
>  arp -i eth0 -Ds x.y.z.78 eth0 pub
>
> On my other wireless router (at home), I also have the same IP number on
> both interfaces (again, eth0 is wired, eth1 is wireless):
>  ifconfig eth0 x.y.z.71 netmask 255.255.255.240 up
>  ifconfig eth1 x.y.z.71 netmask 255.255.255.255 up
> set up routes:
>  route add -host x.y.z.88 dev eth1
>  route add -net default gw x.y.z.88
> turn on forwarding:
>  echo 1 > /proc/sys/net/ipv4/ip_forward
>
> And it all works just fine. I have a number of machines (up to 14) routing
> through this wireless link.
>
> Another option to consider is to use IP-Masquerading (NAT).
>
> Cheers,
>
> Bob Edwards.