Subject: Re: (Revisiting) Using airport- doesn't anyone know?
From: Brice D Ruth (brice@webprojkt.com)
Date: Thu Jun 21 2001 - 08:53:16 MDT
All right, I'll mimic your configuration and go from there. I was
trying to grab YDL 2.0, but it appears that the ISOs aren't available
for download yet (not that I was able to find) - and I don't have a
retail store close by that I can go pick them up at.
Anyway, as far as the eth0/eth1 thing with ping - if you're using your
AirPort card exclusively, the eth0 interface should not be up. I had a
similar setup to you, using the AirPort basestation w/ DHCP to my cable
modem. I recently changed it to simply bridge to my firewall box and a
few servers, so that I could access those via my wireless boxes. Here's
an example of my routing table, on my laptop running Mandrake Linux 8,
with a PrismII wireless card, talking to an AirPort basestation: (route -n)
*Destination Gateway Genmask Flags Metric Ref Use
Iface*
10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
172.16.113.0 0.0.0.0 255.255.255.0 U 0 0 0
vmnet1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 10.0.0.1 0.0.0.0 UG 0 0 0 eth0
In this example, my PrismII wireless card comes up as eth0, since I
don't have any other interfaces plugged in (the Titanium has built-in
ethernet, so it will always detect it first, assign eth0, then detect
the AirPort and assign it eth1). Ignore the vmnet1 - that's for my
VMware virtual session. My wireless card receives the IP address
10.0.0.3 from the DHCP server on my firewall, via the AirPort
basestation that is bridging, hence a route to 10.0.0.0 exists via eth0.
My vmnet1 interface has an assigned IP address of 172.16.113.1, so a
route exists via vmnet1 to 172.16.113.0. My localhost loopback
interface creates a route to 127.0.0.0 via its IP address of 127.0.0.1
and the interface lo. Lastly, my gateway is set as 10.0.0.1 (my
firewall) and the routing table correctly identifies that any packet not
covered by the previous three entries should be sent to 10.0.0.1 via the
eth0 interface. Does this make sense?
Hope this helped clear up the routing table :)
-Brice
William K. Gibson wrote:
>on 6/19/01 5:46 PM, Brice D Ruth at brice@webprojkt.com wrote:
>
>>Just to refresh my memory, what hardware are you running and what distribution
>>are you running? As many details (however insignificant they may seem) as you
>>can provide will help.
>>
>
>Ok, thanks.
>
>I'm using a Titanium powerbook. Originally I started with YDL 1.2 but I
>upgraded to ben's kernel (Linux PPC 2.4.5) in order to take advantage of
>airport and other items. I compiled the kernel myself and tried my darndest
>to include all the options I would need - including legacy tap0 stuff and
>legacy ipchains. Well, ipchains refuses to work in spite of this so I
>switched to iptables anyway. Most of the options came with help, except for
>the airport, which did not. I still don't understand why the airport module
>comes up as eth1 instead of airport.
>
>Again, I'm using the Base Station as a router to my little private network.
>The Base Station itself connects through DHCP to a cable modem.
>
>Here is an interesting tidbit though. When ifconfig brings up both eth0 and
>eth1 and I ping a site- the ping travels from the eth0 interface in spite of
>the fact that I have set eth1 as the gateway device. I verified this by
>setting eth0 and eth1 to two seperate IP addresses and also unplugging the
>ethernet cable from the machine. If I call 'ifconfig eth0 down' and then
>ping, it uses the eth1 interface. Weird- but maybe its just how ping works?
>
>
>
>--William K. Gibson
>1stDesk Systems
>firstdesk@columbus.rr.com
>
-- WebProjkt, Inc. (ph) 773.562.1008 (fax) 608.204.7004 http://www.webprojkt.com/
This archive was generated by hypermail 2a24 : Thu Jun 21 2001 - 07:59:05 MDT