Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - elcoto

#1
You tunnel all through openvpn using the Opnsense router or do you use an openvpn application on your computer and happen to have an opnsense router? Can you show some firewall rules or how you have it setup now?
#2
Since I can't edit...

Was going to screenshot my FW rule and noticed I had mixed the direction OUT/IN.

*facepalm*
#3
This is likely beyond trivial but I am stuck  :-[ I have setup an OpenVPN server that:

1. I am able to connect to
2. Obtain an IP in the range I have setup for it.
3. Can see the traffic being blocked.

My impression is that I set the FW rule on the incoming source interface so this case ~MolnhemOpenvpn (what I named the interface ~ovpn1) to allow VPN network to LAN network and this I have ofcourse set. But still I only see blocked traffic.  :'(

Any pointers, bitchslaps or solutions are much appreciated.

#4
(I don't really have experience with these tools you are using but I will just put my 2 cents since nobody has responded)

If everytime you spin up a new container this begins to present itself and then goes away if it is MTU related then does this mean that the container host corrects the MTU after a bit of time and the resets the MTU? And you have ruled out it's not some weird routing thing that is breaking when you spin up a container momentarily,?(Again, I don't fully understand what it happening and how the routing to the containers is done) Can you see anything funny with the docker containers interface tcpdump?

I don't know if mtu's are adaptive and can change by default.

ifconfig ens10 | grep -i mtu
ifconfig ipvlan(??) | grep -i mtu

and check if this changes when a container is created. And then perhaps as a 'workaround' lower these values?

But again I am just wildly guessing.