Hi Matt,

You can do a simple test. The problem may be that you have both eth0 and ath0 using the same subnet. When you connect, even you specifiy IP 192.168.1.31, it may still use eth0 for communication. I have not expert in networking, probably someone can point this out.

It is better if you have serial console for troubleshoot. Then comment "auto eth0" to see what happen in your wireless interface.

# auto eth0
iface eth0 inet dhcp

Regards,
Punky

On 7/5/2011 8:38, 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@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@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<[email protected]>
To: Big Booger<[email protected]>
Cc: [email protected]
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
[email protected]
http://list.voyage.hk/mailman/listinfo/voyage-linux



--

Regards,
Kim-man "Punky" Tse

* Open Source Embedded Solutions and Systems
  - Voyage Linux (http://linux.voyage.hk)
  - Voyage ONE   (http://linux.voyage.hk/voyage-one)
  - Voyage MPD   (http://linux.voyage.hk/voyage-mpd)
* Voyage Store   (http://store.voyage.hk)


_______________________________________________
Voyage-linux mailing list
[email protected]
http://list.voyage.hk/mailman/listinfo/voyage-linux

Reply via email to