Bad argument `eth0' openvpn after update
-
@ApplegateR great work. My server disabled ipv6. And it still detected my phone tower ipv6 instead cloudron server was it because my cloudron disabled ipv6?
If I try switch to public on ipv6 I still get error this message
AddressUnable to detect IPv6.
API server (ipv6.api.cloudron.io) unreachable -
@ApplegateR said in Bad argument `eth0' openvpn after update:
If I try switch to public on ipv6 I still get error this message
Currently, the IPv6 detection is only done on the app startup. So, if you add/remove IPv6 on the fly, you have to restart the app.
-
@girish okay it disabled and I did restart the app and I still get leak ipv6. So I guessing something configure is missing that bypass ipv6 I think.. but will look more into it
-
@ApplegateR The openvpn.conf should have
push "redirect-gateway def1 ipv6 bypass-dhcp". If it does, then it's probably a client side thing. Are you on a Mac ? I only tested this the setting on linux. -
In openvpn.conf
push "redirect-gateway def1 bypass-dhcp"
Not showing ipv6 so I added second line below that. Let see test see if it works.
push "redirect-gateway def1 bypass-dhcp"
push "redirect-gateway def1 ipv6 bypass-dhcp" -
This post is deleted!
-
@ApplegateR switch to data on my phone and it still get ipv6 however on wifi does not show ipv6
-
@ApplegateR Thanks! Yes, the app will now start without issue, but it's not pushing the IPv6 address -- which isn't a huge issue for us at the moment.
-
@ApplegateR said in Bad argument `eth0' openvpn after update:
@JLX89 yes for me I just don't want it being leak ipv6 on data so still work on it..
Yes, I agree -- so far I did some testing and used https://ipleak.net to see if there were any issues and didn't see any.
