On Thu, Mar 21, 2024 at 12:23:06PM +0300, Vitaliy Makkoveev wrote:
> wg(4) diff was committed to -current. Does the problem exist in upcoming
> 7.5?
Oh, I didn't know a fix had been committed, the referenced thread didn't
mention a final one. Thanks, I'll take a look.
On 24/03/21 04:58PM, Kirill Miazine wrote:
> in this case I added escaped newlines when posting, i have all on one line,
> but I think i could have scripts where a pipe is followed by escaped
> newline. have to check that one.
BTW, this also applies to lists[1], for example:
! false &&
ec
• Страхиња Радић [2024-03-21 16:31]:
On 24/03/20 08:15AM, Kirill Miazine wrote:
#!/bin/sh
ifconfig wg1 | \
grep wgaip | \
awk '{print $2} ' | \
grep /32$ | \
sed 's/\/32//' | \
sort | while read x; do
ping -w 1 -c 1 $x 2>&1
done
Just FYI, you don't need backslash
On 24/03/20 08:15AM, Kirill Miazine wrote:
> #!/bin/sh
> ifconfig wg1 | \
> grep wgaip | \
> awk '{print $2} ' | \
> grep /32$ | \
> sed 's/\/32//' | \
> sort | while read x; do
> ping -w 1 -c 1 $x 2>&1
> done
Just FYI, you don't need backslashes (\) here, as the command endi
On Wed, Mar 20, 2024 at 03:43:52PM -0700, Paul B. Henson wrote:
> On Wed, Mar 20, 2024 at 09:56:06PM +0100, Kirill Miazine wrote:
>
> > Like in this thread, I guess:
> >
> > https://marc.info/?t=16964239631&r=1&w=2
>
> Yes, that is likely the issue we're hitting. Seems last message is from
>
• Paul B. Henson [2024-03-20 15:43]:
> On Wed, Mar 20, 2024 at 09:56:06PM +0100, Kirill Miazine wrote:
>
> > Like in this thread, I guess:
> >
> > https://marc.info/?t=16964239631&r=1&w=2
>
> Yes, that is likely the issue we're hitting. Seems last message is from
> 10/2023 and the issue wasn
On 3/20/2024 20:56 Kirill Miazine wrote:
Like in this thread, I guess:
https://marc.info/?t=16964239631&r=1&w=2
Indeed. Thanks for the link.
On Wed, Mar 20, 2024 at 09:56:06PM +0100, Kirill Miazine wrote:
> Like in this thread, I guess:
>
> https://marc.info/?t=16964239631&r=1&w=2
Yes, that is likely the issue we're hitting. Seems last message is from
10/2023 and the issue wasn't resolved :(, so I guess it's a known
problem with
• Paul B. Henson [2024-03-20 21:14]:
On 3/20/2024 9:21 AM, Zack Newman wrote:
clients in rdomain(4) 0. Last week I ran ifconfig wg1 destroy, replaced
the wgkey and wgpsk for one of the three wgpeers in the second interface,
and ran sh /etc/netstart wg1. Once I did this, the server seemingly
fr
On 3/20/2024 9:21 AM, Zack Newman wrote:
clients in rdomain(4) 0. Last week I ran ifconfig wg1 destroy, replaced
the wgkey and wgpsk for one of the three wgpeers in the second interface,
and ran sh /etc/netstart wg1. Once I did this, the server seemingly froze:
That's similar to what we see, a
• Paul B. Henson [2024-03-20 20:38]:
On 3/20/2024 1:44 AM, Kirill Miazine wrote:
actually I checked, and I do use wgpka on clients, but not on the
server -- I don't remember why I didn't...
In our case the server is on an Internet accessible address, whereas the
clients are behind a NAT fire
On 3/20/2024 1:44 AM, Kirill Miazine wrote:
actually I checked, and I do use wgpka on clients, but not on the
server -- I don't remember why I didn't...
In our case the server is on an Internet accessible address, whereas the
clients are behind a NAT firewall. We also have keepalives enabled
I have two wg(4) interfaces: one that is a site-to-site tunnel (i.e.,
exactly one wgpeer where both sides have wgendpoint configured) in
rdomain(4) 1, and another that is used as the "server" for roaming VPN
clients in rdomain(4) 0. Last week I ran ifconfig wg1 destroy, replaced
the wgkey and wgps
• Lorenz (xha) [2024-03-20 09:29]:
[...]
> > I've seen some issues too, but has not identified a reproducible pattern.
> > What I've seen, however, is that WG packets start flowing when the other end
> > of the connection pings back, so in my setup with a central VPN server I
> > make it ping all t
On Wed, Mar 20, 2024 at 08:15:55AM +0100, Kirill Miazine wrote:
> Hi there
>
> • Paul B. Henson [2024-03-20 05:40]:
> > We're using wireguard to set up VPN connections from various systems
> > deployed on-prem at customer sites to central openbsd boxes to route
> > internal traffic between the rem
Hi there
• Paul B. Henson [2024-03-20 05:40]:
We're using wireguard to set up VPN connections from various systems
deployed on-prem at customer sites to central openbsd boxes to route
internal traffic between the remote boxes and the internal network.
After a fresh reboot with a given configura
16 matches
Mail list logo
