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 <LOCAL_IP> <REMOTE_IP>:4789 vnetid 1 Anyway, if the REMOTE_IP is not static, I should destroy and recreate the vlanx0 interface whenever the REMOTE_IP changes. It would not be difficult with a watchdog script in cron. But I think that, for my purposes, a wireguard configured in client/server mode is better, even with an unnecessary overhead due to encryption. I haven't tested with private LOCAL_IP or REMOTE_IP natted to public IPs. Thanks anyway, regards 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 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) > > How about vxlan(4)? > >
