[Bug 245152] urndis(4) Inseego/Novatel Wireless MiFi 8800/8000 as urndis0 4g/LTE RNDIS fails to tether

2020-03-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245152 Li-Wen Hsu changed: What|Removed |Added URL||https://github.com/freebsd/

[Bug 245152] urndis(4) Inseego/Novatel Wireless MiFi 8800/8000 as urndis0 4g/LTE RNDIS fails to tether

2020-03-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245152 --- Comment #9 from rootl...@gmail.com --- I created a pull-request on Github for the snippet. Please forgive my ignorance of the most appropriate way to submit the change. Thank you for writing and maintaining this driver! -- You are re

[Bug 245152] urndis(4) Inseego/Novatel Wireless MiFi 8800/8000 as urndis0 4g/LTE RNDIS fails to tether

2020-03-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245152 --- Comment #8 from rootl...@gmail.com --- Ok. So I finished my kernel compile and rebooted with the new kernel. I didn't configure loader.local.conf to automatically load if_urndis.ko more as something else keep consistent between kernel

[Bug 245152] urndis(4) Inseego/Novatel Wireless MiFi 8800/8000 as urndis0 4g/LTE RNDIS fails to tether

2020-03-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245152 rootl...@gmail.com changed: What|Removed |Added Attachment #212920|text/x-csrc |text/plain mime type|

[Bug 245152] urndis(4) Inseego/Novatel Wireless MiFi 8800/8000 as urndis0 4g/LTE RNDIS fails to tether

2020-03-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245152 --- Comment #6 from rootl...@gmail.com --- Created attachment 212919 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=212919&action=edit dmesg of new kernel boot -- You are receiving this mail because: You are on the CC list for t

Question about rtadvd

2020-03-31 Thread Fernando Gont
Folks, I'm playing with rtadvd, and I'm curious about a debug message I'm getting when specifying Route Information options. My config file is this: - cut here em0:\ :addr="fc00:1::":prefixlen=64\ :rtprefix="fc00:1::":rtplen=64:rtltime=1000 em1:\ :addr="fc00:2::":prefixle

Re: Issue with epoch_drain_callbacks and unloading iavf(4) [using iflib]

2020-03-31 Thread Mark Johnston
On Tue, Mar 31, 2020 at 12:14:20PM -0700, Eric Joyner wrote: > Mark, > > I tried out a kernel with the tip of CURRENT with both D24214 and D24215 > applied, and I still see the problem. As well, after doing a "sysctl > debug.kdb.enter=1" and viewing the stack trace there for kldunload, it > appear

[Bug 245181] Proxy ARP (net.link.ether.inet.proxyall) does not work for FIB other than 0

2020-03-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245181 --- Comment #6 from Alexander V. Chernikov --- Yep, looking good. I've moved the patch to https://reviews.freebsd.org/D24244 . Will commit tomorrow. -- You are receiving this mail because: You are on the CC list for the bug. _

Re: Issue with epoch_drain_callbacks and unloading iavf(4) [using iflib]

2020-03-31 Thread Eric Joyner
Mark, I tried out a kernel with the tip of CURRENT with both D24214 and D24215 applied, and I still see the problem. As well, after doing a "sysctl debug.kdb.enter=1" and viewing the stack trace there for kldunload, it appears to be similar to the one I posted in my last post. - Eric On Mon, Mar

[Bug 245181] Proxy ARP (net.link.ether.inet.proxyall) does not work for FIB other than 0

2020-03-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245181 --- Comment #5 from Scott Aitken --- Created attachment 212895 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=212895&action=edit ARP FIB patch The attatched patch worked for me. Some caveats: 1) I'm not a good progranner 2) The

pf firewall on bridge member

2020-03-31 Thread peter . blok
I have difficulty filtering one member of a bridge using pf firewall net.link.bridge.pfil_member: 1 net.link.bridge.pfil_bridge: 0 Two segments are bridged, segment 'home' and segment ‘safe'. The idea for segment ’safe’ is to only allow access to the outside world with certain rules, but NO acc

[Bug 241470] dummynet: setting bandwidth and delay causes repeatable panic: mpanic: Assertion in_epoch(net_epoch_preempt)

2020-03-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241470 Kristof Provost changed: What|Removed |Added CC||k...@freebsd.org --- Comment #1