OPNsense Forum

Archive => 22.7 Legacy Series => Topic started by: manilx on October 20, 2022, 12:27:57 AM

Title: superfluous gateways in WAN interface IPv4 Upstream Gateway
Post by: manilx on October 20, 2022, 12:27:57 AM
Hi

I have one gateway defined in System: Gateways: Single.

Name Interface Protocol Priority Gateway Monitor IP RTT RTTd Loss Status Description
WAN_GW (active) WAN IPv4 255 (upstream) 192.168.1.1 1.1.1.1 3.7 ms 0.5 ms 0.0 % Online
Interface WAN Gateway


But when I go to   Interfaces: [WAN]  -  IPv4 Upstream Gateway there's Autodetect and then 5 times the WAN_GW.

They're probably all the same. How can I get rid of the multiple entries?

thx in advance

Title: Re: superfluous gateways in WAN interface IPv4 Upstream Gateway
Post by: franco on October 20, 2022, 08:44:44 AM
Can you try to delete and recreate the gateway? Worst case it needs to be deleted 5 times as there could be 5 copies in the config.xml. You could also try to edit config.xml manually and remove the duplicates.

The gateway system is a bit tricky referencing them only by name. Multiple copies could theoretically exist but are not shown since they share the same name.


Cheers,
Franco
Title: Re: superfluous gateways in WAN interface IPv4 Upstream Gateway
Post by: manilx on October 20, 2022, 08:49:32 AM
Thx Franco

I did that already 10mins ago.

I deleted the interface before. Then deleted the gateway a few times but it always returned. Might NOT have deleted it 5 times though.
Then I created the interface again and attached the gateway and there was now only one to be selected.

All is working so I think this is corrected now.
Title: Re: superfluous gateways in WAN interface IPv4 Upstream Gateway
Post by: manilx on October 20, 2022, 09:43:03 AM
UPDATE:

because of deleting the interface deletion/recreation the fw rules started to act up and firing wrongly.

Reverted snapshot (one big advantage of having this in a VM otherwise would have to restore config also no big deal).

Then did as you suggested and deleted the gateway 5 times. After recreating in the WAN gateway settings and changing from automatic to this gw all is working now again.