Hhmm, I see; just didn't remember it was like that before.
I did notice that we can now delete the gateway from the OpenVPN tap
device (bridged to em1). Any chance we can then at least hide disabled
gateways from the status pages? The IPv4 gateway on a SixXS tunnel will
never come up for example.
On that same note, we also have the OpenVPN rules tab, but rules are
handled in it's separate interface tab. Or in case of some bridge
members, not at all.
Slightly off-topic: If you bridge a tap with an lan interface, would you
recommend filtering on the lan or the bridge it self (tap - lan should
be transparently bridged.)
On 11/26/2014 11:02 PM, Chris Buechler wrote:
On Wed, Nov 26, 2014 at 2:11 PM, Marcus van Dam mar...@marcusvandam.nl wrote:
Hi,
I am running on 2.2-BETA (amd64) for quite a while now, everything is fine
except for one mayor annoyance;
How to trash a gateway? I have a couple of interfaces with their IPv4 and
IPv6 config set to none, for example VPN tunnels. Or IPv4 only interfaces.
If I try to delete the unnecessary IPv6 gateway or both they just re-appear,
enabled and all. Of course never reaching up status for the various reasons.
Sounds like what should happen, and what's always happened, by design.
Dynamic gateways should be there in most VPN circumstances with an
assigned OpenVPN interface, and can't be deleted. They act the same as
a DHCP or other dynamic-type interface in that regard. You don't have
to use them, and can disable monitoring on them if you want, but they
have to be there.
___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list
___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list