[Bug 240685] netgraph/ng_vlan_rotate: IEEE 802.1ad VLAN manipulation netgraph node type (new type)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240685 --- Comment #3 from l...@donnerhacke.de --- This node is part of an A10-NSP development. See https://www.bundesnetzagentur.de/SharedDocs/Downloads/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Breitband/NGA_NGN/NGA-Forum/aktuelledokumente/L2_BSA_II_TechSpezifikation_V10.pdf?__blob=publicationFile&v=2 Carrier networks tend to stack three or more tags for internal purposes and therefore hiding the service tags deep inside of the stack. When decomposing such an access network frame, the processing order is typically reversed: First distinguish by service, than by other means. -- 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 240685] netgraph/ng_vlan_rotate: IEEE 802.1ad VLAN manipulation netgraph node type (new type)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240685 --- Comment #4 from l...@donnerhacke.de --- Created attachment 207732 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=207732&action=edit Updated patch for share/man/man4/ng_vlan_rotate.4 I'm sorry for my errors in the man page. This is an updated version. -- 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 240685] netgraph/ng_vlan_rotate: IEEE 802.1ad VLAN manipulation netgraph node type (new type)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240685 l...@donnerhacke.de changed: What|Removed |Added Attachment #207625|0 |1 is patch|| -- 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: BBR patch on latest src, build failed.
Yes, I saw your email. As my post, I can build the kernel successfully with revision 352483. But can not build with latest src. On Mon, Sep 23, 2019 at 2:39 PM vm finance wrote: > I have successfully built BBR after checking out latest codebase. > I'm also on svn revision: 352483... > > Did you follow the steps I have outlined in previous emails on this topic? > I had to manually create a few sub-directories/copy things etc. Pls check > emails > on this last week. > > On Sat, Sep 21, 2019 at 4:01 PM hshh wrote: > >> Hi all, >> >> I patched D21582.id62213.diff to latest head src that revision 352587, >> kernel build failed. >> >> According to previous mail, I can build the kernel successfully with >> revision 352483. >> >> OS is 13.0-CURRENT amd64. >> >> Kernel config file, >> >> include GENERIC-NODEBUG >> ident hshh >> makeoptions WITH_EXTRA_TCP_STACKS=1 >> options TCPHPTS >> options RATELIMIT >> >> The error log, >> >> --- tcp_bbr.ko.full --- >> ld -m elf_x86_64_fbsd -d -warn-common --build-id=sha1 -d -warn-common >> --build-id=sha1 -d -warn-common --build-id=sha1 -d -warn-common >> --build-id=sha1 -r -d -o tcp_bbr.ko.full bbr.o sack_filter.o >> rack_bbr_common.o bbr.o sack_filter.o rack_bbr_common.o bbr.o >> sack_filter.o >> rack_bbr_common.o bbr.o sack_filter.o rack_bbr_common.o >> ld: error: duplicate symbol: __tcp_bbr >> >>> defined at bbr.c >> >>>bbr.o:(__tcp_bbr) >> >>> defined at bbr.c >> >>>bbr.o:(.data+0x8) >> Some messages similar above. >> -- >> @hshh >> ___ >> 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" >> > -- @hshh ___ 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 233952] if_jme: Does not send/receive packets after 11.2 to 12.0 upgrade
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233952 Mark Johnston changed: What|Removed |Added Assignee|n...@freebsd.org |ma...@freebsd.org -- You are receiving this mail because: You are on the CC list for the bug. 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 233952] if_jme: Does not send/receive packets after 11.2 to 12.0 upgrade
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233952 --- Comment #19 from commit-h...@freebsd.org --- A commit references this bug: Author: markj Date: Mon Sep 23 14:29:05 UTC 2019 New revision: 352625 URL: https://svnweb.freebsd.org/changeset/base/352625 Log: Revert r316820. Despite appearing correct, r316820 breaks packet rx/tx for jme(4) interfaces. With 12.1 approaching, let's just revert the commit for now. PR: 233952 Tested by:Armin Gruner MFC after:3 days Changes: head/sys/dev/jme/if_jme.c -- You are receiving this mail because: You are on the CC list 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 233952] if_jme: Does not send/receive packets after 11.2 to 12.0 upgrade
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233952 Kubilay Kocak changed: What|Removed |Added Blocks||240700 --- Comment #20 from Kubilay Kocak --- Add to 12.1-RELEASE blockers given comment 19 Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240700 [Bug 240700] [META] FreeBSD 12.1-RELEASE blockers -- You are receiving this mail because: You are on the CC list 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 236724] igb(4): Interfaces fail to switch active to inactive state
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236724 Krzysztof Galazka changed: What|Removed |Added CC||krzysztof.gala...@intel.com --- Comment #10 from Krzysztof Galazka --- Should be fixed with this patch: https://reviews.freebsd.org/D21769 -- 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"
代研缥
kfp1118薇 ___ 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 239118] iflib: Panic in ether_output_frame on ESXi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239118 Kubilay Kocak changed: What|Removed |Added Keywords|iflib, panic|crash Summary|in ESXi: Panic in |iflib: Panic in |ether_output_frame |ether_output_frame on ESXi See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=2058 ||76 Flags||mfc-stable12? Status|In Progress |Open CC||virtualizat...@freebsd.org Assignee|virtualizat...@freebsd.org |n...@freebsd.org --- Comment #17 from Kubilay Kocak --- ^Triage: - Set to more appropriate default Assignee, keep virtualization CC'd - Needs a (real) Assignee to be In Progress Once committed to head and merged, please set maintainer-approval on the attachment to ? re@f.o for an explicit approval request -- 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"
dummynet: bandwidth is limited to 2 Gbit/s ?
It seems that the userland component of ipfw/dummynet uses int for the bandwidth represented in bit/s. Also, int is used for passing that value from the userland to the kernel. What would be the best way to extend this? Just use a larger type? Or maybe add another field to try to preserve KBI backward compatibility? Thank you. -- Andriy Gapon ___ 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"
rpc.statd already ipv6 clean?
Hi everyone, Just as mentioned in [1], rpc.statd is not ipv6 clean. Although I have been through the code, and didn't found any issues until now. The code conditionally checks for ipv6/ipv4 everywhere and uses ipv6 compatible functions. As per one old commit [2], seems rpc.statd was already made to function correctly with ipv6. I searched bugzilla(thinking someone may have reported something similar, giving rise to the project), but didn't see anything similar for rpc.statd and ipv6 support. I wanted to ask if someone could share the issues they encountered while using rpc.statd with ipv6? [1] https://wiki.freebsd.org/SummerOfCodeIdeas#IPv6_Userland_Cleanup [2] https://github.com/freebsd/freebsd/commit/83a53d0868085db818fddd8cb38eecc0c39cad8d#diff-b87e28a1a8ec4fe947f72996127f8f40 Kind Regards, Mihir ___ 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"
