Re: New Kernel Breaks IPFW
Ian Freislich wrote: Terry Lambert wrote: Short term, cd /usr/src/sbin/ipfw; make depend make all install ought to fix it. I tried that as well, but the new binary also dumps core, but works well with previous versions of the firewall. Even back as far as my kernel.working from May 7 2003. Bogus header files; specifically, netinet/ip_fw.h. Because you can't build world, you are compiling the ipfw program with the old system include files instead of the new ones. You may also be missing a cvs update on the ipfw sources themselves (specifically, ipfw2.c). No, it did compile ipfw2.c (r1.24). I also installed all new includes before I compiled ipfw and re-worlding to no avail. I figured an old kernel with a working firewall was better than a new kernel with no firewall. No. The problem is that you compiled ipfw2.c with the header /usr/include/netinet/ip_fw.h, and not /usr/src/netinet/ip_fw.h. The way you get the new header is to install it, and as you noticed, that doesn't work. Alternately, you can specify a CFLAGS=-I/usr/src, and it will get the header that matches your kernel. Since the buildworld is a simple fix (back out the changes to the .mk file before trying to build), you should do that, instead. -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New Kernel Breaks IPFW
Ian Freislich wrote: Andre Guibert de Bruet wrote: Ian, The new ipfw binary will work with an up-to-date kernel. What you need to do is boot this new kernel and only then try out the new ipfw binary. That doesn't really explain why the new ipfw binary core dumped with the new kernel, but worked fine with old kernels. Now that I've removed BDECFLAGS, it seems that my buildworld will succeed and whatever it was that was broken that ipfw linked in (statically) will hopefully be fixed and all will be good in my land of -CURRENT, for the moment that is. It was the wrong header file; I said that before. When world is built, it uses the chroot installed header files that come from /usr/src/include; when you build an individual command in situ, it uses the old, stale, evil, nasty, bad, wrong header files from /usr/include. -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New Kernel Breaks IPFW
Daniel C. Sobral wrote: John Stockdale wrote: Hey everyone, I just cvsup'd my src today and was going to buildworld later tonight but when I installed the newly built kernel with IPFIREWALL etc. and rebooted, ipfw fell over, specifically, even after ipfw firewall enable, an ipfw show resulted in a core dump. If its useful, I can post the ipfw core dump. Any ideas why this is? Probably because the ABI between ipfw(8) and it's kernel counterpart has changed. Since you failed to follow the safe path of upgrade (mergemaster -p, builworld, buildkernel, installkernel, reboot -s (fall back in case of problems), mount fs and installkernel, mergemaster), this sort of things can happen. Alas make buildworld fails for the past few days: === usr.sbin/config snip In file included from config.c:1: /usr/include/stdlib.h:102: conflicting types for `restrict' /usr/include/stdlib.h:102: previous declaration of `restrict' /usr/include/stdlib.h:102: warning: redundant redeclaration of `restrict' in same scope /usr/include/stdlib.h:102: warning: previous declaration of `restrict' /usr/include/stdlib.h:103: conflicting types for `restrict' snip (and also stdio.h, string.h, sys/types.h, select.h) Someone posted a link to the failure that I get, so I'll crib: http://www.0xfce3.net/error.txt Granted, that rather laborious process is usually unnecessary. I, myself, often use only buildworld, kernel, installworld, mergemaster and then reboot. And, of course, I'm fully prepared to take Murphy's Revenge upon my shoulder if these simple steps fail to yield a working system (a broken kernel, for instance, with a new world incompatible with the previous kernel). Short term, cd /usr/src/sbin/ipfw; make depend make all install ought to fix it. I tried that as well, but the new binary also dumps core, but works well with previous versions of the firewall. Even back as far as my kernel.working from May 7 2003. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New Kernel Breaks IPFW
Ian Freislich wrote: Alas make buildworld fails for the past few days: === usr.sbin/config snip In file included from config.c:1: /usr/include/stdlib.h:102: conflicting types for `restrict' /usr/include/stdlib.h:102: previous declaration of `restrict' /usr/include/stdlib.h:102: warning: redundant redeclaration of `restrict' in same scope /usr/include/stdlib.h:102: warning: previous declaration of `restrict' /usr/include/stdlib.h:103: conflicting types for `restrict' snip (and also stdio.h, string.h, sys/types.h, select.h) From sys/cdefs.h: - /* * GCC 2.95 provides `__restrict' as an extension to C90 to support the * C99-specific `restrict' type qualifier. We happen to use `__restrict' as * a way to define the `restrict' type qualifier without disturbing older * software that is unaware of C99 keywords. */ #if !(__GNUC__ == 2 __GNUC_MINOR__ == 95) #if __STDC_VERSION__ 199901 #define __restrict #else #define __restrict restrict #endif #endif - The stdlib.h hasn't changed in over two months; sys/cdefs.h hasn't changed in about 7 weeks. Apparently, someone hosed the compiler flags. Looking at your cribbed link: Someone posted a link to the failure that I get, so I'll crib: http://www.0xfce3.net/error.txt We see: cc -O -pipe -std=iso9899:1999 -I/usr/obj/usr/src/i386/legacy/usr/include -static -L/usr/obj/usr/src/i386/legacy/usr/lib -o xinstall xinstall.o -legacy Works. cc -O -pipe -I. -I/usr/src/usr.sbin/config -W -Wall -ansi -pedantic -Wbad-function-cast -Wcast-align -Wcast-qual -Wchar-subscripts -Winline -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings -std=iso9899:1999 -I/usr/obj/usr/src/i386/legacy/usr/include -c config.c Hosed. I believe you'll find that it's the comobination of the compiler flags -ansi -pedantic with -std-iso9899:1999... this might be pilot error in your local make.conf, as well, since I think it turns off GNU extensions, which we apparently depend upon, but my money is on: http://www.freebsd.org/cgi/cvsweb.cgi/src/share/mk/bsd.sys.mk Version 1.29: Be C std strict on i386 and amd64 as we can. Be loose on Alpha and ia64. ...or maybe 1.25: Turn back on c99, the tree should be ready for it now. Short term, cd /usr/src/sbin/ipfw; make depend make all install ought to fix it. I tried that as well, but the new binary also dumps core, but works well with previous versions of the firewall. Even back as far as my kernel.working from May 7 2003. Bogus header files; specifically, netinet/ip_fw.h. Because you can't build world, you are compiling the ipfw program with the old system include files instead of the new ones. You may also be missing a cvs update on the ipfw sources themselves (specifically, ipfw2.c). -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New Kernel Breaks IPFW
Terry Lambert wrote: Apparently, someone hosed the compiler flags. Looking at your cribbed link: Someone posted a link to the failure that I get, so I'll crib: http://www.0xfce3.net/error.txt We see: cc -O -pipe -std=iso9899:1999 -I/usr/obj/usr/src/i386/legacy/usr/include -static -L/usr/obj/usr/src/i386/legacy/usr/lib -o xinstall xinstall.o -legacy Works. cc -O -pipe -I. -I/usr/src/usr.sbin/config -W -Wall -ansi -pedantic -Wbad-function-cast -Wcast-align -Wcast-qual -Wchar-subscripts -Winline -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings -std=iso9899:1999 -I/usr/obj/usr/src/i386/legacy/usr/include -c config.c Hmmm, BDEFLAGS. config.c appears to compile without them. Short term, cd /usr/src/sbin/ipfw; make depend make all install ought to fix it. I tried that as well, but the new binary also dumps core, but works well with previous versions of the firewall. Even back as far as my kernel.working from May 7 2003. Bogus header files; specifically, netinet/ip_fw.h. Because you can't build world, you are compiling the ipfw program with the old system include files instead of the new ones. You may also be missing a cvs update on the ipfw sources themselves (specifically, ipfw2.c). No, it did compile ipfw2.c (r1.24). I also installed all new includes before I compiled ipfw and re-worlding to no avail. I figured an old kernel with a working firewall was better than a new kernel with no firewall. Ian ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New Kernel Breaks IPFW
Ian, The new ipfw binary will work with an up-to-date kernel. What you need to do is boot this new kernel and only then try out the new ipfw binary. Regards, Andre Guibert de Bruet | Enterprise Software Consultant Silicon Landmark, LLC. | http://siliconlandmark.com/ On Tue, 10 Jun 2003, Ian Freislich wrote: Terry Lambert wrote: Apparently, someone hosed the compiler flags. Looking at your cribbed link: Someone posted a link to the failure that I get, so I'll crib: http://www.0xfce3.net/error.txt We see: cc -O -pipe -std=iso9899:1999 -I/usr/obj/usr/src/i386/legacy/usr/include -static -L/usr/obj/usr/src/i386/legacy/usr/lib -o xinstall xinstall.o -legacy Works. cc -O -pipe -I. -I/usr/src/usr.sbin/config -W -Wall -ansi -pedantic -Wbad-function-cast -Wcast-align -Wcast-qual -Wchar-subscripts -Winline -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings -std=iso9899:1999 -I/usr/obj/usr/src/i386/legacy/usr/include -c config.c Hmmm, BDEFLAGS. config.c appears to compile without them. Short term, cd /usr/src/sbin/ipfw; make depend make all install ought to fix it. I tried that as well, but the new binary also dumps core, but works well with previous versions of the firewall. Even back as far as my kernel.working from May 7 2003. Bogus header files; specifically, netinet/ip_fw.h. Because you can't build world, you are compiling the ipfw program with the old system include files instead of the new ones. You may also be missing a cvs update on the ipfw sources themselves (specifically, ipfw2.c). No, it did compile ipfw2.c (r1.24). I also installed all new includes before I compiled ipfw and re-worlding to no avail. I figured an old kernel with a working firewall was better than a new kernel with no firewall. Ian ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New Kernel Breaks IPFW
Andre Guibert de Bruet wrote: Ian, The new ipfw binary will work with an up-to-date kernel. What you need to do is boot this new kernel and only then try out the new ipfw binary. That doesn't really explain why the new ipfw binary core dumped with the new kernel, but worked fine with old kernels. Now that I've removed BDECFLAGS, it seems that my buildworld will succeed and whatever it was that was broken that ipfw linked in (statically) will hopefully be fixed and all will be good in my land of -CURRENT, for the moment that is. Ian ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New Kernel Breaks IPFW
On Tue, 10 Jun 2003, Ian Freislich wrote: Andre Guibert de Bruet wrote: The new ipfw binary will work with an up-to-date kernel. What you need to do is boot this new kernel and only then try out the new ipfw binary. That doesn't really explain why the new ipfw binary core dumped with the new kernel, but worked fine with old kernels. Now that I've removed BDECFLAGS, it seems that my buildworld will succeed and whatever it was that was broken that ipfw linked in (statically) will hopefully be fixed and all will be good in my land of -CURRENT, for the moment that is. With CFLAGS of -O -pipe and a conservative value of CPUTYPE (ie not p4), everything should be okay: It works here(tm)! ;-) Regards, Andre Guibert de Bruet | Enterprise Software Consultant Silicon Landmark, LLC. | http://siliconlandmark.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New Kernel Breaks IPFW
Try rebuilding ipfw. Ken On Mon, 9 Jun 2003, John Stockdale wrote: Hey everyone, I just cvsup'd my src today and was going to buildworld later tonight but when I installed the newly built kernel with IPFIREWALL etc. and rebooted, ipfw fell over, specifically, even after ipfw firewall enable, an ipfw show resulted in a core dump. If its useful, I can post the ipfw core dump. Any ideas why this is? Thanks -John ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New Kernel Breaks IPFW
Alas make buildworld fails for the past few days: === usr.sbin/config snip [snip] Short term, cd /usr/src/sbin/ipfw; make depend make all install ought to fix it. I tried that as well, but the new binary also dumps core, but works well with previous versions of the firewall. Even back as far as my kernel.working from May 7 2003. I have been recompiling kernel/world in a 2-10 days basis for a long time, and haven't noticed this kind of error here. I just finished a make kernel followed by a make world, actually, and everything compiled fine. ipfw works normally, too. I dunno if it's got anything to do with your scenario, but are you trying those compiles with a clean /usr/obj? Fred -- A man does not look behind the door unless he has stood there himself. -- Du Bois pgp0.pgp Description: PGP signature
Re: New Kernel Breaks IPFW
Yep got it all figured out now. I didn't realize that the interface had changed, so I built a new kernel and rebooted before an installworld and ipfw bitched at me. Lesson learnt ;) Thanks for the feedback -John Alas make buildworld fails for the past few days: === usr.sbin/config snip [snip] Short term, cd /usr/src/sbin/ipfw; make depend make all install ought to fix it. I tried that as well, but the new binary also dumps core, but works well with previous versions of the firewall. Even back as far as my kernel.working from May 7 2003. I have been recompiling kernel/world in a 2-10 days basis for a long time, and haven't noticed this kind of error here. I just finished a make kernel followed by a make world, actually, and everything compiled fine. ipfw works normally, too. I dunno if it's got anything to do with your scenario, but are you trying those compiles with a clean /usr/obj? Fred ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
New Kernel Breaks IPFW
Hey everyone, I just cvsup'd my src today and was going to buildworld later tonight but when I installed the newly built kernel with IPFIREWALL etc. and rebooted, ipfw fell over, specifically, even after ipfw firewall enable, an ipfw show resulted in a core dump. If its useful, I can post the ipfw core dump. Any ideas why this is? Thanks -John ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New Kernel Breaks IPFW
John Stockdale wrote: Hey everyone, I just cvsup'd my src today and was going to buildworld later tonight but when I installed the newly built kernel with IPFIREWALL etc. and rebooted, ipfw fell over, specifically, even after ipfw firewall enable, an ipfw show resulted in a core dump. If its useful, I can post the ipfw core dump. Any ideas why this is? Probably because the ABI between ipfw(8) and it's kernel counterpart has changed. Since you failed to follow the safe path of upgrade (mergemaster -p, builworld, buildkernel, installkernel, reboot -s (fall back in case of problems), mount fs and installkernel, mergemaster), this sort of things can happen. Granted, that rather laborious process is usually unnecessary. I, myself, often use only buildworld, kernel, installworld, mergemaster and then reboot. And, of course, I'm fully prepared to take Murphy's Revenge upon my shoulder if these simple steps fail to yield a working system (a broken kernel, for instance, with a new world incompatible with the previous kernel). Short term, cd /usr/src/sbin/ipfw; make depend make all install ought to fix it. -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca VIVO Centro Oeste Norte Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Outros: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Endless the world's turn, endless the sun's spinning Endless the quest; I turn again, back to my own beginning, And here, find rest. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
