2010-01-13 06:07:35     IP changed to 0.0.0.0 after router switched off

Document created by Aaronwu Employee on Aug 20, 2013
Version 1Show Document
  • View in full screen mode

2010-01-13 06:07:35     IP changed to 0.0.0.0 after router switched off

Karthikeyan Jeevanandam (INDIA)

Message: 84537   

 

Hi,

 

   My device is connected to an access point and it is running on the valid ip which is given by the access point(dhcp is enabled in the access point).When connected access point is switched off,after few secs(dhcp daemon time out period - 30 secs) my device ip is changed to 0.0.0.0.I'm sure that the wifi interface is up.When the same test is done using eth0 interface,after cable pull out device ip remains same as before the cable pulling out.

 

Note dhcp deamon is ran using the below command

 

dhcpcd -h - -t 30 <WLAN interface>

 

when the daemon is ran with infinite time parameter,for same usecase IP is not changed to 0.0.0.0

 

dhcpcd -h - -t  FFFFFFFF <wlan interface>

 

Kindly let me know why IP is changed to 0.0.0.0 in wireless mode when daemon is invoked for non-infinite time period.

 

 

QuoteReplyEditDelete

 

 

2010-01-18 08:36:10     Re: IP changed to 0.0.0.0 after router switched off

Karthikeyan Jeevanandam (INDIA)

Message: 84715   

 

This is very critical,please respond to this query.

QuoteReplyEditDelete

 

 

2010-01-18 10:03:06     Re: IP changed to 0.0.0.0 after router switched off

Robin Getz (UNITED STATES)

Message: 84718   

 

Karthikeyan:

 

Your questions has to do with Linux - and Linux userspace - nothing about it is blackfin specific. It is most likely that you will have the same issue on x86 on debian.

 

Questions like that get dumped down to the bottom of the list - to be answered when there is avalible time.

 

If that isn't acceptable to you - you should hire a professional Linux developer.

 

-Robin

QuoteReplyEditDelete

 

 

2010-01-18 18:44:12     Re: IP changed to 0.0.0.0 after router switched off

Mike Frysinger (UNITED STATES)

Message: 84725   

 

i'd also point out that you seem to have already found a simple workaround ... use it

Attachments

    Outcomes