Using madwifi to setup linux router/access point

kragbax · 12-22-2004, 09:04 PM

I got madwifi compiled and a bridge setup. I set the 802.11a/b/g card set to 'b' only with no encryption and 'test' for the SSID and set to master. The laptop can't find it using either net stumbler or the windows networking.

I did notice something kind of funky, anytime I take down ath0 it reverts to 192.168.1.2 not 0.0.0.0

iwconfig gives

Code:

ath0      IEEE 802.11b  ESSID:""
          Mode:Master  Frequency:2.417GHz  Access Point: 00:0F:66:11:BF:C8
          Bit Rate:0kb/s   Tx-Power:50 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:257623  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:6  Invalid misc:9   Missed beacon:1

ifconfig gives this...

Code:

ath0      Link encap:Ethernet  HWaddr 00:0F:66:11:BF:C8
          inet6 addr: fe80::20f:66ff:fe11:bfc8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:803459 dropped:0 overruns:0 frame:610696
          TX packets:646 errors:9 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:199
          RX bytes:0 (0.0 b)  TX bytes:104091 (101.6 Kb)
          Interrupt:10 Memory:22e80000-22e90000

br0       Link encap:Ethernet  HWaddr 00:0F:66:11:BF:C8
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::20f:66ff:fe11:bfc8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:20871 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26073 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1881792 (1.7 Mb)  TX bytes:26115952 (24.9 Mb)

eth0      Link encap:Ethernet  HWaddr 00:A0:CC:40:20:6B
          inet6 addr: fe80::2a0:ccff:fe40:206b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:220767 errors:0 dropped:0 overruns:0 frame:6
          TX packets:269530 errors:0 dropped:0 overruns:0 carrier:0
          collisions:230 txqueuelen:1000
          RX bytes:112559414 (107.3 Mb)  TX bytes:32590540 (31.0 Mb)
          Interrupt:11 Base address:0x6000

eth1      Link encap:Ethernet  HWaddr 00:A0:CC:3D:85:77
          inet6 addr: fe80::2a0:ccff:fe3d:8577/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:271561 errors:1 dropped:0 overruns:0 frame:0
          TX packets:221082 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:32999563 (31.4 Mb)  TX bytes:118456892 (112.9 Mb)
          Interrupt:4 Base address:0xc000

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:20 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:7225 (7.0 Kb)  TX bytes:7225 (7.0 Kb)

ppp0      Link encap:Point-to-Point Protocol
          inet addr:xx.xx.xx.134  P-t-P:172.31.255.251  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
          RX packets:212797 errors:0 dropped:0 overruns:0 frame:0
          TX packets:261615 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:107335733 (102.3 Mb)  TX bytes:26597258 (25.3 Mb)

Ron_shyen · 01-10-2005, 08:32 PM

Hi, are you using a Microsoft OS laptop to access your access point (AP)? I notice that you didn't put an ESSID to your AP. This is the name of the AP, according to my experience, you will need the ESSID name so that the AP is detectable.

Ron_shyen · 01-10-2005, 08:38 PM

I do facing a situation, when the access point is up with the bridge, the desktop-convert AP cannot access to the internet. Is this a normal situation to expect? Is there anyway to make the desktop still accessible to the internet?