Re: CALL FOR TEST axgbe promisc mode

On 8. Oct 2024, at 14:25, Mark Johnston wrote: Maybe the firmware / hardware happens to been ( wrongly ) set to promisc mode already ? Maybe, or the driver is missing some initialization step. That would be the likeliest case although I'm not sure why exiting promisc mode doesn't turn it off

Re: CALL FOR TEST axgbe promisc mode

Hi, > On 1. Oct 2024, at 02:47, Zhenlei Huang wrote: > > The test plan is simple, either of the following should suffice: > > • Do traffic sniffing on axgbe interface. The interface will enter promisc > mode and should see packets not for us. I tested this with and without the patch and it's

leaked igmp packets on multicast cleanup

Hi, This references https://reviews.freebsd.org/D46190 as it is currently broken on FreeBSD 14.0/14.1 but fixed on main. I’m sending this because so far I got no reaction from anyone Involved. It would be nice to get this on stable/14 at least. Cheers, Franco

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

> On 21. Nov 2023, at 10:51, Ronald Klop wrote: > > Interesting. > > Is this: /usr/src/tools/tools/ifinfo ? Yes.

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

> On 20. Nov 2023, at 23:06, Mike Karels wrote: > > On 20 Nov 2023, at 15:16, Franco Fichtner wrote: > >> All that is really missing is a way to print it via ifconfig command. > > That is trivial to add; I just tested it. It also has problems with > epair. Ma

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

Nov 2023, at 22:16, Franco Fichtner wrote: > > >> On 20. Nov 2023, at 21:56, Kristof Provost wrote: >> >> I’d look in the direction of just adding a field to struct ifnet with the >> original interface name (likely easily done in if_attach()), along with a &g

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

> On 20. Nov 2023, at 21:56, Kristof Provost wrote: > > I’d look in the direction of just adding a field to struct ifnet with the > original interface name (likely easily done in if_attach()), along with a new > ioctl to retrieve that field. ifconfig_get_orig_name() already exists, but apart

Re: netstat -I ix0

> On 26. Oct 2022, at 13:11, Cristian Cardoso > wrote: > > Despite the error increments in the interface, I used the equipment for a > month until I migrated my things from the router I had and even with a large > error increment I didn't have any problems with packet loss or routing. The c

Re: Import dhcpcd(8) into FreeBSD base

Hi Roy, I appreciate your answers. More inline below. > On 8. Aug 2022, at 12:42, Roy Marples wrote: > > Both dhclient and rtsold are only activated manually. > For dhclient there is an exponential backoff after each message is sent. If > the messages go nowhere (ie LINK_STATE_DOWN) then this

Re: Import dhcpcd(8) into FreeBSD base

> On 7. Aug 2022, at 4:52 PM, Cy Schubert wrote: > > My opinion as well. I need to see a solid business case why what we have in > FreeBSD base needs to be changed and how any proposed change will benefit > all FreeBSD users, not just one depending distribution. Right now I just > don't see

Re: Import dhcpcd(8) into FreeBSD base

Hi Ben, > On 7. Aug 2022, at 11:27 AM, Ben Woods wrote: > > FreeBSD doesn’t have DHCPv6 support in base today, and therefore should > decide the best way to add it. I appreciate you’ve spent years supporting > dhcp6c and the existing tools, and we are therefore looking at this problem > space

Re: Import dhcpcd(8) into FreeBSD base

Hi Doug, > On 7. Aug 2022, at 2:15 PM, Doug Rabson wrote: > > Of course but this argument is confusing - we are talking about DHCP client, > not server. You brought up Dynamic DNS and I see now that a discussion with you is not fruitful for a multitude of reasons so I am kindly not going to r

Re: Import dhcpcd(8) into FreeBSD base

> On 7. Aug 2022, at 9:38 AM, Doug Rabson wrote: > > I'm not sure what the problem is here? I'm using dhcpcd client in my home lab > with pfsense acting as dhcp and dhcp6 server and it works great, including > prefix delegation. Choosing a new dhcp client in FreeBSD certainly doesn't > requi

Re: Import dhcpcd(8) into FreeBSD base

Hi Ben, > On 7. Aug 2022, at 7:31 AM, Ben Woods wrote: > > Reason: ensure fresh installs of FreeBSD support using DHCPv6 and prefix > delegation to obtain an IP address (not supported by dhclient or rtsold). > Having it in ports/packages could be problematic if people cannot obtain an > IPv6

Re: debugnet_any_ifnet_update: Bad dn_init result

Hi Mark, > On 28. Feb 2022, at 15:51, Mark Johnston wrote: > > Do you have any idea what triggers the message in the first place? I > haven't seen it on my igb-using systems. No but I have hardware here that does this. Short dmesg scan: # dmesg | grep igb2 igb2: port 0x4000-0x401f mem 0xf7d

debugnet_any_ifnet_update: Bad dn_init result

Hi, Looking at https://cgit.freebsd.org/src/commit/?h=65366903c3a29 and seeing it is still the case in stable/13 would it make sense to remove the printf() as it seems to be irritating users... debugnet_any_ifnet_update: Bad dn_init result from igb0 (ifp 0xf80003663800), ignoring. debugnet_a

dhclient VLAN 0 decapsulation

Hi all, We've been working on VLAN 0 decapsulation for dhclient last year and would like a wider audience for the proposed change at https://reviews.freebsd.org/D31515 Basically what is being done is extend the BPF read filter program to parse an optional VL

Re: igb(4) and VLAN issue?

Hi Kevin, [RESENT TO MAILING LIST AS SUBSCRIBER] > On 2. Aug 2021, at 7:51 PM, Kevin Bowling wrote: > > I caught wind that an igb(4) commit I've done to main and that has > been in stable/12 for a few months seems to be causing a regression on > opnsense. The commit in question is > https://cg

[Differential] D9270: Add support for user-supplied Host-Uniq tag and handle PADM messages in Netgraph PPPoE

franco_opnsense.org added a comment. Any news on this? :) REPOSITORY rS FreeBSD src repository REVISION DETAIL https://reviews.freebsd.org/D9270 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: ale, #manpages, wblock, #network, julian, mav, adrian, gl

[Differential] D9270: Add support for user-supplied Host-Uniq tag and handle PADM messages in Netgraph PPPoE

franco_opnsense.org accepted this revision. franco_opnsense.org added a comment. this one is stable, thank you @ale REPOSITORY rS FreeBSD src repository REVISION DETAIL https://reviews.freebsd.org/D9270 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To:

[Differential] D9270: Add support for user-supplied Host-Uniq tag and handle PADM messages in Netgraph PPPoE

franco_opnsense.org added a comment. No, I'm not asking for support that would take a few weeks of ping pong in a bug tracker, if any. This is real world feedback for this review. Take it or leave it. :) REPOSITORY rS FreeBSD src repository REVISION DETAIL https://reviews.freebsd.org/D9

[Differential] D9270: Add support for user-supplied Host-Uniq tag and handle PADM messages in Netgraph PPPoE

franco_opnsense.org added a comment. Thanks, but we've narrowed it down to this commit. REPOSITORY rS FreeBSD src repository REVISION DETAIL https://reviews.freebsd.org/D9270 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: ale, #manpages, wblock, #ne

[Differential] D9270: Add support for user-supplied Host-Uniq tag and handle PADM messages in Netgraph PPPoE

franco_opnsense.org added a comment. We do seem to have a persistent problem with this patch in some PPPoE environments that will cause a crash in ng_pppoe_rcvdata_ether(): https://ibb.co/mRWKHF https://ibb.co/iOxRxF https://forum.opnsense.org/index.php?topic=5697.0 Please advise

Re: Dummynet AQM v0.1- CoDel and FQ-CoDel for FreeBSD's ipfw/dummynet

> On 09 Mar 2016, at 8:58 AM, Don Lewis wrote: > > On 26 Feb, Rasool Al-Saadi wrote: >> Dear all, >> >> I would like to announce that we (myself and Grenville Armitage) released >> Dummynet AQM v0.1, which is an independent implementation of CoDel and >> FQ-CoDel for FreeBSD's ipfw/dummynet f