LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Wireless Networking (http://www.linuxquestions.org/questions/linux-wireless-networking-41/)
-   -   Neat : After wireless Active, it become Inactive Again (http://www.linuxquestions.org/questions/linux-wireless-networking-41/neat-after-wireless-active-it-become-inactive-again-552147/)

yteckong 05-08-2007 12:14 AM

Neat : After wireless Active, it become Inactive Again
 
Hi guys,

I have this problem where I have done all the iwconfig to connect to a router, the Wireless Device in Network Configuration becomes Active but inexplicably got turned off after a few seconds.

I have been able to connect to Router without problem before this.

The commands that I used are
1. iwconfig eth1 essid "network-name"
2. iwconfig eth1 channel number
3. dhclient eth1

After the first set of this commands, subsequent tries, I will make sure that I do a killall dhclient, to turn off any dhclient (found that dhclient will interfere with subsequent re-tries)

Please advise on how to solve this interface become Inactive after activer for a few seconds.

Teck Ong

deadeyes 05-08-2007 01:08 AM

Quote:

Originally Posted by yteckong
Hi guys,

I have this problem where I have done all the iwconfig to connect to a router, the Wireless Device in Network Configuration becomes Active but inexplicably got turned off after a few seconds.

I have been able to connect to Router without problem before this.

The commands that I used are
1. iwconfig eth1 essid "network-name"
2. iwconfig eth1 channel number
3. dhclient eth1

After the first set of this commands, subsequent tries, I will make sure that I do a killall dhclient, to turn off any dhclient (found that dhclient will interfere with subsequent re-tries)

Please advise on how to solve this interface become Inactive after activer for a few seconds.

Teck Ong

Look if you can scan the network.
iwlist [interface] scanning

Be sure your wireless card is working ok.
If you type ifconfig (without -a option) is it in the list?
What is your wireless device?

yteckong 05-08-2007 02:21 AM

Look if you can scan the network.
iwlist [interface] scanning

Be sure your wireless card is working ok.
If you type ifconfig (without -a option) is it in the list?
What is your wireless device?


I have done iwlist eth1 scanning. It s able to scan the network.

with ifconfig, my eth1 is also in the list.

I am using Intel Pro 2200 wireless card

deadeyes 05-09-2007 01:23 AM

Quote:

Originally Posted by yteckong
Look if you can scan the network.
iwlist [interface] scanning

Be sure your wireless card is working ok.
If you type ifconfig (without -a option) is it in the list?
What is your wireless device?


I have done iwlist eth1 scanning. It s able to scan the network.

with ifconfig, my eth1 is also in the list.

I am using Intel Pro 2200 wireless card

Then I think it has to do with the configuration.iwconfig

Did you do the following before doing the other commands? (I am not sure if this is absolutely possible)
iwconfig wlan0 mode Managed


Do you use encryption?
WEP or WAP?

First setup your wireless access point so it uses no encryption at all and try to connect.

then re-enable your encryption.

Is there anything in your syslog? (tail /var/log/syslog)
or in dmesg (just type "dmesg" at console).
or in the messages (tail /var/log/messages)
Look if there is in any of those files something that could be to do with your problem.

You say it is active for a few seconds... Do you mean you can a few seconds ping the router or something else?

And what distro do you use?
Probably there is already a nice howto

yteckong 05-09-2007 07:00 AM

Quote:

Originally Posted by deadeyes
Then I think it has to do with the configuration.iwconfig

Did you do the following before doing the other commands? (I am not sure if this is absolutely possible)
iwconfig wlan0 mode Managed


Do you use encryption?
WEP or WAP?

First setup your wireless access point so it uses no encryption at all and try to connect.

then re-enable your encryption.

Is there anything in your syslog? (tail /var/log/syslog)
or in dmesg (just type "dmesg" at console).
or in the messages (tail /var/log/messages)
Look if there is in any of those files something that could be to do with your problem.

You say it is active for a few seconds... Do you mean you can a few seconds ping the router or something else?

And what distro do you use?
Probably there is already a nice howto

Hi,

I attach the message that I got below:-

May 9 19:40:01 localhost dhclient: Internet Systems Consortium DHCP Client V3.0.5-RedHat
May 9 19:40:01 localhost dhclient: Copyright 2004-2006 Internet Systems Consortium.
May 9 19:40:01 localhost dhclient: All rights reserved.
May 9 19:40:01 localhost dhclient: For info, please visit
May 9 19:40:01 localhost dhclient:
May 9 19:40:01 localhost dhclient: Listening on LPF/eth1/00:0e:35:34:e2:2a
May 9 19:40:01 localhost dhclient: Sending on LPF/eth1/00:0e:35:34:e2:2a
May 9 19:40:01 localhost dhclient: Sending on Socket/fallback
May 9 19:40:01 localhost dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67
May 9 19:40:03 localhost avahi-daemon[2881]: New relevant interface eth1.IPv6 for mDNS.
May 9 19:40:03 localhost avahi-daemon[2881]: Joining mDNS multicast group on interface eth1.IPv6 with address fe80::20e:35ff:fe34:e22a.
May 9 19:40:03 localhost avahi-daemon[2881]: Registering new address record for fe80::20e:35ff:fe34:e22a on eth1.
May 9 19:40:09 localhost dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67
May 9 19:40:28 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
May 9 19:40:34 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 21
May 9 19:40:55 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 20
May 9 19:41:15 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
May 9 19:41:22 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
May 9 19:41:29 localhost dhclient: No DHCPOFFERS received.
May 9 19:41:29 localhost dhclient: Trying recorded lease 172.16.0.18
May 9 19:41:29 localhost kernel: audit(1178710889.075:28): avc: denied { search } for pid=4004 comm="ping" name="locale" dev=dm-0 ino=2777138 scontext=user_u:system_r:ping_t:s0 tcontext=system_u:object_r:locale_t:s0 tclass=dir
May 9 19:41:29 localhost kernel: audit(1178710889.075:29): avc: denied { search } for pid=4004 comm="ping" name="locale" dev=dm-0 ino=2777178 scontext=user_u:system_r:ping_t:s0 tcontext=system_u:object_r:locale_t:s0 tclass=dir
May 9 19:41:29 localhost kernel: audit(1178710889.075:33): avc: denied { search } for pid=4004 comm="ping" name="locale" dev=dm-0 ino=2777138 scontext=user_u:system_r:ping_t:s0 tcontext=system_u:object_r:locale_t:s0 tclass=dir
May 9 19:41:29 localhost kernel: audit(1178710889.075:34): avc: denied { search } for pid=4004 comm="ping" name="locale" dev=dm-0 ino=2777138 scontext=user_u:system_r:ping_t:s0 tcontext=system_u:object_r:locale_t:s0 tclass=dir
May 9 19:41:29 localhost kernel: audit(1178710889.075:35): avc: denied { search } for pid=4004 comm="ping" name="locale" dev=dm-0 ino=2777138 scontext=user_u:system_r:ping_t:s0 tcontext=system_u:object_r:locale_t:s0 tclass=dir
May 9 19:41:29 localhost avahi-daemon[2881]: New relevant interface eth1.IPv4 for mDNS.
May 9 19:41:29 localhost avahi-daemon[2881]: Joining mDNS multicast group on interface eth1.IPv4 with address 172.16.0.18.
May 9 19:41:29 localhost avahi-daemon[2881]: Registering new address record for 172.16.0.18 on eth1.
May 9 19:41:29 localhost avahi-daemon[2881]: Withdrawing address record for 172.16.0.18 on eth1.
May 9 19:41:29 localhost avahi-daemon[2881]: Leaving mDNS multicast group on interface eth1.IPv4 with address 172.16.0.18.
May 9 19:41:29 localhost avahi-daemon[2881]: iface.c: interface_mdns_mcast_join() called but no local address available.
May 9 19:41:29 localhost avahi-daemon[2881]: Interface eth1.IPv4 no longer relevant for mDNS.
May 9 19:41:29 localhost avahi-daemon[2881]: New relevant interface eth1.IPv4 for mDNS.
May 9 19:41:29 localhost avahi-daemon[2881]: Joining mDNS multicast group on interface eth1.IPv4 with address 172.16.0.18.
May 9 19:41:29 localhost avahi-daemon[2881]: Registering new address record for 172.16.0.18 on eth1.
May 9 19:41:32 localhost avahi-daemon[2881]: Withdrawing address record for 172.16.0.18 on eth1.
May 9 19:41:32 localhost avahi-daemon[2881]: Leaving mDNS multicast group on interface eth1.IPv4 with address 172.16.0.18.
May 9 19:41:32 localhost avahi-daemon[2881]: iface.c: interface_mdns_mcast_join() called but no local address available.
May 9 19:41:32 localhost avahi-daemon[2881]: Interface eth1.IPv4 no longer relevant for mDNS.
May 9 19:41:32 localhost avahi-daemon[2881]: Interface eth1.IPv6 no longer relevant for mDNS.
May 9 19:41:32 localhost avahi-daemon[2881]: Leaving mDNS multicast group on interface eth1.IPv6 with address fe80::20e:35ff:fe34:e22a.
May 9 19:41:32 localhost avahi-daemon[2881]: Withdrawing address record for fe80::20e:35ff:fe34:e22a on eth1.
May 9 19:41:32 localhost dhclient: No working leases in persistent database - sleeping.
May 9 19:41:32 localhost dhclient: receive_packet failed on eth1: Network is down


Can you advise on what went wrong?

Thanks.

TEck ONg


All times are GMT -5. The time now is 05:42 AM.