> The WiMAX LED on my laptop doesn't do anything with either the 1.3.0 or 1.4.0
> drivers. Is it supposed to be working? It would be nice to have an
> indication as to whether or not I'm still connected.
> And is there any /proc interface to get WiMAX signal strength (similar to
> /proc/net/wireless for 802.11)? It would be nice to have a signal strength
> meter for WiMAX as well, and since it appears that most 802.11 signal
> strength applets use /proc/net/wireless to obtain their statistics, it would
> likely be easiest if a /proc interface were available for WiMAX so existing
> 802.11 signal strength applets could be easily adapted for WiMAX.
I've run into another problem now that I've been using the 1.4 driver a couple
weeks.
The /usr/local/share/wimax/dhcp_renew.sh script periodically fails to kill
dhclient processes. After a couple hours of being connected to WiMAX, I
typically end up with several hundred dhclient processes running in the
background. I suspect what is happening is that the wimax daemon runs dhclient
and either doesn't get a response, or gets a slow response, so it runs another
dhclient (before the first dhclient is killed), which overwrites the first
dhclient's pid file. So, when the first dhclient process finally times out, it
kills the second dhclient process, but the first one gets left running in the
background.
There's two reasonably trivial ways to fix this.
One is to create multiple PID files by changing dhcp_renew.sh to:
#!/bin/bash
dhclient -1 -q -lf /var/lib/dhcp3/dhclient.wmx0.leases -pf
/var/run/dhclient.wmx0.$$.pid $1 >/dev/null 2>&1
kill -9 `cat /var/run/dhclient.wmx0.$$.pid`
rm /var/run/dhclient.wmx0.$$.pid
Another is to avoid the pid problem entirely by having dhclient kill itself
when it's done. This can be done by creating a
/usr/local/share/wimax/dhclient-script script:
#!/bin/bash
/sbin/dhclient-script $@
case "$reason" in
MEDIUM|ARPCHECK|ARPSEND|PREINIT)
;;
*)
kill $PPID
;;
esac
Then change dhcp_renew.sh to:
#!/bin/bash
dhclient -1 -q -lf /var/lib/dhcp3/dhclient.wmx0.leases -pf
/var/run/dhclient.wmx0.pid -sf /usr/local/share/wimax/dhclient-script $1
>/dev/null 2>&1
I've also noticed that roaming is rather slow. It typically takes atleast 10
seconds, and sometimes takes much longer, to reconnect when I move out of range
of one tower and into the range of another tower (I've been using WiMAX on the
train during my commute, and I'm constantly having to wait for it to reconnect
as I roam from tower to tower). I saw one Xohm demo where they were touting
seamless roaming as a feature of the system ... is there some feature that
needs to be added to the driver to allow seamless roaming, or is the driver
just supposed to be able to reconnect much faster than it is currently
reconnecting?
-Paul
_______________________________________________
wimax mailing list
[email protected]
http://www.linuxwimax.org/mailman/listinfo/wimax
