Internal routing stops when internet goes down
-
Yes it does. I've been doing some testing and I'm pretty sure the problem is my network switch. When I hard wire my laptop to the router I never lose the connection to the router. I'm ordering a new network switch and I will update the post with whether or not it fixed the issue. Thank you!
-
So your wan connection runs through your switch as well? Why would you switch have issues if wan goes down?
-
The WAN is connected directly to the router. Then another connection goes from the router to the switch. I'm not sure the switch is the issue but it is an older device and eliminating it seems to eliminate the issue.
-
Well that doesn't make any sense either to be honest..
-
Do you have a specific rule set up for internal routing? You can test this quickly with an any<->any rule on the LAN interface.
-
I did try that, thanks for the suggestion but it did fix the problem.
-
@johnpoz said in Internal routing stops when internet goes down:
Well that doesn't make any sense either to be honest..
I agree, I can't explain it but I can't argue with results. Today I replaced the old switch with a new brand name switch and I cannot reproduce the problem. (I've tried several times.)
-
Well then maybe just a flaky switch and coincidental? How would a switch have any idea your wan was up or down? It wouldn't.. Unless its some sort of managed/smart switch and need to talk to the mothership on the internet to work? What specific make and model switch was it?
-
It is a managed switch.(Not fully managed but it can do vlans and a few other things.) tp-link TL-SG108E version 4. I thought the same thing about it wanting to talk to the mothership but it didn't have problems when I created a rule to block the switch from the internet. I never even saw it trying to reach the internet. I've had this switch for years and haven't had issues until about a year ago.
-
@jhunt said in Internal routing stops when internet goes down:
tp-link TL-SG108E version 4
Is that one of the models that doesn't do VLANs properly?
-
@jhunt said in Internal routing stops when internet goes down:
I've had this switch for years and haven't had issues until about a year ago.
Look for a firmware update. Although it probably won't fix the issue.
-
Is that one of the models that doesn't do VLANs properly?
Could be? I use a few VLANs and they seemed to work fine. (unless the WAN was down)
-
@user_three said in Internal routing stops when internet goes down:
@jhunt said in Internal routing stops when internet goes down:
I've had this switch for years and haven't had issues until about a year ago.
Look for a firmware update. Although it probably won't fix the issue.
Thanks for the suggestion but I looked before I bought the new switch. The old switch was running the latest firmware. Although the firmware was a few years old.
-
@jhunt said in Internal routing stops when internet goes down:
tp-link TL-SG108E
Yeah those are those one that didn't do vlans correctly, wouldn't let you remove vlan 1. Then they came out with firmware fix for v3 but didn't list it for v2 or 1.. But now looks like they are on v5..
But with the way he described the connections, the wan doesn't even run through the switch as a vlan. So this switch would have no clue to if the wan is up or down, it would even know about it or care... It would be like your switch knowing if my line was up or down ;)
So unless there was some physical path of the wan through the switch, where it might see traffic or know if interface went down that caused a problem I really don't see how his wan status could have anything to do with traffic flowing through the switch. It just not possible. Unless it is checking if it can get to the internet in some way, and when that went down it had an issue.. Really seems unlikely.
But those switches are not very good anyway.. So not a big issue if taken out of the equation.
-
Certain models of TP-Link switches, including your don't handle VLANs properly, in that they allow multicasts to leak. There are apparently issues with VLAN 1 appearing on all VLANs. This may have been fixed with an update.
