Error WAN
Good evening,
after changing the Internet line and then IP, after changing the parameters of the old WAN now the Line navigates but very slowly.
If I connect the PC directly to the router it works perfectly.
If I connect the router to another firewall with the same configuration it works perfectly.
Any solution?
All Replies
-
Hi @neilos2015
Can you try to ping to device gateway or google DNS 8.8.8.8 from ATP/USG, is it stable to access Internet from ATP/USG?
Also, could you share more information about “slowly”? How did you test it? and what is your expected result and actual result.
Go to “MAINTENANCE > Network Tool > PING IPv4”
0 -
# ping 8.8.8.8 -n -c 3 -I eth0 -c 30
PING 8.8.8.8 (8.8.8.8) from 217.59.184.154 eth0: 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=53 time=23.8 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=53 time=23.6 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=53 time=23.9 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=53 time=24.1 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=53 time=23.9 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=53 time=23.7 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=53 time=23.6 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=53 time=23.8 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=53 time=24.2 ms
64 bytes from 8.8.8.8: icmp_seq=11 ttl=53 time=23.7 ms
64 bytes from 8.8.8.8: icmp_seq=12 ttl=53 time=24.1 ms
64 bytes from 8.8.8.8: icmp_seq=13 ttl=53 time=23.6 ms
64 bytes from 8.8.8.8: icmp_seq=14 ttl=53 time=23.9 ms
64 bytes from 8.8.8.8: icmp_seq=15 ttl=53 time=23.9 ms
64 bytes from 8.8.8.8: icmp_seq=16 ttl=53 time=24.0 ms
64 bytes from 8.8.8.8: icmp_seq=17 ttl=53 time=23.6 ms
64 bytes from 8.8.8.8: icmp_seq=18 ttl=53 time=23.9 ms
64 bytes from 8.8.8.8: icmp_seq=19 ttl=53 time=23.9 ms
64 bytes from 8.8.8.8: icmp_seq=20 ttl=53 time=24.0 ms
64 bytes from 8.8.8.8: icmp_seq=21 ttl=53 time=23.8 ms
64 bytes from 8.8.8.8: icmp_seq=22 ttl=53 time=23.6 ms
64 bytes from 8.8.8.8: icmp_seq=23 ttl=53 time=23.6 ms
64 bytes from 8.8.8.8: icmp_seq=24 ttl=53 time=23.6 ms
64 bytes from 8.8.8.8: icmp_seq=25 ttl=53 time=24.1 ms
64 bytes from 8.8.8.8: icmp_seq=26 ttl=53 time=23.8 ms
64 bytes from 8.8.8.8: icmp_seq=27 ttl=53 time=23.7 ms
64 bytes from 8.8.8.8: icmp_seq=28 ttl=53 time=23.9 ms
64 bytes from 8.8.8.8: icmp_seq=29 ttl=53 time=23.8 ms
64 bytes from 8.8.8.8: icmp_seq=30 ttl=53 time=24.3 ms
--- 8.8.8.8 ping statistics ---
30 packets transmitted, 29 received, 3% packet loss, time 29040ms
rtt min/avg/max/mdev = 23.607/23.891/24.349/0.213 ms
0 -
This is Now!
This is how it should be
0 -
Hi @neilos2015
After we capture packets from device wan interface, we can see many dup ack, packets re transmit, TCP handshake fail in packets trace.
Issue was gone by putting a switch between patch panel and USG. It is fine now.
It looks like there are some kind of interoperability between the patch panel and USG WAN.
0
Categories
- All Categories
- 415 Beta Program
- 2.4K Nebula
- 151 Nebula Ideas
- 98 Nebula Status and Incidents
- 5.7K Security
- 277 USG FLEX H Series
- 277 Security Ideas
- 1.4K Switch
- 74 Switch Ideas
- 1.1K Wireless
- 42 Wireless Ideas
- 6.4K Consumer Product
- 250 Service & License
- 395 News and Release
- 85 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.6K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 85 About Community
- 75 Security Highlight