UPDATE
No success with a variety of different methods. It seems that when the ip -6 add is used within the .service file setting up the interface it doesn't like it, so I wrote a simple bash file which first loads and configures the interface then sets the route. Using it from the commandline works great but using it in the .service file for the interface set up instead of the normal script in Execstart doesnt.
Oh well I have lost nothing, it's only a very minor hassle and I have learnt an awful lot about routing, networking and IPv6 along the way.
Now to try to set up wireguard client on a windows 10 box. LOL
Keith
Andy
Yes. Sorry, I answered before but it appeared further down the thread
Hi Keith,
On Thu, Jul 04, 2019 at 06:53:49PM +0100, Keith Williams wrote:
> Now here comes the problem. It is the default route issue.
I've not done anything like this as I rely on A&A's IPv6 when at
home and just VPN everything to BitFolk when out and about on laptop
etc.
Just so I understand what you're wanting to achieve:
Your personal computers have a WireGuard VPN that provides IPv6.
You also sometimes but not always have native IPv6 on these
computers.
When you have an IPv6 default route assigned by SLAAC you want to
use that, but otherwise you want to have an IPv6 default route going out
of wg0 which would VPN the traffic via BitFolk.
Is that correct?
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
users mailing list
users@lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users