Default gateway incorrect

Cry Havok

Well, the cable modem only hands out a 192.168.100/24 address when it doesn't have an Internet connection. I'd agree with TommyBoy180 that it could be your modem going bad.

EddieA

Firstly, why would the cable modem hand out an IP address, It's not a router, it's just a bridge.

Secondly, and more importantly, when the situation corrects itself a couple of minutes later, and I get an IP from my ISP, why isn't the routing table set to the correct gateway. That's the more troubling part.

Cheers.

tommyboy180

@EddieA:

Firstly, why would the cable modem hand out an IP address, It's not a router, it's just a bridge.

Secondly, and more importantly, when the situation corrects itself a couple of minutes later, and I get an IP from my ISP, why isn't the routing table set to the correct gateway. That's the more troubling part.

Cheers.

All modems hand out a private IP address. The DHCP lease is usually set to expire in 60 seconds. This allows the Cable modem to sync with the ISP. Then it will hand you a Public IP. However you are loosing that connection. This makes me think the Cable modem is going bad or your ISP needs troubleshoot with you.

If your pfsense box isn't getting the correct configuration from your ISP then you need to troubleshoot what is happening. Just like I pointed out in my first post, try to eliminate some variables first. Take the pfsense box out of the picture and see if you still have the same problem. Go from there.

EddieA

@tommyboy180:

All modems hand out a private IP address. The DHCP lease is usually set to expire in 60 seconds. This allows the Cable modem to sync with the ISP. Then it will hand you a Public IP. However you are loosing that connection. This makes me think the Cable modem is going bad or your ISP needs troubleshoot with you.

Or it just lost connection for a while, gave me the 192.168.100.10 for a short period, and then I got the IP from the ISP, as can be seen in the logs I quoted. OK, despite the fact I've never seen that before, on either my previous Linux gateway, or pfSense, I can live with this part.
@tommyboy180:

If your pfsense box isn't getting the correct configuration from your ISP then you need to troubleshoot what is happening.

But it is. My ISP wouldn't hand out a gateway address of 192.168.100.1. And it works perfectly well for every other acquire and renew of the lease.

The issue with the gateway only happens after I have the "short term" lease from the cable modem.

BTW, I forgot to give the contents of re_router, when I captured all the other information:

98.148.120.1

So again, please explain why the gateway is not being set correctly when I get the correct lease from my ISP.

Cheers.

tommyboy180

I could be completely wrong, but I don't think your issue is pfsense. I think you have another problem. Do you have the same problem when you connect a PC directly to the modem?

EddieA

No problems. Other machines connect correctly.

pfSense connects correctly when I re-boot, or power cycle it following these occurrences.

pfSense renews it's lease correctly, every time except when it follows the 192.168.100.10 lease.

Cheers.

tommyboy180

Can you try a 30-30-30 reset on your modem?

EddieA

@tommyboy180:

Can you try a 30-30-30 reset on your modem?

I'm out of town for a couple of days, so can't really do too much until I return. When I get back, I'll try that. But, unfortunately, I can't predict if, or when, the issue might happen again.

I'm also going to pull the cable, from the modem, to see if I can simulate an outage, to see if that reproduces it.

Cheers.

EddieA

OK, now I'm back home, I can play with this again. And guess what, I was able to re-produce the issue perfectly. I pulled the cable, from the modem, without powering it off. Obviously I lost all internet connection. When I plugged the cable back in, and checked what was happening in pfSense, I saw exactly the same issues.

Now, as an experiment, I removed this line from my configuration:

<shellcmd>ifconfig vr0 inet 192.168.100.1 netmask 255.255.255.0 alias</shellcmd>

Rebooted, and pulled the cable again.

This time, things worked differently. My IP again went to 192.168.100.10, and here is my routing table:

Routing tables

Internet:
Destination        Gateway            Flags    Refs      Use  Netif Expire
default            192.168.100.1      UGS         0       58    re0
98.148.127.153     127.0.0.1          UGHS        0        2    lo0
127.0.0.1          127.0.0.1          UH          2        0    lo0
192.168.0.0/24     link#1             UC          0        0    vr0

...

Notice this time, that the gateway still points to the WAN interface, not the LAN.

A couple of minutes later, the IP reverted back to my ISP's IP, and now the routing table is:

Routing tables

Internet:
Destination        Gateway            Flags    Refs      Use  Netif Expire
default            98.148.120.1       UGS         0       21    re0
98.148.120.0/21    link#2             UC          0        0    re0
98.148.120.1       00:01:5c:31:76:01  UHLW        2        0    re0   1200
98.148.127.153     127.0.0.1          UGHS        0        4    lo0
127.0.0.1          127.0.0.1          UH          2        0    lo0
192.168.0.0/24     link#1             UC          0        0    vr0
...

All correct, and I am able to access the internet again, without issues.

So, it looks like the alias of 192.168.100.1 I set up, for the LAN interface causes the issues with the gateway.

However, removing that alias now means that my log gets flooded with this error:

kernel: arplookup 192.168.100.1 failed: host is not on local network

Which, makes it difficult to look back through what's happened, should I need to. Is there any other way to suppress that particular error message.

Cheers.

tommyboy180

Good post back. Thanks for sharing your findings!
As far as the arplookup, not sure why your modem is sending arp requests since it already has an IP, perhaps it's how the ISP needs their modems to function. pfSense sees the arp requests and according to its config it is impossible to have this IP on this interface and reacts with the message in log. Check you NAT entries to make sure nothing is mis-configured.

I do have a question though, why would you set up an alias for a node that is outside of your network? What is the benefit? It just sounds really weird.

EddieA

The reason for the alias can be found here. It was a way to stop the errors being generated.

I just noticed that in the "bounty" post, it was suggested to use an alias of 192.168.100.10, not the 192.168.100.1 that I used. Maybe I'll try that next, especially as I can reproduce this now.

Cheers.