wgX iface as slave to a bridge - Linux

Hi guys. Apologies, I'll bother you guys as I failed to find some better places to ask, I searched for forums etc. but failed. Can wiregurard ifaces be enslaved by LInux bridge? I tried but it did not work for me. Similarly "mavclan" - would/should wireguard work that way? What I've tried an

Re: wgX iface as slave to a bridge - Linux

On 25/04/2021 13:21, Chriztoffer Hansen wrote: Can wiregurard ifaces be enslaved by LInux bridge? I tried but it did not work for me. Similarly "mavclan" - would/should wireguard work that way? Why would you want to enslave an L3-only capable interface to an L2 bridge? What is your use case

secondary IP on wg0 fails

Hi guys. I'm experiencing a pretty weird wireguard, or perhaps kernel/OS stack bits behavior. I have three nodes which all can ping each other on wg0's IPs but when I add a secondary IP: -> $ ip addr add 10.0.0.226/24 dev wg0 it gets weird, namely, say when that sec IP is on A -> B ping re

Re: secondary IP on wg0 fails

On 08/05/2021 17:50, Roman Mamedov wrote: On Sat, 8 May 2021 17:31:58 +0100 lejeczek wrote: I'm experiencing a pretty weird wireguard, or perhaps kernel/OS stack bits behavior. I have three nodes which all can ping each other on wg0's IPs but when I add a secondary IP: ->

Re: secondary IP on wg0 fails

On 08/05/2021 17:31, lejeczek wrote: Hi guys. I'm experiencing a pretty weird wireguard, or perhaps kernel/OS stack bits behavior. I have three nodes which all can ping each other on wg0's IPs but when I add a secondary IP: -> $ ip addr add 10.0.0.226/24 dev wg0 it gets

firewall / port forward - ?

Hi guys. I'm still new to wireguard and still not an expert on network stack so I struggle with something what might be trivial. A roadwarrior when connected to the server sees a forward-port on server's internal network as 'closed': 10.3.9.10 -> 10.3.9.1 10.3.1.1 (port forward) => 10.8.9.

MTUs go strange ways - ?

Hi guys I thought there was no better place to ask but here so - both ends are centOS and end up having different MTUs for 'wg' interfaces and that I thought, was wrong. 1370 (server) VS 1320 (client) I expected that would be negotiated between nodes without user involved, right? Moreover if

error - ? - Address already in use

Hi guys what is below error the symptom of? -> $ wg-quick up wg-r2 [#] ip link add wg-r2 type wireguard [#] wg setconf wg-r2 /dev/fd/63 [#] ip -4 address add 10.3.3.254/24 dev wg-r2 [#] ip link set mtu 1320 up dev wg-r2 RTNETLINK answers: Address already in use [#] ip link delete dev wg-r2 I'll

Re: error - ? - Address already in use

On 13/04/2022 20:45, Shulhan wrote: On Wed, 13 Apr 2022 18:45:24 +0100 lejeczek wrote: Hi guys what is below error the symptom of? -> $ wg-quick up wg-r2 [#] ip link add wg-r2 type wireguard [#] wg setconf wg-r2 /dev/fd/63 [#] ip -4 address add 10.3.3.254/24 dev wg-r2 [#] ip link set

something affects wg iface - how to troubleshoot ?

Hi guys. I have quite a peculiar case which possibly might interest anybody - as oppose to just resolving an issue. I use a very popular monitoring tool 'monit' to monit my wg0 iface and that works okey, meaning 'monit' does not see any issue with wg0, but _only_ if 'qbittorrent' is _not_ runn

package from fedorainfracloud for centOS 8 does not build

Hi guys. In case somebody here looks after 'copr:copr.fedorainfracloud.org:jdoss:wireguard' then wireguard-dkms-1.0.20220627-1.el8.noarch for 4.18.0-394.el8.x86_64 fails to build many thanks, L.

Re: package from fedorainfracloud for centOS 8 does not build

On 29/06/2022 13:27, Jason A. Donenfeld wrote: On Wed, Jun 29, 2022 at 2:17 PM lejeczek wrote: Hi guys. In case somebody here looks after 'copr:copr.fedorainfracloud.org:jdoss:wireguard' then wireguard-dkms-1.0.20220627-1.el8.noarch for 4.18.0-394.el8.x86_64 fails to build many

IP which is not there but wg0 replies - ?

Hi guys. Purely accidentally I stumbled uppon: -> $ ping 10.1.101 PING 10.1.101 (10.1.0.101) 56(84) bytes of data. 64 bytes from 10.1.0.101: icmp_seq=1 ttl=64 time=0.148 ms 64 bytes from 10.1.0.101: icmp_seq=2 ttl=64 time=0.415 ms -> $ ip a ls dev wg0 17: wg0: mtu 8920 qdisc noqueue state U

Re: How to post to the mailling list? (Was: IP which is not there but wg0 replies - ?)

Marek Küthe On Thu, 8 Jun 2023 11:30:26 +0200 lejeczek wrote: Hi guys. Purely accidentally I stumbled uppon: -> $ ping 10.1.101 PING 10.1.101 (10.1.0.101) 56(84) bytes of data. 64 bytes from 10.1.0.101: icmp_seq=1 ttl=64 time=0.148 ms 64 bytes from 10.1.0.101: icmp_seq=2 ttl=64 time=0.415

Re: How to post to the mailling list? (Was: IP which is not there but wg0 replies - ?)

On 08/06/2023 14:04, Marek Küthe wrote: On Thu, 8 Jun 2023 13:45:27 +0200 lejeczek wrote: On 08/06/2023 11:47, Marek Küthe wrote: Hello, I would be interested to know how you managed to post something on the Mailling list? I have been trying to do this for several weeks, however my

TEXT test - ignore

ignore