2 gateways showing identical IP ?

madbrain

I have 3 WANs, all connected with separate Ethernet interfaces. Only a single Ethernet interface is currently enabled, the one with the Comcast modem on it.

However, the pfSense home screen is showing 3 gateways :

Comcast (IPv4)
COMCAST_DHCP6 (IPv6)
VERIZON_DHCP (IPv4)

The problems are :

gateways 1 and 3 are displayed with the same IP address, which is the Comcast one. This is obviously incorrect.
since the Verizon interface is disabled, I don't understand why gateway 3 is even listed

I verified that all my interfaces / assignments are separate. Actually, the GUI doesn't you assign the same NIC to 2 interfaces anyway.

Under system/routing/gateways, there are 4 gateways.
2 for Comcast (IPv4 and IPv6), 1 for Sail (IPv4), and 1 for Verizon (IPv4).
These gateways are all assigned to the proper interface, as far as I can tell . None of these 4 gateways are disabled, but the SAIL and VERIZON interfaces are both disabled.

There must be something wrong in my configuration, but it's not obvious to me what I'm missing.

johnpoz

@madbrain said in 2 gateways showing identical IP ?:

Actually, the GUI doesn't you assign the same NIC to 2 interfaces anyway.

No it won't but if you pull dhcp for this gateway, then yeah they could have the same IP. If they were public I would find it highly unlikely that they could ever be the same IP.

But if your device that provides this gateway is actually a nat router, sure you could have say the same 192.168.1.0/24 range on them where .1 is the device, and its doing nat.

Other option would be if they were using cgnat and just happen to be on the same IP range, or they are actually using rfc1918 instead of cgnat range.

Are those IPs your hiding rfc1918 space 10.x.x.x, 192.168.x.x, 172.16-31.x.x ? Or cgnat space 100.64-127.0.0 ?

madbrain

@johnpoz thanks. Everything is bridged. No other router in front of pfSense. No CG-NAT. All 3 ISPs are providing public, routable IPv4 addresses.

johnpoz

@madbrain well then you got something really borked up.. Since how would different companies be using the same IP range?

Mixed up interfaces?

is this after an upgrade? A config restore... or this just happened out of the blue - they were fine different IPs, and now all of sudden they have the same IP? With no reboot, or config change or upgrade to pfsense? Or adding another interface?

This is hardware, or is pfsense a VM?

madbrain

@johnpoz it is bare metal, not a VM. And the 3 ISPs are definitely not sharing the same IP address space. The status / interfaces screen shows that the SAIL and VERIZON interfaces both have "status: disabled" and thus have no listed IP address.
I don't understand why the VERIZON_DHCP shows up at all on the main screen when the underlying interface is disabled, much less with the Comcast IP address.
For what it's worth, the physical interface I use with the Verizon modem is a crappy Realtek 8156B 2.5Gbps USB NIC. 2.5 Gbps is overkill for the Verizon 5G home internet service. I would have used a more stable 1 Gbps USB or PCI-E NIC, but couldn't find one in all the drawers in my garage, even though I'm sure I have at least a couple of them there. The FreeBSD driver for that NIC might be borked, but even that doesn't explain the display issues.

No upgrade to pfSense was made. I did reboot, but only to see if the problem would go away.

Config changes/interface addition : yes, I added the RTL8156B USB NIC yesterday to accommodate 3 ISPs. The other NICs are an Intel X550-T2 (dual port NBASE-T) and a 1 Gbps Intel NIC on the motherboard - not quite sure which model. It shows up as igb0 in pfSense.

madbrain

@madbrain I rebooted one more time, and the problem went away - Verizon gateway no longer showed. Very strange. It's an intermittent problem.

I decided to remove the USB Realtek 8156B NIC, and replace it with a PCI-E Intel I-225V (B3) that I bought at Central Computers earlier today. This necessitated shutting down the machine to insert the PCI-E card.

During the next boot, this is what the interface assignment screen looked like (MAC adresses omitted) :

As you can see, both the Comcast and Verizon interfaces are assigned to the same ix0 network port. Previously, Verizon was assigned to the ue0 network port for the RTL8156B. That port no longer exists since the USB NIC was unplugged. It is a bit disconcerting to see two interfaces on the same NIC, to say the list. Not sure what the right behavior should be, though. Maybe have the interface be unbound (no network port) ?

So far, I am not seeing the same issue with all 4 Ethernet ports using Intel NICs (motherboard 1 Gbe, X550-T2 2 x 10 GBe, I225-V (B3) 2.5 Gbe), but it's only been a few minutes.