| 22 Oct 2020 |
 endor00 | Have you read this? https://www.wireguard.com/netns/
It talks about this exact topic in detail, with some examples too | 03:52:21 |
 Celmor | thanks | 03:52:43 |
| Celmor | is there also a use-case/solution for connecting over multiple WANs to a wireguard server and "combining" each connections bandwith? | 03:53:34 |
| endor00 | I'm not sure that's something you do at the Wireguard level | 04:19:09 |
| Celmor | ok, thanks for the input. I have at least an idea how to solve this. | 04:20:39 |
| endor00 | As in: you need some other solution to 'combine' your connections into one, and then you just run wg on top as if you were connecting to the server normally | 04:20:50 |
| endor00 | You're welcome | 04:21:00 |
| Celmor | I'd just need to "round-robin" my packets over the available wg interfaces and as long as the route through the tunnels and come out at the same destination it should be fine | 04:22:05 |
| Celmor | it appears my pivpn generated invaiid WireGuard configs. wireguard reports reports "Line unrecognized: `Address=10.6.0.2/24'" and "Configuration parsing error", example config: https://termbin.com/ujwi | 04:59:24 |
| Celmor | seems I needed to use wg-quick | 05:12:23 |
| endor00 | In reply to @Celmor:matrix.org
it appears my pivpn generated invaiid WireGuard configs. wireguard reports reports "Line unrecognized: `Address=10.6.0.2/24'" and "Configuration parsing error", example config: https://termbin.com/ujwi Fyi you just published your configuration's private key - anyone could connect to that server and impersonate you. You should generate a new one (and perhaps a new preshared key too) | 05:35:02 |
| Celmor | it was an example config, I've obfuscated the keys and IP obviously | 05:35:32 |
| endor00 | Oh, ok, all good then | 05:36:35 |
| endor00 | (Also, if that's your client config, it should be 10.6.0.2/32, otherwise the client will try to act as a router for the whole /24 subnet and will be unable to talk to other peers other than the server) | 05:37:56 |
| endor00 | (Unless that's your explicit intention) | 05:38:15 |
| endor00 | * (Also, if that's your client config, it should be 10.6.0.2/32, otherwise the client will try to act as a router for the whole /24 subnet and will be unable to talk to other peers other than the server) | 05:38:49 |
| Celmor | it is the config as pivpn generated it, the address semed strange to be too as the page you've linked earlier explicitly assigned a /32 address | 05:39:00 |
| Celmor | ideally I'd just want to assign it via wg, ignore the ip configs and such and setup routes myself too | 05:40:02 |
| endor00 | Why manual routes? | 05:41:05 |
| Celmor | cause I don't wan't to change default route and am just currently trying this out in a custom namespace according to the example you've linked me earlier | 05:41:48 |
| Celmor | I'm trying to use an ip like 192.168.0.200/32 for the interface on the client side where a network of 192.168.0.0/24 is used on the server side and make any connectiony to 192.168.0.0/24 go through the tunnel from the client | 05:43:28 |
| endor00 | Hmm, not sure how to do that. Perhaps https://github.com/pirate/wireguard-docs can help you (look for the Table parameter) | 05:47:56 |
| Celmor | thanks, I'll check it out | 05:50:07 |
| Celmor | though I'm still unsure about the differences between wg and wg-quick tools and accepted configs | 05:50:26 |
| Celmor | I assumed the wg config my pivpn generated would be accepted by all wireguard clients, so does wg not conform to that as opposed to wg-quick? | 05:51:20 |
| endor00 | wg and wg-quick are two different tools | 06:05:25 |
| endor00 | wg directly works on your wireguard interface | 06:05:40 |
| endor00 | wg-quick is a tool (that comes bundled with wg) that reads your config file and applies all the settings at once (or removes them when you bring an interface down) by working through wg under the hood. It automatically does stuff like setting routes too, and allows for Pre/Post Up/Down operations (extra commands you want to run when bringing up/down interfaces) | 06:08:09 |
| endor00 | * wg-quick is a tool (that comes bundled with wg) that reads your config file and applies all the settings at once (or removes them when you bring an interface down) by working through wg under the hood. It automatically does stuff like setting routes too, and allows for Pre/Post Up/Down operations (extra commands you want to run when bringing up/down interfaces) | 06:08:58 |
| 23 Oct 2020 |
| Celmor | how would I disable/ignore ipv6 entirely when using wg-quick to bring a VPN connection up? it seems to error and not establish at all because I've disabled ipv6 on kernel level | 21:14:30 |
