Services Gateway Issue

[cmb991]

Important notices
Our forum is located at https://forum.opnsense.org , please consider joining discussions there in stead of using GitHub for these matters.

Before you ask a new question, we ask you kindly to acknowledge the following:

[X] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md

[X] I have searched the existing issues and I'm convinced that mine is new.

I'm trying to delete some dpinger services manually. It seems that if you go to your gateways > New > create a new gateway, it won't show the gateway in the gateways but it still makes a dpinger for it. What is the best way to do this?

[AdSchellevis]

can you post a screenshot of your gateways (without addresses)? It might be a bug, since dpinger reads the config directly there might be items that are not valid anymore which we now hide (since 19.7). If that's the case and you're not in a huge hurry, I'll try to look into it in the following days.

The workaround is to remove the item(s) from your config.xml manually.

[cmb991]

Please see attached. I believe I have all of these settings correct for Verizon to be the failover too. From: Ad Schellevis <notifications@github.com> Sent: Saturday, August 3, 2019 3:26 AM To: opnsense/core <core@noreply.github.com> Cc: cmb991 <cmb991@gmail.com>; Author <author@noreply.github.com> Subject: Re: [opnsense/core] Services Gateway Issue (#3625) can you post a screenshot of your gateways (without addresses)? It might be a bug, since dpinger reads the config directly there might be items that are not valid anymore which we now hide (since 19.7). If that's the case and you're not in a huge hurry, I'll try to look into it in the following days. The work around is to remove the item(s) from your config.xml manually. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3625?email_source=notifications&email_token=AHL7ELWZIMQGI4SKVRJBMFTQCUXKBA5CNFSM4IJCF6OKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3PJBIQ#issuecomment-517902498> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AHL7ELQT6NRTH3WPJ7DBLF3QCUXKBANCNFSM4IJCF6OA> . <https://github.com/notifications/beacon/AHL7ELSTNMVWBX6VPBDXIU3QCUXKBA5CNFSM4IJCF6OKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3PJBIQ.gif>

[AdSchellevis]

@cmb991 it looks like your attachments lost, can you try pasting them online?

[cmb991]

Sorry. Here are the pictures. The setup is Xfinity as the primary connection and Verizon as the failover. Although, I’m noticing Verizon is taking the primary spot when I plug it in, so I’m not sure what that is about.

[AdSchellevis]

@cmb991 93bbe1e should fix the visibility issue. It's probably best to wait for 19.7.2 tomorrow and apply this patch on top (there are some other changes stashed in the same files).

[AdSchellevis]

I missed a spot (74ff647) and found another small presentation issue while working on this item bb6833d.

To install all changes on OPNsense 19.7.2:

opnsense-patch 93bbe1e 74ff647 bb6833d

[cmb991]

Everything seems to be working now, I just had a question about this setup now; the firewall rules, I only have the one LAN rule in a gateway group called failover. Does that local DNS route firewall rule that the guide says to put in need to have the failover gateway or no since its locally doing the DNS reroute? Screenshot below

[AdSchellevis]

@cmb991 thanks for confirming, let's close the issue then.

The port 53 rule prevents dns traffic being send to the gateway, which is needed if you are using a local forwarder (unbound for example)

[skl283]

opnsense-patch 93bbe1e 74ff647 bb6833d

@AdSchellevis it works! Thank you! The Gateways are now displayed. But i've found a litte Problem with the Checkbox in front of the entries. If i mark all entries and klick on the trash. Some will be present. I have to purge every single item in the list.

[AdSchellevis]

@skl283 I haven't seen the select all issue yet, but I'll try it out on a box over here.

[skl283]

No Problem.Had just issue while delete all "testing"entries before applying the patches ;-)

[alexanderharm]

I had a similar issue since upgrading to 19.7.2. One issue remains though: after applying your patches I cannot modify the automatically generated gateway of a DHCP WAN connection! See attached screenshot. How can I set upstream gateway or priority now? Or do I need a gateway group by default if one WAN connection is DHCP based?

[AdSchellevis]

@alexanderharm the buttons aren't shown on the right? can you resize your screen a bit? when it's a bit smaller it should resize to xs and show the buttons again. You should also be able to scroll to the right (the buttons should be there, there just don't seem to be enough space there).

[alexanderharm]

Thanks, resizing the screen did the job.

[AdSchellevis]

we might use "table-condensed" to strip some of the margins, same as we did recently on the firewall pages.

[AdSchellevis]

@alexanderharm 1aad01c should be better. (although it can still break out in some situations)