Re: kern/177032: [arge] arge1 fails to attach on UBNT Routerstation
please reassign this to -mips, thanks! adrian On 26 March 2013 18:52, wrote: > Old Synopsis: arge1 fails to attach on UBNT Routerstation > New Synopsis: [arge] arge1 fails to attach on UBNT Routerstation > > Responsible-Changed-From-To: freebsd-bugs->freebsd-net > Responsible-Changed-By: linimon > Responsible-Changed-When: Wed Mar 27 01:51:56 UTC 2013 > Responsible-Changed-Why: > Over to -net, although it should possibly be on -mips. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=177032 > ___ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: kern/177362: [netinet] [patch] Wrong control used to return TOS
The following reply was made to PR kern/177362; it has been noted by GNATS. From: Michael Tuexen To: bug-follo...@freebsd.org, ma...@isc.org Cc: Subject: Re: kern/177362: [netinet] [patch] Wrong control used to return TOS Date: Wed, 27 Mar 2013 10:45:48 +0100 It was not done by accident. The returned cmsg_type is IP_RECVTOS = instead of IP_TOS to keep it consistent with the handling of the IP_RECVTTL socket = option. I found it more important to be consistent within the same protocol = family than across different ones. I think that unfortunately IP_RECVTOS is not defined in any standard. Best regards Michael= ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: kern/177362: [netinet] [patch] Wrong control used to return TOS
The following reply was made to PR kern/177362; it has been noted by GNATS. From: Mark Andrews To: Michael Tuexen Cc: bug-follo...@freebsd.org Subject: Re: kern/177362: [netinet] [patch] Wrong control used to return TOS Date: Wed, 27 Mar 2013 22:54:06 +1100 In message <25eb2335-645c-42ed-b90a-6d07a3328...@freebsd.org>, Michael Tuexen w rites: > It was not done by accident. The returned cmsg_type is IP_RECVTOS instead > of IP_TOS to keep it consistent with the handling of the IP_RECVTTL socket > option. > I found it more important to be consistent within the same protocol family > than across different ones. > I think that unfortunately IP_RECVTOS is not defined in any standard. > > Best regards > Michael And Linux uses IP_TOS to return the value. -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: kern/177362: [netinet] [patch] Wrong control used to return TOS
The following reply was made to PR kern/177362; it has been noted by GNATS. From: Michael Tuexen To: Mark Andrews Cc: bug-follo...@freebsd.org Subject: Re: kern/177362: [netinet] [patch] Wrong control used to return TOS Date: Wed, 27 Mar 2013 13:16:30 +0100 On Mar 27, 2013, at 12:54 PM, Mark Andrews wrote: >=20 > In message <25eb2335-645c-42ed-b90a-6d07a3328...@freebsd.org>, Michael = Tuexen w > rites: >> It was not done by accident. The returned cmsg_type is IP_RECVTOS = instead=20 >> of IP_TOS to keep it consistent with the handling of the IP_RECVTTL = socket=20 >> option. >> I found it more important to be consistent within the same protocol = family >> than across different ones. >> I think that unfortunately IP_RECVTOS is not defined in any standard. >>=20 >> Best regards >> Michael >=20 > And Linux uses IP_TOS to return the value. ... which is consistent with the IP_RECVTTL socket option on Linux, = where it returns a cmsg with cmsg_type IP_TTL, which is also different from how this is = handled in FreeBSD. I think Solaris uses for IPv4 socket options the same cmsg_type as the optname for the socket option to enable the reception of the = cmsg. So it looks like there is no standard here, Linux, FreeBSD and Solaris are each consistent with itself, but Linux does it differently from FreeBSD and Solaris. Best regards Michael >=20 > --=20 > Mark Andrews, ISC > 1 Seymour St., Dundas Valley, NSW 2117, Australia > PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org >=20 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: kern/177032: [arge] arge1 fails to attach on UBNT Routerstation
Synopsis: [arge] arge1 fails to attach on UBNT Routerstation Responsible-Changed-From-To: freebsd-net->freebsd-mips Responsible-Changed-By: linimon Responsible-Changed-When: Wed Mar 27 14:42:08 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=177032 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: kern/177417: [ip6] Invalid protocol value in ipsec6_common_input_cb
Old Synopsis: Invalid protocol value in ipsec6_common_input_cb New Synopsis: [ip6] Invalid protocol value in ipsec6_common_input_cb Responsible-Changed-From-To: freebsd-amd64->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Wed Mar 27 23:48:07 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=177417 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
ALTQ + igb(4) + 9-.1-RELEASE
I've been using igb(4) in conjunction with ALTQ under 7.x/8.x for years on hundreds of servers. I recently began upgrading my production servers to 9.1-RELEASE, with the GENERIC kernel including ALTQ support. I recently discovered the hard way that igb(4) no longer supports ALTQ. The issue is the same as presented in this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=177402 And these threads: http://lists.freebsd.org/pipermail/freebsd-net/2012-December/034091.html http://lists.freebsd.org/pipermail/freebsd-hackers/2013-January/041631.html Does anyone know if theres has been any resolution to this problem? Is it fixed in STABLE, or is there a patch I can try? I had researched this problem before migrating to 9.1-RELEASE as it seems to have been discovered during 9.1-RC3. I thought it had been fixed in -RELEASE, but apparently not? ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
