You are aware that setting the MTU is dangerous?
In case some part of your route requires a lower MTU, you're screwed.
If you dictate a value of 1492, it will do so, even if an other router only can
handle 1300
-Original Message-
From: Frank [mailto:ve2...@ve2cii.com]
Sent: dinsdag
I want to thank everyone for the help. At this point it looks like
Rogers is having issues
with their support of vpn on their routers/switches. Lots of
complaints. So I removed
the mtu change from the client and am just using whatever it uses for
default. So i
am saying that this issue ha
Hi Frank,
If you have access to the server configuration, try setting link-mtu 1440.
Rogers had an MTU of 1460 previously but recently migrated all their iPhone
devices to IPv6 only, which requires NAT64 if your VPN server is IPv4-only.
This reduces the MTU by 20 bytes. There appear to be issue
Hi,
The server is ours. And I look after it so I can so what I want. I
think it is best to wait till Rogers
straightens out their issues, rather than trying to fix someone else's
problems.
On 9/26/18 09:23, Kristian McColm wrote:
Hi Frank,
If you have access to the server configurat
Even if they fix the PMTU issues, I'm not sure OpenVPN supports PMTUD (based on
my own testing) so I think it is probably best if you either a) support IPv6
natively, b) reduce your MTU to accommodate NAT64 or c) use TCP transport so
that TCP MSS rewriting can fix your problem. Either way, I am
The server has an IPV6 address, and it is dual stack. I am not
sure if openvpn was compiled
with ipv6 support. It is openvpn-2.0.9. Let me see what I can do.
On 9/26/18 10:01, Kristian McColm wrote:
Even if they fix the PMTU issues, I'm not sure OpenVPN supports PMTUD (based on
my own te
Top posting:
This is exactly right - many ISP's are *NOT* generating/returning the ICMP
"Fragmentation needed" responses - in which case, your reliance on PMTU will
result in a completely failed connection. [For my users, at least, that's the
*MOST UNDESIRABLE* option of any.]
Using a smaller
Ok, I am able to make a connection. It does connect. There is no data
going through the connection.
I am trying to upgrade to 2.4.6 but I am having issues compiling.
The OS is
slackware-12.1 which is very old now so it may not be compatible. I am
getting
an err.h error. Says it finds it
HI,
On Wed, Sep 26, 2018 at 10:13:09AM -0400, Frank wrote:
> The server has an IPV6 address, and it is dual stack. I am not
> sure if openvpn was compiled
> with ipv6 support. It is openvpn-2.0.9. Let me see what I can do.
If you run openvpn 2.0.9 on the *server*, you should upgrade.
L
I am unable to compile 2.4.6. I had compiled 2.4.4 but it would not
run.
I just tried setting the link-mtu to 1440 with 2.0.9 on the server and that
did not work. I was able to connect but still server errors when trying
to surf. Plus it
gave me inconsistant mtu errors in the log.
On 9/26/
I don't have time to walk you through all the details and troubleshoot - but
while 1440 might be a good choice, I'd probably pick something like 1400 or
even 1380. As I've said a few times - if you pick an MTU of 1440 and you really
needed 1339, it won't work. But if you pick 1400 and it could h
11 matches
Mail list logo
