Setting up a a route in FreeBSD with NAT issues
Hi all, I'm trying to setup a gateway between an internal network using Vbox test machines of which one is a FreeBSD router/gateway. Being familiar with Cisco I know how easy this is to do but I think that I'm struggling a bit with the syntax. My setup is as so: Damn Small Linux (virtual machine) - (em1) FreeBSD 8.2 (virtual gateway) (em0) -internal network 10.100.100.2 10.100.100.1 172.16.7.136 172.16.0.0/20 My current configuration within the FreeBSD router looks like so: /etc/rc.conf: gateway_enable=YES hostname=ROUTER.test.org ifconfig_em0=inet 172.16.7.136 netmask 255.255.240.0 #em0_nat=NO ifconfig_em1=inet 10.100.100.1 netmask 255.255.255.192 #em1_nat=YES inetd_enable=YES keymap=uk.iso sshd_enable=YES defaultrouter=172.16.0.1 ipnat_enable=YES ipnat_rules=/etc/ipnat.rules named_enable=YES static_routes=net1 route_net1=-net 10.100.100.0/26 0.0.0.0/0 /etc/ipnat.rules: map tun0 10.100.100.0/26 - 0/0 portmap tcp/udp 1:65000 map tun0 10.100.100.0/26 - 0/0 The router from DSL is set as 10.100.100.1 and it hits it without any problem... running a traceroute however gives this: ROUTER# ipnat -l List of active MAP/Redirect filters: map tun0 10.100.100.0/26 - 0.0.0.0/0 portmap tcp/udp 1:65000 map tun0 10.100.100.0/26 - 0.0.0.0/0 List of active sessions: Something here isn't working and I'm not sure quite what it is :-( Can anyone help??? Thanks Kaya ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Setting up a a route in FreeBSD with NAT issues
Ok I've managed to make some headway however it still isn't working properly: /etc/ipnat.rules #map em1 10.100.100.0/26 - 0.0.0.0/32 portmap tcp/udp 1:65000 map em1 10.100.100.0/26 - 0.0.0.0/32 map em1 10.100.100.0/26 - 0.0.0.0/32 auto I then added this addition to the end of the /etc/rc.conf file: static_routes=em0 em1 route_em1=-net 10.100.100.0/26 172.16.0.0/20 route_em0=-net 172.16.0.0 0.0.0.0/0 when I run traceroute on my host now I can see it going through the system however I'm still not sure it's being NAT'd or routed?? ROUTER# ipnat -l List of active MAP/Redirect filters: map em1 10.100.100.0/26 - 0.0.0.0/32 List of active sessions: MAP 10.100.100.153- - 10.100.100.153[10.100.100.2 32772] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Ross Cameron has left a message for you
Hi, Ross Cameron has left you a message on WAYN. To read message from Ross click on the link below: http://www.wayn.com/invite/23061-kwtcb1/fqe03k-u2977tal38uh All the best, The WAYN Team To stop receiving invite requests from Ross Cameron, click here: http://www.wayn.com/-/23068-kwtcb1?m=1282278c=531038324 To stop receiving any notification from WAYN, click here: http://www.wayn.com/-/23069-kwtcb1?c=531038324 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Ross Cameron has left a message for you
Hi FreeBSD, Ross Cameron has left you a message on WAYN. To read message from Ross click on the link below: http://www.wayn.com/invite/23061-kwtcrl/fqe0og-csqi69276u6qc All the best, The WAYN Team To stop receiving invite requests from Ross Cameron, click here: http://www.wayn.com/-/23068-kwtcrl?m=1282278c=531038992 To stop receiving any notification from WAYN, click here: http://www.wayn.com/-/23069-kwtcrl?c=531038992 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xpdf can not print via cups if started from firefox
On Fri, 11 Mar 2011, O. Hartmann wrote: On 03/11/11 01:13, Polytropon wrote: Maybe you're experiencing a caching problem? I would guess that as you stated there is a temporary file, this should not happen (in relation to Firefox) there should at least be an error message. Did you try to enter the full command into xpdf's printing dialog, e. g. /usr/local/bin/lpr -Pprinter, just in case the .xpdfrc setting hasn't been read upon program start? Yes, I did, still the same problem. I have the strange feeling that a firefox-started xpdf doesn't know anything about CUPS and its printing queues. I try to figure out how to log this ... With a stock lpr/lpd, Firefox and xpdf work as expected. My .xpdfrc is: psFile | lpr -Plaser laser is the queue for my laser printer, defined in /etc/printcap. If the real BSD lpr is being called, you should see errors in /var/log/lpd-errs. There's a CUPS on FreeBSD article: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/cups/index.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Opportunity
Hello, I am developing an international business and I am looking for 2 partners. I entered innovative technologies with international monopoly. The company is listed on NYSE.com and FORBES Magazine Award. The information are PUBLIC. If you are interested to find more about it, please reply to me. Business can be done part-time to start. Sincerely, Daniel Matei ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xpdf can not print via cups if started from firefox
On 03/11/11 16:44, Warren Block wrote: On Fri, 11 Mar 2011, O. Hartmann wrote: On 03/11/11 01:13, Polytropon wrote: Maybe you're experiencing a caching problem? I would guess that as you stated there is a temporary file, this should not happen (in relation to Firefox) there should at least be an error message. Did you try to enter the full command into xpdf's printing dialog, e. g. /usr/local/bin/lpr -Pprinter, just in case the .xpdfrc setting hasn't been read upon program start? Yes, I did, still the same problem. I have the strange feeling that a firefox-started xpdf doesn't know anything about CUPS and its printing queues. I try to figure out how to log this ... With a stock lpr/lpd, Firefox and xpdf work as expected. My .xpdfrc is: psFile | lpr -Plaser laser is the queue for my laser printer, defined in /etc/printcap. If the real BSD lpr is being called, you should see errors in /var/log/lpd-errs. There's a CUPS on FreeBSD article: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/cups/index.html Using xpdf or any other printing client works well with my setup, even xpdf called from a terminal prints correctly, reports pages, access etc. in /var/log/cups/access_log|pages_log as expected. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Setting up a a route in FreeBSD with NAT issues
Eventually I got this thing to work by adding the following syntax into the config files: /etc/rc.conf: gateway_enable=YES hostname=ROUTER.test.org http://ROUTER.test.org ifconfig_em0=inet 172.16.7.136 netmask 255.255.240.0 em0_nat=NO ifconfig_em1=inet 10.100.100.1 netmask 255.255.255.192 em1_nat=YES inetd_enable=YES keymap=uk.iso sshd_enable=YES defaultrouter=172.16.0.1 ipnat_enable=YES ipnat_rules=/etc/ipnat.rules named_enable=YES #static_routes=em0 em1 #route_em1=-net 10.100.100.0/26 http://10.100.100.0/26 172.16.0.0/20 http://172.16.0.0/20 #route_em0=-net 172.16.0.0 0.0.0.0/0 http://0.0.0.0/0 /etc/ipnat.rules #map em0 0.0.0.0/0 http://0.0.0.0/0 - 0/32 proxy port 8080 htto/tcp #map em0 0.0.0.0/0 http://0.0.0.0/0 - 0/32 portmap tcp/udp 1:65000 #map em0 0.0.0.0/0 http://0.0.0.0/0 - 0/32 #map em0 0.0.0.0/0 http://0.0.0.0/0 - 0/32 auto #map em1 10.100.100.0/26 http://10.100.100.0/26 - 0/32 proxy port 8080 http/tcp #map em1 10.100.100.0/26 http://10.100.100.0/26 - 0/32 portmap tcp/udp 1:65000 #map em1 10.100.100.0/26 http://10.100.100.0/26 - 0/32 #map em1 10.100.100.0/26 http://10.100.100.0/26 - 0/32 auto map em0 10.100.100.0/26 http://10.100.100.0/26 - 0/32 proxy port 8080 http/tcp map em0 10.100.100.0/26 http://10.100.100.0/26 - 0/32 portmap tcp/udp 1:65000 map em0 10.100.100.0/26 http://10.100.100.0/26 - 0/32 map em0 10.100.100.0/26 http://10.100.100.0/26 - 0/32 auto The trick was in fact to utilize the external interface within the NAT map file then direct the internal network via the 'gateway of last resort' - default route. The config can be easily adapted and modified from here if anyone is interested in doing something similar or adding extra networks in the middle such as a firewall or proxy Many thanks, Kaya On 03/11/2011 12:34 PM, Kaya Saman wrote: Ok I've managed to make some headway however it still isn't working properly: /etc/ipnat.rules #map em1 10.100.100.0/26 http://10.100.100.0/26 - 0.0.0.0/32 http://0.0.0.0/32 portmap tcp/udp 1:65000 map em1 10.100.100.0/26 http://10.100.100.0/26 - 0.0.0.0/32 http://0.0.0.0/32 map em1 10.100.100.0/26 http://10.100.100.0/26 - 0.0.0.0/32 http://0.0.0.0/32 auto I then added this addition to the end of the /etc/rc.conf file: static_routes=em0 em1 route_em1=-net 10.100.100.0/26 http://10.100.100.0/26 172.16.0.0/20 http://172.16.0.0/20 route_em0=-net 172.16.0.0 0.0.0.0/0 http://0.0.0.0/0 when I run traceroute on my host now I can see it going through the system however I'm still not sure it's being NAT'd or routed?? ROUTER# ipnat -l List of active MAP/Redirect filters: map em1 10.100.100.0/26 http://10.100.100.0/26 - 0.0.0.0/32 http://0.0.0.0/32 List of active sessions: MAP 10.100.100.153 - - 10.100.100.153[10.100.100.2 32772] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
syslog-ng logging stopped
uname -a FreeBSD 7.0-RELEASE syslog-ng --version syslog-ng 2.0.10 change date on syslog-ng.conf is Apr 20 2009 syslog-ng been running untouched for that long. Millions of lines/per day log from 10 source machine. about 00:20 today Friday, all syslogging to syslog-ng stopped. sockstat -4 shows udp/tcp 514 listening chkrootkit shows nothing wrong stop syslog-ng then pkg_delete, and then cd /usr/ports/sysutils/syslog-ng2 make make install start it, no change I rebooted the syslog server. no change trafshow -i bce0 -n then filter 514 ... shows 100KBs arriving from our syslog clients. tshark capture port 514 on syslog-ng box shows plenty of traffic arriving with untouched pf rules active, pfctl -d no change so pfctl -e df shows plenty of disk space for /var suggestions? Len ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Quick question about sound drivers (esp. snd_hda)
It seems to me that under /dev, you can have the following sound-related device files: dspX dspX.Y (among others) I'm having some trouble getting my sound to work (Dell Inspiron E1705/Inspiron 9400 with Sigmatel STAC9220 codec). I've read the manpages for snd and snd_hda (which is the appropriate driver), and increased the verbosity of the drivers and read the kernel log and /dev/sndstat, but I still can't quite wrap my head around everything. What I'm wondering is: what exactly is the meaning of X and Y above? I'm assuming that X comes from the association numbers in the snd_hda driver, but I could be wrong. Please correct me! Thanks, Brian Waters ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Best practices on upgrading, etc.
Hi folks, I'm trying to fully understand the whole FBSD version thing and when, if , and why you should consider upgrading. I have a production server running FBSD 8.1 (and I'm following the errata branch) that works just fine, with no problems. I see that the Production Release of 8.2 is available. Obviously, 8.2 has features that 8.1 does not, but I guess my primary questions is: 1.) If you have a production server that's running well (and is fully patched, i.e. following the errata branch), is there a compelling reason to upgrade or do most people do it because there are features in the new release that you want/need? I guess what I'm really asking is if it makes more sense to take the if it aint broke - don't fix it mindset or should you really consider upgrading when a new version is released??? 2.) If I DO upgrade, I can simply change my supfile to RELENG_8_2 and then: run csup upgrade the ports make buildworld make buildkernel make installkernel make installworld is that right? Is my sequence wrong? 3.) How do I upgrade any installed software (I CAN use portmaster for that, right?)? Thank you, Ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
terminal emulators with secure keyboard capability
For those who aren't aware, XTerm offers a pretty nifty security feature, particular for cases of entering passwords. If you hold down the Ctrl key and the left left mouse button, a menu appears; the second item down is Secure Keyboard. From the XTerm manpage: The Secure Keyboard mode is helpful when typing in passwords or other sensitive data in an unsecure environment; see SECURITY below (but read the limitations carefully). I recommend anyone interested in this feature read the SECURITY section of the xterm(1) manpage, of course. I won't copy all the relevant text here. Let it suffice to say, in summary, that Secure Keyboard mode in XTerm attempts to ensure that all keyboard input is directed only to xterm (using the GrabKeyboard protocol request). I have yet to notice any other terminal emulator with a similar keyboard input protection mode. Does anyone here know of any such terminal emulators, aside from XTerm, that do something like this? -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgpgOnCBREKKX.pgp Description: PGP signature
Re: xorg-driver/xf86-video-ati-6.14.0: Worse performance since last update
On 03/08/11 19:32, Roland Smith wrote: On Tue, Mar 08, 2011 at 07:16:05PM +0100, O. Hartmann wrote: Since the last update of Xorg stuff, including the xf86-video-ati-6.14.0, the video performance of all of our AMD/ATi-driven boxes went worse. The bad performance also occur with the recommendations made in ports/UPDATING for driver radeon. Without those recommendated adding of options even with a working xorg.conf file the performance stays worse. The recommendations have been removed from UPDATING; with the exception of the DynamicPM option, all the others are at their default settings and therefore not necessary. All right, I already adjusted my xorg.conf towards the initial state ... Worse means: using vlc (also after recompilation after upgrades made!), videos are massively bumpy and can not be watched with vlc-screen fully expanded to 1900x1200 pixel with HD4830 graphics card - this worked perfectly before. Check out the logfile '/var/log/Xorg.0.log' if you see anything unusual. Well, for the untrained eye there seems nothing wrong, except the non-existent acceleration ... see below. Moving windows around now looks like having chunks of video content floating around - as on unaccelerated/slow graphics boards. When looking at the logfile '/var/log/Xorg.0.log', does it say the following; (II) RADEON(0): Acceleration enabled (II) RADEON(0): Set up textured video I see this: (II) RADEON(0): MC_FB_LOCATION : 0x00ef00d0 0x001f (II) RADEON(0): MC_AGP_LOCATION : 0x003f (==) RADEON(0): Backing store disabled (WW) RADEON(0): Direct rendering disabled (EE) RADEON(0): Acceleration initialization failed (II) RADEON(0): Acceleration disabled Personally, I have built this port with one of the patches removed. In my case the patch in question hung my machine every time! (there was quite a large thread about it on the mailing-list) Try removing the patch /usr/ports/x11-drivers/xf86-video-ati/files/patch-src-radeon_driver.c and re-install the driver. If that works you can make the change permanent like this: # cd /usr/ports/x11-drivers/xf86-video-ati/files # truncate -s 0 patch-src-radeon_driver.c # chflags schg,sunlnk patch-src-radeon_driver.c Roland Well, yesterday or two days ago there was a change of the port x11-drivers/xf86-video-ati. The file patch-src-radeon_driver.c has gone. But the problems still occur (but not that harsh as before). I realize on all AMD driven graphicsystems this bumpyness, even on those graphics cards, HD4830, which are supposed to deliver a acceptable performance for every day's usage, show now a kind of being cut-off and they are no longer faster than the crappy HD4670 or HD4770 which we also use in some FBSD 9.0 boxes. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Best practices on upgrading, etc.
On Fri, Mar 11, 2011 at 10:03 PM, Ed Flecko edfle...@gmail.com wrote: Hi folks, I'm trying to fully understand the whole FBSD version thing and when, if , and why you should consider upgrading. I have a production server running FBSD 8.1 (and I'm following the errata branch) that works just fine, with no problems. I see that the Production Release of 8.2 is available. Obviously, 8.2 has features that 8.1 does not, but I guess my primary questions is: 1.) If you have a production server that's running well (and is fully patched, i.e. following the errata branch), is there a compelling reason to upgrade or do most people do it because there are features in the new release that you want/need? I guess what I'm really asking is if it makes more sense to take the if it aint broke - don't fix it mindset or should you really consider upgrading when a new version is released??? I do. At a certain point 8.1 will not be supported anymore, and thus no more security updates. 2.) If I DO upgrade, I can simply change my supfile to RELENG_8_2 and then: run csup upgrade the ports make buildworld make buildkernel make installkernel make installworld is that right? Is my sequence wrong? A bit wrong. 1) run csup 2) make buildworld make buildkernel make installkernel 3) reboot 4) make installworld 5) mergemaster 6) reboot 7) upgrade ports 3.) How do I upgrade any installed software (I CAN use portmaster for that, right?)? Yeah, portmaster is key. There is no need to force upgrade of all ports when going from 8.1 to 8.2. -- chs, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Best practices on upgrading, etc.
On Fri, 11 Mar 2011, Ed Flecko wrote: Hi folks, I'm trying to fully understand the whole FBSD version thing and when, if , and why you should consider upgrading. I have a production server running FBSD 8.1 (and I'm following the errata branch) that works just fine, with no problems. I see that the Production Release of 8.2 is available. Obviously, 8.2 has features that 8.1 does not, but I guess my primary questions is: 1.) If you have a production server that's running well (and is fully patched, i.e. following the errata branch), is there a compelling reason to upgrade or do most people do it because there are features in the new release that you want/need? I guess what I'm really asking is if it makes more sense to take the if it aint broke - don't fix it mindset or should you really consider upgrading when a new version is released??? Even with backups, upgrades can be troublesome. Read the release notes. I suggest you have a reason for upgrading in mind -- other than that the number got bumped, and this goes double for a production maching. 2.) If I DO upgrade, I can simply change my supfile to RELENG_8_2 and then: The correct order is given in /usr/src/UPDATING. Do not rely on the following comments, but consult /usr/src/UPDATING. run csup upgrade the ports Update the ports tree and ports after the OS. Otherwise, you may have to do it twice. This is not especially likely in a minor version bump, but it can happen. make buildworld make buildkernel make installkernel make kernel combines the above two steps. Then as single user run mergemaster -p. make installworld then run mergermaster and delete old if you please. -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Best practices on upgrading, etc.
On Fri, 11 Mar 2011 13:03:22 -0800, Ed Flecko edfle...@gmail.com wrote: 1.) If you have a production server that's running well (and is fully patched, i.e. following the errata branch), is there a compelling reason to upgrade or do most people do it because there are features in the new release that you want/need? It mainly depends on program functionality, in my opinion. Let's say you're running a production application (e. g. a server or a service) that needs constant upgrading to be secure to use, and this relies on the new functionality provided by the OS, you should consider upgrading the OS as well. If this is *not* the case, keeping the errata branch of -RELEASE should be sufficient. At some point in time, sooner or later, you'll have to upgrade the OS to the next minor or even major version, and you should keep that in mind. Currently being at 8.1-p is not considered harmful. I guess what I'm really asking is if it makes more sense to take the if it aint broke - don't fix it mindset or should you really consider upgrading when a new version is released??? Depends on your applications and your upgrade policy as well. Personally, I am a big fan of the install once, then keep using approach, providing the recommended and mandatory updates, and keeping everything else intact. 2.) If I DO upgrade, I can simply change my supfile to RELENG_8_2 and then: run csup upgrade the ports make buildworld make buildkernel make installkernel make installworld is that right? Is my sequence wrong? In its presented version: Yes. You should have a look at /usr/src/Makefile and use the procedure mentioned there: 1. `cd /usr/src' (or to the directory containing your source tree). 2. `make buildworld' 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). [steps 3. 4. can be combined by using the kernel target] 5. `reboot'(in single user mode: boot -s from the loader prompt). 6. `mergemaster -p' 7. `make installworld' 8. `make delete-old' 9. `mergemaster' (you may wish to use -U or -ai). 10. `reboot' 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) After the successfully finished make installworld you can start upgrading your installed ports. On the other hand: If you're running a GENERIC kernel, you can easily use the freebsd-update program for binary upgrades. See its manpage for details. 3.) How do I upgrade any installed software (I CAN use portmaster for that, right?)? Yes. See man portupgrade for details (switches -a, -r and -f are important); you can also use portmaster for that, this should be easier than dealing with the ports directly (which is, in any case, possible too). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: syslog-ng logging stopped
-- Original Message -- From: Iñigo Ortiz de Urbina inigoortizdeurb...@gmail.com Date: Fri, 11 Mar 2011 23:12:49 +0100 Whats in dmesg and /var/log/? You shared extensive and excellent troubleshooting info but didnt spot none of these. Keep us updated im sure im not the only one puzzled :) On 3/11/11, Len Conrad lcon...@go2france.com wrote: uname -a FreeBSD 7.0-RELEASE syslog-ng --version syslog-ng 2.0.10 change date on syslog-ng.conf is Apr 20 2009 syslog-ng been running untouched for that long. Millions of lines/per day log from 10 source machine. about 00:20 today Friday, all syslogging to syslog-ng stopped. sockstat -4 shows udp/tcp 514 listening chkrootkit shows nothing wrong stop syslog-ng then pkg_delete, and then cd /usr/ports/sysutils/syslog-ng2 make make install start it, no change I rebooted the syslog server. no change trafshow -i bce0 -n then filter 514 ... shows 100KBs arriving from our syslog clients. tshark capture port 514 on syslog-ng box shows plenty of traffic arriving with untouched pf rules active, pfctl -d no change so pfctl -e df shows plenty of disk space for /var suggestions? Len ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Iñigo Ortiz de Urbina Cazenave http://www.twitter.com/ioc32 = dmesg -a | less showed nothing /var/log/console.log showed nothing /var/log/messages showed nothing ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Quick question about sound drivers (esp. snd_hda)
On Fri, Mar 11, 2011 at 03:29:44PM -0500, Brian Waters wrote: It seems to me that under /dev, you can have the following sound-related device files: dspX dspX.Y (among others) I'm having some trouble getting my sound to work (Dell Inspiron E1705/Inspiron 9400 with Sigmatel STAC9220 codec). I've read the manpages for snd and snd_hda (which is the appropriate driver), and increased the verbosity of the drivers and read the kernel log and /dev/sndstat, but I still can't quite wrap my head around everything. What I'm wondering is: what exactly is the meaning of X and Y above? I'm assuming that X comes from the association numbers in the snd_hda driver, but I could be wrong. Please correct me! Thanks, Brian Waters Have you tried setting the default unit: # sysctl hw.snd.default_unit=1 If that works, you can make it permanent with: # echo hw.snd.default_unit=1 /etc/sysctl.conf If it doesn't, you have to post the output of: $ cat /dev/sndstat Make sure your volume is turned up: mixer(8) HTH. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html pgpzIsMzeo4UM.pgp Description: PGP signature
Re: using dovecot, where is ICOMING mail stored?
On Thu, Mar 10, 2011 at 07:22:45PM -0500, Daniel Staal wrote: --As of March 10, 2011 1:36:45 PM -0800, Gary Kline is alleged to have said: I did try pointing mutt -f at my saved backup /usr/tmp/.../Maildir. Nothing. My copies of saved mail are there, but not what was in the unread queue. I was testing out mutt from a laptop and that has to have been when I accidentially deleted stuff. Too bad there isn't a page on howto set up a mailserver ... for dimwits --As for the rest, it is mine. Ok, my suggestion: First, install Postfix, and check the config option to replace Sendmail. (Sendmail works just fine. It also can be configured to play tic-tack-toe[1]. A mailer that does _not_ have a Turing-complete config file is a lot easier to set up, and you probably won't ever need to use Sendmail's esoteric options. ;) ) I would have replied last night but my shoulder was giving me way too much grief. You know, I use postfix here on my ubuntu desktop. I'm not sure that it is actually used, but it is the default. Equally, by default, sendmail on FBSD. Just so that things work, I'm happy. I've used sendmail since v 2.0.5; bought the book and ground thru about 85 pages before giving up. Pretty sure that there are some spam-blockers in one of the /etc/mail/* files, but that's about all! Then: http://www.perturb.org/display/Postfix___Dovecot___Maildir___IMAPs.html It's a quick walkthrough. It assumes Linux, but that only means the command to install the programs and the location of the config file is wrong. It should get you up and running. This sounds like a must-read. Your mail is probably in /var/mail. That's the default location for mbox files, and you've probably missed setting up Maildir delivery. I don't know how to set that in Sendmail off the top of my head, but it's easy enough to use Postfix. I checked on my server, ethic. Zero. Everything is in ~/Maildir; well, everything but the old files, :-). Daniel T. Staal [1]This is assuming what I've heard on a Turing-complete config file is correct, and not hyperbole. If it's not completely Turing-complete, it's at least very complex. LOL. If it isn't 100% complete, it's close ... I remember the original sendmail. Totally unreable! gary --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 7.98a release of Jottings: http://jottings.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Quick question about sound drivers (esp. snd_hda)
Yeah, I have tried all the basic stuff. At this point, I've basically accepted that solving the problem on my machine is going to involve a whole bunch of technical stuff that I don't have the patience for - reading the HDA spec and the codec datasheet, reading the driver code, and making changes to the driver and default settings where necessary. (The hardware does work fine with the Linux kernel.) So yeah... that's probably never going to happen. I'm still wondering where the numbers in the names for the device special files come from. And thanks, Frank. - BW On Fri, Mar 11, 2011 at 6:31 PM, Frank Shute fr...@shute.org.uk wrote: On Fri, Mar 11, 2011 at 03:29:44PM -0500, Brian Waters wrote: It seems to me that under /dev, you can have the following sound-related device files: dspX dspX.Y (among others) I'm having some trouble getting my sound to work (Dell Inspiron E1705/Inspiron 9400 with Sigmatel STAC9220 codec). I've read the manpages for snd and snd_hda (which is the appropriate driver), and increased the verbosity of the drivers and read the kernel log and /dev/sndstat, but I still can't quite wrap my head around everything. What I'm wondering is: what exactly is the meaning of X and Y above? I'm assuming that X comes from the association numbers in the snd_hda driver, but I could be wrong. Please correct me! Thanks, Brian Waters Have you tried setting the default unit: # sysctl hw.snd.default_unit=1 If that works, you can make it permanent with: # echo hw.snd.default_unit=1 /etc/sysctl.conf If it doesn't, you have to post the output of: $ cat /dev/sndstat Make sure your volume is turned up: mixer(8) HTH. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Quick question about sound drivers (esp. snd_hda)
Hi, On Saturday 12 March 2011 04:29:44 Brian Waters wrote: It seems to me that under /dev, you can have the following sound-related device files: dspX dspX.Y (among others) this is what you see after your driver is loaded. You might have to tell an application which one to use. I'm having some trouble getting my sound to work (Dell Inspiron E1705/Inspiron 9400 with Sigmatel STAC9220 codec). I've read the manpages for snd and snd_hda (which is the appropriate driver), and increased the verbosity of the drivers and read the kernel log and /dev/sndstat, but I still can't quite wrap my head around everything. I have different hardware but I use the same driver. I did not compile it into the kernel after getting into trouble. Since I load it with: kldload snd_hda it works as expected. If trouble come up, I kick it our and reload it. What I'm wondering is: what exactly is the meaning of X and Y above? I'm assuming that X comes from the association numbers in the snd_hda driver, but I could be wrong. Please correct me! I do not really know but I have had to tell vlc which to use. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Quick question about sound drivers (esp. snd_hda)
2011-03-11 21:29, Brian Waters: It seems to me that under /dev, you can have the following sound-related device files: dspX dspX.Y (among others) I'm having some trouble getting my sound to work (Dell Inspiron E1705/Inspiron 9400 with Sigmatel STAC9220 codec). I've read the manpages for snd and snd_hda (which is the appropriate driver), and increased the verbosity of the drivers and read the kernel log and /dev/sndstat, but I still can't quite wrap my head around everything. What I'm wondering is: what exactly is the meaning of X and Y above? I'm assuming that X comes from the association numbers in the snd_hda driver, but I could be wrong. Please correct me! This is what I think. dsp0.0 is the first device on the first bus and so on. %ls -l /dev/ds* crw-rw-rw- 1 root wheel0, 155 11 Mar 19:16 /dev/dsp0.0 crw-rw-rw- 1 root wheel0, 148 9 Mar 11:16 /dev/dsp1.0 crw-rw-rw- 1 root wheel0, 146 9 Mar 11:16 /dev/dsp2.0 crw-rw-rw- 1 root wheel0, 121 9 Mar 11:16 /dev/dsp3.0 %cat /dev/sndstat FreeBSD Audio Driver (newpcm: 64bit 2009061500/amd64) Installed devices: pcm0: HDA Realtek ALC888 PCM #0 Analog (play/rec) default pcm1: HDA Realtek ALC888 PCM #1 Analog (play/rec) pcm2: HDA Realtek ALC888 PCM #2 Digital (play/rec) pcm3: HDA ATI R6xx HDMI PCM #0 HDMI (play) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Installing FreeBSD 8.1 on MacBook 5,1
Hi, I've been trying to dual-boot FreeBSD 8.1 with Mac OS X on my MacBook (5,1) for some time now, but am having trouble trying to get the live cd to boot. I reach the FreeBSD Boot Loader Screen with the options for boot, boot without ACPI etc. However, I cannot select an option. I have tried with both the built in keyboard and a USB keyboard, but I do not think that that is the problem... Previously I have tried dual booting Ubuntu, but had problems with the live CD also. During the boot process, the boot seemed to freeze, and the CD stopped spinning. I think it might be a similiar problem here. Soon after arriving at this screen, the CD stops spinning. Thanks for any advice! BTW. I'm using the amd64 disc1 iso image == Further Boot Info == When booting, Mac's EFI allows me to choose to boot from the CD. The screen goes black, then the following appears: CD Loader 1.2 Building the boot loader arguments Looking up /BOOT/LOADER ... Found Relocating the loader and the BTX Starting the BTX Loader BTX Loader 1.00 BTX version is 1.0.2 Consoles: internal video/keyboard BIOS CD is cd0 BIOS drive C: is disk0 BIOS 639kB/1047552kB available memory Loading /boot/defaults/loader.conf /boot/kernel/kernel text=0x8d5503 data=0x129bf8+039f8 syms=[0x8 + 0xddbf8 + 0x8 + 0xca37e] It then continues to the FreeBSD Boot Loader Screen, and freezes I have also posted this question on the FreeBSD forums, but after a month there has still been no answer. The same can be said for two other sites I posted the question on: super user the Unix and Linux Stackexchange. Sent from my iPod___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to get Huawei USB modem to work ?
Hi, On Sunday 02 January 2011 19:54:57 Manish Jain wrote: Hello, From a similar thread, I picked up some information that I should try kldload'ing usba. But when I ran the command, I got an error message that there is no such module. I searched under sys/modules and there was no usba.ko Can somebody please tell me how to get my Huawei USB dial-up modem to work on FreeBSD 8.1 ? From dmesg, I have the following information : Trying to mount root from ufs:/dev/ad8s2a ugen0.3: HUAWEI TECHNOLOGIES at usbus0 u3g0: Data Interface on usbus0 u3g0: Found 3 ports. umass0: HUAWEI TECHNOLOGIES HUAWEI Mobile, class 0/0, rev 1.10/0.00, addr 3 on usbus0 umass0: SCSI over Bulk-Only; quirks = 0x umass0:0:0:-1: Attached to scbus0 cd0 at umass-sim0 bus 0 scbus0 target 0 lun 0 cd0: HUAWEI Mass Storage 2.31 Removable CD-ROM SCSI-0 device cd0: 1.000MB/s transfers cd0: cd present [16896 x 2048 byte records] (probe0:umass-sim0:0:0:1): TEST UNIT READY. CDB: 0 20 0 0 0 0 (probe0:umass-sim0:0:0:1): CAM status: SCSI Status Error (probe0:umass-sim0:0:0:1): SCSI status: Check Condition (probe0:umass-sim0:0:0:1): SCSI sense: NOT READY asc:3a,0 (Medium not present) da0 at umass-sim0 bus 0 scbus0 target 0 lun 1 da0: HUAWEI SD Storage 2.31 Removable Direct Access SCSI-2 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present drm0: ATI Radeon HD 3200 Graphics on vgapci0 info: [drm] MSI enabled 1 message(s) vgapci0: child drm0 requested pci_enable_busmaster Any help would be greatly appreciated. if your modem is not supported out of the box, go to the file usbdevs and add an entry for it: I got last week a modem not supported by FreeBSD and just did this: product HUAWEI ETS2055 0x1803 CDMA modem 0x1803 is the ID of my modem. The ID is unknown to FreeBSD 8.2. Then add a line like the following to u3g.c: U3G_DEV(HUAWEI, ETS2055, U3GINIT_HUAWEI), Check the file for the other options like U3GINIT_HUAWEI you have. The chances are then pretty high that all will work The next problem will then your ppp.conf. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Best practices on upgrading, etc.
Hi, On Saturday 12 March 2011 05:03:22 Ed Flecko wrote: I have a production server running FBSD 8.1 (and I'm following the errata branch) that works just fine, with no problems. I see that the Production Release of 8.2 is available. Obviously, 8.2 has features that 8.1 does not, but I guess my primary questions is: 1.) If you have a production server that's running well (and is fully patched, i.e. following the errata branch), is there a compelling reason to upgrade or do most people do it because there are features just do use your words: if you have a running system which does not have any problems, wait at least for maybe a month before you install the upgrade. There have been times when even FreeBSD gave problems after an upgrade a few days after release. in the new release that you want/need? I guess what I'm really asking is if it makes more sense to take the if it aint broke - don't fix it mindset or should you really consider upgrading when a new version is released??? I just upgraded to 8.2 on my workstation having a fully operating 8.1 installation on the second disk. upgrade the ports If you upgrade only the minor version number, a portupgrade is normally not needed. At least my ports installed this January still work. It is different on a major version number chance. Anyway, I would suggest to stay with the 8.x branch for this machine until the 10 branch is reliable. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
