Re: ping -R output?

like this? ( ping from 192.168.3.1 -> (192.168.3.2/172.16.42.1) -> 172.16.42.2 root@bsd1:~ # ping -R 172.16.42.2 PING 172.16.42.2 (172.16.42.2): 56 data bytes 64 bytes from 172.16.42.2: icmp_seq=0 ttl=63 time=1.280 ms RR: 172.16.42.1 172.16.42.2 192.168.3.2 192.168.3.1

wireguard integration D26137 connectivity test

I can confirm that the issue reported in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247853 is now resolved. Thanks Peter ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.or

wireguard integration D26137 test on 13-CURRENT r364973

I had a first look at the latest version of the wireguard kernel integration. There was some findings that may need attention. buildkernel stops with kernel option INVARIANTS enabled: --- all_subdir_if_wg --- /usr/src/sys/dev/if_wg/module/if_wg_session.c:1639:22: error: unused variable 'e' [-We

Re: ip(8) in base

From a consumer view I think we should be conservative and not add any additional commands that operates in an area where there already exists well known commands. Not sure i understand what new features you are contributing, but the sound of it i guess it has to do with IP routing and fib’s. If

Re: Wireguard kernel module

Ok!, Then I would need instructions how i get that diff in to the src tree :-) any pointers to documentation will be helpful. Thanks Peter > 25 juli 2020 kl. 12:34 skrev Goran Mekić : > > On Sat, Jul 25, 2020 at 12:32:00PM +0200, Peter Libassi wrote: >> I got information that th

Wireguard kernel module

I got information that there are work on a kernel module for Wireguard https://reviews.freebsd.org/D25425 Where can I download and test this? I have a spare amd64 currently running 13.0-CURRENT r363439 available for test purposes. /Peter

Re: somewhat reproducable vimage panic

Is this related to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234985 and https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326 /Peter > 21 juli 2020 kl. 22:23 skre