NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
GS108Ev3 refuses to connect
I have 4 GS108Ev3 switches. As they are all configured and working well I don't need to administer them often. Today I wanted to login to them - and can't. All 4 refuse to connect when I acces...
Here what Tailscale says about such issues:
Packet size limits can also cause connection problems on certain types of networks.
Tailscale uses a maximum transmission unit (MTU) of 1280. If there are other interfaces which might send a packet larger than this, those packets might get dropped silently. These can be verified by using tcpdump.
The limitation in your use case isn't (only) Tailscale.
It's much more the very simple IP stack "glued on" to the GS108Ev3, and many more Plus resp. Easy Smart switches not built in a real managed switch core, therefore not supporting PMTUD (Path MTU DIscovery), and not allowing MTU smaller but the default 1500.The ubiquitous ICMP Ping check not allowing fragmentation does show the effective path MTU limit
PS C:\> ping 10.10.1.176 -f -l 1472
Pinging 10.10.1.176 with 1472 bytes of data:
Reply from 10.10.1.176: bytes=1472 time=8ms TTL=64
Reply from 10.10.1.176: bytes=1472 time=2ms TTL=64
Reply from 10.10.1.176: bytes=1472 time=3ms TTL=64
Reply from 10.10.1.176: bytes=1472 time=3ms TTL=64
Ping statistics for 10.10.1.176:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 8ms, Average = 4ms
But beyond:
PS C:\> ping 10.10.1.176 -f -l 1473
Pinging 10.10.1.176 with 1473 bytes of data:
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Ping statistics for 10.10.1.176:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
This site can’t be reached
192.168.0.231 refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
Your home LAN is really on the 192.168.0.x/24 IP subnet?
What does
ipconfig
show on your computer?
Yes - my LAN is 192.168.0.X - that has not changed in years.
I read all about the default 192.168.0.239 address related to these switches so I moved the device that was on that address elsewhere to free it up, just in case.Ethernet adapter Main Ethernet:
Connection-specific DNS Suffix . : **redacted**
IPv4 Address. . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.254
Because these devices respond to ping (and I know it is them and not some spurious device because they stop when I cut their power), it seems clear to me that the subnet and address issues are not the problem. Why these devices refuse browser connections is what confuses me.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
