Re: panic: tcp_do_segment: sent too much

On 1/13/25 13:01, Michael Tuexen wrote: On 13. Jan 2025, at 02:44, Kyle Evans wrote: Hi, I seem to have hit this panic during normal laptop usage with a -CURRENT running at 2832af7b4ea256b18ef4dbf2ff97a50765f0609a: panic: tcp_do_segment: sent too much cpuid = 5 time = 1736731772 KDB: stack

panic: tcp_do_segment: sent too much

ring if there's anything else useful I could extract here / if anyone has a theory about what happened. Thanks, Kyle Evans

Re: How to tell if a network interface was renamed (and from what)

with an obvious group there's no clear way, AFAICT, to determine which driver created it without perusing pciconf output or whatnot and hopefully being able to associate the NICs listed with the new names (easier when there's only one NIC, of course). Kind of a pain when you're working on a remote machine that you're not at all familiar with. Thanks, Kyle Evans

domain(9) reviews

oot https://reviews.freebsd.org/D26709 - tracks protocols that have fasttimo/slowtimo callbacks so that pfslowtimo() and pffasttimo() only iterate over protocols actually known to have callbacks (very few) Thanks, Kyle Evans

Re: Client Networking Issues / NIC Lab

ed drivers then reaching out to vendors once we can demonstrate that plan field of dreams can work and drive some substantial amount of business. Thanks, Kyle Evans [0] https://reviews.freebsd.org/D18856 [1] https://reviews.freebsd.org/D19433 ___ fre

Re: source of ether address for tap0 ?

id out of the way and letting the hostid rc scripts generate and save a new one, assuming they're not getting their data from bogus/duplicate smbios uuids. Thanks, Kyle Evans ___ 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: Domain Patches

On Wed, Oct 7, 2020 at 11:45 AM Kyle Evans wrote: > > Hi, > > I have a couple of domain patches in review, if anyone would like to > comment/review the area: > > https://reviews.freebsd.org/D25062 adds a dom_probe callback so that > domains can indicate whether they shoul

Domain Patches

doing this previously is that pfslowtimo/pffasttimo have already been setup and may be called on domains that aren't completely initialized. There are some additional races re: socket creation that should be addressed, but this review should be sufficient for at least removing the warning. Than

Re: Abandoning ifnet work

On Thu, Jul 23, 2020 at 3:38 AM Hans Petter Selasky wrote: > > On 2020-07-23 05:45, Kyle Evans wrote: > > abandoning because the review process for this area is simply not > > Are you looking for this: > > https://reviews.freebsd.org/D24914 > No, not at all. The rac

Abandoning ifnet work

on of this that coordinates if_vmove() and vnet shutdown's evacuation of ifnets with if_detach() to render some of the common epair/vnet races harmless. Feel free to tag me for reviewing if you want to pick it up. Thanks, Kyle Evans [0] https://review

[Differential] D24989: netinet: Generate a random RSS key on boot.

kevans added inline comments. INLINE COMMENTS > neel_neelc.org wrote in rss_config.c:251 > I'm not sure, I'm not an expert on entropy, but we could wait for entropy > before calling this. When in doubt, perhaps CC #csprng REPOSITORY rS FreeBSD src re

Re: Bridges on VLAN-tagged interfaces.

onfiguration and performance > of the ESXi vswitch paradigm in FreeBSD if we can implement it with > this code in a reasonable fasion. > > I can provide some sample config files if desired. > I think something like [0] would do the trick, but this is only compile-tested and proba

Re: Bridges on VLAN-tagged interfaces.

function and everything goes off the rails. This is not an unsolvable problem, though, from a developer perspective. I think if_bridge(4) simply needs to be taught a little about if_vlan(4) (needs more hooks...) so that traffic coming in on re0 with a vlan that matches an if_vlan(4) interface doesn

if_bridge(4)/bpf on incoming packets

to pull a DHCP address from the em0 side of the bridge for... reasons. =) I also anticipate needing to actually monitor traffic received from the bridge by wlan0 along with traffic received on wlan0, rather than monitoring the bridge, so the above change makes this most convenient. Thanks, Kyl

Re: if_bridge(4)/bpf on incoming packets

On Sat, Mar 16, 2019 at 11:37 PM Kyle Evans wrote: > > On Sat, Mar 16, 2019 at 11:17 PM Kyle Evans wrote: > > > > Hi, > > > > Given a setup like: > > > > ifconfig bridge0 create > > ifconfig bridge0 addm em0 addm wlan0 up > > > > Pac

Re: if_bridge(4)/bpf on incoming packets

On Sat, Mar 16, 2019 at 11:17 PM Kyle Evans wrote: > > Hi, > > Given a setup like: > > ifconfig bridge0 create > ifconfig bridge0 addm em0 addm wlan0 up > > Packets coming in on em0 that get routed to wlan0 by the bridge will > not be passed over to wlan0's bpf

Re: iwn(4) association issues in 11-Stable (and maybe RC)

On Wed, Aug 24, 2016 at 2:45 PM, Glen Barber wrote: > Dumb question, but with reason. > > Does ifconfig(8) actually show wlan0 'UP'? > > I'm asking this because I'm seeing something strange locally on one > machine. > > Glen Follow up dumb question, but I've very recently experienced (with ath(4)

Re: How can I send packets to 255.255.255.255 from the command line?

Hello! Is netcat [nc(1)] an option? It doesn't seem to have any objections to doing this, but I don't have a setup to test it properly with at the moment. Thanks, Kyle Evans On Thu, Aug 18, 2016 at 2:29 PM, Ryan Stone wrote: > I want to test a change to broadcast packet handling