Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 5 subscribers
  • Views 7028 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

All traffic stopped flowing after 5 day Mediacom outage

EddieRock

We had a verified connectivity issue with Mediacom (called Mediacom and they couldn't ping my router) that lasted 5 days. After we restored connectivity, the UTM won't allow any traffic through. No DNS, ping (to 8.8.8.8) or anything. I can log into it and check logs and everything. Multiple reboots haven't fixed it. I noticed that when I reboot now, the local console login screen comes up but it takes somewhere like 5 minutes till I hear the 4 beeps and I can log in.

I do see some events where rule 60011 is blocking traffic but I can't see where the NAT or masquerading rules could be not allowing the traffic. I checked all cables (replaced) and also connected my laptop directly to my modem, received and IP and everything worked great (220MBps up 30MBps down).

while I was troubleshooting, I tried another modem. It was a Netgear CM600 and it NAT'd the traffic. Basically, it created a 192.160.100.x subnet and my UTM9 received 192.168.100.20 address. I switched back to my Arris modem. Not sure if this could have affected the UTM9 but it was worth mentioning.

When I try to change my WAN NIC to a 4th nic (Internal), or any Nic, I get an error that says "IPv6 Default Gateway is not set" even though IPv6 is disabled. Not sure if this is relevant but I haven't seen this in the past during other troubleshooting. I've been able to switch NICs when I rebuilt my UTM9.

I've uploaded logs here: drive.google.com/.../view

Any help would be appreciated!

EddieRock



This thread was automatically locked due to age.
Parents
  • 0

    The ptoblem is still primarily with your ISP.

    Does your laptop get the same ip configuration as UTM?  

    For example, I have seen my ISP flip me from syatic to dynsmic after an outage.  I have also had an ISP lock onto a MAC address and not allow any others.

    If dhcp ip, did you have any furewall rules tied to the old subnet?

  • +1 in reply to DouglasFoster

    I had noticed that my "External" NIC was receiving a 10.x.x.x address (Non routable like 192.168.x.x). As a test, I blew away my external NIC and setup a new one. I lost all my configuration in my rules (NAT, Masquerade and such) but I knew I could restore back using a backup. When I plugged into the new NIC, I received a real routable IP but since my rules were not there any longer, I couldn't surf.

    So, I did the following (Which worked)

    1. Restored back to July 1st backup
    2. Enabled IPV6
    3. Renewed my IP (it said it wouldn't support IPv6 because my MTU was to low)
    4. Changed the hardware on my WAN interface
    5. Got a real routable IP ...yah!!!
    6. It warned me that IPv6 wouldn't be supported with similar warning as above
    7. Waited...
    8. tested and everythng works

    So, I don't know why my ISP was providing a 10.x.x.x address on my original NIC. Maybe it was in a DHCP table somewhere.

    Thanks! Hope others find this useful. I was down for days and spent 5+ hours trying to figure it out.

    EddieRock 

Reply
  • +1 in reply to DouglasFoster

    I had noticed that my "External" NIC was receiving a 10.x.x.x address (Non routable like 192.168.x.x). As a test, I blew away my external NIC and setup a new one. I lost all my configuration in my rules (NAT, Masquerade and such) but I knew I could restore back using a backup. When I plugged into the new NIC, I received a real routable IP but since my rules were not there any longer, I couldn't surf.

    So, I did the following (Which worked)

    1. Restored back to July 1st backup
    2. Enabled IPV6
    3. Renewed my IP (it said it wouldn't support IPv6 because my MTU was to low)
    4. Changed the hardware on my WAN interface
    5. Got a real routable IP ...yah!!!
    6. It warned me that IPv6 wouldn't be supported with similar warning as above
    7. Waited...
    8. tested and everythng works

    So, I don't know why my ISP was providing a 10.x.x.x address on my original NIC. Maybe it was in a DHCP table somewhere.

    Thanks! Hope others find this useful. I was down for days and spent 5+ hours trying to figure it out.

    EddieRock 

Children
No Data