Cable Modem or Router Issue?
-
Yeah it's such an annoying issue. For me as a way to alleviate some of this, I'm using this script.
http://forum.pfsense.org/index.php/topic,17243.msg89348.html
It auto-renews the connection after it sense it's been down. The Cronjob runs every three minutes. However the wan issue will continue to persist. I'm gonna get intel nics to try for my pfsense sense they're currently on realtek. I never use to have this issue on 2.0, but then I decided to upgrade….
-
Well, I still can't really tell if it is definitely a router/pfsense issue, or something with the cable modem.
I plugged my old Linksys router/AP in last night and seemed to see the same problem with connectivity, but it doesn't have any logs to speak of and no way to really diagnose the problem. It does make me think that it's either a Comcast problem, or a cable modem problem. So if you know any way to troubleshoot who's at fault there (besides buying a new cable modem) let me know!
-
it makes no difference for me with intel NIC's as that is what I am using. Just for giggles to make sure it was certainly not my hardware, I used the live cd for zeroshell (I know, I know, I hate it too) and I have not lost a single packet through continuous testing over the last 8 hours. =/ I hate the zeroshell UI, and the stupid "Sorry we don't have an installer just use the live boot" crap, can we please get some love from pfsense?
-
This may be the case of modems causing NIC link to cycle rapidly, then our check_reload_status skipped doing anything with the NIC to prevent other problems. This was fixed very recently in 2.0.3 and 2.1.
-
@cmb:
This may be the case of modems causing NIC link to cycle rapidly, then our check_reload_status skipped doing anything with the NIC to prevent other problems. This was fixed very recently in 2.0.3 and 2.1.
I just tried with last nights build of 2.1beta because I read it may have a fix for https://redmine.pfsense.org/issues/2792 which another thread suggested was the cause. No luck
-
Would it matter in this case that pfSense is running in a VM? It has a 2 port Intel NIC dedicated to it, one NIC port on a virtual switch dedicated to the WAN, and another dedicated to the LAN.
-
Would it matter in this case that pfSense is running in a VM?
Depends on the hypervisor. If it cycles the virtual NIC's link when the physical NIC cycles link, then yes. Otherwise no.
-
I'm running ESXI 5.1.0 using the default drivers for the Intel card..
I'm mainly trying to find some way to prove the problem is with the cable modem or connection rather than the router.
-
Well I'm using a physical machine for the gateway, my Pfsense VM that I use to DMZ my VM's is on intel nics in ESXi 5.0u4 and doesn't have this problem. I do see the link cycle on the WAN side of the phys gateway though… which is linked directly to the modem for WAN. Now my question to you is.... Do you have a motorola modem? Mine is the squarish Docsis 3.0 Motorola Modem with VOIP. I think it is handling DHCP req's by cycling the link fast instead of re broadcasting. Is this common? Is that how its supposed to work? idk. I only got through CCNA 1 and that was before cable modems were a thing >_< Vmware and big Storage are all I know.
-
I do have a Motorola cable modem, the 6121 I believe.
I haven't seen any unusual activity on the ESXI machine, but maybe I can dig through the network logs some more.
The problem has been intermittent..it went back to normal about a day after I posted this and has been working fine ever since.