Yes, it ends after discovering wifi network(s) and successful end of
dhclient. If there is no know network, it will end very fast. It's not
'classic' daemon where program stays in background and waits for change.
Well, I think this means that this is how wifi-radar was designed to work, ie.
** Changed in: wifi-radar (Ubuntu)
Importance: Medium = Wishlist
Status: Needs Info = Confirmed
--
wifi-radar daemon (-d) ends
https://launchpad.net/bugs/64051
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Is this still an issue?
--
wifi-radar daemon (-d) ends
https://launchpad.net/bugs/64051
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have had similar problems, but I solved it when I identified the
interface in wifi-radar.conf. I put interface = eth1 and it works again.
--
wifi-radar daemon (-d) ends
https://launchpad.net/bugs/64051
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
U Sub, 14. {$Month}. 2006., u 19:39 +, Ahmed El-Mahmoudy je
napisao/la:
Now I don't get any errors when running wifi-radar -d, except for that
it does end, which makes me wonder: is wifi-radar -d designed to end
after the scan_timeout period ?
Yes, it ends after discovering wifi
I removed those lines:
mode = Managed
security = restricted
Now I don't get any errors when running wifi-radar -d, except for that
it does end, which makes me wonder: is wifi-radar -d designed to end
after the scan_timeout period ?
--
wifi-radar daemon (-d) ends
I tried today to run : sudo wifi-radar -d
AFTER the wifi connection is established manually (ie. I set the ESSID key of
the AP using iwconfig, and configured the andIP addresses using ifconfig
route), so I got this:
dhclient3 --version 21
Error for wireless request Set Frequency (8B04) :
SET
Please attach your /etc/wifi-radar.conf. I just noticed that your logs
don't show eth1 (I guess eth0 is wired interface). syslog would be nice
also, when wifi-radar fails to connect to AP. This:
down: error fetching interface information: Device not found
SIOCSIFNETMASK: No such device
SIOCADDRT:
Yes, eth0 is wired interface.
I just found that there is an paramater called interface in wifi-radar.conf,
I set it to eth1 and tried wifi-radar -d, and same thing it also ends, the only
difference is that it doesn't give any messages about lo,sit0,eth0 interfaces
being not wireless interfaces.
** Attachment added: wifi-radar.conf
http://librarian.launchpad.net/4704332/wifi-radar.conf
--
wifi-radar daemon (-d) ends
https://launchpad.net/bugs/64051
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
There's nothing in /var/log/messages regarding wireless when I run wifi-
radar.
I don't think that there is a problem with driver because I can
configure it manually.
--
wifi-radar daemon (-d) ends
https://launchpad.net/bugs/64051
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Well, does wifi-radar -d starts dhclient and creates a connection?
--
wifi-radar daemon (-d) ends
https://launchpad.net/bugs/64051
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I tried it once in existance of AP. It reported that it found the AP,
and reported an error about running dhclient, and then it ends.
When an AP does NOT exist, it also ends after a very short period.
--
wifi-radar daemon (-d) ends
https://launchpad.net/bugs/64051
--
ubuntu-bugs mailing list
Here are some logs:
no-ap: is in the absence of AP.
ap: is in the presence of an AP. (note that the essid of the AP is AP_ESSID)
The wifi interface is eth1.
In both cases dhclient is not running (I mean after the wifi-radar stopped,
dhclient is not running). But I noticed that dhcdbd is
** Attachment added: Log during absence of AP
http://librarian.launchpad.net/4702705/no-ap
--
wifi-radar daemon (-d) ends
https://launchpad.net/bugs/64051
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Your network card doesn't support scaning? What card is that? If your
card doesn't support scaning, wifi-radar can't autodetect which AP is
available.
--
wifi-radar daemon (-d) ends
https://launchpad.net/bugs/64051
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Does wifi-radar starts if you run it like client?
** Changed in: wifi-radar (Ubuntu)
Importance: Undecided = Medium
Status: Unconfirmed = Needs Info
--
wifi-radar daemon (-d) ends
https://launchpad.net/bugs/64051
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Yes, running sudo wifi-radar does start wifi-radar, and it doesn't end
like the daemon does.
--
wifi-radar daemon (-d) ends
https://launchpad.net/bugs/64051
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
18 matches
Mail list logo
