Re: kern/188247: [PATCH] include/rpcsvc/yp_prot.h: remove typedef of bool.
On Fri, 4 Apr 2014, Yasuhiro KIMURA wrote: Description: There have been typedef of bool in rpcsvc/yp_prot.h since it is added to source tree in August 1994. But there is also definition of bool in stdbool.h, and they conflict when both headers are used. An acutual example of conflict is building Zsh on NIS client of 10.x or later. It is already repoted as following PR. ports/183253: [PATCH] shells/zsh: fail to build on 10.0-BETA1 http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/183253 While stdbool.h and bool definition in it are requirement of C99 standard, it seems bool typedef in ryp_prot.h is not necessarily required. So removing the latter is a solution. rpc seems to have been only partly converted from using bool to using bool_t. There are some reasons that removing bool typedef from yp_prot.h doesn't seems to cause problem. Many places still use bool. E.g.: rpc/rpcb_prot.x rpcsvc/klm_prot.x rpcsvc/nfx_prot.x rpcsvc/nis.x rpcsvc/nis_callback.x rpcsvc/nlm_prot.x rpcsvc/rquota.x rpcsvc/yp.x rpcsvc/ypprot.h (this definition) rpcsvc/ypxfrd.x None of these places include stdbool.h, and neither does your patch, so it is unclear how anything works. * Building and installing FreeBSD seems to work fine without it. I applied attached patch to 8.4-RELEASE, 9.2-RELEASE and 10.0-RELEASE source tree and tried regular rebuilding steps described in /usr/src/Makefile. All rebuild succeeded without error, and all of reinstalled systems seems to work fine. * NetBSD have already removed it in October 2007, and since then they have been done well. --- patch-src_include_rpcsvc_yp_prot.h begins here --- Index: include/rpcsvc/yp_prot.h === --- include/rpcsvc/yp_prot.h(revision 260673) +++ include/rpcsvc/yp_prot.h(working copy) @@ -67,11 +67,6 @@ * YPPROC_MAPLIST takes (char *), returns (struct ypmaplist *). */ -#ifndef BOOL_DEFINED -typedef u_int bool; -#define BOOL_DEFINED -#endif - /* Program and version symbols, magic numbers */ #define YPPROG ((u_long)14) --- patch-src_include_rpcsvc_yp_prot.h ends here --- Including stdbool.h should work in most cases, but the standard bool can be almost anything. It might have a different size. Then there might be ABI breakage from using it. The fake version in stdbool.h for compilers that don't support it has type int. This has the same size, but different signedness. Bruce ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/188247: [PATCH] include/rpcsvc/yp_prot.h: remove typedef of bool.
The following reply was made to PR kern/188247; it has been noted by GNATS. From: Bruce Evans To: Yasuhiro KIMURA Cc: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: kern/188247: [PATCH] include/rpcsvc/yp_prot.h: remove typedef of bool. Date: Fri, 4 Apr 2014 18:57:41 +1100 (EST) On Fri, 4 Apr 2014, Yasuhiro KIMURA wrote: >> Description: > > There have been typedef of bool in rpcsvc/yp_prot.h since it > is added to source tree in August 1994. But there is also > definition of bool in stdbool.h, and they conflict when both > headers are used. An acutual example of conflict is building > Zsh on NIS client of 10.x or later. It is already repoted as > following PR. > > ports/183253: [PATCH] shells/zsh: fail to build on 10.0-BETA1 > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/183253 > > While stdbool.h and bool definition in it are requirement of > C99 standard, it seems bool typedef in ryp_prot.h is not > necessarily required. So removing the latter is a solution. rpc seems to have been only partly converted from using bool to using bool_t. > There are some reasons that removing bool typedef from > yp_prot.h doesn't seems to cause problem. Many places still use bool. E.g.: rpc/rpcb_prot.x rpcsvc/klm_prot.x rpcsvc/nfx_prot.x rpcsvc/nis.x rpcsvc/nis_callback.x rpcsvc/nlm_prot.x rpcsvc/rquota.x rpcsvc/yp.x rpcsvc/ypprot.h (this definition) rpcsvc/ypxfrd.x None of these places include stdbool.h, and neither does your patch, so it is unclear how anything works. > * Building and installing FreeBSD seems to work fine without > it. I applied attached patch to 8.4-RELEASE, 9.2-RELEASE and > 10.0-RELEASE source tree and tried regular rebuilding steps > described in /usr/src/Makefile. All rebuild succeeded > without error, and all of reinstalled systems seems to work > fine. > * NetBSD have already removed it in October 2007, and since > then they have been done well. > > --- patch-src_include_rpcsvc_yp_prot.h begins here --- > Index: include/rpcsvc/yp_prot.h > === > --- include/rpcsvc/yp_prot.h (revision 260673) > +++ include/rpcsvc/yp_prot.h (working copy) > @@ -67,11 +67,6 @@ > * YPPROC_MAPLISTtakes (char *), returns (struct ypmaplist *). > */ > > -#ifndef BOOL_DEFINED > -typedef u_int bool; > -#define BOOL_DEFINED > -#endif > - > /* Program and version symbols, magic numbers */ > > #define YPPROG ((u_long)14) > --- patch-src_include_rpcsvc_yp_prot.h ends here --- Including stdbool.h should work in most cases, but the standard bool can be almost anything. It might have a different size. Then there might be ABI breakage from using it. The fake version in stdbool.h for compilers that don't support it has type int. This has the same size, but different signedness. Bruce ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
kern/188253: ICMP / NAT issues using pf on -CURRENT
>Number: 188253 >Category: kern >Synopsis: ICMP / NAT issues using pf on -CURRENT >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Apr 04 08:30:02 UTC 2014 >Closed-Date: >Last-Modified: >Originator: Daniel Engberg >Release:FreeBSD 11.0-CURRENT >Organization: >Environment: FreeBSD miyuki.pyret.net 11.0-CURRENT FreeBSD 11.0-CURRENT #2 r263658: Sun Mar 23 12:06:39 CET 2014 dii...@miyuki.pyret.net:/usr/obj/usr/src/sys/MIYUKI amd64 >Description: Sent to mailing-list back in February, bug confirmed by other user. http://lists.freebsd.org/pipermail/freebsd-pf/2014-February/007300.html http://lists.freebsd.org/pipermail/freebsd-pf/2014-March/007327.html r261486 and r263658 experiences the same issues >How-To-Repeat: Enable NAT and try to use ICMP ping on a client behind NAT >Fix: >Release-Note: >Audit-Trail: >Unformatted: ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: misc/186412: WITHOUT_NIS support for ObsoleteFiles.inc
The following reply was made to PR misc/186412; it has been noted by GNATS. From: Volodymyr Kostyrko To: bug-follo...@freebsd.org, "freebsd-sta...@freebsd.org" Cc: Subject: Re: misc/186412: WITHOUT_NIS support for ObsoleteFiles.inc Date: Fri, 04 Apr 2014 17:05:59 +0300 Hi all. 8 weeks passed since this was patched at HEAD and there are requests present to MFC this one. This will fix python builds misdetecting the NIS if it's not updated. Can someone help please? -- Sphinx of black quartz, judge my vow. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: misc/186412: commit references a PR
The following reply was made to PR misc/186412; it has been noted by GNATS.
From: dfil...@freebsd.org (dfilter service)
To: bug-follo...@freebsd.org
Cc:
Subject: Re: misc/186412: commit references a PR
Date: Fri, 4 Apr 2014 14:18:53 + (UTC)
Author: emaste
Date: Fri Apr 4 14:18:37 2014
New Revision: 264116
URL: http://svnweb.freebsd.org/changeset/base/264116
Log:
MFC r261521 by antoine: Add files to remove WITHOUT_NIS
PR: misc/186412
Sponsored by:The FreeBSD Foundation
Modified:
stable/10/tools/build/mk/OptionalObsoleteFiles.inc
Directory Properties:
stable/10/ (props changed)
Modified: stable/10/tools/build/mk/OptionalObsoleteFiles.inc
==
--- stable/10/tools/build/mk/OptionalObsoleteFiles.inc Fri Apr 4 13:35:36
2014(r264115)
+++ stable/10/tools/build/mk/OptionalObsoleteFiles.inc Fri Apr 4 14:18:37
2014(r264116)
@@ -3278,9 +3278,60 @@ OLD_FILES+=usr/bin/nc
OLD_FILES+=usr/share/man/man1/nc.1.gz
.endif
-#.if ${MK_NIS} == no
-# to be filled in
-#.endif
+.if ${MK_NIS} == no
+OLD_FILES+=usr/bin/ypcat
+OLD_FILES+=usr/bin/ypchfn
+OLD_FILES+=usr/bin/ypchpass
+OLD_FILES+=usr/bin/ypchsh
+OLD_FILES+=usr/bin/ypmatch
+OLD_FILES+=usr/bin/yppasswd
+OLD_FILES+=usr/bin/ypwhich
+OLD_FILES+=usr/include/ypclnt.h
+OLD_FILES+=usr/lib/libypclnt.a
+OLD_FILES+=usr/lib/libypclnt.so
+OLD_LIBS+=usr/lib/libypclnt.so.4
+OLD_FILES+=usr/lib/libypclnt_p.a
+.if ${TARGET_ARCH} == "amd64" || ${TARGET_ARCH} == "powerpc64"
+OLD_FILES+=usr/lib32/libypclnt.a
+OLD_FILES+=usr/lib32/libypclnt.so
+OLD_LIBS+=usr/lib32/libypclnt.so.4
+OLD_FILES+=usr/lib32/libypclnt_p.a
+.endif
+OLD_FILES+=usr/libexec/mknetid
+OLD_FILES+=usr/libexec/yppwupdate
+OLD_FILES+=usr/libexec/ypxfr
+OLD_FILES+=usr/sbin/rpc.yppasswdd
+OLD_FILES+=usr/sbin/rpc.ypupdated
+OLD_FILES+=usr/sbin/rpc.ypxfrd
+OLD_FILES+=usr/sbin/yp_mkdb
+OLD_FILES+=usr/sbin/ypbind
+OLD_FILES+=usr/sbin/ypinit
+OLD_FILES+=usr/sbin/yppoll
+OLD_FILES+=usr/sbin/yppush
+OLD_FILES+=usr/sbin/ypserv
+OLD_FILES+=usr/sbin/ypset
+OLD_FILES+=usr/share/man/man1/ypcat.1.gz
+OLD_FILES+=usr/share/man/man1/ypchfn.1.gz
+OLD_FILES+=usr/share/man/man1/ypchpass.1.gz
+OLD_FILES+=usr/share/man/man1/ypchsh.1.gz
+OLD_FILES+=usr/share/man/man1/ypmatch.1.gz
+OLD_FILES+=usr/share/man/man1/yppasswd.1.gz
+OLD_FILES+=usr/share/man/man1/ypwhich.1.gz
+OLD_FILES+=usr/share/man/man5/netid.5.gz
+OLD_FILES+=usr/share/man/man8/mknetid.8.gz
+OLD_FILES+=usr/share/man/man8/rpc.yppasswdd.8.gz
+OLD_FILES+=usr/share/man/man8/rpc.ypxfrd.8.gz
+OLD_FILES+=usr/share/man/man8/yp_mkdb.8.gz
+OLD_FILES+=usr/share/man/man8/ypbind.8.gz
+OLD_FILES+=usr/share/man/man8/ypinit.8.gz
+OLD_FILES+=usr/share/man/man8/yppoll.8.gz
+OLD_FILES+=usr/share/man/man8/yppush.8.gz
+OLD_FILES+=usr/share/man/man8/ypserv.8.gz
+OLD_FILES+=usr/share/man/man8/ypset.8.gz
+OLD_FILES+=usr/share/man/man8/ypxfr.8.gz
+OLD_FILES+=var/yp/Makefile
+OLD_FILES+=var/yp/Makefile.dist
+.endif
#.if ${MK_NLS} == no
# to be filled in
___
svn-src-...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: misc/186412: commit references a PR
The following reply was made to PR misc/186412; it has been noted by GNATS.
From: dfil...@freebsd.org (dfilter service)
To: bug-follo...@freebsd.org
Cc:
Subject: Re: misc/186412: commit references a PR
Date: Fri, 4 Apr 2014 14:42:46 + (UTC)
Author: emaste
Date: Fri Apr 4 14:42:43 2014
New Revision: 264117
URL: http://svnweb.freebsd.org/changeset/base/264117
Log:
MFC r261521 by antoine: Add files to remove WITHOUT_NIS
PR: misc/186412
Sponsored by:The FreeBSD Foundation
Modified:
stable/9/tools/build/mk/OptionalObsoleteFiles.inc
Directory Properties:
stable/9/tools/build/ (props changed)
Modified: stable/9/tools/build/mk/OptionalObsoleteFiles.inc
==
--- stable/9/tools/build/mk/OptionalObsoleteFiles.inc Fri Apr 4 14:18:37
2014(r264116)
+++ stable/9/tools/build/mk/OptionalObsoleteFiles.inc Fri Apr 4 14:42:43
2014(r264117)
@@ -2935,9 +2935,60 @@ OLD_FILES+=usr/bin/nc
OLD_FILES+=usr/share/man/man1/nc.1.gz
.endif
-#.if ${MK_NIS} == no
-# to be filled in
-#.endif
+.if ${MK_NIS} == no
+OLD_FILES+=usr/bin/ypcat
+OLD_FILES+=usr/bin/ypchfn
+OLD_FILES+=usr/bin/ypchpass
+OLD_FILES+=usr/bin/ypchsh
+OLD_FILES+=usr/bin/ypmatch
+OLD_FILES+=usr/bin/yppasswd
+OLD_FILES+=usr/bin/ypwhich
+OLD_FILES+=usr/include/ypclnt.h
+OLD_FILES+=usr/lib/libypclnt.a
+OLD_FILES+=usr/lib/libypclnt.so
+OLD_LIBS+=usr/lib/libypclnt.so.4
+OLD_FILES+=usr/lib/libypclnt_p.a
+.if ${TARGET_ARCH} == "amd64" || ${TARGET_ARCH} == "powerpc64"
+OLD_FILES+=usr/lib32/libypclnt.a
+OLD_FILES+=usr/lib32/libypclnt.so
+OLD_LIBS+=usr/lib32/libypclnt.so.4
+OLD_FILES+=usr/lib32/libypclnt_p.a
+.endif
+OLD_FILES+=usr/libexec/mknetid
+OLD_FILES+=usr/libexec/yppwupdate
+OLD_FILES+=usr/libexec/ypxfr
+OLD_FILES+=usr/sbin/rpc.yppasswdd
+OLD_FILES+=usr/sbin/rpc.ypupdated
+OLD_FILES+=usr/sbin/rpc.ypxfrd
+OLD_FILES+=usr/sbin/yp_mkdb
+OLD_FILES+=usr/sbin/ypbind
+OLD_FILES+=usr/sbin/ypinit
+OLD_FILES+=usr/sbin/yppoll
+OLD_FILES+=usr/sbin/yppush
+OLD_FILES+=usr/sbin/ypserv
+OLD_FILES+=usr/sbin/ypset
+OLD_FILES+=usr/share/man/man1/ypcat.1.gz
+OLD_FILES+=usr/share/man/man1/ypchfn.1.gz
+OLD_FILES+=usr/share/man/man1/ypchpass.1.gz
+OLD_FILES+=usr/share/man/man1/ypchsh.1.gz
+OLD_FILES+=usr/share/man/man1/ypmatch.1.gz
+OLD_FILES+=usr/share/man/man1/yppasswd.1.gz
+OLD_FILES+=usr/share/man/man1/ypwhich.1.gz
+OLD_FILES+=usr/share/man/man5/netid.5.gz
+OLD_FILES+=usr/share/man/man8/mknetid.8.gz
+OLD_FILES+=usr/share/man/man8/rpc.yppasswdd.8.gz
+OLD_FILES+=usr/share/man/man8/rpc.ypxfrd.8.gz
+OLD_FILES+=usr/share/man/man8/yp_mkdb.8.gz
+OLD_FILES+=usr/share/man/man8/ypbind.8.gz
+OLD_FILES+=usr/share/man/man8/ypinit.8.gz
+OLD_FILES+=usr/share/man/man8/yppoll.8.gz
+OLD_FILES+=usr/share/man/man8/yppush.8.gz
+OLD_FILES+=usr/share/man/man8/ypserv.8.gz
+OLD_FILES+=usr/share/man/man8/ypset.8.gz
+OLD_FILES+=usr/share/man/man8/ypxfr.8.gz
+OLD_FILES+=var/yp/Makefile
+OLD_FILES+=var/yp/Makefile.dist
+.endif
#.if ${MK_NLS} == no
# to be filled in
___
svn-src-...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: misc/186412: WITHOUT_NIS support for ObsoleteFiles.inc
The following reply was made to PR misc/186412; it has been noted by GNATS. From: Sean Bruno To: Volodymyr Kostyrko Cc: bug-follo...@freebsd.org, "freebsd-sta...@freebsd.org" Subject: Re: misc/186412: WITHOUT_NIS support for ObsoleteFiles.inc Date: Fri, 04 Apr 2014 07:50:16 -0700 --=-+gtsuUSmEjrGGyMB1eBW Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2014-04-04 at 17:05 +0300, Volodymyr Kostyrko wrote: > misc/186412 It looks like emaste has MFC'd this to 10. Should it go to 9 as well? sean --=-+gtsuUSmEjrGGyMB1eBW Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAABAgAGBQJTPsaoAAoJEBkJRdwI6BaHYTIH/3lhU9ggK2/kN3asBQHpgoBi y4CwKHuWAt/SujP7Mf61sgNGV/wVbYAO2+WC/jQbmepDGJkQ5MAH4YjLSzWarxxm D5vOJyMsmLOSbhgOnv1HQMp76OQaz6CID9Y1rqOM6iVZk2rfLkHqW0w2xPSMkgJi 9kn+1StoczOhc8poDtosRxPvrd3MUHme6O6vPaBU+x/hJ8uvTbNWIdjPXFBo3Ch3 jQxtT1vOzvsaZ7s2ZSmH5SdZzP22PJVHp8v4G2Z/Q5R251XZW+hHXnPB3o3h2mqu MCdZf6owzv9pw22cgLOvFp7Oto7TsV4n6KgWDsGM0tvrv32vbVNBUI0Rqga9vAM= =xoKo -END PGP SIGNATURE- --=-+gtsuUSmEjrGGyMB1eBW-- ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: misc/186412: WITHOUT_NIS support for ObsoleteFiles.inc
Synopsis: WITHOUT_NIS support for ObsoleteFiles.inc State-Changed-From-To: patched->closed State-Changed-By: emaste State-Changed-When: Fri Apr 4 15:07:37 UTC 2014 State-Changed-Why: Committed to stable/10 (r264116) and stable/9 (r264117) http://www.freebsd.org/cgi/query-pr.cgi?pr=186412 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
misc/188261: FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.
>Number: 188261 >Category: misc >Synopsis: FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen >PV guests on same Dom0 Host. >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Apr 04 15:30:00 UTC 2014 >Closed-Date: >Last-Modified: >Originator: Karl Pielorz >Release:9.2-STABLE / 10.0-RELEASE >Organization: >Environment: FreeBSD host 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789 : Thu Jan 16 22:34:59 UTC 2014r...@snap.freebsd.org/usr/obj/usr/src/sys/GENERIC amd64 >Description: When running FreeBSD under Xen as a DomU guest - a PVHVM based FreeBSD machine cannot route traffic for any other PV based DomU guests on the same Xen Dom0. >How-To-Repeat: Install XenServer 6.2. Install FreeBSD 9.2 / 10.0 as a DomU guest, using the PVHVM (so you end up with a NIC called 'xn0' etc.) Set this first machine up with (for example) 'gateway_enable="YES"' etc. and configure it to route or NAT traffic to the Internet. Install another DomU guest (e.g. FreeBSD again, or Windows) on the same XenServer. Make the default gateway of the 2nd DomU the IP of the first DomU. Even though the fist DomU machine can fetch data/route traffic to/from "The Internet" - the second DomU machine cannot use it as a gateway. Pings will work, TCP sessions will initially 'connect' but cannot exchange any traffic. If you replace the 'router' DomU machine with say a Linux box (or Windows box) it works as expected. Only FreeBSD in PVHVM mode does not work as the gateway. >Fix: To fix the problem either: - Replace the DomU router machine with a Linux guest (not ideal!) - Drop the DomU router machine into HVM mode (i.e. xn0 etc. get replaced by rl0 et'al) - Drop the other DomU guests from PV/PVHVM mode down to HVM mode (this also appears to fix the problem!) - Move the DomU router machine to a different XenServer, even if it's in the same pool (problem only happens if the DomU router machine, and the DomU guest trying to use it as a gateway are on the same physical Xen Dom0 host). None of these solutions are ideal - it's basically precluding you from running a 'gateway' machine on XenServer unless it's either cited on it's own pool - or not efficient (i.e. HVM mode only) - which in turn makes it non-agile. >Release-Note: >Audit-Trail: >Unformatted: ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/188032: IPv6 on lo never leaves 'tentative' state if configured with prefixlen 128
The following reply was made to PR kern/188032; it has been noted by GNATS. From: Darren Baginski To: Andrey V. Elsukov , "freebsd-gnats-sub...@freebsd.org" Cc: Subject: Re: kern/188032: IPv6 on lo never leaves 'tentative' state if configured with prefixlen 128 Date: Fri, 04 Apr 2014 21:18:23 +0400 I do configure IPv6, output clearly says that, and more specifically I configure it with /128. Let me show again again: case A, getting 'tentative' # ifconfig lo8 create # ifconfig lo8 up # ifconfig lo8 inet6 fc00::ff prefixlen 128 <- configuring IPv6 address with /128 prefix case B, all good, NO 'tentative' # ifconfig lo8 create # ifconfig lo8 up # ifconfig lo8 inet6 fc00::ff prefixlen 127 <- configuring IPv6 address with /127 prefix On FreeBSD 7.x, 8.x, 9.x case A works, while on 10.x interface is stuck in `tentative` permanently. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/188032: IPv6 on lo never leaves 'tentative' state if configured with prefixlen 128
The following reply was made to PR kern/188032; it has been noted by GNATS. From: "Andrey V. Elsukov" To: Darren Baginski , "freebsd-gnats-sub...@freebsd.org" Cc: Subject: Re: kern/188032: IPv6 on lo never leaves 'tentative' state if configured with prefixlen 128 Date: Fri, 04 Apr 2014 21:25:47 +0400 On 04.04.2014 21:18, Darren Baginski wrote: > I do configure IPv6, output clearly says that, and more specifically I > configure it with /128. > Let me show again again: > > case A, getting 'tentative' > # ifconfig lo8 create > # ifconfig lo8 up > # ifconfig lo8 inet6 fc00::ff prefixlen 128 <- configuring > IPv6 address with /128 prefix > > case B, all good, NO 'tentative' > # ifconfig lo8 create > # ifconfig lo8 up > # ifconfig lo8 inet6 fc00::ff prefixlen 127 <- configuring IPv6 > address with /127 prefix > > On FreeBSD 7.x, 8.x, 9.x case A works, while on 10.x interface is stuck in > `tentative` permanently. I described why this works as you see in the first message. There are number of configuration variables related to IPv6 configuration. I.e. ipv6_enable, ipv6_activate_all_interfaces, ifconfig_xxx_ipv6. These variables controls behavior of the system when new interface will appears. You can read /etc/network.subr and you will see that presence of IFDISABLED flag depends from these variables. -- WBR, Andrey V. Elsukov ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
kern/188270: mpt unable to communicate with LSI7202XP Fibrechannel
>Number: 188270 >Category: kern >Synopsis: mpt unable to communicate with LSI7202XP Fibrechannel >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Apr 04 22:00:00 UTC 2014 >Closed-Date: >Last-Modified: >Originator: Ian Allison >Release:10.0 >Organization: UBC >Environment: FreeBSD pauli 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Fri Jan 17 08:49:04 UTC 2014 r...@snap.freebsd.org:/usr/obj/powerpc.powerpc64/usr/src/sys/GENERIC64 powerpc This is a fresh install from the 10.0 CD image >Description: I'm trying to connect to an external storage shelf over fibre channel. My system is a xserve g5 and the shelf is an xserve raid. The HBA in the xserve is a PCI-X card from LSILogic, it is listed as LSI7202XP PCI-X HBA. From mpt(4) I thought this would work, but mptutil returns garbage whenever I try to configure the shelf. Here are the relevant lines from dmesg mpt0: port 0x400-0x4ff mem 0x9003-0x9003,0x9002-0x9002 irq 181 at device 3.0 on pci2 mpt0: MPI Version=1.3.2.0 mpt1: mem 0x9001-0x9001,0x9000-0x9000 irq 181 at device 3.1 on pci2 mpt1: MPI Version=1.3.2.0 And here is the output of pciconf -lv mpt0@pci1:6:3:0:class=0x0c0400 card=0x10d01000 chip=0x06261000 rev=0x81 hdr=0x00 vendor = 'LSI Logic / Symbios Logic' device = 'FC929X Fibre Channel Adapter' class = serial bus subclass = Fibre Channel mpt1@pci1:6:3:1:class=0x0c0400 card=0x10d01000 chip=0x06261000 rev=0x81 hdr=0x00 vendor = 'LSI Logic / Symbios Logic' device = 'FC929X Fibre Channel Adapter' class = serial bus subclass = Fibre Channel mptutil gives garbled results, for example the show adapter command mptutil show adapter mpt0 Adapter: Board Name: Board Assembly: Chip Name: U? Chip Revision: mptutil: mpt_read_ioc_page(2): Status: 0x2200 mptutil: mpt_read_ioc_page(6): Status: 0x2200 mpt0 Adapter: Board Name: Board Assembly: ?\H Chip Name: ?a Chip Revision: ?#0 mptutil: mpt_read_ioc_page(2): Status: 0x2200 mptutil: mpt_read_ioc_page(6): Status: 0x2200 or show drives mptutil show drives mptutil: Reading config page header failed: Status: 0x2200 mptutil: Failed to fetch volume list: Input/output error mptutil: Failed to get drive list: Input/output error I have looked at /usr/src/UPDATING but couldn't see anything, and all of my searches turned up nothing relevant. >How-To-Repeat: >From 10.0 with GENERIC kernel mptutil show adapter >Fix: >Release-Note: >Audit-Trail: >Unformatted: ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
