Hello,
I have currently a patch in review with jamie which is the current jail
maintainer and kyle evans, if anyone else could comment/review this patch :
https://reviews.freebsd.org/D26782
What has been done is the following :
Raw socket access is allowed for ICMP protocol as is required by
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248652
--- Comment #18 from Michael Muenz ---
(In reply to vistalba from comment #17)
- Install Vanilla FreeBSD12
- pkg install git
- cd /usr && git clone https://github.com/opnsense/tools
- cd tools && make update
- make kernel
You can also
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248652
--- Comment #17 from vistalba ---
(In reply to Vincenzo Maffione from comment #14)
Is there a easy way to test this on my opnsense vm with vmx interfaces. As far
as I know my netmap issue on vmx is related to this timer issue as well.
I'm
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248652
--- Comment #16 from Sylvain Galliano ---
(In reply to Vincenzo Maffione from comment #14)
Here are the results:
X520 with 1 queue
ix0: PCI Express Bus: Speed 5.0GT/s Width x8
ix0: netmap queues/slots: TX 1/2048, RX 1/2048
thanks! that's really interesting. Different from what I was expecting
but what I'd expect from
the code dropping into Fuchsia.
It's such a pity our ping doesn't support ping -T (timestamps)
but Linux does and I'd love to see [(Linux) 'ping -T tsandaddr
{machine B}'] >[FreeBSD A] ->
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
Can someone send me the output of a ping -R , starting with FreeBSD
machine, through a second FreeBSD machine and bouncing back from a
third FreeBSD machine? I don't have three in a row like that
anywhere. Probably best to send it back through the list so I people
can see if i get an answer.
