Hello all-
I am struggling to get my WISP (v.2290) AP up and running, I was hoping
to have it done today (DSL router came today, woohoo!) but I am
definitely missing a key part of the setup entirely.
Here's the issue. I am using a USR 2445 PLX based PCI adapter with a
USR prism2 based PCMCIA card. When I insert the hostap_plx module, it
correctly finds the card and configures it as wlan0. Following the
instructions in previous post about this device name problem with WISP,
I added the following to my /etc/init.d/networking script:
echo eth1 > /tmp/newname.wlan0
ip link set wlan0 name eth1
before the call to "ifup -a" in the "start)" case.
The renaming works, so that now I can config eth1 through wdistconfig,
but I can't get the wireless configs to stick (i.e. ESSID,channel,rate,
etc.). From looking at the directory /etc/network, it would appear that
these parameters are set by the wireless-start script which reads from
the config file "wireless.config". For the life of me I can't 1)find
what calls the wireless-start script in the startup routine and 2) how
the device renaming that this script does works in my setup.
To run the wireless-start, I first have to disable the interface:
wisprouter: -root-
$ ip link show
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:90:d1:06:19:a7 brd ff:ff:ff:ff:ff:ff
4: eth0: <BROADCAST,MULTICAST,PROMISC,UP> mtu 1500 qdisc pfifo_fast qlen
100
link/ether 00:60:b0:a4:ba:db brd ff:ff:ff:ff:ff:ff
wisprouter: -root-
$ ip link set eth1 down
wisprouter: -root-
$ ./wireless-start eth1
RTNETLINK answers: File exists
wisprouter: -root-
$ ip link show
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
3: netcs: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:90:d1:06:19:a7 brd ff:ff:ff:ff:ff:ff
4: eth0: <BROADCAST,MULTICAST,PROMISC,UP> mtu 1500 qdisc pfifo_fast qlen
100
link/ether 00:60:b0:a4:ba:db brd ff:ff:ff:ff:ff:ff
wisprouter: -root-
$ iwconfig netcs
netcs IEEE 802.11-DS ESSID:"test"
Mode:Master Frequency:2.422GHz Access Point:
00:90:D1:06:19:A7
Bit Rate:2Mb/s Tx-Power:0 dBm Sensitivity=1/3
Retry min limit:8 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
(^ are the default options for the card, the ESSID should be "zack")
Can anyone offer some insight into this? I am sure that I am not the
only person to be running a PLX card and WISP.
Thanks,
Z
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
