Re: I want copy pf.conf from FreeBSD 8.2 to OpenBSD 5 and use it
Mostaf Faridi wrote: > Thanks all guys > Sorry for my bad English I , only understand is this pf.conf work in > openbsd 5 or no .? Which part I must edit and change it > Is this pf.conf is correct ? > Thanks in advance You're doing it wrong. Three ways you could write a pf.conf for OpenBSD ... 1. ... start from scratch (start from nothing). Read the documentation that comes with that release, in this case the pf.conf man page for OpenBSD 5.0 ... http://www.openbsd.org/cgi-bin/man.cgi?query=pf.conf&sektion=5&manpath=OpenBSD+5.0 Read a vendor supplied FAQ ... for additional help ... if it relates to that release. In this case: http://www.openbsd.org/faq/pf/index.html If you are careful and do your homework you might have the odd question and then you can search the archives, do a Google, post to misc@ and so on. See here: http://www.openbsd.org/mail.html Dumping an entire pf.conf isn't part of this process. 2. ... you go from one OpenBSD release to another OpenBSD release. For example OpenBSD 4.9 to OpenBSD 5.0 ... and use this: http://www.openbsd.org/plus50.html Everything to do with pf.conf (e.g. the first item on that page) should prompt you to examine your existing rules and see if they need modifying ... referring to the pf.conf man page, which is probably good practice anyway. Note, that requires a working pf.conf from the same vendor (e.g. an existing ruleset from OpenBSD) and a willingness to follow the dots (i.e. the plus pages) ... Dumping an entire pf.conf isn't part of this process either. 3. Use a pf.conf from a different release ... and a different operating system ... You either have to track between FreeBSD then and OpenBSD now ... two different trees over however many years ... ... or track between FreeBSD then, whatever pf they imported from OpenBSD then and do method 2 over any number of OpenBSD releases ... Sometimes starting from scratch is the way to go. If you can get a new pf.conf from a FreeBSD one without too much confusion you should still understand it anyway to apply it to your real ruleset as opposed to your copy paste example ... see method 1. Regardless, dumping a large conf and asking people to "fix" it for you without any evidence you've tried yourself won't fly around here. Copy and paste administration will only lead to misery or reading man pages anyway or both ... Apart from the lack of paragraphs in your first mail your english is fine. Best wishes.
Re: 5.0 vmt0 kernel panic in Linux KVM
Am 07.11.2011 16:06, schrieb Alexander Polakov: > I don't know of an easy way to disable it but recompiling the kernel > with this: > > Index: sys/arch/i386/i386/machdep.c > === > RCS file: /cvs/src/sys/arch/i386/i386/machdep.c,v > retrieving revision 1.506 > diff -u -p -r1.506 machdep.c > --- sys/arch/i386/i386/machdep.c 2 Nov 2011 23:53:44 - 1.506 > +++ sys/arch/i386/i386/machdep.c 7 Nov 2011 15:04:49 - > @@ -1347,8 +1347,10 @@ amd_family6_setperf_setup(struct cpu_inf > k8_powernow_init(); > break; > } > +#if 0 > if (ci->ci_family >= 0x10) > k1x_init(ci); > +#endif > } > #endif Thanks! I'll try this once I have installed 5.0 on a real spare machine, cannot get a 5.0 kernel to build under 4.9, but this OT here. For the curious, though, compilation fails: ioconf.c:1049: warning: excess elements in struct initializer I also got informed that is a VM emulator bug and have therefore forwarded the bug to "upstream" k...@vger.kernel.org. Regards, Walter
how to disable fsck when power failure
misc#,Dz:C#! when the box with OpenBSD had a power failure and the system did not unmount properly. it sometimes gets stuck.The system is asking me to RUN fsck MANUALLY. as a gateway ,so i can't go to fix it manually everytime.How do I advoid this? i want to disable it crumbling to single mode. thanks. /dev/rwd0e: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY. AUTOMATIC FILE SYSTEM CHECK FAILED; HELP! Enter pathname of shell or RETURN for sh: Best Regards Cosmo Wu
Re: 5.0 vmt0 kernel panic in Linux KVM
Am 07.11.2011 16:06, schrieb Alexander Polakov: > k1x_init() is not related to vmt, it is from k1x-pstate.c, which > is cpu power state driver for K10 processors. Because of this reference, I found a workaround: Rather than running 5.0 under the host cpu (PhenomII), I emulate an older cpu (e.g. athlon). This works. Thanks! Regards, Walter
Re: how to disable fsck when power failure
On Tue, 08 Nov 2011, co...@tetrachina.com wrote: > misc#,Dz:C#! > > when the box with OpenBSD had a power failure and the system did not > unmount properly. > it sometimes gets stuck.The system is asking me to RUN fsck MANUALLY. > as a gateway ,so i can't go to fix it manually everytime.How do I advoid > this? > i want to disable it crumbling to single mode. thanks. > > /dev/rwd0e: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY. > AUTOMATIC FILE SYSTEM CHECK FAILED; HELP! > Enter pathname of shell or RETURN for sh: > > Best Regards You can try something like this patch: Index: rc === RCS file: /cvs/src/etc/rc,v retrieving revision 1.396 diff -u -p -r1.396 rc --- rc 13 Oct 2011 07:54:06 - 1.396 +++ rc 8 Nov 2011 10:08:35 - @@ -294,8 +294,16 @@ elif [ X"$1" = X"autoboot" ]; then exit 1 ;; 8) - echo "Automatic file system check failed; help!" - exit 1 + echo "File system check failed; trying fsck -y." + fsck -y + case $? in + 0) + ;; + *) + echo "Ok, now it's really fscked... " + exit 1 + ;; + esac ;; 12) echo "Boot interrupted."
Re: I want copy pf.conf from FreeBSD 8.2 to OpenBSD 5 and use it
Thanks Your 3 way is good . I choose number 3 . I have pf.conf from FreeBSD and it work good for me over 3 months. But sometimes it dose not work good , I said my problem in first email . I want only understand : is this pf.conf work great in opnbsd or no ? And I want find my mistake if I have in pf.conf I want know is this pf.conf has problems or no ? Thanks all guys help me to solve this problem On Nov 8, 2011 1:18 PM, "David Walker" wrote: > Mostaf Faridi wrote: > > Thanks all guys > > Sorry for my bad English I , only understand is this pf.conf work in > > openbsd 5 or no .? Which part I must edit and change it > > Is this pf.conf is correct ? > > Thanks in advance > > You're doing it wrong. > > Three ways you could write a pf.conf for OpenBSD ... > > 1. > ... start from scratch (start from nothing). > Read the documentation that comes with that release, in this case the > pf.conf man page for OpenBSD 5.0 ... > > http://www.openbsd.org/cgi-bin/man.cgi?query=pf.conf&sektion=5&manpath=OpenBSD+5.0 > Read a vendor supplied FAQ ... for additional help ... if it relates > to that release. > In this case: > http://www.openbsd.org/faq/pf/index.html > If you are careful and do your homework you might have the odd > question and then you can search the archives, do a Google, post to > misc@ and so on. See here: > http://www.openbsd.org/mail.html > Dumping an entire pf.conf isn't part of this process. > > 2. > ... you go from one OpenBSD release to another OpenBSD release. > For example OpenBSD 4.9 to OpenBSD 5.0 ... and use this: > http://www.openbsd.org/plus50.html > Everything to do with pf.conf (e.g. the first item on that page) > should prompt you to examine your existing rules and see if they need > modifying ... referring to the pf.conf man page, which is probably > good practice anyway. > Note, that requires a working pf.conf from the same vendor (e.g. an > existing ruleset from OpenBSD) and a willingness to follow the dots > (i.e. the plus pages) ... > Dumping an entire pf.conf isn't part of this process either. > > 3. > Use a pf.conf from a different release ... and a different operating > system ... > You either have to track between FreeBSD then and OpenBSD now ... two > different trees over however many years ... > ... or track between FreeBSD then, whatever pf they imported from > OpenBSD then and do method 2 over any number of OpenBSD releases ... > > Sometimes starting from scratch is the way to go. > > If you can get a new pf.conf from a FreeBSD one without too much > confusion you should still understand it anyway to apply it to your > real ruleset as opposed to your copy paste example ... see method 1. > > Regardless, dumping a large conf and asking people to "fix" it for you > without any evidence you've tried yourself won't fly around here. > Copy and paste administration will only lead to misery or reading man > pages anyway or both ... > > Apart from the lack of paragraphs in your first mail your english is fine. > > Best wishes.
Re: how to disable fsck when power failure
On Tue Nov 8 2011 17:41, co...@tetrachina.com wrote: > misc#,Dz:C#! > > > > when the box with OpenBSD had a power failure and the system did not > unmount properly. > > it sometimes gets stuck.The system is asking me to RUN fsck MANUALLY. > > as a gateway ,so i can't go to fix it manually everytime.How do I advoid > this? Disabling or skipping fsck(8)s is generally a very bad idea. However, you could install a UPS. Further, partition your discs properly and mount filesystems, if possible, read-only. This greatly minimises the risk of filesystem inconsistencies/corruption. Norman.
Re: how to disable fsck when power failure
On Tue, 8 Nov 2011 11:09:32 +0100 David Coppa wrote: > You can try something like this patch: > > Index: rc > === > RCS file: /cvs/src/etc/rc,v > retrieving revision 1.396 > diff -u -p -r1.396 rc > --- rc13 Oct 2011 07:54:06 - 1.396 > +++ rc8 Nov 2011 10:08:35 - > @@ -294,8 +294,16 @@ elif [ X"$1" = X"autoboot" ]; then > exit 1 > ;; > 8) > - echo "Automatic file system check failed; help!" > - exit 1 > + echo "File system check failed; trying fsck -y." > + fsck -y > + case $? in > + 0) > + ;; > + *) > + echo "Ok, now it's really fscked... " > + exit 1 > + ;; > + esac > ;; > 12) > echo "Boot interrupted." It would depend on your purpose as to whether the above was the best aproach or making the system read-only with an mfs /tmp /var? and exported logs. Something which is far easier with OpenBSD than most OS.
admin hc与您共享了照片
Good morning my friend, How are you going with your business? Hope everything goes well. I am writing to you to offer service for your printing need. We are an experienced company in printing work. We have been in printing field for many years and have many customers from various countries. Our products are of a wide variety: books, catalogs, flyers, magazines, calendars etc. We have advantages in the quality, price, service and logistics. If you have any printing work at hand, do not hesitate to tell me. We will be very glad to give you the best quotation upon receipt of your detailed requirements. Any enquiries, feel free to contact me by ad...@printinglot.com . Best wishes, Serena [demime 1.01d removed an attachment of type image/jpeg which had a name of HC.jpg]
Re: how to disable fsck when power failure
> Disabling or skipping fsck(8)s is generally a very bad idea. > > Norman. > @Norman: is it! BTW... @Cosmo Wu man 5 fstab is your friend. Quick and dirt: Edit /etc/fstab and change the last digit of the corrispondent mount point line form [1|2] to 0 Ex. default 515f3560ef6f35f5.a / ffs rw 1 1 to 515f3560ef6f35f5.a / ffs rw 1 0 Bye Matteo
Re: how to disable fsck when power failure
On Tue Nov 8 2011 12:03, Matteo Leccardi wrote: > > Disabling or skipping fsck(8)s is generally a very bad idea. > > > > Norman. > > > > @Norman: is it! BTW... > @Cosmo Wu > man 5 fstab is your friend. > Quick and dirt: Edit /etc/fstab and change the last digit of the > corrispondent mount point line form [1|2] to 0 > Ex. > default > 515f3560ef6f35f5.a / ffs rw 1 1 > to > 515f3560ef6f35f5.a / ffs rw 1 0 It must be said again, it is absolutely risky and unsafe to skip fsck(8)s for root filesystems in particular. If you have not taken any precaution to prevent or to detect a filesystem corruption, then chances are, you render your system non-operational very easily. You have the choice.
Re: I want copy pf.conf from FreeBSD 8.2 to OpenBSD 5 and use it
Mostaf Faridi wrote: > Thanks > Your 3 way is good . I choose number 3 . Please note carefully how number 3 works ... *You* either have to track between FreeBSD then and OpenBSD now ... two different trees over however many years ... ... or track between FreeBSD then, whatever pf they imported from OpenBSD then and do method 2 over any number of OpenBSD releases ... Note the asterisks - *You* Please let me know how it goes. ... method 1 is far simpler and better suited to your circumstances. If you *try* method 1 (asterisks) you'll probably get pretty far on your own and get enough help after that to get it working. One rule at a time ... Trying to do method 3 by yourself or asking others to help you or asking others to do it all for you ... is not as good as method 1 ... > I have pf.conf from FreeBSD and it > work good for me over 3 months. But sometimes it dose not work good , I > said my problem in first email . I avoided that bit. It was the lack of paragraphs. Yet you want to use it as a foundation for an OpenBSD pf.conf ... This is problematic ... maybe you could start again from scratch? See method 1 ... > I want only understand : is this pf.conf work great in opnbsd or no ? If it's designed for FreeBSD ... and doesn't work in FreeBSD ... it's not realistic to think it might somehow work in OpenBSD. I'm not sure if your english is a problem for you but you're way off course. Best wishes.
Re: I want copy pf.conf from FreeBSD 8.2 to OpenBSD 5 and use it
Thanks My problem is this I do not enough time to start from scratch and make new rule .in my work place , my boss find another person can do internet sharing with Windows 2008 and ISA and this person say he can make best internet sharing server , I said before my my pf.conf in FreeBSD work good , but sometimes some user lost internet and they can not browse web pages , but they can chat with paltalk , after reboot or disbable or enable PF this problem solve . I think I have mistakes or problems in my PF.conf . So after search in Google , I see PF version in FreeBSD is so old , so I decided move from FreeBSD to openBSD . I wish my PF work good in OpenBSD Thanks in advance. On Nov 8, 2011 3:38 PM, "David Walker" wrote: > Mostaf Faridi wrote: > > Thanks > > Your 3 way is good . I choose number 3 . > > Please note carefully how number 3 works ... > > *You* either have to track between FreeBSD then and OpenBSD now ... two > different trees over however many years ... > ... or track between FreeBSD then, whatever pf they imported from > OpenBSD then and do method 2 over any number of OpenBSD releases ... > > Note the asterisks - *You* > Please let me know how it goes. > ... method 1 is far simpler and better suited to your circumstances. > If you *try* method 1 (asterisks) you'll probably get pretty far on > your own and get enough help after that to get it working. > One rule at a time ... > > Trying to do method 3 by yourself or asking others to help you or > asking others to do it all for you ... is not as good as method 1 ... > > > I have pf.conf from FreeBSD and it > > work good for me over 3 months. But sometimes it dose not work good , I > > said my problem in first email . > > I avoided that bit. It was the lack of paragraphs. > Yet you want to use it as a foundation for an OpenBSD pf.conf ... > This is problematic ... maybe you could start again from scratch? > See method 1 ... > > > I want only understand : is this pf.conf work great in opnbsd or no ? > > If it's designed for FreeBSD ... and doesn't work in FreeBSD ... it's > not realistic to think it might somehow work in OpenBSD. > > I'm not sure if your english is a problem for you but you're way off > course. > > Best wishes.
Re: how to disable fsck when power failure
On Nov 08 12:03:33, Matteo Leccardi wrote: > Quick and dirt: Edit /etc/fstab and change the last digit of the > corrispondent mount point line form [1|2] to 0 > Ex. > default > 515f3560ef6f35f5.a / ffs rw 1 1 > to > 515f3560ef6f35f5.a / ffs rw 1 0 and run with an unclean root filesystem. Way to go!
Re: how to disable fsck when power failure
Curiosity killed the cat What I wrote is (totally unwise and) wrong. Setting 515f3560ef6f35f5.a / ffs rw 1 0 result is a system with an unclean root filesystem, mounted read-only booting in single user mode. Btw; from fstab(5) " If the sixth field is not present or is zero, a value of zero is returned and fsck(8) will assume that the filesystem does not need to be checked." Fall back to previuos post: properly partition your drive and mount filesystems, if possible, read-only. for i in 1 2 3 4 5; do echo "I'm sorry" && sleep 2; done Matteo 2011/11/8 Matteo Leccardi > > Disabling or skipping fsck(8)s is generally a very bad idea. >> >> Norman. >> > > @Norman: is it! BTW... > @Cosmo Wu > man 5 fstab is your friend. > Quick and dirt: Edit /etc/fstab and change the last digit of the > corrispondent mount point line form [1|2] to 0 > Ex. > default > 515f3560ef6f35f5.a / ffs rw 1 1 > to > 515f3560ef6f35f5.a / ffs rw 1 0 > > Bye > > Matteo
Re: I want copy pf.conf from FreeBSD 8.2 to OpenBSD 5 and use it
Mostaf Faridi wrote: > My problem is this I do not enough time to start from scratch and make new > rule . If you were moderately familiar with OpenBSD you could have, in the time between the start of this thread and now, read pf.conf for OpenBSD 5.0 and written on paper or wherever a complex ruleset. If your boss won't allocate time for this and expects you to outsource it to the web and whatever then he's doing it wrong. You don't have a good enough familiarity with OpenBSD (or FreeBSD) to know where to start. Right? If you do plan to migrate then you should build a machine, install OpenBSD 5.0, write a ruleset and test it. In your workplace, testing may mean swapping the machines until everyone complains and you swap them back and try again but doing it the way you're doing it now (no experience, asking for copy and paste administration, no testing) is wrong. > in my work place , my boss find another person can do internet > sharing with Windows 2008 and ISA and this person say he can make best > internet sharing server So you want pf on OpenBSD and don't want to see a Windows machine ... ... but you're not interested in reading about pf on OpenBSD ... Who's running the current FreeBSD machine? How come they can't understand it? Why not troubleshoot that? Etcetera ... How will swapping to a new operating system be better than using the current one which almost works? If you want to stay with FreeBSD you should at a minimum understand your current ruleset (removing any non-essential lines might be a good start) if you want to get help on it. Again though you're in the wrong place. Can you explain what every line in the pf.conf you sent is for? If not, find out, if it does nothing, delete it, whatever. Describe your network, do you have issues with DNS, do you have a http proxy, what tests have you done from clients, etcetera ... Have you looked here: http://www.freebsd.org/cgi/man.cgi?query=pfctl&sektion=8&manpath=FreeBSD+8.2-RELEASE So on and so forth. Under those circumstances, maybe Windows is the better choice. Certainly without any relevant OpenBSD experience you're better off with FreeBSD right? > I said before my my pf.conf in FreeBSD work good , but sometimes some user > lost internet and they can not browse web pages , but they can chat with > paltalk , after reboot or disbable or enable PF this problem solve . Fine. You have choices. Fix your current setup which should involve reading the FreeBSD pf.conf documentation and talking to people on the FreeBSD lists. Goodbye. Build an OpenBSD machine, in which case, talk to you when you've got a machine running and you have some more appropriate questions. People will help you. Either way you're should be willing to invest time and if you won't do that on your own and your boss doesn't want you to do it in work time then let the Windows people worry about it. Good times. Best wishes.
Unversioned files in 5.0 xenocara.tar.gz
FYI, I noticed that the 5.0 xenocara source tarball (md5 6a93f3cdcda1c22e6f65f8b978b14227) contains a number of items not found in CVS. Cursory inspection of a few files indicates they were attic'd between 4.9 and 5.0. Thanks for another great release! --david ? app/cwm/input.c ? app/iceauth/autogen.sh ? app/iceauth/iceauth.man ? app/xauth/xauth.man ? app/xkbcomp/README.config ? app/xkbcomp/README.enhancing ? app/xkbcomp/xkbcomp.man ? app/xlsclients/xlsclients.man ? app/xrdb/xrdb.man ? data/xkeyboard-config/rules/extras ? data/xkeyboard-config/symbols/extras ? dist/Mesa/progs ? dist/Mesa/include/GL/glew.h ? dist/Mesa/include/GL/glxew.h ? dist/Mesa/include/GL/wglew.h ? dist/Mesa/src/glew ? dist/xkeyboard-config/rules/extras ? dist/xkeyboard-config/symbols/extras ? doc/xorg-docs/man/general ? doc/xorg-docs/specs/Composite ? doc/xorg-docs/specs/Damage ? doc/xorg-docs/specs/FSProtocol ? doc/xorg-docs/specs/Fixes ? doc/xorg-docs/specs/GL ? doc/xorg-docs/specs/ICE ? doc/xorg-docs/specs/PM ? doc/xorg-docs/specs/RX ? doc/xorg-docs/specs/Randr ? doc/xorg-docs/specs/Render ? doc/xorg-docs/specs/SIAddresses ? doc/xorg-docs/specs/SM ? doc/xorg-docs/specs/X11 ? doc/xorg-docs/specs/XDMCP ? doc/xorg-docs/specs/XIM ? doc/xorg-docs/specs/XKB ? doc/xorg-docs/specs/XPRINT ? doc/xorg-docs/specs/XProtocol ? doc/xorg-docs/specs/Xaw ? doc/xorg-docs/specs/Xi ? doc/xorg-docs/specs/Xmu ? doc/xorg-docs/specs/Xt ? doc/xorg-docs/specs/Xv ? doc/xorg-docs/specs/XvMC ? doc/xorg-docs/specs/i18n ? doc/xorg-docs/specs/rstart ? doc/xorg-docs/specs/saver ? doc/xorg-docs/specs/xfs ? doc/xorg-docs/specs/xtrans ? doc/xorg-docs/specs/CTEXT/ctext.tbl.ms ? doc/xorg-docs/specs/ICCCM/icccm.ms ? doc/xorg-docs/specs/ICCCM/indexmacros.t ? doc/xorg-docs/specs/XLFD/xlfd.tbl.ms ? doc/xorg-docs/specs/Xext/AppGroup.mif ? doc/xorg-docs/specs/Xext/DPMS.ms ? doc/xorg-docs/specs/Xext/DPMSLib.ms ? doc/xorg-docs/specs/Xext/bigreq.ms ? doc/xorg-docs/specs/Xext/buffer.ms ? doc/xorg-docs/specs/Xext/dbe.tex ? doc/xorg-docs/specs/Xext/dbelib.tex ? doc/xorg-docs/specs/Xext/evi.ms ? doc/xorg-docs/specs/Xext/lbx.book ? doc/xorg-docs/specs/Xext/lbx.mif ? doc/xorg-docs/specs/Xext/lbxalg.mif ? doc/xorg-docs/specs/Xext/mit-shm.ms ? doc/xorg-docs/specs/Xext/record.ms ? doc/xorg-docs/specs/Xext/recordlib.ms ? doc/xorg-docs/specs/Xext/security.tex ? doc/xorg-docs/specs/Xext/shape.ms ? doc/xorg-docs/specs/Xext/shapelib.ms ? doc/xorg-docs/specs/Xext/sync.tex ? doc/xorg-docs/specs/Xext/synclib.tex ? doc/xorg-docs/specs/Xext/tog-cup.ms ? doc/xorg-docs/specs/Xext/xc-misc.ms ? doc/xorg-docs/specs/Xext/xtest.ms ? doc/xorg-docs/specs/Xext/xtest1.info ? doc/xorg-docs/specs/Xext/xtest1.mm ? doc/xorg-docs/specs/Xext/xtestlib.ms ? doc/xorg-docs/specs/Xserver/Xprt.book ? doc/xorg-docs/specs/Xserver/Xprt.mif ? doc/xorg-docs/specs/Xserver/XprtIX.doc ? doc/xorg-docs/specs/Xserver/XprtTOC.doc ? doc/xorg-docs/specs/Xserver/Xprt_cov.mif ? doc/xorg-docs/specs/Xserver/analysis.tex ? doc/xorg-docs/specs/Xserver/appgroup.ms ? doc/xorg-docs/specs/Xserver/ddx.tbl.ms ? doc/xorg-docs/specs/Xserver/fontlib.ms ? doc/xorg-docs/specs/Xserver/secint.tex ? driver/xf86-input-mouse/src/xf86OSmouse.h ? lib/freetype/docs/GPL.TXT ? lib/freetype/include/freetype/internal/pcftypes.h ? lib/libX11/m4/dolt.m4 ? lib/libX11/nls/localerules.in ? lib/libX11/nls/C/Makefile.am ? lib/libX11/nls/am_ET.UTF-8/Makefile.am ? lib/libX11/nls/armscii-8/Makefile.am ? lib/libX11/nls/el_GR.UTF-8/Makefile.am ? lib/libX11/nls/en_US.UTF-8/Makefile.am ? lib/libX11/nls/fi_FI.UTF-8/Makefile.am ? lib/libX11/nls/georgian-academy/Makefile.am ? lib/libX11/nls/georgian-ps/Makefile.am ? lib/libX11/nls/ibm-cp1133/Makefile.am ? lib/libX11/nls/iscii-dev/Makefile.am ? lib/libX11/nls/isiri-3342/Makefile.am ? lib/libX11/nls/iso8859-1/Makefile.am ? lib/libX11/nls/iso8859-10/Makefile.am ? lib/libX11/nls/iso8859-11/Makefile.am ? lib/libX11/nls/iso8859-13/Makefile.am ? lib/libX11/nls/iso8859-14/Makefile.am ? lib/libX11/nls/iso8859-15/Makefile.am ? lib/libX11/nls/iso8859-2/Makefile.am ? lib/libX11/nls/iso8859-3/Makefile.am ? lib/libX11/nls/iso8859-4/Makefile.am ? lib/libX11/nls/iso8859-5/Makefile.am ? lib/libX11/nls/iso8859-6/Makefile.am ? lib/libX11/nls/iso8859-7/Makefile.am ? lib/libX11/nls/iso8859-8/Makefile.am ? lib/libX11/nls/iso8859-9/Makefile.am ? lib/libX11/nls/iso8859-9e/Makefile.am ? lib/libX11/nls/ja/Makefile.am ? lib/libX11/nls/ja.JIS/Makefile.am ? lib/libX11/nls/ja.S90/Makefile.am ? lib/libX11/nls/ja.SJIS/Makefile.am ? lib/libX11/nls/ja.U90/Makefile.am ? lib/libX11/nls/ja_JP.UTF-8/Makefile.am ? lib/libX11/nls/ko/Makefile.am ? lib/libX11/nls/ko_KR.UTF-8/Makefile.am ? lib/libX11/nls/koi8-c/Makefile.am ? lib/libX11/nls/koi8-r/Makefile.am ? lib/libX11/nls/koi8-u/Makefile.am ? lib/libX11/nls/microsoft-cp1251/Makefile.am ? lib/libX11/nls/microsoft-cp1255/Makefile.am ? lib/libX11/nls/microsoft-cp1256/Makefile.am ? lib/libX11/nls/mulelao-1/Makefile.am ? lib/libX11/nls/nokhchi-1/Makefile.am ? lib/libX11/nls/pt_BR.UTF-8/Makefile.am ? lib/libX11/nls/ru_
Re: OpenSMTPD and aliases
Hi all, I was hoping someone on the list could confirm for me what the proper format for the ~/.forward file is for use with procmail (and OpenSMTPd on OpenBSD). Currently I have ~/.forward | /usr/local/bin/procmail but other information I've seen says it should be "|IFS=' ' && exec /usr/local/bin/procmail || exit 75 #your_user_name" Which is correct, or is there a different format altogether that I should be using? --- Some context of why I ask about this: - yes, I'm a procmail newbie. - I've seen my current ~/.forward file (the first version above) works as expected when mail is sent to an individual user, however when I define an alias for OpenSMTPd that points to a list of users, mail sent to the alias is delivered to only a subset of intended recipients. So for an alias like: mylist: us...@example.com, us...@example.com, us...@example.com,us...@example.com An email to myl...@example.com will be alias expanded correctly by OpenSMTPd, but only some of the users in the list will actually get the mail (the users WITHOUT .forward file reliably get the mail, and ONLY ONE of the users WITH a .forward file gets it) I'm not sure how to work around this. Perhaps my .forward files contain the wrong invocation of procmail, or there is a bug in (my version of) OpenSMTPd. Any comments would be appreciated. :-) Sarah
Re: OpenSMTPD and aliases
Hi Sarah, On Tue, Nov 08, 2011 at 10:11:17AM -0500, s.casw...@protocol6.com wrote: > Hi all, > > I was hoping someone on the list could confirm for me what the proper format > for the ~/.forward file is for use with procmail (and OpenSMTPd on OpenBSD). > > Currently I have ~/.forward > > | /usr/local/bin/procmail > > but other information I've seen says it should be > > "|IFS=' ' && exec /usr/local/bin/procmail || exit 75 #your_user_name" > > > Which is correct, or is there a different format altogether that I should be > using? > in theory the second one is the right one, but when I wrote the code a while ago I think I detected the use of ", I need to double check as aliases support went through a major rewrite a few months ago and I'm unsure if both are considered valid by the parser. if there is no ambiguity either one should work > --- > > Some context of why I ask about this: > > [...] > > Perhaps my .forward files contain the wrong invocation of procmail, or there > is a bug in (my version of) OpenSMTPd. > it's a bug, and I actually have it is actually very high in my TODO as it can cause an entire list to be rejected at session time when ONE recipient is rejected. I will get back to you when I have a diff to test, but that's very unlikely in the coming days. > Any comments would be appreciated. > > :-) > -- Gilles Chehade http://www.poolp.org/@poolpOrg
problem connecting to verizon.net
I discovered an odd issue once I upgraded my OpenBSD pf firewall/router that manifested itself by preventing my email server from sending to verizon.net customers. The strange thing was that mail was going out to other domains. I figured out that I did something odd in my ruleset and fixed it, so now I am wondering what is going on. I am only aware of one other individual with these symptoms, but he was using a bridge with pf and our fixes are at least semantically different. I have reduced everything to basic working parts and tested a few times to narrow down what is happening. In summary, I found that I can create two pass-only rules to nat outgoing traffic using carp and rdomains, but the traffic to verizon.net doesn't work unless I use a combination of two pass rules and a match rule. The basic setup where you can see this behavior follows (public IPs changed to protect the innocent): # ifconfig em0 em0: flags=8843 mtu 1500 lladdr 00:90:0b:1f:72:e4 priority: 0 groups: egress media: Ethernet autoselect (1000baseT full-duplex,master,rxpause,txpause) status: active inet 10.0.0.1 netmask 0xfffc broadcast 10.0.0.3 # ifconfig em1 em1: flags=28b43 rdomain 1 mtu 1500 lladdr 00:90:0b:1f:72:e5 priority: 0 media: Ethernet autoselect (100baseTX full-duplex,rxpause,txpause) status: active inet 9.9.9.170 netmask 0xfff0 broadcast 9.9.9.175 # ifconfig carp1 carp1: flags=28843 rdomain 1 mtu 1500 lladdr 00:00:5e:00:01:09 priority: 0 carp: MASTER carpdev em1 vhid 9 advbase 1 advskew 0 groups: carp status: master inet 9.9.9.167 netmask 0xfff0 broadcast 9.9.9.175 inet 9.9.9.168 netmask 0x broadcast 9.9.9.168 # route -T 0 -n show -inet Routing tables Internet: DestinationGatewayFlags Refs Use Mtu Prio Iface default10.0.0.1 UGS09 - 8 em0 10.0.0.0/30link#1 UC 20 - 4 em0 10.0.0.1 00:90:0b:1f:72:e4 HLc10 - 4 lo0 10.0.0.2 00:14:22:2e:ba:8c UHLc 0 10 - 4 em0 9.9.9.168 127.0.0.1 UGHS 00 33200 8 lo0 127/8 127.0.0.1 UGRS 00 33200 8 lo0 127.0.0.1 127.0.0.1 UH 20 33200 4 lo0 224/4 127.0.0.1 URS00 33200 8 lo0 # route -T 1 -n show -inet Routing tables Internet: DestinationGatewayFlags Refs Use Mtu Prio Iface default9.9.9.161 UGS0 14 - 8 em1 9.9.9.160/28 link#2 UC 10 - 4 em1 9.9.9.161 00:1b:54:b7:81:a8 UHLc 10 - 4 em1 9.9.9.168/32 9.9.9.168 U 0 10 - 4 carp1 # cat /etc/hostname.em0 inet 10.0.0.1 255.255.255.252 NONE # cat /etc/hostname.em1 inet 9.9.9.170 255.255.255.240 9.9.9.175 rdomain 1 !route -T 1 add default 9.9.9.161 # cat /etc/hostname.carp1 inet 9.9.9.167 255.255.255.240 9.9.9.175 vhid 9\ pass password rdomain 1 inet alias 9.9.9.168 255.255.255.255 # cat /etc/mygate 10.0.0.1 # cat /etc/pf.conf set skip on lo block # LAN to Internet with three rules and rdomain # (fixes the verizon issue) #match out on em1 inet from 10.0.0.2\ to any nat-to 9.9.9.170 #pass out on em1 inet from 9.9.9.170\ to any #pass in on em0 from 10.0.0.2\ to any rtable 1 # example LAN to Internet with two rules and rdomain # (doesn't work) # Seeing TTL expired in transit #pass in on em0 inet from 10.0.0.2\ to any nat-to 9.9.9.170 rtable 1 #pass out on em1 inet from 9.9.9.170 to any # Internet access over rdomain and carp # (creates the verizon issue) pass in quick on em0 inet from 10.0.0.2\ to any nat-to 9.9.9.168 rtable 1 pass out quick on em1 inet from 9.9.9.168\ to any --- >From 10.0.0.2 I run the following commands: (first a non-verizon smtp server) telnet 207.155.253.210 25 (works, but a little slower to display the banner under the pass-only rules) (now one of the relay.verizon.net smtp servers) telnet 206.46.232.11 25 (fails to connect unless I use the match/pass rule combo) In the rules above I also found that the two-rule setup doesn't work in any case with the public if physical IP in the rdomain. I have looked at these over tcpdump and I can see the traffic going out with the proper NAT to either server, but the returning SYN/ACKs in the handshake from verizon arrive and do not forward to the internal host. One thing I have noticed is that the verizon ttl is higher than the other server, but I don't know how this makes a difference. Given the fact that there is a ttl expired in transit when I try to nat-to the public physical if IP I
Re: hardware looking for a new home
Hi all, just wanted to give a little update. So far I receive a fewed mails from people who are interested in some of the items, but I am still collecting and will sort it out during the next weekend or so. Regards, Michael Am 06.11.11 14:38, schrieb Michael Lechtermann: > Hi all, > > I am moving soon and want to take that opportunity to get rid of some > old hardware I either don't need anymore or don't have the space for. > > All items are located in Germany, about an hour drive north of Frankfurt. > > 1x 19" Schroff rack > - 2x door, 1 key > - 2x side walls (from another model, but can be made to fit) > - roof with 6 fans > - lots of universal rack mount rails > - 2x EU Schuko power bars > > 1x Sun Fire v440 > - 4x 1062 Mhz > - 8GB RAM > - 2x 36GB and 2x 73GB HDD inside + 1x36GB and 1x73GB as spare > - some fibrechannel card > - 1x CPU replacement board with RAM > > 1x Sun Fire v100 > - 1x 650 Mhz > - 1GB RAM > - 1x 40GB HDD > > 1x Dell PE750 > - 1x 2.8 Ghz > - 4 GB RAM > - 2x WD Raptor 73GB > - DRAC III > - 4x USB 2.0 PCI card > > 1x Soekris 4801 > - 256 MB RAM > - 7x 100MBit > - VPN encryption card > - no power supply > > 1x PC Engines wrap > - 128 MB RAM > - 1x 100Mbit > - no power supply > > 2x Dell Optiplex SX270 (working) > - some CPU > - some RAM > - some HDD > - with power supply > > 1x Dell Optiplex SX270 (defective) > - some CPU > - some RAM > - no HDD > - with power supply > - doesn't power up, I have the replacement parts for the mainboard > though. If you know how to use a soldering iron, it is easy to fix, did > it for 2 others already a few years ago and they are still running. > > 1x Linksys SRW2016, 16 Port Gbit managed switch, 19" > > 1x LevelOne 16 Port 100Mbit switch, 19" > > > If anyone is interested in something please contact me off-list so we > can talk about how to get it to you. For all items, if a developer is > interested, he/she gets priority over other requests. > > > -Michael
Re: I want copy pf.conf from FreeBSD 8.2 to OpenBSD 5 and use it
On 11/8/11 4:25 AM, Mostaf Faridi wrote: Thanks My problem is this I do not enough time to start from scratch and make new rule .in my work place , my boss find another person can do internet sharing with Windows 2008 and ISA and this person say he can make best internet sharing server , I said before my my pf.conf in FreeBSD work good , but sometimes some user lost internet and they can not browse web pages , but they can chat with paltalk , after reboot or disbable or enable PF this problem solve . I think I have mistakes or problems in my PF.conf . So after search in Google , I see PF version in FreeBSD is so old , so I decided move from FreeBSD to openBSD . I wish my PF work good in OpenBSD Thanks in advance. Yo Most... You have selected the wrong product for your little project. If you don't have the time, don't have a lot of expertise - don't select a high-end system to implement. Let me suggest a smoother path for you... pfSense. It is pf, based on FreeBSD and is web-based. It should ease you into this pf world and get you going fairly fast. Throw away the pf.conf you keep wagging and start from scratch ... even in pfSense. It gets you going very fast. And the pfSense community (mailing list) is much more aligned to help a newbie such as yourself. Mehma
Re: 5.0 vmt0 kernel panic in Linux KVM
On Mon, Nov 07, 2011 at 03:51:50PM +0100, Walter Haidinger wrote: > cpu0: AMD Phenom(tm) II X6 1100T Processor ("AuthenticAMD" 686-class, 512KB > L2 cache) 3.31 GHz > cpu0: > FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,POPCNT > ... > bios0: vendor Bochs version "Bochs" date 01/01/2007 > bios0: Bochs Bochs They shouldn't be pretending to be AMD, especially if that emulation is very incompatible. > acpicpu0 at acpi0 ..but this is fortunate, I can workaround the bug. > kernel: protection fault trap, code=0 > Stopped at k1x_init+0x56: rdmsr > k1x_init(d0ad7540,d0b8ce58,d059ce20,0,3002) at k1x_init+0x56 > mainbus_attach(0,d130bfc0,0,d09aafc0,0) at mainbus_attach+0xc1 > config_attach(0,d09aafc0,0,0,d0a1bc40) at config_attach+0x1bb > config_rootfound(d08cde8c,0,0,d03d8b51,0) at config_rootfound+0x46 > cpu_configure(d0ad7540,1,1000,cff3f000,1) at cpu_configure+0x29 > main(d02004ba,d02004c2,0,0,0) at main+0x3ea > ddb> This wouldn't panic on a real K10 processor, however, it can be avoided here if we check acpi before doing the msr read. Can you try the following? -Bryan. Index: amd64/amd64/k1x-pstate.c === RCS file: /cvs/src/sys/arch/amd64/amd64/k1x-pstate.c,v retrieving revision 1.2 diff -u -p -u -r1.2 k1x-pstate.c --- amd64/amd64/k1x-pstate.c29 May 2011 12:29:28 - 1.2 +++ amd64/amd64/k1x-pstate.c8 Nov 2011 18:18:01 - @@ -75,7 +75,7 @@ struct k1x_cpu_state *k1x_current_state; void k1x_transition(struct k1x_cpu_state *, int); #if NACPICPU > 0 -void k1x_acpi_init(struct k1x_cpu_state *, u_int64_t); +void k1x_acpi_init(struct k1x_cpu_state *); void k1x_acpi_states(struct k1x_cpu_state *, struct acpicpu_pss *, int, u_int64_t); #endif @@ -154,14 +154,17 @@ k1x_acpi_states(struct k1x_cpu_state *cs } void -k1x_acpi_init(struct k1x_cpu_state *cstate, u_int64_t msr) +k1x_acpi_init(struct k1x_cpu_state *cstate) { struct acpicpu_pss *pss; + u_int64_t msr; cstate->n_states = acpicpu_fetch_pss(&pss); if (cstate->n_states == 0) return; + msr = rdmsr(MSR_K1X_STATUS); + k1x_acpi_states(cstate, pss, cstate->n_states, msr); return; @@ -172,12 +175,9 @@ k1x_acpi_init(struct k1x_cpu_state *csta void k1x_init(struct cpu_info *ci) { -#if NACPICPU > 0 - u_int64_t msr; -#endif - u_int i; struct k1x_cpu_state *cstate; struct k1x_state *state; + u_int i; if (setperf_prio > 1) return; @@ -190,7 +190,7 @@ k1x_init(struct cpu_info *ci) #if NACPICPU > 0 msr = rdmsr(MSR_K1X_STATUS); - k1x_acpi_init(cstate, msr); + k1x_acpi_init(cstate); #endif if (cstate->n_states) { printf("%s: %d MHz: speeds:", Index: i386/i386/k1x-pstate.c === RCS file: /cvs/src/sys/arch/i386/i386/k1x-pstate.c,v retrieving revision 1.2 diff -u -p -u -r1.2 k1x-pstate.c --- i386/i386/k1x-pstate.c 29 May 2011 12:29:28 - 1.2 +++ i386/i386/k1x-pstate.c 8 Nov 2011 18:18:02 - @@ -75,7 +75,7 @@ struct k1x_cpu_state *k1x_current_state; void k1x_transition(struct k1x_cpu_state *, int); #if NACPICPU > 0 -void k1x_acpi_init(struct k1x_cpu_state *, u_int64_t); +void k1x_acpi_init(struct k1x_cpu_state *); void k1x_acpi_states(struct k1x_cpu_state *, struct acpicpu_pss *, int, u_int64_t); #endif @@ -154,14 +154,17 @@ k1x_acpi_states(struct k1x_cpu_state *cs } void -k1x_acpi_init(struct k1x_cpu_state *cstate, u_int64_t msr) +k1x_acpi_init(struct k1x_cpu_state *cstate) { struct acpicpu_pss *pss; + u_int64_t msr; cstate->n_states = acpicpu_fetch_pss(&pss); if (cstate->n_states == 0) return; + msr = rdmsr(MSR_K1X_STATUS); + k1x_acpi_states(cstate, pss, cstate->n_states, msr); return; @@ -172,12 +175,9 @@ k1x_acpi_init(struct k1x_cpu_state *csta void k1x_init(struct cpu_info *ci) { -#if NACPICPU > 0 - u_int64_t msr; -#endif - u_int i; struct k1x_cpu_state *cstate; struct k1x_state *state; + u_int i; if (setperf_prio > 1) return; @@ -189,8 +189,7 @@ k1x_init(struct cpu_info *ci) cstate->n_states = 0; #if NACPICPU > 0 - msr = rdmsr(MSR_K1X_STATUS); - k1x_acpi_init(cstate, msr); + k1x_acpi_init(cstate); #endif if (cstate->n_states) { printf("%s: %d MHz: speeds:",
Re: 5.0 vmt0 kernel panic in Linux KVM
On Tue, Nov 08, 2011 at 01:27:37PM -0500, Brynet wrote: > @@ -190,7 +190,7 @@ k1x_init(struct cpu_info *ci) > > #if NACPICPU > 0 > msr = rdmsr(MSR_K1X_STATUS); > - k1x_acpi_init(cstate, msr); > + k1x_acpi_init(cstate); Whoops, fixed patch for amd64. -Bryan. Index: amd64/amd64/k1x-pstate.c === RCS file: /cvs/src/sys/arch/amd64/amd64/k1x-pstate.c,v retrieving revision 1.2 diff -u -p -u -r1.2 k1x-pstate.c --- amd64/amd64/k1x-pstate.c29 May 2011 12:29:28 - 1.2 +++ amd64/amd64/k1x-pstate.c8 Nov 2011 18:30:59 - @@ -75,7 +75,7 @@ struct k1x_cpu_state *k1x_current_state; void k1x_transition(struct k1x_cpu_state *, int); #if NACPICPU > 0 -void k1x_acpi_init(struct k1x_cpu_state *, u_int64_t); +void k1x_acpi_init(struct k1x_cpu_state *); void k1x_acpi_states(struct k1x_cpu_state *, struct acpicpu_pss *, int, u_int64_t); #endif @@ -154,14 +154,17 @@ k1x_acpi_states(struct k1x_cpu_state *cs } void -k1x_acpi_init(struct k1x_cpu_state *cstate, u_int64_t msr) +k1x_acpi_init(struct k1x_cpu_state *cstate) { struct acpicpu_pss *pss; + u_int64_t msr; cstate->n_states = acpicpu_fetch_pss(&pss); if (cstate->n_states == 0) return; + msr = rdmsr(MSR_K1X_STATUS); + k1x_acpi_states(cstate, pss, cstate->n_states, msr); return; @@ -172,12 +175,9 @@ k1x_acpi_init(struct k1x_cpu_state *csta void k1x_init(struct cpu_info *ci) { -#if NACPICPU > 0 - u_int64_t msr; -#endif - u_int i; struct k1x_cpu_state *cstate; struct k1x_state *state; + u_int i; if (setperf_prio > 1) return; @@ -189,8 +189,7 @@ k1x_init(struct cpu_info *ci) cstate->n_states = 0; #if NACPICPU > 0 - msr = rdmsr(MSR_K1X_STATUS); - k1x_acpi_init(cstate, msr); + k1x_acpi_init(cstate); #endif if (cstate->n_states) { printf("%s: %d MHz: speeds:",
Re: I want copy pf.conf from FreeBSD 8.2 to OpenBSD 5 and use it
Thanks Your guide learn me many thing .my experience with FreeBSD and OpenBSD is good .but my experience with FreeBSD is much better . In work place I run FreeBSD server for Samba and NAT and this server work good and work like charm , but I do not know why PF does not work good , if you see my conf , you see my conf does not has problem , but I do not know why this conf does not work good , and sometimes some users do not have internet and can not browse webpage but they can chat with messenger . I want migrate from FreeBSD to OpenBSD , yesterday I install OpenBSD 5 amd64 and run samba server with OpenBSD and it work good . In first step I run samba server with OpenBSD , and after this I want run NAT server with OpenBSD . And for start I want understand , is my PF.conf work in OpenBSD or no ? I hate Windows OS , and want only run all of my servers with BSD, specially OpenBSD. Thanks in advance On Nov 8, 2011 5:32 PM, "David Walker" wrote: > Mostaf Faridi wrote: > > My problem is this I do not enough time to start from scratch and make > new > > rule . > > If you were moderately familiar with OpenBSD you could have, in the > time between the start of this thread and now, read pf.conf for > OpenBSD 5.0 and written on paper or wherever a complex ruleset. > If your boss won't allocate time for this and expects you to outsource > it to the web and whatever then he's doing it wrong. > You don't have a good enough familiarity with OpenBSD (or FreeBSD) to > know where to start. Right? > > If you do plan to migrate then you should build a machine, install > OpenBSD 5.0, write a ruleset and test it. > In your workplace, testing may mean swapping the machines until > everyone complains and you swap them back and try again but doing it > the way you're doing it now (no experience, asking for copy and paste > administration, no testing) is wrong. > > > in my work place , my boss find another person can do internet > > sharing with Windows 2008 and ISA and this person say he can make best > > internet sharing server > > So you want pf on OpenBSD and don't want to see a Windows machine ... > ... but you're not interested in reading about pf on OpenBSD ... > > Who's running the current FreeBSD machine? > How come they can't understand it? > Why not troubleshoot that? > Etcetera ... > How will swapping to a new operating system be better than using the > current one which almost works? > > If you want to stay with FreeBSD you should at a minimum understand > your current ruleset (removing any non-essential lines might be a good > start) if you want to get help on it. Again though you're in the wrong > place. > Can you explain what every line in the pf.conf you sent is for? > If not, find out, if it does nothing, delete it, whatever. > > Describe your network, do you have issues with DNS, do you have a http > proxy, what tests have you done from clients, etcetera ... > Have you looked here: > > http://www.freebsd.org/cgi/man.cgi?query=pfctl&sektion=8&manpath=FreeBSD+8.2-RELEASE > So on and so forth. > > Under those circumstances, maybe Windows is the better choice. > Certainly without any relevant OpenBSD experience you're better off > with FreeBSD right? > > > I said before my my pf.conf in FreeBSD work good , but sometimes some > user > > lost internet and they can not browse web pages , but they can chat with > > paltalk , after reboot or disbable or enable PF this problem solve . > > Fine. > You have choices. > > Fix your current setup which should involve reading the FreeBSD > pf.conf documentation and talking to people on the FreeBSD lists. > Goodbye. > > Build an OpenBSD machine, in which case, talk to you when you've got a > machine running and you have some more appropriate questions. People > will help you. > > Either way you're should be willing to invest time and if you won't do > that on your own and your boss doesn't want you to do it in work time > then let the Windows people worry about it. Good times. > > Best wishes.
Re: I want copy pf.conf from FreeBSD 8.2 to OpenBSD 5 and use it
No it will not. The version in FreeBSD is older and thus the syntax has changed. Read the pf faq on the OpenBSD website. Also why are you running samba on your firewall? Sent from my Android phone using TouchDown (www.nitrodesk.com) -Original Message- From: Mostaf Faridi [mostafafar...@gmail.com] Received: Tuesday, 08 Nov 2011, 1:46pm To: David Walker [davidianwal...@gmail.com] CC: misc@openbsd.org [misc@openbsd.org] Subject: Re: I want copy pf.conf from FreeBSD 8.2 to OpenBSD 5 and use it Thanks Your guide learn me many thing .my experience with FreeBSD and OpenBSD is good .but my experience with FreeBSD is much better . In work place I run FreeBSD server for Samba and NAT and this server work good and work like charm , but I do not know why PF does not work good , if you see my conf , you see my conf does not has problem , but I do not know why this conf does not work good , and sometimes some users do not have internet and can not browse webpage but they can chat with messenger . I want migrate from FreeBSD to OpenBSD , yesterday I install OpenBSD 5 amd64 and run samba server with OpenBSD and it work good . In first step I run samba server with OpenBSD , and after this I want run NAT server with OpenBSD . And for start I want understand , is my PF.conf work in OpenBSD or no ? I hate Windows OS , and want only run all of my servers with BSD, specially OpenBSD. Thanks in advance On Nov 8, 2011 5:32 PM, "David Walker" wrote: > Mostaf Faridi wrote: > > My problem is this I do not enough time to start from scratch and make > new > > rule . > > If you were moderately familiar with OpenBSD you could have, in the > time between the start of this thread and now, read pf.conf for > OpenBSD 5.0 and written on paper or wherever a complex ruleset. > If your boss won't allocate time for this and expects you to outsource > it to the web and whatever then he's doing it wrong. > You don't have a good enough familiarity with OpenBSD (or FreeBSD) to > know where to start. Right? > > If you do plan to migrate then you should build a machine, install > OpenBSD 5.0, write a ruleset and test it. > In your workplace, testing may mean swapping the machines until > everyone complains and you swap them back and try again but doing it > the way you're doing it now (no experience, asking for copy and paste > administration, no testing) is wrong. > > > in my work place , my boss find another person can do internet > > sharing with Windows 2008 and ISA and this person say he can make best > > internet sharing server > > So you want pf on OpenBSD and don't want to see a Windows machine ... > ... but you're not interested in reading about pf on OpenBSD ... > > Who's running the current FreeBSD machine? > How come they can't understand it? > Why not troubleshoot that? > Etcetera ... > How will swapping to a new operating system be better than using the > current one which almost works? > > If you want to stay with FreeBSD you should at a minimum understand > your current ruleset (removing any non-essential lines might be a good > start) if you want to get help on it. Again though you're in the wrong > place. > Can you explain what every line in the pf.conf you sent is for? > If not, find out, if it does nothing, delete it, whatever. > > Describe your network, do you have issues with DNS, do you have a http > proxy, what tests have you done from clients, etcetera ... > Have you looked here: > > http://www.freebsd.org/cgi/man.cgi?query=pfctl&sektion=8&manpath=FreeBSD+8.2- RELEASE > So on and so forth. > > Under those circumstances, maybe Windows is the better choice. > Certainly without any relevant OpenBSD experience you're better off > with FreeBSD right? > > > I said before my my pf.conf in FreeBSD work good , but sometimes some > user > > lost internet and they can not browse web pages , but they can chat with > > paltalk , after reboot or disbable or enable PF this problem solve . > > Fine. > You have choices. > > Fix your current setup which should involve reading the FreeBSD > pf.conf documentation and talking to people on the FreeBSD lists. > Goodbye. > > Build an OpenBSD machine, in which case, talk to you when you've got a > machine running and you have some more appropriate questions. People > will help you. > > Either way you're should be willing to invest time and if you won't do > that on your own and your boss doesn't want you to do it in work time > then let the Windows people worry about it. Good times. > > Best wishes.
Multiple ISPs: send packets to the interface they came from
Hi all, I'm very new to OpenBSD so please bear with me as I'm certainly doing a rookie mistake... I'm using a Soekris net5501 as a loadbalancer using Debian and I want to switch to OpenBSD. We have two ISPs coming to the net5501 as vlan1 and vlan10. My default gateway is set to vlan1. The problem that I have is that when I try to connect to the ip on vlan10, the response packets are sent to vlan1 and discarded by the router because it looks like ip spoofing. I searched a lot about this but all I can find is about load balancing a NATed network between multiple ISPs (equal-cost multipath routing). It's not what I want to do, this machine will not do any NAT. I also tried using pf route-to but that seems to only work with NAT... So basically my question is how to tell OpenBSD to send packets to the interface they came from? Thanks a lot, GFK's PS: On my debian box, I did it like that: iface eth1 inet static address CC.DD.200.226 netmask 255.255.255.0 post-up ip route add CC.DD.200.0/24 dev eth1 src CC.DD.200.226 table uq post-up ip route add default via CC.DD.200.1 table uq post-up ip rule add from CC.DD.200.0/24 table uq post-down ip rule del from CC.DD.200.0/24 table uq PPS: Here's an example of the problem: >From a box outside of the network (delta.sanitized.com) I try to connect to the OpenBSD box on vlan10: gfk@delta:~$ ssh -v AA.BB.57.185 OpenSSH_5.1p1 Debian-5, OpenSSL 0.9.8g 19 Oct 2007 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to AA.BB.57.185 [AA.BB.57.185] port 22. ... On the OpenBSD box, the SYN packets come to vlan10 $ sudo tcpdump -i vlan10 host delta.sanitized.com tcpdump: listening on vlan10, link-type EN10MB 15:08:45.136610 delta.sanitized.com.53784 > AA.BB.57.185.ssh: S 3553316437:3553316437(0) win 5840 (DF) 15:08:51.136691 delta.sanitized.com.53784 > AA.BB.57.185.ssh: S 3553316437:3553316437(0) win 5840 (DF) ^C 342 packets received by filter 0 packets dropped by kernel # but the SYN/ACK are sent back on vlan1, to be then dropped by the router. $ sudo tcpdump -i vlan1 host delta.sanitized.com Password: tcpdump: listening on vlan1, link-type EN10MB 15:08:45.136763 AA.BB.57.185.ssh > delta.sanitized.com.53784: S 307933727:307933727(0) ack 3553316438 win 16384 (DF) 15:08:48.127203 AA.BB.57.185.ssh > delta.sanitized.com.53784: S 307933727:307933727(0) ack 3553316438 win 16384 (DF) 15:08:51.136784 AA.BB.57.185.ssh > delta.sanitized.com.53784: S 307933727:307933727(0) ack 3553316438 win 16384 (DF) 15:08:54.127383 AA.BB.57.185.ssh > delta.sanitized.com.53784: S 307933727:307933727(0) ack 3553316438 win 16384 (DF) ^C 724 packets received by filter 0 packets dropped by kernel $ ifconfig -A lo0: flags=8049 mtu 33196 priority: 0 groups: lo inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 inet 127.0.0.1 netmask 0xff00 vr0: flags=8b43 mtu 1500 lladdr 00:00:24:cb:a7:84 priority: 0 trunk: trunkdev trunk0 media: Ethernet autoselect (100baseTX full-duplex) status: active inet6 fe80::200:24ff:fecb:a785%vr0 prefixlen 64 scopeid 0x1 vr1: flags=8b43 mtu 1500 lladdr 00:00:24:cb:a7:84 priority: 0 trunk: trunkdev trunk0 media: Ethernet autoselect (100baseTX full-duplex) status: active inet6 fe80::200:24ff:fecb:a786%vr1 prefixlen 64 scopeid 0x2 vr2: flags=8802 mtu 1500 lladdr 00:00:24:cb:a7:86 priority: 0 media: Ethernet autoselect (none) status: no carrier vr3: flags=8843 mtu 1500 lladdr 00:00:24:cb:a7:87 priority: 0 media: Ethernet autoselect (none) status: no carrier inet6 fe80::200:24ff:fecb:a787%vr3 prefixlen 64 scopeid 0x4 enc0: flags=0<> priority: 0 groups: enc status: active trunk0: flags=8943 mtu 1500 lladdr 00:00:24:cb:a7:84 priority: 0 trunk: trunkproto loadbalance trunkport vr1 active trunkport vr0 master,active groups: trunk media: Ethernet autoselect status: active inet6 fe80::200:24ff:fecb:a784%trunk0 prefixlen 64 scopeid 0x7 vlan1: flags=8943 mtu 1500 lladdr 00:00:24:cb:a7:84 priority: 0 vlan: 1 priority: 0 parent interface: trunk0 groups: vlan egress status: active inet6 fe80::200:24ff:fecb:a784%vlan1 prefixlen 64 scopeid 0x8 inet CC.DD.200.225 netmask 0xff00 broadcast CC.DD.200.255 vlan10: flags=8843 mtu 1500 lladdr 00:00:24:cb:a7:84 priority: 0 vlan: 10 priority: 0 parent interface: trunk0 groups: vlan status: active inet6 fe80::200:24ff:fecb:a784%vlan10 prefixlen 64 scopeid 0x9 inet AA.BB.57.185 netmask 0xffe0 broadcast AA.BB.57.191 pfsync0: flags=41 mtu 1500 priority: 0 groups: carp pfsync pflog0: flags=141 mtu 33196
Re: Multiple ISPs: send packets to the interface they came from
Le Tue, 08 Nov 2011 15:27:02 -0500, Guillaume Filion a icrit : > Hi all, Hello, > I also tried using pf route-to but that seems to only work with > NAT... No it does routing. I use it without nat. > So basically my question is how to tell OpenBSD to send packets to the > interface they came from? See reply-to Regards.
Re: Multiple ISPs: send packets to the interface they came from
Thanks a lot Patrick, it was really to the point! >From man pf.conf: reply-to The reply-to option is similar to route-to, but routes packets that pass in the opposite direction (replies) to the specified interface. Opposite direction is only defined in the context of a state entry, and reply-to is useful only in rules that create state. It can be used on systems with multiple external connections to route all outgoing packets of a connection through the interface the incoming connection arrived through (symmetric routing enforcement). Two simples lines in pf.conf did the trick: pass in on vlan1 all keep state reply-to {(vlan1 CC.DD.200.1)} pass in on vlan10 all keep state reply-to {(vlan10 AA.BB.57.161)} If I may add a comment, coming from the debian world, I'm really impressed by how simple the instructions are for configuring OpenBSD. 3-4 lines of config on debian are usually reduced to just one in OpenBSD. Really impressive! Thanks again, GFK's 2011/11/8 Patrick Lamaiziere > > Le Tue, 08 Nov 2011 15:27:02 -0500, > Guillaume Filion a C)crit : > > > Hi all, > > Hello, > > > I also tried using pf route-to but that seems to only work with > > NAT... > > No it does routing. I use it without nat. > > > So basically my question is how to tell OpenBSD to send packets to the > > interface they came from? > > See reply-to > > Regards. -- http://guillaume.filion.org/
Re: I want copy pf.conf from FreeBSD 8.2 to OpenBSD 5 and use it
Mostaf Faridi wrote: > I want migrate from FreeBSD to OpenBSD , yesterday I install OpenBSD 5 > amd64 and run samba server with OpenBSD and it work good . In first step I > run samba server with OpenBSD , and after this I want run NAT server with > OpenBSD . Great. > And for start I want understand , is my PF.conf work in OpenBSD > or no ? No. Next question ... What's the best way to get from there to OpenBSD 5.0 pf.conf? Start from scratch. If you can do all the other things (install, samba, etcetera) you can start writing a pf.conf from scratch. You should be writing one for the Samba server ... so you should look upon this as an essential skill. Besides, if somebody moves the network in the future (add a few machines maybe) what will you do? Follow the dots. Get the pf.conf man page ... Work out your macros ... Hint, that's all the stuff from the old pf.conf with an "=". Another hint, this is the entire macro text as it applies to you: Macros can be defined that will later be expanded in context. Macro names must start with a letter, and may contain letters, digits and underscores. Macro names may not be reserved words (for example pass, in, out). Macros are not expanded inside quotes. For example: ext_if = "kue0" all_ifs = "{" $ext_if lo0 "}" pass out on $ext_if from any to any pass in on $ext_if proto tcp from any to any port 25 Next hint, the only difficult bit about that is "Macros are not expanded inside quotes." and the use of quotes inside the braces ... The $ should help you work that out. Happy hint, that's half your work done in five minutes by copying and pasting from your old pf.conf ... In this case it's okay if you follow the dots - read the man page, if it's the same syntax then it's the same syntax. Work out your OPTIONS ... Keep it really simple, for example in your old pf.conf you load fingerprints but don't appear to use them. Hint, you probably don't need any options at all to start (i.e. default will be fine). Do you understand your timeouts and limit? If not, don't use them. Work out your TABLES ... Or better yet don't use them until you have a working NAT system. Hint, as near as I can tell ... you're not using any of the tables in your pf.conf ... Check that and then ... get rid of them. Read the small section in the man page on "Translation" under PACKET FILTERING - its a few pages down. Look at the EXAMPLES for some ideas. Write one NAT rule and one RDR rule, using your macros. If you get stuck go here: http://www.openbsd.org/faq/pf/nat.html#config http://www.openbsd.org/faq/pf/rdr.html#filter If you're still stuck go here: http://www.openbsd.org/faq/pf/example1.html Bear in mind that parts of the PF FAQ might be still in 4.9 and you want 5.0 ... Someone else should be able to answer that but ... the man page will give you an answer. Once you've got that worked out ... Do NAT and RDR for all your other macros ... Test. Then worry about all the other stuff. If you can install and use OpenBSD you can learn pf or at least if you won't learn pf you shouldn't be installing and using OpenBSD at least not in a packet filtering role. :] > I hate Windows OS , and want only run all of my servers with BSD, specially > OpenBSD. I only want my servers to run OpenBSD but I'm happy to use Windows on the desktop. Best wishes.
Re: using xmodmap to make Caps Lock a control key: worked <= 4.9, broken in 5.0
On 2011-11-08, Jonathan Thornburg wrote: > [If it helps, I'd be happy to have Caps Lock be a control key system-wide, > i.e., in the console as well as in X.] I can't help with the details of what changed in 5.0 (though thanks for the detailed problem report, this is *exactly* the right sort of detail to include), but for the simple fix, you should be able to do this: # kbd us.swapctrlcaps And to make it permanent: # echo us.swapctrlcaps > /etc/kbdtype Unless my memory fails me, X uses these settings in the absence of other keyboard config.
Re: using xmodmap to make Caps Lock a control key: worked <= 4.9, broken in 5.0
On Tue, Nov 8, 2011 at 8:49 PM, Jonathan Thornburg wrote: > I've just installed 5.0/amd64 (from the CD set) on a Lenovo Thinkpad T60 > laptop (dmesg below). I'm not running xdm; I normally use this system > by logging in at the console, then typing "startx&;logout" to start X. > My .xinitrc (given in full below) contains (among other things) the > section > > # make Caps Lock key be another control key > xmodmap - <<'EOF' > remove Lock = Caps_Lock > add Control = Caps_Lock > !! Swap Caps_Lock and Control_L (adapted from the xmodmap(1) man page) > !!remove Lock = Caps_Lock > !!remove Control = Control_L > !!keysym Control_L = Caps_Lock > !!keysym Caps_Lock = Control_L > !!add Lock = Caps_Lock > !!add Control = Control_L > EOF > > to make the "Caps Lock" key be a(nother) control key. For OpenBSD 4.9 > and earlier (on both this and other laptops), this worked fine. But as > of my newly-installed 5.0-release, this seems to be a no-op: "Caps Lock" > stays a caps-lock key. > > My basic question is, what's wrong and what can/should I do about it? You also need to change the keysym on the key and not just the modifier. I.e., your xmodmap input needs to be: remove Lock = Caps_Lock keysym Caps_Lock = Control_L add control = Control_L Philip Guenther
Re: how to disable fsck when power failure
Hi,Matteo Leccardi ccThanks guys for all your replys. appreciate it. Matteo , before i maned the fstab ,and found it ' If the sixth field is not present or is zero, a value of zero is returned and fsck(8) will assume that the filesystem does not need to be checked. " but it didn't works ,there something funny came across . after the failure ,the OpenBSD system repeated rebooting. so i had to boot into single mode ,and edited it again to the default setting ,then it recovered. i can't transfer the /var to mfs ,because i have to accumulate some logs ,such as mrtg/trafd logs .--would you mind telling how to transfer the /var/ to MFS ? thank you very much . @Norman Golisz , thanks your suggesting . but the little box with OpenBSD like "Soekris" works under mal-condition , i don't intend to suply a UPS. could any ways be done to avoid /disable fsck and jump to single user mode ? thanks. @David Coppa , thanks for your patch , i will try that .did it work for you now ? Disabling or skipping fsck(8)s is generally a very bad idea. Norman. @Norman: is it! BTW... @Cosmo Wu man 5 fstab is your friend. Quick and dirt: Edit /etc/fstab and change the last digit of the corrispondent mount point line form [1|2] to 0 Ex. default 515f3560ef6f35f5.a / ffs rw 1 1 to 515f3560ef6f35f5.a / ffs rw 1 0 Bye Matteo = = = = = = = = = = = = = = = = = = = = = = h4 g$
Re: how to disable fsck when power failure
On 11/08/11 04:41, co...@tetrachina.com wrote: > misc#,Dz:C#! > > when the box with OpenBSD had a power failure and the system did not > unmount properly. > it sometimes gets stuck.The system is asking me to RUN fsck MANUALLY. > as a gateway ,so i can't go to fix it manually everytime.How do I advoid > this? > i want to disable it crumbling to single mode. thanks. > > /dev/rwd0e: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY. > AUTOMATIC FILE SYSTEM CHECK FAILED; HELP! > Enter pathname of shell or RETURN for sh: > > Best Regards > > Cosmo Wu I have run a lot of OpenBSD gateway machines, I almost always power them down by wacking the power switch, not by orderly shutdown, and yet, only a very few times has one not come back up well and on their own. I tend to use very small (by modern standards) partitions (i.e., only a small part of a modern disk. No one says you have to allocate all 250G of a 250G disks. You can leave 246G unallocated!), so the fsck times will be tolerable. So, I suspect you are doing something OTHER than running just a gateway, something that is causing more disk activity than a typical gateway does. After your first post, you mentioned mrtg. Ah-hah. I think the answer is, move mrtg to another machine, let your gateway be a gateway. I think that will reduce your problem to manageable levels. The few times I had an OpenBSD gateway not come up on their own at a customer site (I can think of once), I had no trouble walking non-technical people through fsck over the phone. Nick.
Re: I want copy pf.conf from FreeBSD 8.2 to OpenBSD 5 and use it
On 8 November 2011 23:25, Mostaf Faridi wrote: > Thanks > My problem is this I do not enough time to start from scratch and make new > rule Your philosophy is not compatible with OpenBSD. Grabbing a random incompatible ruleset from the Internet and then trying to fix it is going to take more time that learning how to deal with this from scratch. So find the time for: http://www.openbsd.org/faq/pf/nat.html and especially: http://www.openbsd.org/faq/pf/nat.html#binat and this for reference: http://www.openbsd.org/cgi-bin/man.cgi?query=pf.conf&manpath=OpenBSD+5.0 Or otherwise the answer to your questions is, no.
em(4) watchdog timeouts on 5.0-release
My em(4)'s stopped working with 5.0 - has anyone seen this on 82571EBs? I'll try backing out the MSO patch. Perhaps this is related: ftp://download.intel.com/design/network/specupdt/82571eb_72ei.pdf Page 22, Errata 7: Device Transmit Operation Might Halt in TCP Segmentation Offload (TSO) Mode when Multiple Requests (MULR) Are Enabled. OpenBSD 5.0 (GENERIC) #43: Wed Aug 17 10:10:52 MDT 2011 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Xeon(R) CPU E5502 @ 1.87GHz ("GenuineIntel" 686-class) 1.87 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,SSE4.2,POPCNT24 pins,CMOV,PAT,PSE36,CF real mem = 2136694784 (2037MB)SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3 avail mem = 2091687936 (1994MB).2,POPCNT mainbus0 at root0: bus 4 (IPT5)) bios0 at mainbus0: AT/286+ BIOS, date 12/31/99, BIOS32 rev. 0 @ 0xf, SMBIOS rev. 2.6 @ 0x7f7fe000 (134 entries) bios0: vendor HP version "W07" date 10/02/2009, BIOS32 rev. 0 @ 0xf, SMBIOS bios0: HP ProLiant DL320 G6T03)) date 12/31/99, BIOS32 rev. 0 @ 0xf, SMBIOS acpi0 at bios0: rev 2s 13 (PT01)es) 10/02/2009 acpi0: sleep states S0 S4 S5I0)date 10/02/2009 acpi0: tables DSDT FACP SPCR MCFG HPET SPMI ERST APIC SRAT BERT HEST DMAR SSDT SSDT SSDT acpi0: wakeup devices PCI0(S4)perature is 31 degCxcd600/0x1000 0xce600/0x1000 0x acpitimer0 at acpi0: 3579545 Hz, 24 bits0x2600! 0xcd600/0x1000 0xce600/0x1000 0x acpimcfg0 at acpi0 addr 0xe800, bus 0-63SPMI ERST APIC SRAT BERT HEST D acpihpet0 at acpi0: 14318179 Hzration mode 1 (bios) acpimadt0 at acpi0 addr 0xfee0: PC-AT compatos)v 0x13 cpu0 at mainbus0: apid 16 (boot processor) Host" rev 0x13 cpu0: apic clock running at 133MHzel X58 PCIE" rev 0x13 cpu at mainbus0: not configuredntel PRO/1000 PT (82571EB)" rev 0x06: msi, addres ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins 0x06: msi, addres ioapic1 at mainbus0: apid 0 pa 0xfec8, version 20, 24 pins acpiprt0 at acpi0: bus 1 (IP2P) acpiprt1 at acpi0: bus 3 (NIB1) acpiprt2 at acpi0: bus 4 (IPT5) acpiprt3 at acpi0: bus -1 (PRB2) acpiprt4 at acpi0: bus 10 (PT07) acpiprt5 at acpi0: bus 7 (PT03) acpiprt6 at acpi0: bus 13 (PT01) acpiprt7 at acpi0: bus 0 (PCI0) acpicpu0 at acpi0 acpitz0 at acpi0: critical temperature is 31 degC bios0: ROM list: 0xc/0xb000 0xcb000/0x2600! 0xcd600/0x1000 0xce600/0x1000 0xcf600/0x1000 0xd0600/0x1000 ipmi at mainbus0 not configured pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 "Intel 5500 Host" rev 0x13 ppb0 at pci0 dev 1 function 0 "Intel X58 PCIE" rev 0x13 pci1 at ppb0 bus 13 em0 at pci1 dev 0 function 0 "Intel PRO/1000 PT (82571EB)" rev 0x06: msi, address 00:26:55:d5:86:f2 em1 at pci1 dev 0 function 1 "Intel PRO/1000 PT (82571EB)" rev 0x06: msi, address 00:26:55:d5:86:f3 ppb1 at pci0 dev 3 function 0 "Intel X58 PCIE" rev 0x13 pci2 at ppb1 bus 7 ppb2 at pci0 dev 7 function 0 "Intel X58 PCIE" rev 0x13 pci3 at ppb2 bus 10 em2 at pci3 dev 0 function 0 "Intel PRO/1000 PT (82571EB)" rev 0x06: msi, address 00:26:55:d5:8f:b4 em3 at pci3 dev 0 function 1 "Intel PRO/1000 PT (82571EB)" rev 0x06: msi, address 00:26:55:d5:8f:b5 pchb1 at pci0 dev 13 function 0 vendor "Intel", unknown product 0x343a rev 0x13 pchb2 at pci0 dev 13 function 1 vendor "Intel", unknown product 0x343b rev 0x13 pchb3 at pci0 dev 13 function 2 vendor "Intel", unknown product 0x343c rev 0x13 pchb4 at pci0 dev 13 function 3 vendor "Intel", unknown product 0x343d rev 0x13 pchb5 at pci0 dev 13 function 4 "Intel 5520/X58 QuickPath" rev 0x13 pchb6 at pci0 dev 13 function 5 "Intel 5520 QuickPath" rev 0x13 pchb7 at pci0 dev 13 function 6 vendor "Intel", unknown product 0x341a rev 0x13 pchb8 at pci0 dev 14 function 0 vendor "Intel", unknown product 0x341c rev 0x13 pchb9 at pci0 dev 14 function 1 vendor "Intel", unknown product 0x341d rev 0x13 pchb10 at pci0 dev 14 function 2 vendor "Intel", unknown product 0x341e rev 0x13 pchb11 at pci0 dev 14 function 3 vendor "Intel", unknown product 0x341f rev 0x13 pchb12 at pci0 dev 14 function 4 vendor "Intel", unknown product 0x3439 rev 0x13 "Intel X58 Misc" rev 0x13 at pci0 dev 20 function 0 not configured "Intel X58 GPIO" rev 0x13 at pci0 dev 20 function 1 not configured "Intel X58 RAS" rev 0x13 at pci0 dev 20 function 2 not configured uhci0 at pci0 dev 26 function 0 "Intel 82801JI USB" rev 0x00: apic 8 int 20 uhci1 at pci0 dev 26 function 1 "Intel 82801JI USB" rev 0x00: apic 8 int 23 uhci2 at pci0 dev 26 function 2 "Intel 82801JI USB" rev 0x00: apic 8 int 22 ehci0 at pci0 dev 26 function 7 "Intel 82801JI USB" rev 0x00: apic 8 int 22 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 ppb3 at pci0 dev 28 function 0 "Intel 82801JI PCIE" rev 0x00 pci4 at ppb3 bus 2 ppb4 at pci4 dev 0 function 0 "ServerWorks PCIE-PCIX" rev 0xb5 pci5 at ppb4 bus 3 bge0 at pci
Re: using xmodmap to make Caps Lock a control key: worked <= 4.9, broken in 5.0
Hi Jonathan, On Tue, Nov 8, 2011 at 1:49 PM, Jonathan Thornburg wrote: > to make the "Caps Lock" key be a(nother) control key. B For OpenBSD 4.9 > and earlier (on both this and other laptops), this worked fine. B But as > of my newly-installed 5.0-release, this seems to be a no-op: "Caps Lock" > stays a caps-lock key. You can just run "setxkbmap -option ctrl:swapcaps". -- Anthony J. Bentley
Cómo Ganar Licitaciones con CFE, Taller de Actualización
290205 [IMAGE] Pms de Mixico prestigiada firma de Capacitacisn presenta: Licitaciones Pzblicas para la CFE 15 de Noviembre, Ciudad de Mixico. Promociones especiales por cierre de aqo. Experto consultor Mtro. Alberto Ledesma G. Obtenga las herramientas necesarias para alcanzar un sptimo desempeqo en su funcisn. Empresa Registrada ante la STPS Smguenos en Twitter@pmscapacitacion o bien en Facebook PMS de Mixico. !Solicite Mayores Informes! Por favor responda este e-mail con los datos siguientes. Empresa: Nombre: Telifono: Email: Nzmero de Interesados: En breve recibira la informacisn completa de este inigualable evento. Comunmquese a los telifonos y con gusto uno de nuestros ejecutivos le atendera. Telifonos: (0133) 8851-2365, (0133) 8851-2741. 10 lmneas a su servicio. Copyright (C) 2011, PMS Capacitacisn Efectiva de Mixico S.C. Derechos Reservados. PMS de Mixico, El logo de PMS de Mixico son marcas registradas. ADVERTENCIA PMS de Mixico no cuenta con alianzas estratigicas de ningzn tipo dentro de la Republica Mexicana. NO SE DEJE ENGAQAR - DIGA NO A LA PIRATERIA. Todos los logotipos, marcas comerciales e imagenes son propiedad de sus respectivas corporaciones y se utilizan con fines informativos solamente. Este Mensaje ha sido enviado a misc@openbsd.org como usuario de Pms de Mixico o bien un usuario le refiris para recibir este boletmn. Como usuario de Pms de Mixico, en este acto autoriza de manera expresa que Pms de Mixico le puede contactar vma correo electrsnico u otros medios. Si usted ha recibido este mensaje por error, haga caso omiso de el y reporte su cuenta respondiendo este correo con el subject BAJACFE Unsubscribe to this mailing list, reply a blank message with the subject UNSUBSCRIBE BAJACFE Tenga en cuenta que la gestisn de nuestras bases de datos es de suma importancia y no es intencisn de la empresa la inconformidad del receptor. [demime 1.01d removed an attachment of type image/jpeg which had a name of licitaciones cfe.jpg]
Re: 5.0 vmt0 kernel panic in Linux KVM
Am 08.11.2011 19:27, schrieb Brynet: > > On Mon, Nov 07, 2011 at 03:51:50PM +0100, Walter Haidinger wrote: >> cpu0: AMD Phenom(tm) II X6 1100T Processor ("AuthenticAMD" 686-class, 512KB >> L2 cache) 3.31 GHz >> cpu0: >> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,POPCNT >> ... >> bios0: vendor Bochs version "Bochs" date 01/01/2007 >> bios0: Bochs Bochs > > They shouldn't be pretending to be AMD, especially if that emulation is > very incompatible. I guess I need to clarify this. I ran qemu-kvm with the "-cpu host" option which passes all available host processor features to the guest. This is in fact a tuning option but I never ever had any problems using it before (running OpenBSD, NetBSD, Linux, Solaris-x86, FreeDOS, AROS and several Windows flavors to name a few), so I actually forgot about it. AFAICT, qemu-kvm uses sane defaults, e.g. "qemu64" cpu emulation on 64-bit platforms. http://www.linux-kvm.org/page/Tuning_KVM Walter
Re: 5.0 vmt0 kernel panic in Linux KVM
Am 08.11.2011 19:33, schrieb Brynet: > > On Tue, Nov 08, 2011 at 01:27:37PM -0500, Brynet wrote: >> @@ -190,7 +190,7 @@ k1x_init(struct cpu_info *ci) >> >> #if NACPICPU > 0 >> msr = rdmsr(MSR_K1X_STATUS); >> -k1x_acpi_init(cstate, msr); >> +k1x_acpi_init(cstate); > > Whoops, fixed patch for amd64. I did run i386 bsd. /usr/src/sys/arch/i386/i386/k1x-pstate.c also has k1x_acpi_init(cstate, msr); in line 193 of 5.0's k1x_init(). Can you send me the patch below for i386 to test? Thanks, Walter > -Bryan. > > Index: amd64/amd64/k1x-pstate.c > === > RCS file: /cvs/src/sys/arch/amd64/amd64/k1x-pstate.c,v > retrieving revision 1.2 > diff -u -p -u -r1.2 k1x-pstate.c > --- amd64/amd64/k1x-pstate.c 29 May 2011 12:29:28 - 1.2 > +++ amd64/amd64/k1x-pstate.c 8 Nov 2011 18:30:59 - > @@ -75,7 +75,7 @@ struct k1x_cpu_state *k1x_current_state; > void k1x_transition(struct k1x_cpu_state *, int); > > #if NACPICPU > 0 > -void k1x_acpi_init(struct k1x_cpu_state *, u_int64_t); > +void k1x_acpi_init(struct k1x_cpu_state *); > void k1x_acpi_states(struct k1x_cpu_state *, struct acpicpu_pss *, int, > u_int64_t); > #endif > @@ -154,14 +154,17 @@ k1x_acpi_states(struct k1x_cpu_state *cs > } > > void > -k1x_acpi_init(struct k1x_cpu_state *cstate, u_int64_t msr) > +k1x_acpi_init(struct k1x_cpu_state *cstate) > { > struct acpicpu_pss *pss; > + u_int64_t msr; > > cstate->n_states = acpicpu_fetch_pss(&pss); > if (cstate->n_states == 0) > return; > > + msr = rdmsr(MSR_K1X_STATUS); > + > k1x_acpi_states(cstate, pss, cstate->n_states, msr); > > return; > @@ -172,12 +175,9 @@ k1x_acpi_init(struct k1x_cpu_state *csta > void > k1x_init(struct cpu_info *ci) > { > -#if NACPICPU > 0 > - u_int64_t msr; > -#endif > - u_int i; > struct k1x_cpu_state *cstate; > struct k1x_state *state; > + u_int i; > > if (setperf_prio > 1) > return; > @@ -189,8 +189,7 @@ k1x_init(struct cpu_info *ci) > cstate->n_states = 0; > > #if NACPICPU > 0 > - msr = rdmsr(MSR_K1X_STATUS); > - k1x_acpi_init(cstate, msr); > + k1x_acpi_init(cstate); > #endif > if (cstate->n_states) { > printf("%s: %d MHz: speeds:",