Are these the new GREs?

senseivita

I just switched the tunnel type on an interface from OpenVPN to GRE.

It already existed si it was already named, I only swapped the tunnel so I can't quite explain how I ended back on that page. Most if not all tunnel-backed interfaces have no options.

But this one has, and plenty:

I thought GRE was L3, there's multicast stuff and MAC-centric stuff. It seems like a glitch too but I have already rebooted, so…yeah.

What's up with this GRE? Is it normal? ️

(and thanks, BTW)

stephenw10

Hmm, yeah that seems like a bug. Like you found a way through the input validation somehow.

What pfSense version is that?

You re-assigned the interface from openvpn to gre?

Steve

senseivita

@stephenw10 Thanks ! I found it. Over SSH I went over the interfaces and noticed two GRE interfaces had the same um… lemme check…

(about 10m later)

This is the second time this week distraction due to ADHD have been useful. I forfot to delete the copy I made of the bad config file before editing it live. :)

	<gres>
		<gre>
			<if>_vip63daa3edb8910</if>
			<tunnel-local-addr>192.168.96.2</tunnel-local-addr>
			<tunnel-remote-addr>192.168.96.1</tunnel-remote-addr>
			<tunnel-local-addr6></tunnel-local-addr6>
			<tunnel-remote-addr6></tunnel-remote-addr6>
			<tunnel-remote-net>30</tunnel-remote-net>
			<tunnel-remote-net6>128</tunnel-remote-net6>
			<remote-addr>2607:f298:5:101d:f816:3eff:fed9:5319</remote-addr>
			<descr><![CDATA[Cloudfront208]]></descr>
			<link1></link1>
			<greif>gre0</greif>
		</gre>
		<gre>
			<if>_vip63c2ede3714bc</if>
			<tunnel-local-addr>192.168.95.2</tunnel-local-addr>
			<tunnel-remote-addr>192.168.95.1</tunnel-remote-addr>
			<tunnel-local-addr6></tunnel-local-addr6>
			<tunnel-remote-addr6></tunnel-remote-addr6>
			<tunnel-remote-net>30</tunnel-remote-net>
			<tunnel-remote-net6>128</tunnel-remote-net6>
			<remote-addr>2607:f298:5:101d:f816:3eff:fe40:b3eb</remote-addr>
			<descr><![CDATA[Cloudfront064]]></descr>
			<link1></link1>
			<greif>gre0</greif>
		</gre>
	</gres>

In the GUI, I couldn't delete either. It told me repeatedly that the interface was assigned. One of them was but it turns out both of them were "one of them".

I had been swapping interfaces repeatedly testing tunnels, so I wouldn't lose the related information to the assignment (rules, routing, DHCP6, etc.) but since the symptoms presented much later, it didn't occur to me to trace it back to that. Sometimes when I started "from scratch", the tunnel interfaces that is, I would set some random VLAN to hold the assignment.

Thanks again!

Almost forgot, it's version 2.6.0

stephenw10

Hmm, so removing the duplicate gre entries resolved the issue?