wireless network is freezing sometime, IP 0.0.0.0

[mirceadobre78]

Hi guys,

I setup a network of routers and sometime (1-2 times every day) the network is failing. Sometime you cannot access nothing, sometime I am getting IP 0.0.0.0 on my phone's network connection. See attached the diagram of the network.
Oh, the connection is ADSL, ISP Dynamic IP, main router is a Movistar Peru (Askey), routers 2 and 3 TP Link 801ND, router Floor5 is a D-Link (kind of old version).
Sometime I add a Switch in between Switch 1 and Floor5 router. Same story. Working some time, then it freezes.

See URL of the diagram's network.
http://

Thanks,

 

[aligwashington]

so let me understand you have 3 wifi router that you are trying to use as AP on a network, not going to go into details as all routers are different models, first on main router you will set DHCP scope excluding all static IP addresses including 3 routers that you want to use as AP so lets say DHCP scope will be 192.168.1.11-254 with subnet 255.255.255.0 now you configure the routers with different SSID for different zones floor1, floor2 , floor3 and give it WAP now disable DHCP on all the 3 routers which you need to use as AP you will not connect the AP routers WAN ports but use the LAN port to connect it to the switch which is connected to the main router you should be all set at this point.

 

[slyverine]

What i can do is to suggest you a better network topology, which has less failure points and you can troubleshoot easier. Replace 1.2 , 1.3 ,1.4 routers with access points. Where router 1.4 is use another switch so you can connect your card things,cctv and pc.

 

[mirceadobre78]

Hi,

Thanks for all your answers. Should explain it better I guess.
Yes, the routers are set as AP. I change the login class as of 192.168.1.... because the original it was 192.168.0.254. The main router it's on class 192.168.1.1.
For thsi I set as 192.168.1.2 (admin login), ...1.3 and ...1.4.
Then I disable DHCP and let the main router as DHCP Enable to give the IP's to each connection.
The DVR is using 192.168.1.10 and Visa 192.168.1.50.
The range of DHCP starts 192.168.1.100-199.
The AP's are wired connected.
On router 4 I use LAN connection and not WAN (because DHCP is disabled). The routers 2 and 3 are AP, wired on the only available port (Ethernet). It's a TP-Link TL-WA801ND.

Thanks,

 

[aligwashington]

if all connected as you are telling you should not have this problem unless you are suing same SSID across the network and they are overlapping and are using same channels

 

[RealBeast]

From your network map it should work if you have it all set up properly.

Do you have the static addresses of the APs set outside the main router (.1.1) DHCP range to prevent dynamic assignment to a static address?

Also, how many users in total are you supporting with the main router DHCP and do you have sufficient DHCP range allotted?

And for all the APs do you use the 1.1 address for your DNS? For some ISPs it seems to work better to use the Google public DNS at 8.8.8.8 and 8.8.4.4.

I know that my ISP DNS sucks and using Google is a big improvement.

 

[mirceadobre78]

From your network map it should work if you have it all set up properly.

Do you have the static addresses of the APs set outside the main router (.1.1) DHCP range to prevent dynamic assignment to a static address?

Also, how many users in total are you supporting with the main router DHCP and do you have sufficient DHCP range allotted?

And for all the APs do you use the 1.1 address for your DNS? For some ISPs it seems to work better to use the Google public DNS at 8.8.8.8 and 8.8.4.4.

I know that my ISP DNS sucks and using Google is a big improvement.

The APs are set 1.2, 1.3 and 1.4. The main router its 1.1. The range from the main router starts at 1.15. Now, considering that the main router was a ISP one, cheapy, I just change the main router to a ADSL Router TP Link (TD-W8961N). Faster user connections yes, but still last night the red got freezing.
Usually we have around 10-15 users connected to the red.

Do you think maybe one of the APs might suck? I already change the main router, maybe I will go for APs as well.
Oh, I check the cables with a tester and all looks fine. The 2 computers that connects to the red I put them on a static IP accrding to DHCP assign to them.

Thanks,

 

[aligwashington]

you need to check one at a time if network goes down, first the main router then the switch then each AP its most likely either the router or the switch, also look at the traffic and see whats going might be a station issuing mass ARP and flooding the network.

 

[mirceadobre78]

you need to check one at a time if network goes down, first the main router then the switch then each AP its most likely either the router or the switch, also look at the traffic and see whats going might be a station issuing mass ARP and flooding the network.

Hmmm, good point. Didn't check for flooding the network. Maybe one of the compu's it's flooding the network. I will look into that today.

Thanks,

 

[RealBeast]

If you are using all the same SSID, the stupid devices may all be connecting to one AP -- or at least too many. Yes, and you need to analyzed the traffic from each device.

 

[mirceadobre78]

If you are using all the same SSID, the stupid devices may all be connecting to one AP -- or at least too many. Yes, and you need to analyzed the traffic from each device.

Nop, all the AP's have different SSID's. One it's called "Hotel San Francisco INN 1", "Hotel San Francisco INN 2", "Hotel San Francisco INN 4" and "dobre". The last SSID has different password encription than the others. Should be this causing an issue?
I unplug from the internet one computer that I am suspecting might be infected. It doesn't behave
as might be infected, but many people access it, usb's, phone;s connected, etc.

Thanks

 

[RealBeast]

If you are using all the same SSID, the stupid devices may all be connecting to one AP -- or at least too many. Yes, and you need to analyzed the traffic from each device.

Nop, all the AP's have different SSID's. One it's called "Hotel San Francisco INN 1", "Hotel San Francisco INN 2", "Hotel San Francisco INN 4" and "dobre". The last SSID has different password encription than the others. Should be this causing an issue?
I unplug from the internet one computer that I am suspecting might be infected. It doesn't behave
as might be infected, but many people access it, usb's, phone;s connected, etc.

Thanks

No a different password is not an issue. The connection that may be infected could be the problem -- it would be using more bandwidth than the AP can handle and that would cause similar problems do disconnection is a good idea.

 

[aligwashington]

if its a hospitality network you might wanna use MIMO AP with dual band as you can't stop users or check every user device also you need to use business class equipment as your normal AP can only handle 3-4 devices and business class usually have a better processor where most can handle 15-50 devices at a time.Other benefit will be to have bandwidth cap per device,station isolation and Vlan tagging etc,
I manage many hotel networks with different typologies massive deployments like 16-20 AP per site so can tell you from experience its not an easy thing to manage them with consumer grade equipment.

 

[mirceadobre78]

Hi guys,

From the logs of the router I have some errors. Check this out if somebody knows what means:
"dns2str too long"
Looking into routers logs and this is showing:

1/1/2000 0:0:45> Quick bridge not allow multi-channel
1/1/2000 0:0:45> bridge only stop
1/1/2000 0:0:45> SNMP TRAP 3: link up
1/1/2000 0:0:45> Quick bridge not allow multi-channel
1/1/2000 0:0:45> bridge only stop
1/1/2000 0:0:45> SNMP TRAP 3: link up
1/1/2000 0:0:45> Quick bridge not allow multi-channel
1/1/2000 0:0:45> bridge only stop
1/1/2000 0:0:45> SNMP TRAP 3: link up
1/1/2000 0:0:45> PPPoE: Recieve PADT
1/1/2000 0:0:46> PPPoE: Send PADI
1/1/2000 0:0:46> PPPoE: Recieve PADO
1/1/2000 0:0:46> PPPoE: Send PADR
1/1/2000 0:0:46> PPPoE: Recieve PADS
1/1/2000 0:0:47> PAP Authentication Successful
1/1/2000 0:0:47> ppp_ready: ch:804dc904, iface:8040098c
1/1/2000 0:0:47> PPP get IP Address:190.238.145.134
1/1/2000 0:0:47> PPP gateway:192.168.33.8
1/1/2000 0:0:47> PPP subnetmask:255.255.255.255
1/1/2000 0:0:47> PPP primary DNS:200.48.225.130
1/1/2000 0:0:47> PPP secondary DNS:200.48.225.146
1/1/2000 0:0:47> SNMP TRAP 3: link up
1/1/2000 0:0:47> Accept() fail
1/1/2000 0:1:6> Last errorlog repeat 1 Times
1/1/2000 0:1:6> sending request to NTP server(45)
1/1/2000 0:1:6> received from NTP server(45)
6/1/2017 14:52:31> Adjust time to 59302a2f
6/1/2017 14:52:31> adjtime task pause 1 day

 

[aligwashington]

Hi guys,

From the logs of the router I have some errors. Check this out if somebody knows what means:
"dns2str too long"
Looking into routers logs and this is showing:

1/1/2000 0:0:45> Quick bridge not allow multi-channel
1/1/2000 0:0:45> bridge only stop
1/1/2000 0:0:45> SNMP TRAP 3: link up
1/1/2000 0:0:45> Quick bridge not allow multi-channel
1/1/2000 0:0:45> bridge only stop
1/1/2000 0:0:45> SNMP TRAP 3: link up
1/1/2000 0:0:45> Quick bridge not allow multi-channel
1/1/2000 0:0:45> bridge only stop
1/1/2000 0:0:45> SNMP TRAP 3: link up
1/1/2000 0:0:45> PPPoE: Recieve PADT
1/1/2000 0:0:46> PPPoE: Send PADI
1/1/2000 0:0:46> PPPoE: Recieve PADO
1/1/2000 0:0:46> PPPoE: Send PADR
1/1/2000 0:0:46> PPPoE: Recieve PADS
1/1/2000 0:0:47> PAP Authentication Successful
1/1/2000 0:0:47> ppp_ready: ch:804dc904, iface:8040098c
1/1/2000 0:0:47> PPP get IP Address:190.238.145.134
1/1/2000 0:0:47> PPP gateway:192.168.33.8
1/1/2000 0:0:47> PPP subnetmask:255.255.255.255
1/1/2000 0:0:47> PPP primary DNS:200.48.225.130
1/1/2000 0:0:47> PPP secondary DNS:200.48.225.146
1/1/2000 0:0:47> SNMP TRAP 3: link up
1/1/2000 0:0:47> Accept() fail
1/1/2000 0:1:6> Last errorlog repeat 1 Times
1/1/2000 0:1:6> sending request to NTP server(45)
1/1/2000 0:1:6> received from NTP server(45)
6/1/2017 14:52:31> Adjust time to 59302a2f
6/1/2017 14:52:31> adjtime task pause 1 day

This is just basic authentication on dsl /adsl router via PPP any error will result in no internet not a 0.0.0.0 IP to a lan device.