Centos 5.2 Firewall / AccessPoint using Atheros AR5212

JulianTosh · 01-22-2009, 02:49 PM

Reaching out for some help on this one. I've come so far and learned a lot but I think I've reached the end of the road as far as my brain and google links will take me.

I've got a home firewall setup running CentOs 5.2. It's got two wired interfaces: inside and out and I'm successfully using iptables to filter and nat traffic in and out as expected.

Recently I've added an AirLink101 AWLH4030 wireless nic that is recognized as the AR5212/AR5213 chipset.

It appears that I have everything configured properly and I've eradicated every error encountered so far. Currently, I have my ath0 interface up and essid set but am unable to connect or even see the AP from my laptop.

Any help to get me over this next hurdle is massively appreciated!

Here is a metric shit ton of debug/output for any networking gurus to ponder over:

Ethernet Devices:

Code:

alias lsEth='lspci -v | grep "Ethernet" -A 7'

Code:

lsEth 
01:09.0 Ethernet controller: VIA Technologies, Inc. VT6105 [Rhine-III] (rev 86)
	Subsystem: D-Link System Inc Unknown device 1406
	Flags: bus master, stepping, medium devsel, latency 64, IRQ 209
	I/O ports at b800 [size=256]
	Memory at ee000000 (32-bit, non-prefetchable) [size=256]
	[virtual] Expansion ROM at eff00000 [disabled] [size=64K]
	Capabilities: [40] Power Management version 2

01:0a.0 Ethernet controller: Atheros Communications Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01)
	Subsystem: Unknown device 1948:3ab9
	Flags: bus master, medium devsel, latency 168, IRQ 169
	Memory at ed800000 (32-bit, non-prefetchable) [size=64K]
	Capabilities: [44] Power Management version 2

01:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
	Subsystem: Sony Corporation Unknown device 80ea
	Flags: bus master, medium devsel, latency 64, IRQ 209
	I/O ports at b400 [size=256]
	Memory at ed000000 (32-bit, non-prefetchable) [size=256]
	Capabilities: [50] Power Management version 2

Interesting entries from DMESG:

Code:

alias dmesgEth='dmesg | egrep "`lsEth | grep "^..:..\." | cut -f1 -d" "  | tr "\n" "\|"`^[ea]th.:|^wifi"'

Code:

ACPI: PCI Interrupt 0000:01:0a.0[A] -> GSI 22 (level, low) -> IRQ 169
wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
wifi0: turboG rates: 6Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
wifi0: H/W encryption support: WEP AES AES_CCM TKIP
wifi0: mac 7.9 phy 4.5 radio 5.6
wifi0: Use hw queue 1 for WME_AC_BE traffic
wifi0: Use hw queue 0 for WME_AC_BK traffic
wifi0: Use hw queue 2 for WME_AC_VI traffic
wifi0: Use hw queue 3 for WME_AC_VO traffic
wifi0: Use hw queue 8 for CAB traffic
wifi0: Use hw queue 9 for beacons
wifi0: Atheros 5212: mem=0xed800000, irq=169
8139cp 0000:01:0d.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
8139cp 0000:01:0d.0: Try the "8139too" driver instead.
ACPI: PCI Interrupt 0000:01:09.0[A] -> GSI 21 (level, low) -> IRQ 209
eth0: VIA Rhine III at 0xee000000, 00:1c:f0:d5:7d:0a, IRQ 209.
eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link cde1.
ACPI: PCI Interrupt 0000:01:0d.0[A] -> GSI 21 (level, low) -> IRQ 209
eth1: RealTek RTL8139 at 0xe0078000, 00:0c:6e:0a:8c:88, IRQ 209
eth1:  Identified 8139 chip type 'RTL-8101'
eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
eth1: link up, 100Mbps, full-duplex, lpa 0xCDE1
eth1: no IPv6 routers present
eth0: no IPv6 routers present
ath0: no IPv6 routers present

Related mods:

Code:

lsmod | egrep "hostap|mii|8139|via_rhine|ath"
hostap_pci             55797  0 
hostap                100937  1 hostap_pci
ieee80211_crypt        10049  1 hostap
dm_multipath           22089  0 
8139too                28737  0 
via_rhine              27597  0 
8139cp                 26305  0 
mii                     9409  3 8139too,via_rhine,8139cp
ath_pci                86180  0 
ath_rate_sample        16896  1 ath_pci
wlan                  172636  4 wlan_scan_ap,ath_pci,ath_rate_sample
ath_hal               195280  3 ath_pci,ath_rate_sample

One thing I've seen referenced in my journey is "hostap_crypt", which is not present and trying to probe it gives me "FATAL: Module hostap_crypt not found." Not sure if I need it since I'm going for an OpenWiFi.

All your interface are belong to us:

Code:

ifconfig -a
ath0      Link encap:Ethernet  HWaddr 00:11:95:E7:69:7B  
          inet6 addr: fe80::211:95ff:fee7:697b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:7282 (7.1 KiB)

eth0      Link encap:Ethernet  HWaddr 00:0C:6E:0A:8C:88  
          inet addr:xxx.xxx.xxx.xxx  Bcast:xxx.xxx.xxx.xxx  Mask:255.255.255.0
          inet6 addr: fe80::20c:6eff:fe0a:8c88/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:25759 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8992 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:6581623 (6.2 MiB)  TX bytes:2766613 (2.6 MiB)
          Interrupt:209 Base address:0x8000 

eth1      Link encap:Ethernet  HWaddr 00:1C:F0:D5:7D:0A  
          inet addr:192.168.2.1  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::21c:f0ff:fed5:7d0a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:11909 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10962 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3048509 (2.9 MiB)  TX bytes:5761780 (5.4 MiB)
          Interrupt:209 Base address:0x4000 

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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

sit0      Link encap:IPv6-in-IPv4  
          NOARP  MTU:1480  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:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

wifi0     Link encap:UNSPEC  HWaddr 00-11-95-E7-69-7B-F8-1C-00-00-00-00-00-00-00-00  
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5888 errors:0 dropped:0 overruns:0 frame:54556
          TX packets:696 errors:543 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:199 
          RX bytes:334021 (326.1 KiB)  TX bytes:88156 (86.0 KiB)
          Interrupt:169 Memory:e01a0000-e01b0000

iwconfig Info:

Code:

iwconfig ath0
ath0      IEEE 802.11b  ESSID:"OpenWifi"  
          Mode:Master  Frequency:2.427 GHz  Access Point: Not-Associated   
          Bit Rate:0 kb/s   Tx-Power:18 dBm   Sensitivity=0/3  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=0/94  Signal level=-95 dBm  Noise level=-95 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Other debugging crap (to me) I've seen people post:

Code:

find /proc -name ath0 -ls
4026532429    0 dr-xr-xr-x   2 root     root            0 Jan 22 11:41 /proc/sys/net/ath0
4026532436    0 dr-xr-xr-x   2 root     root            0 Jan 22 11:41 /proc/net/madwifi/ath0

Code:

cat /proc/net/wireless 
Inter-| sta-|   Quality        |   Discarded packets               | Missed | WE
 face | tus | link level noise |  nwid  crypt   frag  retry   misc | beacon | 20
  ath0: 0000    0.  161.  161.       0      0      0      0      0        0

JulianTosh · 01-22-2009, 07:17 PM

Moderator: I just noticed there was a linux wireless sub-forum... feel free to move this there.

JulianTosh · 01-24-2009, 03:53 AM

<crickets>chirp, chirp, chirp</crickets>

Can someone tell me the difference or significance of having seemingly duplicate interfaces (wifi0 vs ath0)?

Or, any idea what's up with the aphost_crypt error?

And, is there any command to trace a kernel module to a device? For instance, how can I tell explicitly that kernel module "8139too" is indeed identifying and managing the pci device "0000:01:0d.0"?

Thanks!