Ernillew / wl500g

Automatically exported from code.google.com/p/wl500g
0 stars 0 forks source link

Unable to get WAN address by DHCP #362

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Hi. Sometimes my Asus WL500G Premium v2 detect IP incorrectly. I have static IP 
and enabled "Automatic IP" option. I tried 3 lastest firmware and no one fix 
this issuse. I don't think that it's my provider problem because when connect 
WAN cable to computer all is ok. And if return WAN cable to router again, it 
detect incorrect IP.

Original issue reported on code.google.com by mrDoctorWho on 15 Oct 2012 at 11:26

GoogleCodeExporter commented 9 years ago
please provide details, it's unclear what did you mean.

Original comment by themiron.ru on 15 Oct 2012 at 3:44

GoogleCodeExporter commented 9 years ago
What can i do?

Original comment by mrDoctorWho on 15 Oct 2012 at 3:55

GoogleCodeExporter commented 9 years ago
There are correct detection (1) and incorrect (2). 

Original comment by mrDoctorWho on 15 Oct 2012 at 4:04

Attachments:

GoogleCodeExporter commented 9 years ago
First of all, you must provide exact firmware version & syslog.log.

WL500gP V2 has not such strong transmitter as PC, so it might be bad Ethernet 
cable to ISP. There was many reports with similar problem. Easy can be check by 
any good external hub plugged in before router.

Original comment by lly.dev on 15 Oct 2012 at 6:19

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Firmware ver: 1.9.2.7-rtn-r4667. Maybe also it have many info for you:

(From PC that connected to router)
$ ping ya.ru
64 bytes from www.yandex.ru (93.158.134.203): icmp_req=36 ttl=49 time=73.1 ms
# all was is ok. Then address automatically switched to incorrect
From WL-E0CB4E89CF5C (192.168.1.1) icmp_seq=97 Destination Net Unreachable
From 169.254.9.82 icmp_seq=114 Destination Host Unreachable

I ask my provider for it. Of course, provider said "This is not our problem. 
Ask router/firmware developer". 

Original comment by mrDoctorWho on 16 Oct 2012 at 9:18

Attachments:

GoogleCodeExporter commented 9 years ago
Your ISP simply don't want to support router, it is your zone of 
responsibility. 

I see following line in syslog before problem:

 wan: disconnected manually (unit 0)

for which reason it was done? Are you understand what you are doing?

Probably your ISP has some "guard" interval for DHCP requests. If you repeat 
exactly the same action on your PC, you will give the same result.

P.S. Try to read wl500g.info forum, it contain many useful info on ASUS routers

Original comment by lly.dev on 16 Oct 2012 at 10:31

GoogleCodeExporter commented 9 years ago
> wan: disconnected manually (unit 0)
Cable was not unplugged. I tried to reconnect router to wan in web-interface 
when it got incorrect IP. It's helpful for some time.

Original comment by mrDoctorWho on 16 Oct 2012 at 10:35

GoogleCodeExporter commented 9 years ago
I can't see any sign of problem before following line:

 Oct 16 16:06:39 wan: disconnected manually (unit 0)

You must check IP on vlan1 & ping test before doing any "magic" actions.

"wrong" IP address 169.254.9.82 assigned in case of all attempts to get DHCP 
lease was failed. My guess still the same - bad WAN cable.

Original comment by lly.dev on 16 Oct 2012 at 4:33

GoogleCodeExporter commented 9 years ago
Roter still was on it place. If it dont moved and (maybe) cable broken, why it 
happens just sometimes? Also if really cable broken, why router get IP? I think 
that here should not be any connection.

Original comment by mrDoctorWho on 16 Oct 2012 at 4:38

GoogleCodeExporter commented 9 years ago
dhcp works on timeout basis.
that means once the lease is obtained for some time, before it expires, lease 
should be renewed. if at that time, dhcp server isn't accesible, and lease time 
has expired, ip address will be defaulted to 169.254.x.x/16 zero-conf one.

Original comment by themiron.ru on 17 Oct 2012 at 4:45

GoogleCodeExporter commented 9 years ago
Ok, thank you.

Original comment by mrDoctorWho on 17 Oct 2012 at 4:54

GoogleCodeExporter commented 9 years ago
broken hardware link

Original comment by lly.dev on 24 Oct 2012 at 5:15

GoogleCodeExporter commented 9 years ago
I think it's a firmware bug. I tried firmware WL500gpv2-1.9.2.7-d-r2624, there 
are all is ok! Ip detecting correctly. 

Original comment by mrDoctorWho on 1 May 2013 at 1:49