zhuravskiy / wl500g

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

DHCP issue with bridge mode #354

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Set on first router Operation Mode - Default Gateway
2. Set 2 other routers in Access Point and make bridge connection with main 
router.(Add 2 MAC address in Remote Bridge List)
3. It works fine, but some times (2-3 times in day) AP-routers cant working 
with DHCP requests from clients. If you try to connect near main router - all 
works perfect. But if you work with AP-routers - you cant take IP and as result 
- no Internet connection

What is the expected output? What do you see instead?
If i rebooting main router - problem will be solved, but after some time - it 
is come again. I dont know main reason for this problem

What version of the product are you using?
I have 3 routers ASUS RT-N16 and RT-N16-1.9.2.7-rtn-r4330.trx firmware on each 
device

Please, can you help me with this issue?
P.S. Sorry for my bad English :))

Original issue reported on code.google.com by St.Ing...@gmail.com on 18 Sep 2012 at 8:43

GoogleCodeExporter commented 8 years ago
Unfortunately, I can't build exact environment for tests.

Is DHCP server(dnsmasq) is up on gateway at problematic time? 

Are DHCP packets received on gateway? Try to sniff traffic - "tcpdump -i 
<lan_if> -nvvv -s 1500 port 67 or port 68"

Additionally you can try to read wl500g.info forum.

Original comment by lly.dev on 18 Sep 2012 at 10:46

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Well, here some additional information about config:
Main router have WAN address - 192.168.10.31, LAN address - 192.168.1.1, DHCP 
server (for wi-fi clients) with scope 192.168.1.2 - 192.168.10.254.
AP-routers have manualy assigned IP adresses - 192.168.1.2 and 192.168.1.3
When client connecting to router - routers give IP from correct scope. After 
few hours - clients can get IP only from main router, not from Repeaters 
(Routers in Access Point mode)

Yes, DHCP work fine on main router in any time.
Okey, great idea to shiff traffic!

Can i give you some logs or files, which can help?

Original comment by St.Ing...@gmail.com on 18 Sep 2012 at 11:53

GoogleCodeExporter commented 8 years ago
IP addresses are insignificant, problem might be, either in DHCP server, or 
Wi-Fi bridge itself. Unfortunately, Wi-Fi driver sources closed by Broadcom and 
we unable to change something in it. The only chance to fix problem - if it 
caused by some kernel bug or wrong tunable value.

Have you tried official firmware?

No, Wi-Fi driver write log message in case of it compiled in debug mode only.

Original comment by lly.dev on 19 Sep 2012 at 7:35

GoogleCodeExporter commented 8 years ago
I think, the common problem in bridge mode. Something gone wrong here ^)
Official firmware... I can try it, but i think best practice - use same 
firmware on all devices, not on single router. 
First of all - i will check network by tcpdump. 
And one more - i cant find solution, how to prepare cron service to reboot main 
router every hour or two.
Each howto's subscribe solution with additional device (USB disk or Flash 
drive, (mounting in /opt), but i cant use any additional devices in this 
routers.

i know, that firmware have crontab and crond files, but how to configure it - i 
dont know. Simple created file in crontabs with script command?...

Original comment by St.Ing...@gmail.com on 19 Sep 2012 at 9:53

GoogleCodeExporter commented 8 years ago
About cron - create crontab and put start of crond in post-boot script, nothing 
special. Try to read wl500g.info forum or use google.

Original comment by lly.dev on 3 Oct 2012 at 6:45

GoogleCodeExporter commented 8 years ago
Just one advice, You said:

DHCP server (for wi-fi clients) with scope 192.168.1.2 - 192.168.10.254.
AP-routers have manualy assigned IP adresses - 192.168.1.2 and 192.168.1.3.

Set DHCP scope range different so the ap-routers aren't within it. Could be a 
case when DHCP gives a client 192.168.1.2 which is in fact a ap-route ip.

Original comment by radoslaw...@gmail.com on 15 Oct 2012 at 11:13

GoogleCodeExporter commented 8 years ago
Ok, i will do this for sure!

At this moment i have cron task, which sending reboot signal for main router 
every 4 hours)

Original comment by St.Ing...@gmail.com on 15 Oct 2012 at 4:24

GoogleCodeExporter commented 8 years ago
Unreproducible

Original comment by lly.dev on 1 Jan 2013 at 2:39