Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


NaNaNaNathan

8 posts

Wannabe Geek


#177188 25-Jul-2015 18:43
Send private message

Hi 

I have a strange problem since moving from Vodafone to TrustPower ADSL with my previous configuration working flawlessly.

My symptoms are that with my new TrustPower-supplied desktop wired to the ADSL router (Netcomm NB604N-NZ) I have no problems connecting to and surfing the web
PC wired to Netcomm

If I plug in my Linksys EA6500 (running as a WAP in bridge mode dishing our addresses via DHCP in a separate subset to the DSL router) into one of the Netcomm LAN ports, after about two minutes the internet on my wired PC (and WiFi devices slows to a halt. See below for a trace route to www.google.com from my wired PC. You'll see it's flying along nicely @ ~22ms and it starts slowing at about the 130th ping iteration and then times out
Linksys plugged into Netcomm LAN port

Reply from 131.203.2.42: bytes=32 time=22ms TTL=59
Reply from 131.203.2.42: bytes=32 time=24ms TTL=59
Reply from 131.203.2.42: bytes=32 time=24ms TTL=59
Reply from 131.203.2.42: bytes=32 time=23ms TTL=59
Reply from 131.203.2.42: bytes=32 time=23ms TTL=59
Reply from 131.203.2.42: bytes=32 time=43ms TTL=59
Reply from 131.203.2.42: bytes=32 time=56ms TTL=59
Reply from 131.203.2.42: bytes=32 time=25ms TTL=59
Reply from 131.203.2.42: bytes=32 time=25ms TTL=59
Reply from 131.203.2.42: bytes=32 time=56ms TTL=59
Reply from 131.203.2.42: bytes=32 time=49ms TTL=59
Reply from 131.203.2.42: bytes=32 time=24ms TTL=59
Reply from 131.203.2.42: bytes=32 time=23ms TTL=59
Reply from 131.203.2.42: bytes=32 time=22ms TTL=59
Reply from 131.203.2.42: bytes=32 time=23ms TTL=59
Reply from 131.203.2.42: bytes=32 time=22ms TTL=59
Reply from 131.203.2.42: bytes=32 time=26ms TTL=59
Reply from 131.203.2.42: bytes=32 time=35ms TTL=59
Reply from 131.203.2.42: bytes=32 time=75ms TTL=59
Reply from 131.203.2.42: bytes=32 time=23ms TTL=59
Reply from 131.203.2.42: bytes=32 time=391ms TTL=59
Reply from 131.203.2.42: bytes=32 time=865ms TTL=59
Reply from 131.203.2.42: bytes=32 time=636ms TTL=59
Reply from 131.203.2.42: bytes=32 time=640ms TTL=59
Reply from 131.203.2.42: bytes=32 time=894ms TTL=59
Reply from 131.203.2.42: bytes=32 time=1055ms TTL=59
Reply from 131.203.2.42: bytes=32 time=1348ms TTL=59
Reply from 131.203.2.42: bytes=32 time=1713ms TTL=59
Reply from 131.203.2.42: bytes=32 time=2281ms TTL=59
Reply from 131.203.2.42: bytes=32 time=2995ms TTL=59
Reply from 131.203.2.42: bytes=32 time=3759ms TTL=59
Request timed out.

Ping statistics for 131.203.2.42:
Packets: Sent = 140, Received = 139, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 3759ms, Average = 142ms

I also have a Yealink W52P VOIP handset and similar behavior occurs plugged into the Netcomm with or without the Linksys.

I have not changed the config on the Linksys or the Yealink. The Netcomm is out of the box as per TrustPower's supply. 
What is strange is I cant ping the 'external' interface of the WAP (the Netcomm side) but I can see the Netcomm DHCP server has successfully dished out an IP address.

I'm beginning to this I should give both the VOIP handset and the WAP static IP addresses. Other than that, any clues?

thanks in advance!

Create new topic
NaNaNaNathan

8 posts

Wannabe Geek


  #1351723 25-Jul-2015 20:48
Send private message

Update: My Yealink is now working after a factory reset. Linksys still misbehaving although I have some more evidence

Having a look at the pings below. The latency increases when I turn the WiFi on on my Samsung Galaxy S5 which then automatically connects to the SSID configured on the Linksys. Turning it off again corrects this. 

Reply from 131.203.2.19: bytes=32 time=22ms TTL=59
Reply from 131.203.2.19: bytes=32 time=23ms TTL=59
Reply from 131.203.2.19: bytes=32 time=23ms TTL=59
Reply from 131.203.2.19: bytes=32 time=24ms TTL=59
Reply from 131.203.2.19: bytes=32 time=23ms TTL=59
Reply from 131.203.2.19: bytes=32 time=48ms TTL=59
Reply from 131.203.2.19: bytes=32 time=36ms TTL=59
Reply from 131.203.2.19: bytes=32 time=125ms TTL=59
Reply from 131.203.2.19: bytes=32 time=22ms TTL=59
Reply from 131.203.2.19: bytes=32 time=22ms TTL=59
Reply from 131.203.2.19: bytes=32 time=651ms TTL=59
Reply from 131.203.2.19: bytes=32 time=887ms TTL=59
Reply from 131.203.2.19: bytes=32 time=928ms TTL=59
Reply from 131.203.2.19: bytes=32 time=1007ms TTL=59
Reply from 131.203.2.19: bytes=32 time=1150ms TTL=59
Reply from 131.203.2.19: bytes=32 time=1391ms TTL=59
Reply from 131.203.2.19: bytes=32 time=1678ms TTL=59
Reply from 131.203.2.19: bytes=32 time=2051ms TTL=59
Reply from 131.203.2.19: bytes=32 time=2615ms TTL=59
Reply from 131.203.2.19: bytes=32 time=3094ms TTL=59
Request timed out.
Reply from 131.203.2.19: bytes=32 time=1463ms TTL=59
Reply from 131.203.2.19: bytes=32 time=22ms TTL=59
Reply from 131.203.2.19: bytes=32 time=23ms TTL=59
Reply from 131.203.2.19: bytes=32 time=24ms TTL=59

Then I turned WiFi back on my S5 and it worked fine.

Then I tried to access the IP address of the Linksys via Chrome browser and this happened below. Total loss of internet via wired PC/ This time I have to disconnect the Linksys from the Netcomm to get internet back.

Reply from 131.203.2.44: bytes=32 time=3669ms TTL=59
Reply from 131.203.2.44: bytes=32 time=48ms TTL=59
Reply from 131.203.2.44: bytes=32 time=30ms TTL=59
Reply from 131.203.2.44: bytes=32 time=22ms TTL=59
Reply from 131.203.2.44: bytes=32 time=23ms TTL=59
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 131.203.2.44: bytes=32 time=3525ms TTL=59
Reply from 131.203.2.44: bytes=32 time=732ms TTL=59
Reply from 131.203.2.44: bytes=32 time=22ms TTL=59
Reply from 131.203.2.44: bytes=32 time=23ms TTL=59
Reply from 131.203.2.44: bytes=32 time=22ms TTL=59
Reply from 131.203.2.44: bytes=32 time=23ms TTL=59
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 131.203.2.44: bytes=32 time=914ms TTL=59
Reply from 131.203.2.44: bytes=32 time=22ms TTL=59
Reply from 131.203.2.44: bytes=32 time=23ms TTL=59
Reply from 131.203.2.44: bytes=32 time=23ms TTL=59
Reply from 131.203.2.44: bytes=32 time=23ms TTL=59
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.





mikesmac
17 posts

Geek


  #1351769 25-Jul-2015 23:35
Send private message

My guess is that your wap is also running dhcp on the interface connected to the netcomm router. Is there any reason why you are running dhcp on the linksys?

sbiddle
30853 posts

Uber Geek

Retired Mod
Trusted
Biddle Corp
Lifetime subscriber

  #1351816 26-Jul-2015 09:34
Send private message

I don't quite understand why you want a double NAT setup like that.




NaNaNaNathan

8 posts

Wannabe Geek


  #1354319 29-Jul-2015 12:20
Send private message

What I did to solve it was ditch the Netcomm and now use a Dreytek 130. It worked fine out of the box. I also have the WAPs no longer running DGCP. In doing sso I lose some of the management functionality of the Linksys WAPs. Ho hum...

Create new topic





News and reviews »

Air New Zealand Starts AI adoption with OpenAI
Posted 24-Jul-2025 16:00


eero Pro 7 Review
Posted 23-Jul-2025 12:07


BeeStation Plus Review
Posted 21-Jul-2025 14:21


eero Unveils New Wi-Fi 7 Products in New Zealand
Posted 21-Jul-2025 00:01


WiZ Introduces HDMI Sync Box and other Light Devices
Posted 20-Jul-2025 17:32


RedShield Enhances DDoS and Bot Attack Protection
Posted 20-Jul-2025 17:26


Seagate Ships 30TB Drives
Posted 17-Jul-2025 11:24


Oclean AirPump A10 Water Flosser Review
Posted 13-Jul-2025 11:05


Samsung Galaxy Z Fold7: Raising the Bar for Smartphones
Posted 10-Jul-2025 02:01


Samsung Galaxy Z Flip7 Brings New Edge-To-Edge FlexWindow
Posted 10-Jul-2025 02:01


Epson Launches New AM-C550Z WorkForce Enterprise printer
Posted 9-Jul-2025 18:22


Samsung Releases Smart Monitor M9
Posted 9-Jul-2025 17:46


Nearly Half of Older Kiwis Still Write their Passwords on Paper
Posted 9-Jul-2025 08:42


D-Link 4G+ Cat6 Wi-Fi 6 DWR-933M Mobile Hotspot Review
Posted 1-Jul-2025 11:34


Oppo A5 Series Launches With New Levels of Durability
Posted 30-Jun-2025 10:15









Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.