I decided to do a watchdog script,
vxlan works fine.
One endpoint is an old 5$ raspberry 0, its
CPU is much happier with vxlan than with wg.
Thanks again
Il giorno gio 16 nov 2023 alle 10:41 Stuart Henderson
ha scritto:
> Ah, so it's an existing upstream feature that just isn't working on
>
Ah, so it's an existing upstream feature that just isn't working on
OpenBSD yet. That wasn't clear from the earlier mails.
That could be something which is reasonable to patch in ports.
Though for your use case, I think you'll be happier with performance
of something in-kernel. If vxlan doesn't
Socat upstream tells me that they don't have resource/time
to add tun/tap support on OpenBSD.
No matter anyway.
Thanks again
Il giorno lun 13 nov 2023 alle ore 10:19 Luca Di Gregorio
ha scritto:
> I will do it.
> Anyway, a few months ago I noticed a similar issue on vlc.
> Prior 7.4, OpenBSD
Hi, with vlanx(4):
In both endpoints I can set p-t-p mode with a destination UDP port,
but I can't set what is the source UDP port to bind to.
With static IP address I tested and it works fine:
# ifconfig vxlan0 tunnel :4789 vnetid 1
Anyway, if the REMOTE_IP is not static, I should destroy and
> Linux UDP Client, start a ping but no replies received
> $ ping 192.168.74.1
>
> OpenBSD UDP Server, tcpdump -ni tun0 shows:
> 11:02:15.130291
>
> So, maybe socat doesn't know how to decode raw data received on tun0.
OpenBSD tun(4) devices always prepend the address family of the
received
Test:
OpenBSD UDP Server:
# ifconfig tun0 create
# ifconfig tun0 inet 192.168.74.1/24
# socat -d -d UDP-LISTEN:11443,reuseaddr GOPEN:/dev/tun0
2023/11/13 10:30:58 socat[31554] N listening on UDP LEN=16 AF=2
0.0.0.0:11443
2023/11/13 10:33:27 socat[31554] N accepting UDP connection from LEN=16
AF=2
I was thinking about using a more "point-to-point-oriented" method than
vxlan.
Anyway, I'll do some tests with it and let you know.
Thanks
Il giorno lun 13 nov 2023 alle ore 07:49 Stuart Henderson <
s...@spacehopper.org> ha scritto:
> On 2023/11/11 14:17, Luca Di Gregorio wrote:
> > I would like
I will do it.
Anyway, a few months ago I noticed a similar issue on vlc.
Prior 7.4, OpenBSD port didn't have the telnet interface available.
Some gentlemen here in ports@openbsd.org added it and now it's available in
7.4.
That is why I submitted the question related to socat and TUN.
Thanks
Il
On 2023/11/11 14:17, Luca Di Gregorio wrote:
> I would like to set a point to point interface encapsulating packets via
> UDP.
>
> It would be like a point to point wireguard but:
> - without authentication (I can set permissions in PF on source ip)
> - without encryption (content is already
Luca Di Gregorio writes:
> So, I installed socat with pkg_add and tried to do like this:
> http://www.dest-unreach.org/socat/doc/socat-tun.html
>
> Anyway, I see this:
> # socat UDP:1.2.3.4:11443 TUN:192.168.255.2/24,up
> 2023/11/11 14:11:27 socat[4504] E unknown device/address "TUN"
>
Have you
you would need to talk to socat upstream, because in general the ports
team do not add features
Luca Di Gregorio wrote:
> I would like to set a point to point interface encapsulating packets via
> UDP.
>
> It would be like a point to point wireguard but:
> - without authentication (I can set
I would like to set a point to point interface encapsulating packets via
UDP.
It would be like a point to point wireguard but:
- without authentication (I can set permissions in PF on source ip)
- without encryption (content is already encrypted by source application)
I can't use GIF or GRE
12 matches
Mail list logo