[Bug 227770] [run] run(4) driver does not support modification of the txpower level using ifconfig(8)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227770 Sean Bruno changed: What|Removed |Added CC||sbr...@freebsd.org --- Comment #6 from Sean Bruno --- There is no code to do this in this driver as far as I can tell. Someone would have to write it. :-( -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 229384] Can't remove address from carp
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229384 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|n...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: 'no route to host" for cloned lo1 iface 12.0-CURRENT r334376+56a973815425(master) amd64
> > > > # invalid IP
> > > >
> > > > TLDR 10.241.0.0/16 is technically not a valid host IP but it has
> > > obviously worked in the past.
Just following this up, kmacy@'s recent commits resolved this - thanks!
Finally, I came up with this, as a way of keeping the "symmetry" of the
0.0 and still if I read the RFC correctly, have a valid host IP:
# jail networks
cloned_interfaces="${cloned_interfaces} lo1"
ifconfig_lo1="inet 10.241.0.0/15" --- should be a host mask x.1.0.0
ifconfig_lo1_aliases="inet 10.241.0.1-15/32"
# ifconfig lo1
lo1: flags=8049 metric 0 mtu 16384
options=680003
inet6 ::1 prefixlen 128 tentative
inet 10.241.0.0 netmask 0xfffe
inet 10.241.0.1 netmask 0x
inet 10.241.0.2 netmask 0x
inet 10.241.0.3 netmask 0x
inet 10.241.0.4 netmask 0x
inet 10.241.0.5 netmask 0x
inet 10.241.0.6 netmask 0x
...
thanks everybody for the patches and the insight.
FWIW the alternative (original breaking config) also works again:
# jail networks
cloned_interfaces="${cloned_interfaces} lo1"
ifconfig_lo1_aliases="inet 10.241.0.1-15/15"
A+
Dave
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: unloading pf causes desktop system to freeze since ~ r335651 [solved]
On Tue, 26 Jun 2018, at 09:52, Dave Cottlehuber wrote: > > The HPET NMI watchdog patch was very timely - works a treat: > https://reviews.freebsd.org/D15630 > > > However each time there's no crashdump, & the usual ctrl-alt-esc does't > > work either. > > I bumped my /usr/src to latest HEAD, applied HPET NMI watchdog hack & > after freezing via `service pf stop`, I was rewarded with a coredump > on next reboot; full log: https://git.io/f4Q4P > > [1202] panic: Assertion !in_epoch() && ! > mtx_owned(&(&(*(__typeof(vnet_entry_tcbinfo)*) (__curthread())- > >td_vnet))->vnet_data_base) + (uintptr_t)&vnet_entry_tcbinfo)))- > >ipi_lock) failed at /usr/src/sys/netinet/tcp_input.c:802 I narrowed it down to setting this sysctl: net.inet.ip.process_options=0 # ignore IP options in the incoming packets (default 1) and it looks like it was fixed here: r335749 thanks glebius@ https://svnweb.freebsd.org/base/head/sys/netinet/tcp_subr.c?r1=335749&r2=335748&pathrev=335749 I've not had a repeat since building off this. A+ Dave ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 219428] em network driver broken in current
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219428 t...@unhooked.net changed: What|Removed |Added CC||t...@unhooked.net --- Comment #11 from t...@unhooked.net --- This started happening on a couple of my boxes as well. (optiplex 7010, lenovo thinkcentre m90p) em0: TX(0) desc avail = 41, pidx = 788 link state changed to down em0: link state changed to DOWN em0: TX(0) desc avail = 1024, pidx = 0 em0: TX(0) desc avail = 1024, pidx = 0 dell - em0@pci0:0:25:0:class=0x02 card=0x052c1028 chip=0x15028086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '82579LM Gigabit Network Connection (Lewisville)' class = network subclass = ethernet thinkcentre - em0@pci0:0:25:0:class=0x02 card=0x306017aa chip=0x10ef8086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = '82578DM Gigabit Network Connection' class = network subclass = ethernet No panic, no other messages other than "kernel out of bufferspace" I've added -tso -lro -rxcsum -txcsum to ifconfig and we'll see if it stops puking. It usually takes a couple of days to trigger it. Didn't start happening on the dell till last week. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 219428] em network driver broken in current
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219428 Matthew Macy changed: What|Removed |Added CC||mm...@nextbsd.org --- Comment #12 from Matthew Macy --- The only recent change was r335303. Can you try r335302 or prior? -M -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
