[Voyage-linux] Basic Wifi problem
Teco Boot
(spam-protected)
Tue May 10 15:15:41 HKT 2011
Op 9 mei 2011, om 18:02 heeft Gustin Johnson het volgende geschreven:
> I would not say that having an IP on both interfaces in the same
> network is wrong, it does introduce a few problems.
>
> There are a couple of ways of solving this. Probably the easiest is
> to create a bridge interface and assign both physical interfaces to
> it, then assign the IP to the bridge interface. There are examples in
> the default interfaces file.
Agreed.
There should be one bridge connecting the two segments. STP
could do the job, having one active bridge.
I would not configure a WLAN station (not AP) as a bridge.
> Another approach is to statically assign an IP to the ethernet device
> but do not specify a default gateway. This way you can ssh in and
> bring up the wifi device and make sure that DHCP is working. Of
> course you have to connect from a machine in the same network for this
> to work.
I don't know what the problem was. I doubt if this solves the problem.
When SSH from same subnet: same problem. From other subnet: when WLAN
is down, SSH is not possible at all (no GW on eth0).
> As Punky suggested, having a console available over a serial port is
> pretty much indispensable when configuring the ALIX boards since it
> will work even when you horribly break the network config. Make sure
> that your computer has a serial port as well, or else you will need to
> pick up a USB to serial (RS-232) adapter as well.
Ack.
But reliable IP connectivity to the box is more than nice to have, IMHO.
> There is another option that involves creating queues
(do you mean: routing tables?)
> for each
> interface, and then some rules for which traffic gets put into which
> queue (this is the short short description). This is probably not the
> best option for you right now. If you get curious about this sort of
> thing the Linux Advanced Routing and Traffic Control Howto is pretty
> much the bible on this sort of thing:
> http://lartc.org
What about a handy script, creating rules for "strong host" behavior:
return packets with source address that matches a configured address on
an interface leave the box on that interface.
Teco
>
> Hth.
>
> On Mon, May 9, 2011 at 2:55 AM, Teco Boot <teco at inf-net.nl> wrote:
>> eth0 could be used for the return path. When the cable is disconnected, goes eth0 down?
>> Down means there is no "UP" in ifconfig, and eth0 is removed in routing table.
>>
>> Teco
>>
>> Op 7 mei 2011, om 08:26 heeft Steve Holdoway het volgende geschreven:
>>
>>> Shouldn't both interfaces be on separate subnets???
>>>
>>> On Fri, 2011-05-06 at 17:38 -0700, Big Booger wrote:
>>>> Hi Punky
>>>>
>>>> I have attached the output from running the commands you recommended.
>>>> #ifconfig -a
>>>> #route -n.
>>>>
>>>> I didn't know what you meant by the serial console so I googled it. Tommorow I
>>>> will try to get a cable and enable it and let you know.
>>>>
>>>> Thanx again,
>>>>
>>>> Matt
>>>>
>>>> root at voyage:~# ifconfig -a
>>>> ath0 Link encap:Ethernet HWaddr 06:02:6f:44:e1:3e
>>>> inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
>>>> inet6 addr: fe80::402:6fff:fe44:e13e/64 Scope:Link
>>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>>> RX packets:1522 errors:0 dropped:0 overruns:0 frame:0
>>>> TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
>>>> collisions:0 txqueuelen:0
>>>> RX bytes:93400 (91.2 KiB) TX bytes:1117 (1.0 KiB)
>>>>
>>>> eth0 Link encap:Ethernet HWaddr 00:0d:b9:1b:e3:e8
>>>> inet addr:192.168.1.31 Bcast:192.168.1.255 Mask:255.255.255.0
>>>> inet6 addr: fe80::20d:b9ff:fe1b:e3e8/64 Scope:Link
>>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>>> RX packets:1978 errors:0 dropped:0 overruns:0 frame:0
>>>> TX packets:1234 errors:0 dropped:0 overruns:0 carrier:0
>>>> collisions:0 txqueuelen:1000
>>>> RX bytes:142546 (139.2 KiB) TX bytes:81661 (79.7 KiB)
>>>> Interrupt:10 Base address:0xa000
>>>>
>>>> eth1 Link encap:Ethernet HWaddr 00:0d:b9:1b:e3:e9
>>>> BROADCAST MULTICAST MTU:1500 Metric:1
>>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>>> collisions:0 txqueuelen:1000
>>>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>>>> Interrupt:15 Base address:0xe000
>>>>
>>>> lo Link encap:Local Loopback
>>>> inet addr:127.0.0.1 Mask:255.0.0.0
>>>> inet6 addr: ::1/128 Scope:Host
>>>> UP LOOPBACK RUNNING MTU:16436 Metric:1
>>>> RX packets:30 errors:0 dropped:0 overruns:0 frame:0
>>>> TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
>>>> collisions:0 txqueuelen:0
>>>> RX bytes:2442 (2.3 KiB) TX bytes:2442 (2.3 KiB)
>>>>
>>>> wifi0 Link encap:UNSPEC HWaddr
>>>> 00-02-6F-44-E1-3E-65-74-00-00-00-00-00-00-00-00
>>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>>> RX packets:1933 errors:0 dropped:0 overruns:0 frame:12
>>>> TX packets:126 errors:5 dropped:0 overruns:0 carrier:0
>>>> collisions:0 txqueuelen:280
>>>> RX bytes:317333 (309.8 KiB) TX bytes:9096 (8.8 KiB)
>>>> Interrupt:11
>>>>
>>>>
>>>> root at voyage:~# route -n
>>>> Kernel IP routing table
>>>> Destination Gateway Genmask Flags Metric Ref Use Iface
>>>> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
>>>> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 ath0
>>>> 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 ath0
>>>> 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
>>>>
>>>>
>>>>
>>>> ----- Original Message ----
>>>> From: Kim-man 'Punky' TSE <punkytse at punknix.com>
>>>> To: Big Booger <furrybailey at yahoo.ca>
>>>> Cc: voyage-linux at voyage.hk
>>>> Sent: Fri, May 6, 2011 12:35:03 AM
>>>> Subject: Re: [Voyage-linux] Basic Wifi problem
>>>>
>>>> Hi Matt,
>>>>
>>>> This is the exactly the same config I have in my office eveyday, it works for me
>>>> without problem. Can you show the
>>>>
>>>> output of:
>>>>
>>>> # ifconfig -a
>>>> # route -n
>>>>
>>>> To further troubshoot you should have enable serial console in ALIX box in order
>>>> to see what happens.
>>>>
>>>> Regards,
>>>> Punky
>>>>
>>>> On 5/6/2011 12:53 PM, Big Booger wrote:
>>>>> Hi
>>>>>
>>>>> I am having some wifi problems with an Alix board and an athereos wifi mini
>>>> PCI
>>>>> card. I have voyage mpd 7.7.0 on the alix. I have the board running no
>>>>> problem
>>>>> through ethernet, and the wifi card scans (see iwlist below). Also when I run
>>>>> nmap on my network I get the ethernet connection showing and another address
>>>>> that I assume is the wifi connection. I can ssh into the wifi address (at
>>>>> least
>>>>> I assume it is the wifi address), but when I disconnect the ethernet cable my
>>>>> connection through the wifi address is disabled. Does anyone have any insight
>>>>> into what is going on here? I would like to have this alix board supply my
>>>> DAC
>>>>> and connect to my Arch Server through wifi - i do not want to have to have an
>>>>> ethernet cable permenently connected to the board. I have tried booting the
>>>>> board up with out an Ethernet cable connected, and nmap shows no new
>>>> connection
>>>>> onto my network. Any help is appreciated.
>>>>>
>>>>> I have attached some information below. Let me know if I should supply any
>>>>> more
>>>>> information.
>>>>>
>>>>> Regards,
>>>>> Matt
>>>>>
>>>>>
>>>>>> From running #iwlist ath0 scan
>>>>> Cell 02 - Address: 06:26:F2:F4:31:E5
>>>>> ESSID:"TestMatt"
>>>>> Mode:Master
>>>>> Frequency:2.422 GHz (Channel 3)
>>>>> Quality=42/70 Signal level=-53 dBm Noise level=-95 dBm
>>>>> Encryption key:on
>>>>> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
>>>>> 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
>>>>> 48 Mb/s; 54 Mb/s
>>>>> Extra:bcn_int=200
>>>>> IE: IEEE 802.11i/WPA2 Version 1
>>>>> Group Cipher : TKIP
>>>>> Pairwise Ciphers (2) : CCMP TKIP
>>>>> Authentication Suites (1) : PSK
>>>>> IE: WPA Version 1
>>>>> Group Cipher : TKIP
>>>>> Pairwise Ciphers (2) : CCMP TKIP
>>>>> Authentication Suites (1) : PSK
>>>>>
>>>>> Extra:wme_ie=dd180050f2020101850003a4000027a4000042435e0062322f00
>>>>>
>>>>>
>>>>> Interfaces file contents:
>>>>> # Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or
>>>>> # /usr/share/doc/ifupdown/examples for more information.
>>>>> auto lo
>>>>> iface lo inet loopback
>>>>>
>>>>> auto eth0
>>>>> iface eth0 inet dhcp
>>>>>
>>>>> auto ath0
>>>>> iface ath0 inet dhcp
>>>>> madwifi-base wifi0
>>>>> wireless-mode Managed
>>>>> wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
>>>>>
>>>>>
>>>>> Contents of wpa_supplicant.conf:
>>>>> network={
>>>>> ssid="TestMatt"
>>>>> #psk="password"
>>>>> psk=96c98dc5ca179fe2286d29eb0dd5021ad44fac388c1aeae121b8de6e40e2fa65
>>>>> key_mgmt=WPA-PSK
>>>>> proto=WPA
>>>>> # proto=RSN #uncomment for WPA2
>>>>> }
>>>>>
>>>>>
>>>>> Output of # lspci
>>>>> 00:01.0 Host bridge: Advanced Micro Devices [AMD] CS5536 [Geode companion]
>>>> Host
>>>>> Bridge (rev 33)
>>>>> 00:01.2 Entertainment encryption device: Advanced Micro Devices [AMD] Geode LX
>>>>> AES Security Block
>>>>> 00:09.0 Ethernet controller: VIA Technologies, Inc. VT6105M [Rhine-III] (rev
>>>>> 96)
>>>>> 00:0b.0 Ethernet controller: VIA Technologies, Inc. VT6105M [Rhine-III] (rev
>>>>> 96)
>>>>> 00:0e.0 Ethernet controller: Atheros Communications Inc. AR5413 802.11abg NIC
>>>>> (rev 01)
>>>>> 00:0f.0 ISA bridge: Advanced Micro Devices [AMD] CS5536 [Geode companion] ISA
>>>>> (rev 03)
>>>>> 00:0f.2 IDE interface: Advanced Micro Devices [AMD] CS5536 [Geode companion]
>>>>> IDE
>>>>> (rev 01)
>>>>> 00:0f.4 USB Controller: Advanced Micro Devices [AMD] CS5536 [Geode companion]
>>>>> OHC (rev 02)
>>>>> 00:0f.5 USB Controller: Advanced Micro Devices [AMD] CS5536 [Geode companion]
>>>>> EHC (rev 02)
>>>>>
>>>>> _______________________________________________
>>>>> Voyage-linux mailing list
>>>>> Voyage-linux at list.voyage.hk
>>>>> http://list.voyage.hk/mailman/listinfo/voyage-linux
>>>>
>>>>
>>>
>>> --
>>> Steve Holdoway <steve at greengecko.co.nz>
>>> http://www.greengecko.co.nz
>>> MSN: steve at greengecko.co.nz
>>> Skype: sholdowa
>>>
>>>
>>> _______________________________________________
>>> Voyage-linux mailing list
>>> Voyage-linux at list.voyage.hk
>>> http://list.voyage.hk/mailman/listinfo/voyage-linux
>>
>>
>> _______________________________________________
>> Voyage-linux mailing list
>> Voyage-linux at list.voyage.hk
>> http://list.voyage.hk/mailman/listinfo/voyage-linux
>>
More information about the Voyage-linux
mailing list