Hello
Le 30/08/2021 à 19:59, Roman Mamedov a écrit :
On Mon, 30 Aug 2021 19:44:21 +0200
Daniel wrote:
Do you get WG working at all, between some other two hosts (not involving this
particular server for now)?
Yes. Clients are shown on both sides as connected, trafic seems to go
out on each s
Again :)
Le 31/08/2021 à 19:50, Daniel a écrit :
Hi
Le 30/08/2021 à 19:59, Roman Mamedov a écrit :
On Mon, 30 Aug 2021 19:44:21 +0200
Daniel wrote:
Do you get WG working at all, between some other two hosts (not
involving this
particular server for now)?
Yes. Clients are shown on both sid
Hi
Le 30/08/2021 à 19:59, Roman Mamedov a écrit :
On Mon, 30 Aug 2021 19:44:21 +0200
Daniel wrote:
Do you get WG working at all, between some other two hosts (not involving this
particular server for now)?
Yes. Clients are shown on both sides as connected, trafic seems to go
out on each side
Le 30/08/2021 à 19:38, Roman Mamedov a écrit :
On Mon, 30 Aug 2021 19:28:11 +0200
Daniel wrote:
To be sure (and I think it is as I have no problem with ipv4):
. my interfaces are named wig4tootai our wigserver Nothing wrong here ?
. conf file are not named .conf but server.conf or
anyname.
Le 30/08/2021 à 18:43, Roman Mamedov a écrit :
On Mon, 30 Aug 2021 12:24:01 +0200
Daniel wrote:
Using tcpdump -i any I see the trafic coming to the gre interface and
that's all. But netstat show
udp6 0 0 :::12345 :::*
0 125391 -
and ps aux output is
dh@peech:~$ ps
On Mon, 30 Aug 2021 19:44:21 +0200
Daniel wrote:
> > Do you get WG working at all, between some other two hosts (not involving
> > this
> > particular server for now)?
> Yes. Clients are shown on both sides as connected, trafic seems to go
> out on each side but other one as received near to no
On Mon, 30 Aug 2021 19:28:11 +0200
Daniel wrote:
> To be sure (and I think it is as I have no problem with ipv4):
>
> . my interfaces are named wig4tootai our wigserver Nothing wrong here ?
>
> . conf file are not named .conf but server.conf or
> anyname.conf Nothing wrong here too ?
Interfac
On Mon, 30 Aug 2021 12:24:01 +0200
Daniel wrote:
> Using tcpdump -i any I see the trafic coming to the gre interface and
> that's all. But netstat show
>
> udp6 0 0 :::12345 :::*
> 0 125391 -
>
> and ps aux output is
>
> dh@peech:~$ ps a
Hi
Le 27/08/2021 à 23:44, Roman Mamedov a écrit :
On Sat, 28 Aug 2021 07:05:45 +0930
Mike O'Connor wrote:
On a 1500 link I'm having to use 1280 to get ipv6 to successfully go
over a wireguard link.
Then it is not a true 1500 MTU link, something in-between drops packets at a
lower bar. Or may
On 8/30/21 1:24 PM, Daniel wrote:
Hi
Le 27/08/2021 à 23:44, Roman Mamedov a écrit :
On Sat, 28 Aug 2021 07:05:45 +0930
Mike O'Connor wrote:
On a 1500 link I'm having to use 1280 to get ipv6 to successfully go
over a wireguard link.
Then it is not a true 1500 MTU link, something in-between d
root@gw:~# ping -M do -s 1472 13.17.1.2
PING 103.127.123.217 (13.17.1.2) 1472(1500) bytes of data.
1480 bytes from 13.17.1.2: icmp_seq=1 ttl=60 time=7.93 ms
Link can transmit a max of 1500 bytes as seen above.
Pinging a LAN segment has the same limit. ie PC to PC has the same result.
Mike
On 2
On Sat, 28 Aug 2021 07:05:45 +0930
Mike O'Connor wrote:
> On a 1500 link I'm having to use 1280 to get ipv6 to successfully go
> over a wireguard link.
Then it is not a true 1500 MTU link, something in-between drops packets at a
lower bar. Or maybe not all of them, but just UDP, for example.
B
Hi
On a 1500 link I'm having to use 1280 to get ipv6 to successfully go
over a wireguard link.
I really think wireguard should be able to fragment and send via
multiply UDP packets.
wireguard works very well other than this issue, performance is
extremely good.
Mike
On 28/8/21 2:46 am,
Hi ROman
Le 27/08/2021 à 18:14, Roman Mamedov a écrit :
On Thu, 26 Aug 2021 13:14:00 +0200
Daniel wrote:
Correction
Le 25/08/2021 à 17:25, Daniel a écrit :
Hi list,
I setup wireguard on a server running Debian 11 and get it to work with
2 clients (Debian 11 and Ubuntu 20.04). Clients and s
Hi list,
I setup wireguard on a server running Debian 11 and get it to work with
2 clients (Debian 11 and Ubuntu 20.04). Clients and server are on
separate networks, one client behind a FW the other direct on Internet,
no FW at all (VPS).
With this setup and ipv4 connection to the public IP
Correction
Le 25/08/2021 à 17:25, Daniel a écrit :
Hi list,
I setup wireguard on a server running Debian 11 and get it to work with
2 clients (Debian 11 and Ubuntu 20.04). Clients and server are on
separate networks, one client behind a FW the other direct on Internet,
no FW at all (VPS).
On Thu, 26 Aug 2021 13:14:00 +0200
Daniel wrote:
> Correction
>
> Le 25/08/2021 à 17:25, Daniel a écrit :
> > Hi list,
> >
> > I setup wireguard on a server running Debian 11 and get it to work with
> > 2 clients (Debian 11 and Ubuntu 20.04). Clients and server are on
> > separate networks, o
17 matches
Mail list logo
