Re: Best upgrade strategy
jason henson [EMAIL PROTECTED] writes: Glyn Millington wrote: Greetings! I'm a newcomer to FreeBSD, an immigrant from the wonderful world of Slackware Linux. Finished installing on Sunday! I wanted to make sure the system was up to date with regard to security fixes etc so used cvsup to upgrade source and re-built the kernel - it all went like a dream - what a system!! What documentation!! Hold on, just the kernel or the kernel and world. You have to keep these in sync on FreeBSD. Just checking because I hear you can just upgrade the linux kernel to your hearts content without messing with the other stuff on the system. Bless you, no, I did the lot! Buildworld, installworld, the works as described in the handbook. And was staggered by how straightforward it was, to be honest. No, my question was about swapping the target for cvsup at the point when 5.4 becomes a production release - can I then simply track 5.4 for security releases etc or will that cause complications with a system that has tracked 5-stable for the few days it has been in existence. It sems form the various replies I've had that there should be no problem. Many thanks Glyn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
About Apache
I installed Awstat, the log report url is something like http://www.mydomain.com/awstats/awstats.pl, I added password protection for the directory /awstats, everything works fine. But I found someone accessed the url http://www.mydomain.com/cgi-bin/awstats.pl, it's supposed to be a 404 error, but it is redirected to http://www.mydomain.com/awstats/awstats.pl . My question is why the url http://www.mydomain.com/cgi-bin/awstats.pl is working, any other options to make it work besides rewrite, alias and link. Thanks! Here is all related lines in httpd.conf: --- ScriptAlias /cgi-bin/ /usr/local/www/cgi-bin/ ScriptAlias /awstats/ /usr/local/etc/awstats/wwwroot/cgi-bin/ Directory /usr/local/etc/awstats/wwwroot Options None AllowOverride authconfig Order allow,deny Allow from All /Directory --- Output of ll /usr/local/www/cgi-bin/, nothing is related to /awstats/ -rw-r--r-- 1 root wheel0 Nov 3 17:24 EXAMPLE_DIRECTORY-DONT_ADD_OR_TOUCH_ANYTHING -rw-r--r-- 1 root wheel 274 Nov 3 17:24 printenv -rw-r--r-- 1 root wheel 757 Nov 3 17:24 test-cgi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
spam alert
got a message from my ISP saying that my email address was sending out spam, possibly from a trojan on my pc that was allowing a remote program to access my SMTP server and send email without my knowledge. I was shocked since I'm running ZoneAlarm and don't remember getting any alerts about a program accessing my email. I ran Norton's and it didn't find anything. BUT it was blocking a heap of outgoing emails with sexually explicit content after I disabled ZoneAlarm. So ZoneAlarm must be blocking them when it is on, but periodically I turn it off because some web pages don't load correctly when I use ZoneAlarm. Well I disabled ZoneAlarm tonight and right away I got popups from Nortons alerting me that there were sexually explicit emails trying to be sent using my mail account, at a rate of about 20 per minute! I turned ZoneAlarm back on and immediately it told me that IP address 204.152.184.73 was trying to send emails and make a connection with my mail server, which of course I blocked. 204.152.184.73 resolves to freebsd.isc.org. what gives? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SMBQ
Message: 3 Date: Tue, 12 Apr 2005 15:38:27 +0200 From: Lis [EMAIL PROTECTED] Subject: Re: SMBQ To: FreeBSD-Questions@FreeBSD.ORG Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; format=flowed; charset=Windows-1252; reply-type=response u must change the security to user the public to no only guest to no But that would change the entire directory, not just a subdirectory. What I was hoping to be able to do was create a new subdirectory but ask the users for a password for that subdiretory only, not the entire branch. Does anyone know if this is possible in Samba ? Even if I could just create a new password protected share without changing or effecting existing ones... can you do anything like this? [Private] comment = Private path = /Private public = no writable = yes only guest = no password = 9letmein9 Thanks for your replies. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
how to make my RAID device WORM(write once and read many)
hai, I am working Raid5 storage device and i want to make my device WORM(write once and read many) and undeleatable. I formated the target device in vfat, when i am mounting the device in host machine it should behavie like WORM. To achive this feature whether i have to change in host machine or target machine, which one is better approach and plz tell me how to achive this. bye ppk __ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: spam alert
On Wed, Apr 13, 2005 at 03:29:03AM -0400, Robert wrote: my email address was sending out spam, [snip] IP address 204.152.184.73 was trying to send emails and make a connection with my mail server, which of course I blocked. 204.152.184.73 resolves to freebsd.isc.org. what gives? freebsd.isc.org is not anything to do with freebsd as such. The first part of that output is the hostname, and refers to the name that isc.org gave to one of their computers. Perhaps you should get in contact with them directly. From whois: Domain Name:ISC.ORG Last Updated On:06-Apr-2005 01:33:20 UTC Expiration Date:05-Apr-2006 04:00:00 UTC Sponsoring Registrar:Alice's Registry, Inc. (R16-LROR) Registrant ID:ALICE-ISC1-CT Registrant Name:Internet Systems Consortium, Inc. Registrant Street1:950 Charter Street Registrant City:Redwood City Registrant State/Province:CA Registrant Postal Code:94063 Registrant Country:US Registrant Phone:+1.6507797000 Registrant FAX:+1.6507797055 Registrant Email:[EMAIL PROTECTED] Admin Name:Internet Systems Consortium, Inc. Admin Street1:950 Charter Street Admin City:Redwood City Admin State/Province:CA Admin Postal Code:94063 Admin Phone:+1.6507797000 Admin Email:[EMAIL PROTECTED] Otherwise, block the port, and look into the configuration of your mailserver to check that it is not relaying mail for others servers that you don't trust. Without knowing anything about your mailserver, I'm unable to help further. Cheers, Tim ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem with inetd and ssh(d)
Hello list, I have since days ervery ten minutes on my workstation xxx.domain.tld a entry in my /var/log/messages and on the console at the root-account these messages are appearing: -8 Apr 13 10:30:53 xxx inetd[500]: ssh/tcp: bind: Address already in use Apr 13 10:40:53 xxx inetd[500]: ssh/tcp: bind: Address already in use Apr 13 10:50:53 xxx inetd[500]: ssh/tcp: bind: Address already in use Apr 13 11:00:53 xxx inetd[500]: ssh/tcp: bind: Address already in use Apr 13 11:10:53 xxx inetd[500]: ssh/tcp: bind: Address already in use Apr 13 11:20:53 xxx inetd[500]: ssh/tcp: bind: Address already in use Apr 13 11:30:53 xxx inetd[500]: ssh/tcp: bind: Address already in use -8 I know that inetd was writing this in this file and that ssh(d) has a problem. bind (named) is not running on my workstation. ssh/sshd is definitly running because I am using it at the moment. My problem is that I don't know how to handle with the problem, because I don't know what inetd wants from me. I looked in man inetd but there is not this error described... With regards Stevan Tiefert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hard drive fullness limits information help request
Message-id: [EMAIL PROTECTED] NMH [EMAIL PROTECTED], Learn Comply with http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html#ERESOURCES-MAIL No cross posting No personal attacks Else do not post to FreeBSD lists. cc'd [EMAIL PROTECTED] - Julian StaceyNet Sys Eng Consultant, Munich http://berklix.com Mail in Ascii (Html=Spam). Ihr Rauch = mein allergischer Kopfschmerz. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with inetd and ssh(d)
Stevan Tiefert wrote: Hello list, I have since days ervery ten minutes on my workstation xxx.domain.tld an entry in my /var/log/messages and on the console at the root-account these messages are appearing: Apr 13 10:30:53 xxx inetd[500]: ssh/tcp: bind: Address already in use Is sshd running as an independent daemon and also enabled in the /etc/inetd.conf file? That will cause a clash on port 22. If you have sshd_enable=YES in /etc/rc.conf, then disable it in /etc/inetd.conf; and vice versa. (you should prefer the first option). Rob. __ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with inetd and ssh(d)
Stevan Tiefert wrote: Apr 13 10:30:53 xxx inetd[500]: ssh/tcp: bind: Address already in use I know that inetd was writing this in this file and that ssh(d) has a problem. bind (named) is not running on my workstation. Someone already made a suggestion, but you should know that bind in this message is nothing to do with DNS Bind software. The bind is a system call involved in setting up a socket. See man 2 bind. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)
On Wed, Apr 13, 2005 at 01:10:42AM -0500, Edgar Martinez wrote: All, I cant begin to tell you how horrible of a time I have had trying to get this system installed and running. Sysinstall kept throwing up a privilege fault kernel error randomly (7sed...4m.7m..etc), and after I go fast enough to get lucky to an install complete..the system then spends its time periodically rebooting.this is the first venture into AMD64 turf as I historically stick with i386.so any pointers.gotchas.tweaks or tips.. please let me know..I really don't want to give up, so I want to see what can be done to stabilize this. Sounds like the usual bad hardware story..check RAM, power supply, CPU cooling, cabling, etc. kris pgpKNP0L6zNAb.pgp Description: PGP signature
ssh dies
Dear All, An interesting and disturbing problem recently appeared on our server which is running FBSD 5.3. Rather suddenly, all users found themselves locked out because ssh stopped working. We had to send an email to tech support at our hosting service (Netsonic). They said this seems to be happening frequently on many FreeBSD servers (something to do with reaching the limit of ssh connections). They didn't tell us how to solve the problem, but they suggested rebooting, which should return the server under our control. We asked them to reboot and they did, problem solved for now. I'm wondering if anyone knows what is causing this, and if there is a permanent solution? The server was running fine for four months without issues - this just suddenly came out of the blue. TIA, Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH] puc/ppc and amd64
On Thu, 07 Apr 2005, David Taylor wrote: Hi, I've got an amd64 box with 1 built-in parallel port, which works fine. I also bought an add-on parallel port adapter card (a MosChip SemiConductors Nm9805 chip). After discovering puc, I enabled device puc and the card is now detected by puc, but doesn't appear to be picked up by the ppc driver. I have now, finally, figured out what was going on. After much wasted time trying to debug ppc_puc.c, I realised it wasn't even being compiled in the kernel. After adding dev/ppc/ppc_puc.c to files.amd64, everything worked a lot better. A patch (against 5-STABLE) is attached, which adds ppc_puc.c to all architectures with ppc.c listed (alpha, amd64, ia64 -- I can only test amd64, however). If this gets lost for ages, I'll add a PR... -- David Taylor --- sys/conf/files.alpha.oldWed Apr 13 12:20:57 2005 +++ sys/conf/files.alphaWed Apr 13 12:21:43 2005 @@ -183,6 +183,7 @@ dev/kbd/kbd.c optionalsc dev/kbd/kbd.c optionalukbd dev/ppc/ppc.c optionalppc +dev/ppc/ppc_puc.c optionalppc puc pci dev/sio/sio.c optionalsio dev/sio/sio_isa.c optionalsio isa dev/syscons/schistory.coptionalsc --- sys/conf/files.amd64.oldWed Apr 13 12:21:15 2005 +++ sys/conf/files.amd64Wed Apr 13 12:21:53 2005 @@ -133,6 +133,7 @@ dev/kbd/kbd.c optionalukbd dev/mem/memutil.c optionalmem dev/ppc/ppc.c optionalppc +dev/ppc/ppc_puc.c optionalppc puc pci dev/sio/sio.c optionalsio dev/sio/sio_isa.c optionalsio isa dev/syscons/apm/apm_saver.coptionalapm_saver apm --- sys/conf/files.ia64.old Wed Apr 13 12:21:05 2005 +++ sys/conf/files.ia64 Wed Apr 13 12:22:11 2005 @@ -59,6 +59,7 @@ dev/kbd/kbd.c optionalsc dev/kbd/kbd.c optionalukbd dev/ppc/ppc.c optionalppc isa +dev/ppc/ppc_puc.c optionalppc puc pci dev/syscons/schistory.coptionalsc dev/syscons/scmouse.c optionalsc dev/syscons/scterm-dumb.c optionalsc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make option for openoffice-devel?
Trey Sizemore [EMAIL PROTECTED] writes: I've got openoffice-devel installed and there's a newer version available in ports. It's currently marked as broken/ignore. What is the correct make option to go ahead with the upgrade? And for future reference, where are these options located? Like - DDISABLE_VULNERABILITIES, Most of the time, there is no such option. If a porter knew how to un-break the port, they would have done that, and removed the BROKEN line completely. In this particular case, just try building the port and it will tell you about the kind of system upgrade you need to let that port build successfully. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: postfix, what does this mean?
Henry wrote: Err, I've got a bunch of mail questions... What the heck is going on here? Apr 12 23:26:48 postfix/qmgr[73146]: 8B46133C3E: from=, size=2716, nrcpt=1 (queue active) Apr 12 23:26:48 postfix/qmgr[73146]: D956C33C39: from=, size=2712, nrcpt=1 (queue active) Apr 12 23:26:48 postfix/qmgr[73146]: 5C36533C23: from=, size=2994, nrcpt=1 (queue active) Apr 12 23:26:48 postfix/qmgr[73146]: B9A8E33C21: from=, size=2950, nrcpt=1 (queue active) Apr 12 23:26:48 postfix/smtp[73236]: connect to smtp2.nix.paypal.com[64.4.240.75]: Operation not permitted (port 25) Apr 12 23:26:48 postfix/smtp[73236]: connect to smtp1.nix.paypal.com[64.4.240.74]: Operation not permitted (port 25) Apr 12 23:26:48 postfix/smtp[73236]: connect to smtp1.sc5.paypal.com[64.4.244.74]: Operation not permitted (port 25) Apr 12 23:26:48 postfix/smtp[73239]: connect to smtp1.nix.paypal.com[64.4.240.74]: Operation not permitted (port 25) Apr 12 23:26:48 postfix/smtp[73239]: connect to smtp1.sc5.paypal.com[64.4.244.74]: Operation not permitted (port 25) Apr 12 23:26:48 postfix/smtp[73239]: connect to smtp2.nix.paypal.com[64.4.240.75]: Operation not permitted (port 25) Apr 12 23:26:48 postfix/smtp[73236]: 8B46133C3E: to=[EMAIL PROTECTED], relay=none, delay=182913, status=deferred (connect to smtp1.sc5.paypal.com[64.4.244.74]: Operation not permitted) Apr 12 23:26:48 postfix/smtp[73239]: D956C33C39: to=[EMAIL PROTECTED], relay=none, delay=190298, status=deferred (connect to smtp2.nix.paypal.com[64.4.240.75]: Operation not permitted) Apr 12 23:26:48 postfix/smtp[73240]: connect to rsliberty.nswebhost.com[67.18.67.68]: Operation not permitted (port 25) Apr 12 23:26:48 postfix/smtp[73240]: 5C36533C23: to=[EMAIL PROTECTED], relay=none, delay=60736, status=deferred (connect to rsliberty.nswebhost.com[67.18.67.68]: Operation not permitted) There from is not an omitted address... What is paypal trying to do? The last log is someone on nswebhost trying to use my smtp to send their mail correct? Is that what paypal is trying to do? But why? Subscribe to the Postfix users list. -- Best regards, Chris The first bug to hit a clean windshield lands directly in front of your eyes. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Using PPPoE
Hello All, Sorry if this was discused here before but I couldn't find it on archives.. I have an ADSL PPPoE connection with my Internet provider, my modem is an Alcatel Speed Touch Pro, bridged mode. It works fine on windows (using a built-in dialer) and linux (using rp-pppoe) - multi boot box. I've followed the handbook instructions (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/pppoe.html) to make it work on FreeBSD with PPPoE without success. My ppp.conf is just like section 21.5.2: default: set log phase chat connect lcp ipcp tun command set ifaddr 10.0.0.140/32 0.0.0.0/0 brtelecom: set device PPPoE:sis0 set authname myusername set authkey mypassword set dial set login add default HISADDR When I run ppp -ddial brt modem lights start to blink, but ifconfig shows interface tun0 without any IP address and /var/log/ppp.log shows: [EMAIL PROTECTED] ppp]# tail -f /var/log/ppp.log Apr 12 01:13:01 alex ppp[9723]: tun0: IPCP: deflink: Oops, RCR in Initial. Apr 12 01:13:04 alex ppp[9723]: tun0: IPCP: deflink: RecvConfigReq(112) state = Initial Apr 12 01:13:04 alex ppp[9723]: tun0: IPCP: IPADDR[6] 200.103.98.174 Apr 12 01:13:04 alex ppp[9723]: tun0: IPCP: deflink: Oops, RCR in Initial. Apr 12 01:13:07 alex ppp[9723]: tun0: IPCP: deflink: RecvConfigReq(113) state = Initial Apr 12 01:13:07 alex ppp[9723]: tun0: IPCP: IPADDR[6] 200.103.98.174 Apr 12 01:13:07 alex ppp[9723]: tun0: IPCP: deflink: Oops, RCR in Initial. Apr 12 01:13:10 alex ppp[9723]: tun0: IPCP: deflink: RecvConfigReq(114) state = Initial Apr 12 01:13:10 alex ppp[9723]: tun0: IPCP: IPADDR[6] 200.103.98.174 Apr 12 01:13:10 alex ppp[9723]: tun0: IPCP: deflink: Oops, RCR in Initial. Apr 12 01:13:13 alex ppp[9723]: tun0: IPCP: deflink: RecvConfigReq(115) state = Initial Apr 12 01:13:13 alex ppp[9723]: tun0: IPCP: IPADDR[6] 200.103.98.174 Apr 12 01:13:13 alex ppp[9723]: tun0: IPCP: deflink: Oops, RCR in Initial. Apr 12 01:13:16 alex ppp[9723]: tun0: IPCP: deflink: RecvConfigReq(116) state = Initial Apr 12 01:13:16 alex ppp[9723]: tun0: IPCP: IPADDR[6] 200.103.98.174 Apr 12 01:13:16 alex ppp[9723]: tun0: IPCP: deflink: Oops, RCR in Initial. Apr 12 01:13:19 alex ppp[9723]: tun0: IPCP: deflink: RecvConfigReq(117) state = Initial Apr 12 01:13:19 alex ppp[9723]: tun0: IPCP: IPADDR[6] 200.103.98.174 Apr 12 01:13:19 alex ppp[9723]: tun0: IPCP: deflink: Oops, RCR in Initial. Apr 12 01:13:22 alex ppp[9723]: tun0: IPCP: deflink: RecvConfigReq(118) state = Initial Apr 12 01:13:22 alex ppp[9723]: tun0: IPCP: IPADDR[6] 200.103.98.174 Apr 12 01:13:22 alex ppp[9723]: tun0: IPCP: deflink: Oops, RCR in Initial I don't have a default gateway.. and PPP can get the ISPs DNS! I think there's something really small that I'm missing.. Anyone could help me? Thanks in advance. Alexandre ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
nvidia stale dependency
x11/nvidia-driver depends (at install-time) on ${X_SERVER_PORT}
--
Arseny Nasokin (aka Tarc)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Using PPPoE
This is described in detail in the FreeBSD Install book at http://freebsd.easyasthat.co.uk/ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Alexandre Vasconcelos Sent: Wednesday, April 13, 2005 9:04 AM To: freebsd-questions@freebsd.org Subject: Using PPPoE Hello All, Sorry if this was discused here before but I couldn't find it on archives.. I have an ADSL PPPoE connection with my Internet provider, my modem is an Alcatel Speed Touch Pro, bridged mode. It works fine on windows (using a built-in dialer) and linux (using rp-pppoe) - multi boot box. I've followed the handbook instructions (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/pppoe.htm l) to make it work on FreeBSD with PPPoE without success. My ppp.conf is just like section 21.5.2: default: set log phase chat connect lcp ipcp tun command set ifaddr 10.0.0.140/32 0.0.0.0/0 brtelecom: set device PPPoE:sis0 set authname myusername set authkey mypassword set dial set login add default HISADDR When I run ppp -ddial brt modem lights start to blink, but ifconfig shows interface tun0 without any IP address and /var/log/ppp.log shows: [EMAIL PROTECTED] ppp]# tail -f /var/log/ppp.log Apr 12 01:13:01 alex ppp[9723]: tun0: IPCP: deflink: Oops, RCR in Initial. Apr 12 01:13:04 alex ppp[9723]: tun0: IPCP: deflink: RecvConfigReq(112) state = Initial Apr 12 01:13:04 alex ppp[9723]: tun0: IPCP: IPADDR[6] 200.103.98.174 Apr 12 01:13:04 alex ppp[9723]: tun0: IPCP: deflink: Oops, RCR in Initial. Apr 12 01:13:07 alex ppp[9723]: tun0: IPCP: deflink: RecvConfigReq(113) state = Initial Apr 12 01:13:07 alex ppp[9723]: tun0: IPCP: IPADDR[6] 200.103.98.174 Apr 12 01:13:07 alex ppp[9723]: tun0: IPCP: deflink: Oops, RCR in Initial. Apr 12 01:13:10 alex ppp[9723]: tun0: IPCP: deflink: RecvConfigReq(114) state = Initial Apr 12 01:13:10 alex ppp[9723]: tun0: IPCP: IPADDR[6] 200.103.98.174 Apr 12 01:13:10 alex ppp[9723]: tun0: IPCP: deflink: Oops, RCR in Initial. Apr 12 01:13:13 alex ppp[9723]: tun0: IPCP: deflink: RecvConfigReq(115) state = Initial Apr 12 01:13:13 alex ppp[9723]: tun0: IPCP: IPADDR[6] 200.103.98.174 Apr 12 01:13:13 alex ppp[9723]: tun0: IPCP: deflink: Oops, RCR in Initial. Apr 12 01:13:16 alex ppp[9723]: tun0: IPCP: deflink: RecvConfigReq(116) state = Initial Apr 12 01:13:16 alex ppp[9723]: tun0: IPCP: IPADDR[6] 200.103.98.174 Apr 12 01:13:16 alex ppp[9723]: tun0: IPCP: deflink: Oops, RCR in Initial. Apr 12 01:13:19 alex ppp[9723]: tun0: IPCP: deflink: RecvConfigReq(117) state = Initial Apr 12 01:13:19 alex ppp[9723]: tun0: IPCP: IPADDR[6] 200.103.98.174 Apr 12 01:13:19 alex ppp[9723]: tun0: IPCP: deflink: Oops, RCR in Initial. Apr 12 01:13:22 alex ppp[9723]: tun0: IPCP: deflink: RecvConfigReq(118) state = Initial Apr 12 01:13:22 alex ppp[9723]: tun0: IPCP: IPADDR[6] 200.103.98.174 Apr 12 01:13:22 alex ppp[9723]: tun0: IPCP: deflink: Oops, RCR in Initial I don't have a default gateway.. and PPP can get the ISPs DNS! I think there's something really small that I'm missing.. Anyone could help me? Thanks in advance. Alexandre ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)
OK, removed all misc cards, devices, recabled...attempting to reinstall with 5.3, and I continue to get a kernel: priviledged instruction fault followed by a reboot...RAM is brand new Patriot 2-2-2-5...mem timings? -Original Message- From: Kris Kennaway [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 13, 2005 5:23 AM To: Edgar Martinez Cc: freebsd-questions@freebsd.org Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install) On Wed, Apr 13, 2005 at 01:10:42AM -0500, Edgar Martinez wrote: All, I cant begin to tell you how horrible of a time I have had trying to get this system installed and running. Sysinstall kept throwing up a privilege fault kernel error randomly (7sed...4m.7m..etc), and after I go fast enough to get lucky to an install complete..the system then spends its time periodically rebooting.this is the first venture into AMD64 turf as I historically stick with i386.so any pointers.gotchas.tweaks or tips.. please let me know..I really don't want to give up, so I want to see what can be done to stabilize this. Sounds like the usual bad hardware story..check RAM, power supply, CPU cooling, cabling, etc. kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)
Its using the default bios settings and nothing is overclocked at all.. -Original Message- From: Trevor Sullivan [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 13, 2005 9:00 AM To: [EMAIL PROTECTED] Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install) Edgar Martinez wrote: OK, removed all misc cards, devices, recabled...attempting to reinstall with 5.3, and I continue to get a kernel: priviledged instruction fault followed by a reboot...RAM is brand new Patriot 2-2-2-5...mem timings? -Original Message- From: Kris Kennaway [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 13, 2005 5:23 AM To: Edgar Martinez Cc: freebsd-questions@freebsd.org Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install) On Wed, Apr 13, 2005 at 01:10:42AM -0500, Edgar Martinez wrote: All, I cant begin to tell you how horrible of a time I have had trying to get this system installed and running. Sysinstall kept throwing up a privilege fault kernel error randomly (7sed...4m.7m..etc), and after I go fast enough to get lucky to an install complete..the system then spends its time periodically rebooting.this is the first venture into AMD64 turf as I historically stick with i386.so any pointers.gotchas.tweaks or tips.. please let me know..I really don't want to give up, so I want to see what can be done to stabilize this. Sounds like the usual bad hardware story..check RAM, power supply, CPU cooling, cabling, etc. kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Is this computer overclocked at all? I would highly recommend running it at the speeds it was meant to...you can avoid a lot of errors that way. -Trevor ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)
New error before death Panic: page fault -Original Message- From: Trevor Sullivan [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 13, 2005 9:00 AM To: [EMAIL PROTECTED] Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install) Edgar Martinez wrote: OK, removed all misc cards, devices, recabled...attempting to reinstall with 5.3, and I continue to get a kernel: priviledged instruction fault followed by a reboot...RAM is brand new Patriot 2-2-2-5...mem timings? -Original Message- From: Kris Kennaway [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 13, 2005 5:23 AM To: Edgar Martinez Cc: freebsd-questions@freebsd.org Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install) On Wed, Apr 13, 2005 at 01:10:42AM -0500, Edgar Martinez wrote: All, I cant begin to tell you how horrible of a time I have had trying to get this system installed and running. Sysinstall kept throwing up a privilege fault kernel error randomly (7sed...4m.7m..etc), and after I go fast enough to get lucky to an install complete..the system then spends its time periodically rebooting.this is the first venture into AMD64 turf as I historically stick with i386.so any pointers.gotchas.tweaks or tips.. please let me know..I really don't want to give up, so I want to see what can be done to stabilize this. Sounds like the usual bad hardware story..check RAM, power supply, CPU cooling, cabling, etc. kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Is this computer overclocked at all? I would highly recommend running it at the speeds it was meant to...you can avoid a lot of errors that way. -Trevor ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
What sound drive should I use?
I have problems with sound on FreeBSD 5.3 on KDE 3.3.0. My ASUS P4P800SE motherboard has ADI AD (Analog Device) 1985 Sound MAX 6-channel CODEC sound card. I don't know if it is supported. In the list of supported sound drivers I found snd_ad_1816 driver, but it doesn't work with my card. System detects my sound card correctly when I use the kldload snd_drivers command: Analog Device AD1985 Ac 97 Codec. But there is no such driver like snd_ad1985, only snd_ad1816!!! 1. Every time when I use only this snd_ad1816 driver by typing kldload snd_ad1816 or adding snd_ad1816_load=YES in /boot/loader.conf file, I have the following message: Sound server informational message: Error while initializing the sound driver: device /dev/dsp can't be opened (No such file or directory) The sound server will continue, using the null output device. At the same time there is no record in /dev/sndstat file and no /dev/dsp file. 2. There is no such bad message when I load all!!! drivers: kldload snd_drivers or add snd_driver_load=YES in /boot/loader.conf file. But still no sound! On the other hand several empty /dev/dsp files appears: dsp0.0;dsp0.1;dspr0.1;dspW0.0;dspW0.1. And the following record appears in /dev/sndstat: FreeBSD Audio Driver (newpcm) Installed devices: pcm0: Intel ICH5 (82801EB) at io 0xfebff800, 0xfebff400 irq 17 bufsz 16384 kld snd_ich (1p/1r/0v channels duplex default) I will be appreciate if someone can help me. Regards, Sasha ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)
Yep, Tried 5.3 mini, two different 5.3 Disc 1, 5.4RC2 Disc 1 Strangely enough, I disabled in the bios the CPU Cache and although the system is sluggish and slow, it has not freaked out yet.. -Original Message- From: Trevor Sullivan [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 13, 2005 9:13 AM To: [EMAIL PROTECTED] Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install) Edgar Martinez wrote: New error before death Panic: page fault -Original Message- From: Trevor Sullivan [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 13, 2005 9:00 AM To: [EMAIL PROTECTED] Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install) Edgar Martinez wrote: OK, removed all misc cards, devices, recabled...attempting to reinstall with 5.3, and I continue to get a kernel: priviledged instruction fault followed by a reboot...RAM is brand new Patriot 2-2-2-5...mem timings? -Original Message- From: Kris Kennaway [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 13, 2005 5:23 AM To: Edgar Martinez Cc: freebsd-questions@freebsd.org Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install) On Wed, Apr 13, 2005 at 01:10:42AM -0500, Edgar Martinez wrote: All, I cant begin to tell you how horrible of a time I have had trying to get this system installed and running. Sysinstall kept throwing up a privilege fault kernel error randomly (7sed...4m.7m..etc), and after I go fast enough to get lucky to an install complete..the system then spends its time periodically rebooting.this is the first venture into AMD64 turf as I historically stick with i386.so any pointers.gotchas.tweaks or tips.. please let me know..I really don't want to give up, so I want to see what can be done to stabilize this. Sounds like the usual bad hardware story..check RAM, power supply, CPU cooling, cabling, etc. kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Is this computer overclocked at all? I would highly recommend running it at the speeds it was meant to...you can avoid a lot of errors that way. -Trevor Is there perhaps a problem with the burned CD? Did you check the hash after downloading it, and verify the cd's contents after burning it? Sorry it's a stab in the dark, but maybe it'll give you a push in the direction of making it work =D -Trevor ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ssh dies
Robert Storey wrote: Dear All, An interesting and disturbing problem recently appeared on our server which is running FBSD 5.3. Rather suddenly, all users found themselves locked out because ssh stopped working. We had to send an email to tech support at our hosting service (Netsonic). They said this seems to be happening frequently on many FreeBSD servers (something to do with reaching the limit of ssh connections). They didn't tell us how to solve the problem, but they suggested rebooting, which should return the server under our control. We asked them to reboot and they did, problem solved for now. I'm wondering if anyone knows what is causing this, and if there is a permanent solution? The server was running fine for four months without issues - this just suddenly came out of the blue. TIA, Robert We had exactly the same problem with 5.3 on a dual opteron machine. One minute it worked and the next minute it stopped and had to be rebooted. The host insisted that this was clear evidence that machine had been compromised but this was nonsense. I have spoken to other people using 5.2 and 5.3 who report identical behavior. I don't know if it's a physical connection limit that's causing the problem though, because only two people log into my BSD server. I think a safer bet is this worm that tries to compromise servers by ssh. Perhaps the ssh server isn't cleaning up the failed connections well enough, or maybe it's detecting an attack and simply shutting down. This worm can generate a thousand or more connection attempts in a single session, so I can see how a tiny memory leak could grow into a big problem in a hurry. -- John Davis ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with inetd and ssh(d)
Rob schrieb: Stevan Tiefert wrote: Hello list, I have since days ervery ten minutes on my workstation xxx.domain.tld an entry in my /var/log/messages and on the console at the root-account these messages are appearing: Apr 13 10:30:53 xxx inetd[500]: ssh/tcp: bind: Address already in use Is sshd running as an independent daemon and also enabled in the /etc/inetd.conf file? That will cause a clash on port 22. If you have sshd_enable=YES in /etc/rc.conf, then disable it in /etc/inetd.conf; and vice versa. (you should prefer the first option). Rob. __ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/ Hello Rob, You are a hero!!! Thanks! That was the solution! And it worked! My workstation is silent, that is how it should work! Silent and without errors!!! With regards :-) Stevan Tiefert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with inetd and ssh(d)
Alex Zbyslaw schrieb: Stevan Tiefert wrote: Apr 13 10:30:53 xxx inetd[500]: ssh/tcp: bind: Address already in use I know that inetd was writing this in this file and that ssh(d) has a problem. bind (named) is not running on my workstation. Someone already made a suggestion, but you should know that bind in this message is nothing to do with DNS Bind software. The bind is a system call involved in setting up a socket. See man 2 bind. --Alex Hello Alex, ah, now I understand bind in the error message! Thanks :-) With regards Stevan Tiefert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)
I appreciate your help! There is NO stupid question or answer...as far as I am concerned ANY help is always WELCOME help...THANKS So, yeah being from the i386 world, I am also aware of the timing quirks in the intel world. The CPU is a 754 pin...specs below..hope this sheds some light on the situation...if anyone wants me to throw up some debug info let me know!! AMD Athlon 64 3000+, 1MB L2 Cache, 64-bit Processor for DTR Notebooks - OEM Model# AMA3000BEX5AP Item # N82E16819103444 Specifications: Model: AMD Athlon 64 3000+ Core: ClawHammer Operating Frequency: 1.8 GHz FSB: Integrated into Chip Cache: L1/64K+64K; L2/1MB Voltage: 1.5V Process: 0.13Micron Socket: Socket 754 Multimedia Instruction: MMX, SSE, SSE2, 3DNOW!, 3DNOW!+ Packaging: OEM(Processor Only) PATRIOT Extreme Performance 184-Pin 512MB DDR PC-3200 w/ XBL Technology, Model PEP5123200+XBL - Retail Model# PEP5123200+XBL Item # N82E16820220036 Specifications: Manufacturer: PDP Systems Speed: DDR400(PC3200) Type: 184-Pin DDR SDRAM Error Checking: Non-ECC Registered/Unbuffered: Unbuffered Cas Latency: 2-2-2-5 T1 Support Voltage: 2.8V Bandwidth: 3.2GB/s Organization: 64M x 64 -Bit Warranty: Lifetime -Original Message- From: Alex Zbyslaw [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 13, 2005 9:40 AM To: [EMAIL PROTECTED] Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install) Edgar Martinez wrote: OK, removed all misc cards, devices, recabled...attempting to reinstall with 5.3, and I continue to get a kernel: priviledged instruction fault followed by a reboot...RAM is brand new Patriot 2-2-2-5...mem timings? I don't know this brand of RAM, and I may be completely wrong but... When looking at 939 pin AMD CPUs, and what memory to get, I noticed that for one major quality RAM maker, the timings they recommended for Intel CPUs were faster than those they recommended for AMD CPUs and your figures look eerily familiar. It was something like 2-2-2-5 for Intel and 2-2.5-2-5 for AMD. I'm no expert on RAM, but your error does sound very hardware related. Can you check the RAM manufacturer's web site to see if they say anything? Also, some motherboards can be very picky about RAM. Is it worth trying with just one RAM chip? Does the machine POST ok with full memory tests on? (It doesn't prove anything, but if a chip is really duff it should find it). A little heretical, I realise, but is there the possibility of trying another OS (Windows, Linux) just to see if you have the same kinds of problems? I'm not copying to the list because I'm no real expert on this kind of thing; just stuff picked up from background reading. If you try any of this and it works can you post back to the list what finally worked? Best, --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What sound drive should I use?
Oleksandr Semenko wrote: I have problems with sound on FreeBSD 5.3 on KDE 3.3.0. My ASUS P4P800SE motherboard has ADI AD (Analog Device) 1985 Sound MAX 6-channel CODEC sound card. I don't know if it is supported. In the list of supported sound drivers I found snd_ad_1816 driver, but it doesn't work with my card. System detects my sound card correctly when I use the kldload snd_drivers command: Analog Device AD1985 Ac 97 Codec. But there is no such driver like snd_ad1985, only snd_ad1816!!! 1. Every time when I use only this snd_ad1816 driver by typing kldload snd_ad1816 or adding snd_ad1816_load=YES in /boot/loader.conf file, I have the following message: Sound server informational message: Error while initializing the sound driver: device /dev/dsp can't be opened (No such file or directory) The sound server will continue, using the null output device. At the same time there is no record in /dev/sndstat file and no /dev/dsp file. 2. There is no such bad message when I load all!!! drivers: kldload snd_drivers or add snd_driver_load=YES in /boot/loader.conf file. But still no sound! On the other hand several empty /dev/dsp files appears: dsp0.0;dsp0.1;dspr0.1;dspW0.0;dspW0.1. And the following record appears in /dev/sndstat: FreeBSD Audio Driver (newpcm) Installed devices: pcm0: Intel ICH5 (82801EB) at io 0xfebff800, 0xfebff400 irq 17 bufsz 16384 kld snd_ich (1p/1r/0v channels duplex default) I will be appreciate if someone can help me. Regards, Sasha Try this as root: `kldload snd_ich.ko`; I'm guessing that the snd_ich driver would be what you need, as FBSD seem to think that's what it is. The relevant line in /boot/loader.conf would be, then: snd_ich_load=YES HTH, Kevin Kinsey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What sound drive should I use?
On Wed, Apr 13, 2005 at 06:00:49PM +0400, Oleksandr Semenko wrote: I have problems with sound on FreeBSD 5.3 on KDE 3.3.0. My ASUS P4P800SE motherboard has ADI AD (Analog Device) 1985 Sound MAX 6-channel CODEC sound card. I don't know if it is supported. In the list of supported sound drivers I found snd_ad_1816 driver, but it doesn't work with my card. System detects my sound card correctly when I use the kldload snd_drivers command: Analog Device AD1985 Ac 97 Codec. But there is no such driver like snd_ad1985, only snd_ad1816!!! snip 2. There is no such bad message when I load all!!! drivers: kldload snd_drivers or add snd_driver_load=YES in /boot/loader.conf file. But still no sound! On the other hand several empty /dev/dsp files appears: dsp0.0;dsp0.1;dspr0.1;dspW0.0;dspW0.1. Device files are special files that do not really have a size. If you're doing ls -l you're seeing device numbers, not file sizes. And the following record appears in /dev/sndstat: FreeBSD Audio Driver (newpcm) Installed devices: pcm0: Intel ICH5 (82801EB) at io 0xfebff800, 0xfebff400 irq 17 bufsz 16384 kld snd_ich (1p/1r/0v channels duplex default) Looks like the system picks manages to load a driver (snd_ich). If you get no sound in kde, I suspect that the permissions on the sound devices are not correct, or that kde is looking for the wrong device. If you use xmms, and point it to /dev/dsp0.0, do you get sound? Roland -- R.F. Smith /\ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ /No HTML/RTF in e-mail http://www.xs4all.nl/~rsmith/ X No Word docs in e-mail public key: http://www.keyserver.net / \Respect for open standards pgpCMBtBnON4b.pgp Description: PGP signature
Fw: DOH! Adaptec AIC-8110X SATA RAID Controller
I meant to indicate I could not find any info on the Adaptec AIC-8110X controller. the MB is a ASUS PSCH-SR-SATA NoGo with FreeBSD 5.3 Sorry, Kurt White ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
SSL Certificate question.
All, I'm usually just a lurker on this list but I ran into a small problem. I recently found out that the SSL certificate I created for my sendmail server has expired. I need to update it. I was following along with the suggestions at http://veldt.com/2003/08/smtp-auth-ssl-with-sendmail-freebsd/ but I ran into a problem, I was hoping I could just generate a new certificate with the following commands: next, youll need to generate certificates for sendmail to use. mkdir /etc/mail/certs cd /etc/mail/certs mktemp /tmp/openssl.X1 mktemp /tmp/openssl.X2 PEM1='/tmp/openssl.X1' PEM2='/tmp/openssl.X2' openssl req -newkey rsa:1024 -keyout $PEM1 \ -nodes -x509 -days 365 -out $PEM2 cat $PEM1 sendmail.pem echo sendmail.pem cat $PEM2 sendmail.pem cp $PEM2 ca-bundle.crt rm $PEM1 $PEM2 chmod 400 sendmail.pem chmod 400 ca-bundle.crt I ran into some problems around PEM1='/tmp'openssl.X1' for some reason FreeBSD is now seeing this as a command, and is responding PEM1=/tmp/openssl.X1: Command not found. I am certain that these are the commands I ran the first time (04/12/2004) to create the certificates, why aren't they working now? Thanks for your help... tco2# uname -a FreeBSD tco2.iaminsane.net 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE #0: Fri Apr 23 07:02:47 EDT 2004 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/REM_0.0.3 i386 ~REM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ELF type 3 not known
I got this error on one of two 4.11 boxes. The other box seems to have upgraded without incident. I use gnome_upgrade.sh --- Installing the new version via the port with make flags: BATCH=yes GNOME_UPGRADE_SH_VER=2.10-3 DISABLE_VULNERABILITIES=1 === Installing for linux-gtk2-2.2.1_3 === linux-gtk2-2.2.1_3 depends on file: /compat/linux/usr/X11R6/lib/libX11.so.6 - found === linux-gtk2-2.2.1_3 depends on file: /compat/linux/usr/lib/libglib-2.0.so.0 - found === linux-gtk2-2.2.1_3 depends on file: /compat/linux/usr/lib/libatk-1.0.so.0 - found === linux-gtk2-2.2.1_3 depends on file: /compat/linux/usr/lib/libjpeg.so.62 - found === linux-gtk2-2.2.1_3 depends on file: /compat/linux/usr/lib/libpng12.so.0.1.2.7 - found === linux-gtk2-2.2.1_3 depends on file: /compat/linux/usr/lib/libtiff.so.3.6.1 - found === linux-gtk2-2.2.1_3 depends on file: /compat/linux/usr/lib/libpango-1.0.so.0.200.1 - found === linux-gtk2-2.2.1_3 depends on executable: rpm - found === Generating temporary packing list === Checking if x11-toolkits/linux-gtk2 already installed gtk2-2.2.1-4.i386.rpm ELF binary type 3 not known. Abort trap *** Error code 134 Steven Friedrich 5112 Mount Holyoke Drive Louisville, KY 40216 502-447-7730 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SSL Certificate question.
Okay, so I'm a bit slow on the uptake but I figured out that the PEM1 and PEM2 commands are supposed to be preceeded by set in my shell. I have now generated the new certificate, but how do I get sendmail to recognize it? I have even built sendmail from the src on my local machine. for some reason it's still utilizing the old openssl certificate that I generated over a year ago (even though the actual file was removed before I ran the commands below. Your help is appreciated. ~REM Richard Mcintyre wrote: All, I'm usually just a lurker on this list but I ran into a small problem. I recently found out that the SSL certificate I created for my sendmail server has expired. I need to update it. I was following along with the suggestions at http://veldt.com/2003/08/smtp-auth-ssl-with-sendmail-freebsd/ but I ran into a problem, I was hoping I could just generate a new certificate with the following commands: next, youll need to generate certificates for sendmail to use. mkdir /etc/mail/certs cd /etc/mail/certs mktemp /tmp/openssl.X1 mktemp /tmp/openssl.X2 PEM1='/tmp/openssl.X1' PEM2='/tmp/openssl.X2' openssl req -newkey rsa:1024 -keyout $PEM1 \ -nodes -x509 -days 365 -out $PEM2 cat $PEM1 sendmail.pem echo sendmail.pem cat $PEM2 sendmail.pem cp $PEM2 ca-bundle.crt rm $PEM1 $PEM2 chmod 400 sendmail.pem chmod 400 ca-bundle.crt I ran into some problems around PEM1='/tmp'openssl.X1' for some reason FreeBSD is now seeing this as a command, and is responding PEM1=/tmp/openssl.X1: Command not found. I am certain that these are the commands I ran the first time (04/12/2004) to create the certificates, why aren't they working now? Thanks for your help... tco2# uname -a FreeBSD tco2.iaminsane.net 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE #0: Fri Apr 23 07:02:47 EDT 2004 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/REM_0.0.3 i386 ~REM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ELF type 3 not known
On Wed, 13 Apr 2005, Steven Friedrich wrote: I got this error on one of two 4.11 boxes. The other box seems to have upgraded without incident. I use gnome_upgrade.sh --- Installing the new version via the port with make flags: BATCH=yes GNOME_UPGRADE_SH_VER=2.10-3 DISABLE_VULNERABILITIES=1 === Installing for linux-gtk2-2.2.1_3 === linux-gtk2-2.2.1_3 depends on file: /compat/linux/usr/X11R6/lib/libX11.so.6 - found === linux-gtk2-2.2.1_3 depends on file: /compat/linux/usr/lib/libglib-2.0.so.0 - found === linux-gtk2-2.2.1_3 depends on file: /compat/linux/usr/lib/libatk-1.0.so.0 - found === linux-gtk2-2.2.1_3 depends on file: /compat/linux/usr/lib/libjpeg.so.62 - found === linux-gtk2-2.2.1_3 depends on file: /compat/linux/usr/lib/libpng12.so.0.1.2.7 - found === linux-gtk2-2.2.1_3 depends on file: /compat/linux/usr/lib/libtiff.so.3.6.1 - found === linux-gtk2-2.2.1_3 depends on file: /compat/linux/usr/lib/libpango-1.0.so.0.200.1 - found === linux-gtk2-2.2.1_3 depends on executable: rpm - found === Generating temporary packing list === Checking if x11-toolkits/linux-gtk2 already installed gtk2-2.2.1-4.i386.rpm ELF binary type 3 not known. Abort trap *** Error code 134 Steven Friedrich 5112 Mount Holyoke Drive Louisville, KY 40216 502-447-7730 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Do you have linprocfs mounted? e.g. %df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s2a12670256738 5982849%/ devfs 11 0 100%/dev /dev/ad0s2f253678 658 232726 0%/tmp /dev/ad0s2g 16881250 10172764 535798666%/usr /dev/ad0s2e253678 140832 9255260%/var linprocfs 44 0 100%/usr/compat/linux/proc /dev/cd04877648776 0 100%/cdrom and an entry in /etc/fstab? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
isc-dhcp3-server port
I'm having a problem when making this port: === Building for isc-dhcp3-server-3.0.2_7 Making all in common cc -O -pipe -D_PATH_DHCPD_CONF=\/usr/local/etc/dhcpd.conf\ -D_PATH_DHCPD_DB=\/var/db/dhcpd.leases\ -D_PATH_DHCPD_PID=\/var/run/dhcpd.pid\ -D_PATH_DHCRELAY_PID=\/var/run/dhcrelay.pid\ -D_PATH_DHCLIENT_CONF=\/usr/local/etc/dhclient.conf\ -D_PATH_DHCLIENT_SCRIPT=\/usr/local/sbin/dhclient-script\ -D_PATH_DHCLIENT_DB=\/var/db/dhclient.leases\ -D_PATH_DHCLIENT_PID=\/var/run/dhclient.pid\ -Dwarn=dhcp_warn -DNOMINUM -DPARANOIA -DJAIL -I/usr/local/include -DUSE_SSL -I/usr/include -I/usr/ports/net/isc-dhcp3-server/work/dhcp-3.0.2 -I/usr/ports/net/isc-dhcp3-server/work/dhcp-3.0.2/includes -O -Wall -Wno-unused -Werror -c icmp.c In file included from icmp.c:42: /usr/include/netinet/ip.h:156: syntax error before `n_long' /usr/include/netinet/ip.h:159: syntax error before `n_long' In file included from icmp.c:43: /usr/include/netinet/ip_icmp.h:64: syntax error before `n_short' /usr/include/netinet/ip_icmp.h:71: syntax error before `n_short' /usr/include/netinet/ip_icmp.h:93: syntax error before `n_time' icmp.c: In function `icmp_echorequest': icmp.c:169: structure has no member named `icd_seq' icmp.c:174: structure has no member named `icd_id' cc1: warnings being treated as errors icmp.c: In function `icmp_echoreply': icmp.c:247: warning: implicit declaration of function `IP_HL' *** Error code 1 Stop in /usr/ports/net/isc-dhcp3-server/work/dhcp-3.0.2/work.freebsd/common. *** Error code 1 Stop in /usr/ports/net/isc-dhcp3-server/work/dhcp-3.0.2/work.freebsd. *** Error code 1 Stop in /usr/ports/net/isc-dhcp3-server/work/dhcp-3.0.2. *** Error code 1 Stop in /usr/ports/net/isc-dhcp3-server. Does anyone know how to fix this syntax error? Thankx, Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
installation messup
I have a problem to fix in an installation I just did, and I need to know if it's possible to misuse/abuse sysinstall in the manner I need to. I was putting a copy of FreeBSD into a system of a friend. hhis system is based on scsi, and I couldn't seem to get it to boot from ide, so instead of using the ide drive he'd given me, I installed FreeBSD into a drive I gave him. Smallish, but 9 Gigs is more than enough for a nice FreeBSD system, and besides, it woud compare better against the scsi based Windows install that he's going to be comparing it to. So, I did the install, and booted it twice, just to make sure. I had installed KDE, and I was amazed to see that the install worked like a miracle, all the way to the last KDE detail. Unfortunately, when he came 2 days later to pick up the machine, now at the disk manager f1 prompt, it's giving me a symbol that is like F(down-arrow), and I didn't even realize that the system could produce that down-arrow character. Well, so I figure that the best idea is to reinstall the disk manager. If I go into the experts install, can I get it to install just the disk manager only? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vinum setup
Lowell Gilbert wrote: Chuck Robey [EMAIL PROTECTED] writes: Sorry, I'm having a miserable time trying to get vinum working on my amd64 system. Vinum tells me that it can't load the kernel (vinum: Kernel module not available: No such file or directory). Gvinum simply refuses to take any commands at all. I tried looking at /boot/kernel, naturally didn't find any such module, so I wanted to see about building one, but I can't get device vinum to pass config's purview. Does vinum work on amd64's? Shouldn't that be gvinum? when I wrote that, I didn't understand the difference between vinum and gvinum. I do now, but I tell you, gvinum sure as heck needs documentation. Fixing the resetconfig command would be a really good thing, too. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: isc-dhcp3-server port
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 13 Apr 2005, Tom Frontera wrote: I'm having a problem when making this port: === Building for isc-dhcp3-server-3.0.2_7 Making all in common cc -O -pipe -D_PATH_DHCPD_CONF=\/usr/local/etc/dhcpd.conf\ -D_PATH_DHCPD_DB=\/var/db/dhcpd.leases\ -D_PATH_DHCPD_PID=\/var/run/dhcpd.pid\ -D_PATH_DHCRELAY_PID=\/var/run/dhcrelay.pid\ -D_PATH_DHCLIENT_CONF=\/usr/local/etc/dhclient.conf\ -D_PATH_DHCLIENT_SCRIPT=\/usr/local/sbin/dhclient-script\ -D_PATH_DHCLIENT_DB=\/var/db/dhclient.leases\ -D_PATH_DHCLIENT_PID=\/var/run/dhclient.pid\ -Dwarn=dhcp_warn -DNOMINUM -DPARANOIA -DJAIL -I/usr/local/include -DUSE_SSL -I/usr/include -I/usr/ports/net/isc-dhcp3-server/work/dhcp-3.0.2 -I/usr/ports/net/isc-dhcp3-server/work/dhcp-3.0.2/includes -O -Wall -Wno-unused -Werror -c icmp.c In file included from icmp.c:42: /usr/include/netinet/ip.h:156: syntax error before `n_long' /usr/include/netinet/ip.h:159: syntax error before `n_long' In file included from icmp.c:43: /usr/include/netinet/ip_icmp.h:64: syntax error before `n_short' /usr/include/netinet/ip_icmp.h:71: syntax error before `n_short' /usr/include/netinet/ip_icmp.h:93: syntax error before `n_time' icmp.c: In function `icmp_echorequest': icmp.c:169: structure has no member named `icd_seq' icmp.c:174: structure has no member named `icd_id' cc1: warnings being treated as errors icmp.c: In function `icmp_echoreply': icmp.c:247: warning: implicit declaration of function `IP_HL' *** Error code 1 Stop in /usr/ports/net/isc-dhcp3-server/work/dhcp-3.0.2/work.freebsd/common. *** Error code 1 Stop in /usr/ports/net/isc-dhcp3-server/work/dhcp-3.0.2/work.freebsd. *** Error code 1 Stop in /usr/ports/net/isc-dhcp3-server/work/dhcp-3.0.2. *** Error code 1 Stop in /usr/ports/net/isc-dhcp3-server. Does anyone know how to fix this syntax error? Hi, i haven't seen this while i upgraded the port to 3.0.2 on my systems. could you please provide some additional information e.g. which FreeBSD version ... thanks Joerg - -- The beginning is the most important part of the work. -Plato -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCXWuzSPOsGF+KA+MRAn15AJ99I17O+2TQn3BZQfnE+FEFqdptEACfSxDG GDiNaqWiaGOUQDDxIQH9Fes= =vE7G -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: isc-dhcp3-server port - [ScanMail certified]
FreeBSD 4.11-RELEASE and I updated the ports, but that didn't help. -Tom Joerg Pulz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 13 Apr 2005, Tom Frontera wrote: I'm having a problem when making this port: === Building for isc-dhcp3-server-3.0.2_7 Making all in common cc -O -pipe -D_PATH_DHCPD_CONF=\/usr/local/etc/dhcpd.conf\ -D_PATH_DHCPD_DB=\/var/db/dhcpd.leases\ -D_PATH_DHCPD_PID=\/var/run/dhcpd.pid\ -D_PATH_DHCRELAY_PID=\/var/run/dhcrelay.pid\ -D_PATH_DHCLIENT_CONF=\/usr/local/etc/dhclient.conf\ -D_PATH_DHCLIENT_SCRIPT=\/usr/local/sbin/dhclient-script\ -D_PATH_DHCLIENT_DB=\/var/db/dhclient.leases\ -D_PATH_DHCLIENT_PID=\/var/run/dhclient.pid\ -Dwarn=dhcp_warn -DNOMINUM -DPARANOIA -DJAIL -I/usr/local/include -DUSE_SSL -I/usr/include -I/usr/ports/net/isc-dhcp3-server/work/dhcp-3.0.2 -I/usr/ports/net/isc-dhcp3-server/work/dhcp-3.0.2/includes -O -Wall -Wno-unused -Werror -c icmp.c In file included from icmp.c:42: /usr/include/netinet/ip.h:156: syntax error before `n_long' /usr/include/netinet/ip.h:159: syntax error before `n_long' In file included from icmp.c:43: /usr/include/netinet/ip_icmp.h:64: syntax error before `n_short' /usr/include/netinet/ip_icmp.h:71: syntax error before `n_short' /usr/include/netinet/ip_icmp.h:93: syntax error before `n_time' icmp.c: In function `icmp_echorequest': icmp.c:169: structure has no member named `icd_seq' icmp.c:174: structure has no member named `icd_id' cc1: warnings being treated as errors icmp.c: In function `icmp_echoreply': icmp.c:247: warning: implicit declaration of function `IP_HL' *** Error code 1 Stop in /usr/ports/net/isc-dhcp3-server/work/dhcp-3.0.2/work.freebsd/common. *** Error code 1 Stop in /usr/ports/net/isc-dhcp3-server/work/dhcp-3.0.2/work.freebsd. *** Error code 1 Stop in /usr/ports/net/isc-dhcp3-server/work/dhcp-3.0.2. *** Error code 1 Stop in /usr/ports/net/isc-dhcp3-server. Does anyone know how to fix this syntax error? Hi, i haven't seen this while i upgraded the port to 3.0.2 on my systems. could you please provide some additional information e.g. which FreeBSD version ... thanks Joerg - -- The beginning is the most important part of the work. -Plato -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCXWuzSPOsGF+KA+MRAn15AJ99I17O+2TQn3BZQfnE+FEFqdptEACfSxDG GDiNaqWiaGOUQDDxIQH9Fes= =vE7G -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)
--- Edgar Martinez [EMAIL PROTECTED] wrote: All, I cant begin to tell you how horrible of a time I have had trying to get this system installed and running. Sysinstall kept throwing up a privilege fault kernel error randomly (7sed...4m.7m..etc), and after I go fast enough to get lucky to an install complete..the system then spends its time periodically rebooting.this is the first venture into AMD64 turf as I historically stick with i386.so any pointers.gotchas.tweaks or tips.. please let me know..I really don't want to give up, so I want to see what can be done to stabilize this. Unless someone else can vouch for that MB, it can be a suspect as well. While AMD is good, not all MB's for them are. Also ACPI can cause weird stuff like that too. Perhaps try turning that off or try other settings in the BIOS. I had that problem once. It actually did then when ACPI was turned off in the bios. Best of luck. NMH MSI K8T Neo AMD64 3000 w/1MB Thanks! ## SNIP ## The Large Print Giveth And The Small Print Taketh Away -- Anon __ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)
Yep first thing I assumed...ACPI was disabled...both in BIOS and via MENU...no joy...UDMA disabled...in fact.. PATA DISABLED (after install via CD) USB DISABLED FDD DIABLED APM DIABLED SMART DISABLED LAN DISABLED SOUND DISABLED FIREWIRE DISABLED =) If you cant tell, I have literally installed over a hundred FBSD boxes and have encountered TONS of caveats...however this one has def got me stumped..after the install, the system seems to be holding stable with the BIOS INTERNAL/EXTERNAL cache disabled...its SLLLOOOWWW but stable... -Original Message- From: NMH [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 13, 2005 2:19 PM To: [EMAIL PROTECTED]; questions Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install) --- Edgar Martinez [EMAIL PROTECTED] wrote: All, I cant begin to tell you how horrible of a time I have had trying to get this system installed and running. Sysinstall kept throwing up a privilege fault kernel error randomly (7sed...4m.7m..etc), and after I go fast enough to get lucky to an install complete..the system then spends its time periodically rebooting.this is the first venture into AMD64 turf as I historically stick with i386.so any pointers.gotchas.tweaks or tips.. please let me know..I really don't want to give up, so I want to see what can be done to stabilize this. Unless someone else can vouch for that MB, it can be a suspect as well. While AMD is good, not all MB's for them are. Also ACPI can cause weird stuff like that too. Perhaps try turning that off or try other settings in the BIOS. I had that problem once. It actually did then when ACPI was turned off in the bios. Best of luck. NMH MSI K8T Neo AMD64 3000 w/1MB Thanks! ## SNIP ## The Large Print Giveth And The Small Print Taketh Away -- Anon __ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: isc-dhcp3-server port - [ScanMail certified]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 13 Apr 2005, Tom Frontera wrote: FreeBSD 4.11-RELEASE and I updated the ports, but that didn't help. [snip] Hi, here is a quick fix and a short description. FIX: please run 'make config' again and DESELECT the DHCP_LDAP_SSL OPTION. Description: the isc-dhcp3-server port comes with it's own version of the ip.h and ip_icmp.h files. these can be found, once the ports source is extracted, in work/dhcp-3.0.2/includes/netinet/. the use of the DHCP_LDAP_SSL and OPENSSL_BASE OPTION add's an additional -I/usr/include to let the compiler find the right OpenSSL includes, which causes the problem on your system as your compiler is using the FreeBSD version of netinet/ip.h and netinet/ip_icmp.h located in /usr/inlcude instead of the port ones. there is no problem on my various 5.x system so i think it is a special thing with the gcc version in your 4.11 system. unfortunately i have no 4.x system running but i will try to find a suitable machine to check this for myself and to provide a better solution to fix this problem. please let me know if it builds now on your system. regards Joerg - -- The beginning is the most important part of the work. -Plato -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCXXVjSPOsGF+KA+MRAmRpAKCV0OX625nCkT0q8WzxFwMOj+AL3gCfbCfJ nMuMk27nTXA87IJf1x9l7NM= =J8rL -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Which mail server is the best for me?
One of these days I want to release a small tutorial on how to do this. That would be great! --Nick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: isc-dhcp3-server port - [ScanMail certified]
I worked fine. Thank You for your help. -Tom Joerg Pulz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 13 Apr 2005, Tom Frontera wrote: FreeBSD 4.11-RELEASE and I updated the ports, but that didn't help. [snip] Hi, here is a quick fix and a short description. FIX: please run 'make config' again and DESELECT the DHCP_LDAP_SSL OPTION. Description: the isc-dhcp3-server port comes with it's own version of the ip.h and ip_icmp.h files. these can be found, once the ports source is extracted, in work/dhcp-3.0.2/includes/netinet/. the use of the DHCP_LDAP_SSL and OPENSSL_BASE OPTION add's an additional -I/usr/include to let the compiler find the right OpenSSL includes, which causes the problem on your system as your compiler is using the FreeBSD version of netinet/ip.h and netinet/ip_icmp.h located in /usr/inlcude instead of the port ones. there is no problem on my various 5.x system so i think it is a special thing with the gcc version in your 4.11 system. unfortunately i have no 4.x system running but i will try to find a suitable machine to check this for myself and to provide a better solution to fix this problem. please let me know if it builds now on your system. regards Joerg - -- The beginning is the most important part of the work. -Plato -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCXXVjSPOsGF+KA+MRAmRpAKCV0OX625nCkT0q8WzxFwMOj+AL3gCfbCfJ nMuMk27nTXA87IJf1x9l7NM= =J8rL -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Supported six-channel sound cards
Greetings all, As a desktop FreeBSD user, I'd like to know if there is a list of supported 5.1 sound cards somewhere. The Holy Handbook mentions some supported cards, yes, but it doesn't say whether they are supported in 5.1 mode or only plain stereo. My current card, an onboard nForce (A7N8X-E Deluxe motherboard), is capable of 5.1, but the drivers currently don't offer this possibility (maybe in the near future?), and all I have is stereo. My FreeBSD is 5.3 with kernel and ports tree updated half an hour ago. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Supported six-channel sound cards
José de Paula Rodrigues wrote: Greetings all, As a desktop FreeBSD user, I'd like to know if there is a list of supported 5.1 sound cards somewhere. The Holy Handbook mentions some supported cards, yes, but it doesn't say whether they are supported in 5.1 mode or only plain stereo. My current card, an onboard nForce (A7N8X-E Deluxe motherboard), is capable of 5.1, but the drivers currently don't offer this possibility (maybe in the near future?), and all I have is stereo. I am trying to get my SoundBlaster Audify working with FreeBSD. Sound I have, at a minimum, but I want 6 channel digital sound like I had working with this card while I was experimenting with Linux. My speakers have both optical and digital inputs, and I have the digital ones wired to the output of the Audigy. I know I have that right, I had this same connection working before under Linux. I guess one of the things I need to test is a mp3 that has 6 channel source. Anyone have one of those? I have a mp3 I have been using for testing, but it's stereo only, and that won't do for 6 channel testing. I need to learn how to use a52dec. BTW, I am a pro when it comes to using my ears, I spent years as a communications technician. I can tell you beyond all doubt that 6 channel sound is quite, quite audibly a huge improvement over stereo, and worth our time to get working. My FreeBSD is 5.3 with kernel and ports tree updated half an hour ago. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: too many illegal connection attempts through ssh
Forgive the top posting (long message) ;) A quick way to make that crap go away is to run your ssh on a different port. quick, simple, effective. I used to have those brute force attacks every day and fill my logs and I would go in and create and entry that that entire Netmask in the ipfw and hosts.allow files but that got tedious real quick. Changing the port made my life easier. ssh -p 99 -l yournamehere 192.168.1.10 On Wed, 2005-04-06 at 07:15 +, Edwin D. Vinas wrote: hello, shown below is snapshot of too many illegal attempts to login to my server from a suspicious hacker. this is taken from the /var/log/auth.log. my question is, how do i automatically block an IP address if it is attempting to guess my login usernames? can i configure the firewall to check the instances a certain IP has attempted to access/ssh the sevrer, and if it has failed to login for about x number of attempts, it will be blocked automatically? thank you in advance! -edwin Mar 26 05:00:00 pawikan newsyslog[11879]: logfile turned over due to size100K Mar 26 22:49:29 pawikan sshd[66637]: Illegal user test from 211.176.33.46 Mar 26 22:49:32 pawikan sshd[66639]: Illegal user guest from 211.176.33.46 Mar 26 22:49:35 pawikan sshd[66641]: Illegal user admin from 211.176.33.46 Mar 26 22:49:37 pawikan sshd[66643]: Illegal user admin from 211.176.33.46 Mar 26 22:49:40 pawikan sshd[66645]: Illegal user user from 211.176.33.46 Mar 26 22:49:50 pawikan sshd[66654]: Illegal user test from 211.176.33.46 Mar 27 02:50:12 pawikan sshd[69369]: Illegal user test from 210.0.141.89 Mar 27 02:50:14 pawikan sshd[69463]: Illegal user guest from 210.0.141.89 Mar 27 02:50:15 pawikan sshd[69650]: Illegal user admin from 210.0.141.89 Mar 27 02:50:17 pawikan sshd[69745]: Illegal user admin from 210.0.141.89 Mar 27 02:50:18 pawikan sshd[69858]: Illegal user user from 210.0.141.89 Mar 27 02:50:24 pawikan sshd[70319]: Illegal user test from 210.0.141.89 Mar 27 04:10:58 pawikan sshd[5171]: Illegal user test from 218.188.9.202 Mar 27 04:10:59 pawikan sshd[5173]: Illegal user guest from 218.188.9.202 Mar 27 04:11:00 pawikan sshd[5175]: Illegal user admin from 218.188.9.202 Mar 27 04:11:01 pawikan sshd[5190]: Illegal user admin from 218.188.9.202 Mar 27 04:11:02 pawikan sshd[5192]: Illegal user user from 218.188.9.202 Mar 27 04:11:07 pawikan sshd[5200]: Illegal user test from 218.188.9.202 Mar 27 12:13:21 pawikan sshd[9236]: Did not receive identification string from 61.59.143.27 Mar 27 12:23:03 pawikan sshd[13482]: Illegal user jordan from 61.59.143.27 Mar 27 12:23:07 pawikan sshd[13484]: Illegal user michael from 61.59.143.27 Mar 27 12:23:11 pawikan sshd[13486]: Illegal user nicole from 61.59.143.27 Mar 27 12:23:14 pawikan sshd[13488]: Illegal user daniel from 61.59.143.27 Mar 27 12:23:18 pawikan sshd[13490]: Illegal user andrew from 61.59.143.27 Mar 27 12:23:21 pawikan sshd[13492]: Illegal user nathan from 61.59.143.27 Mar 27 12:23:25 pawikan sshd[13494]: Illegal user matthew from 61.59.143.27 Mar 27 12:23:29 pawikan sshd[13496]: Illegal user magic from 61.59.143.27 Mar 27 12:23:33 pawikan sshd[13498]: Illegal user lion from 61.59.143.27 Mar 27 12:23:37 pawikan sshd[13500]: Illegal user david from 61.59.143.27 Mar 27 12:23:41 pawikan sshd[13502]: Illegal user jason from 61.59.143.27 Mar 27 12:23:45 pawikan sshd[13504]: Illegal user ben from 61.59.143.27 Mar 27 12:23:49 pawikan sshd[13506]: Illegal user carmen from 61.59.143.27 Mar 27 12:23:53 pawikan sshd[13510]: Illegal user justin from 61.59.143.27 Mar 27 12:23:57 pawikan sshd[13512]: Illegal user charlie from 61.59.143.27 Mar 27 12:24:02 pawikan sshd[13514]: Illegal user steven from 61.59.143.27 Mar 27 12:24:06 pawikan sshd[13517]: Illegal user brandon from 61.59.143.27 Mar 27 12:24:09 pawikan sshd[13519]: Illegal user brian from 61.59.143.27 Mar 27 12:24:13 pawikan sshd[13521]: Illegal user stephen from 61.59.143.27 Mar 27 12:24:17 pawikan sshd[13523]: Illegal user william from 61.59.143.27 Mar 27 12:24:21 pawikan sshd[13525]: Illegal user angel from 61.59.143.27 Mar 27 12:24:27 pawikan sshd[13527]: Illegal user emily from 61.59.143.27 Mar 27 12:24:31 pawikan sshd[13529]: Illegal user eric from 61.59.143.27 Mar 27 12:24:36 pawikan sshd[13531]: Illegal user joe from 61.59.143.27 Mar 27 12:24:39 pawikan sshd[13533]: Illegal user tom from 61.59.143.27 Mar 27 12:24:43 pawikan sshd[13535]: Illegal user billy from 61.59.143.27 Mar 27 12:24:47 pawikan sshd[13537]: Illegal user buddy from 61.59.143.27 Mar 27 12:24:50 pawikan sshd[13540]: Illegal user jeremy from 61.59.143.27 Mar 27 12:24:54 pawikan sshd[13542]: Illegal user vampire from 61.59.143.27 Mar 27 12:24:57 pawikan sshd[13544]: Illegal user betty from 61.59.143.27 Mar 27 12:25:00 pawikan sshd[13546]: Illegal user henry from 61.59.143.27 Mar 27 12:25:04 pawikan sshd[13749]: Illegal user max from 61.59.143.27 Mar 27 12:25:07 pawikan sshd[14024]: Illegal user nicholas
Re: spam alert
On Wed, 13 Apr 2005 03:29:03 -0400 Robert [EMAIL PROTECTED] wrote: ||got a message from my ISP saying that my email address was sending out ||spam, possibly from a trojan on my pc that was allowing a remote program ||to access my SMTP server and send email without my knowledge. I was ||shocked since I'm running ZoneAlarm and don't remember getting any ||alerts about a program accessing my email. I ran Norton's and it didn't ||find anything. BUT it was blocking a heap of outgoing emails with ||sexually explicit content after I disabled ZoneAlarm. So ZoneAlarm ||must be blocking them when it is on, but periodically I turn it off ||because some web pages don't load correctly when I use ZoneAlarm. Well I ||disabled ZoneAlarm tonight and right away I got popups from Nortons ||alerting me that there were sexually explicit emails trying to be sent ||using my mail account, at a rate of about 20 per minute! I turned ||ZoneAlarm back on and immediately it told me that IP address ||204.152.184.73 was trying to send emails and make a connection with my ||mail server, which of course I blocked. 204.152.184.73 resolves to ||freebsd.isc.org. what gives ** Reply Separator ** Wednesday, April 13, 2005 4:39:26 PM I use Zone Alarm on all of my Windows based PC's. Assuming that you are not using the free; i.e., basically useless version, there is no reason to have to disable it for any reason. I would seriously suggest that you look into how you have it configured. Zone Alarm has an excellent forum where you can post questions. Their online support is not too bad, but it is not the quickest in the world when it comes to getting a speedy reply. As always, YMMV. -- Gerard Seibert [EMAIL PROTECTED] Isn't having a smoking section in a restaurant like having a peeing section in a swimming pool? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: How to interpret ipfw log?
On Tue, 2005-04-12 at 23:28 -0400, [EMAIL PROTECTED] wrote: Your ipfw rule 2500 is denying those outbound packets 192.168.0.200:65117 is your ip address: port number 65.87.165.45:5800 is the remote target ip address and port number and this is leaving your pc on NIC named tx0 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Sergei Gnezdov Sent: Tuesday, April 12, 2005 11:08 PM To: freebsd-questions@freebsd.org Subject: How to interpret ipfw log? The following firewall log seems to make very little sense to me. What could it possibly mean? Apr 11 04:27:05 name kernel: ipfw: 2500 Deny TCP 192.168.0.200:65117 65.87.165.45:5800 out via tx0 Apr 11 04:27:05 name kernel: ipfw: 2500 Deny TCP 192.168.0.200:49761 65.87.165.45:1003 out via tx0 Apr 11 04:27:05 name kernel: ipfw: 2500 Deny TCP 192.168.0.200:50116 65.87.165.45:1362 out via tx0 Apr 11 04:27:05 name kernel: ipfw: 2500 Deny TCP 192.168.0.200:50055 65.87.165.45:6101 out via tx0 Apr 11 04:27:05 name kernel: ipfw: 2500 Deny TCP 192.168.0.200:62352 65.87.165.45:888 out via tx0 Apr 11 04:27:05 name kernel: ipfw: 2500 Deny TCP 192.168.0.200:61272 65.87.165.45:969 out via tx0 Apr 11 04:27:05 name kernel: ipfw: 2500 Deny TCP 192.168.0.200:58267 65.87.165.45:471 out via tx0 Apr 11 04:27:05 name kernel: ipfw: 2500 Deny TCP 192.168.0.200:54164 65.87.165.45:1496 out via tx0 Apr 11 04:27:05 name kernel: ipfw: 2500 Deny TCP 192.168.0.200:61306 65.87.165.45:5716 out via tx0 Apr 11 04:27:05 name kernel: ipfw: 2500 Deny TCP 192.168.0.200:64970 65.87.165.45:281 out via tx0 Apr 11 04:27:05 name kernel: ipfw: 2500 Deny TCP 192.168.0.200:64115 65.87.165.45:106 out via tx0 Apr 11 04:27:05 name kernel: ipfw: 2500 Deny TCP 192.168.0.200:62007 65.87.165.45:284 out via tx0 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] looks like nmap ;) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: spam alert
Robert wrote: got a message from my ISP saying that my email address was sending out spam, possibly from a trojan on my pc that was allowing a remote program to access my SMTP server and send email without my knowledge. I was shocked since I'm running ZoneAlarm and don't remember getting any alerts about a program accessing my email. I ran Norton's and it didn't find anything. BUT it was blocking a heap of outgoing emails with sexually explicit content after I disabled ZoneAlarm. So ZoneAlarm must be blocking them when it is on, but periodically I turn it off because some web pages don't load correctly when I use ZoneAlarm. Well I disabled ZoneAlarm tonight and right away I got popups from Nortons alerting me that there were sexually explicit emails trying to be sent using my mail account, at a rate of about 20 per minute! I turned ZoneAlarm back on and immediately it told me that IP address 204.152.184.73 was trying to send emails and make a connection with my mail server, which of course I blocked. 204.152.184.73 resolves to freebsd.isc.org. what gives? I would suggest that you take your Windows computer to the nearest a] repair center or b] deep body of water, place it inside, and hope for the best whilst being prepared to pay the piper. I have found neither Zone Alarm nor Norton software to be of any use whatsoever for protecting a Windows machine that is connected to any network, anywhere. Either vigilant management and constant user re-education, combined with almost any AV software besides Norton et al, or a *nixlike firewall with deny ip from any to winbox are the only solutions that seem to work with any degree of guaranteeable success. I would certainly agree with the poster who suggested you contact ISC directly --- possibly something is amiss there, but there is also no guarantee that the IP address being fed to ZoneAlarm is spoofed; this is not at all beyond the means of almost any spammer working today, although the issue of whether they'd go to the trouble may merit some debate. Notwithstanding that, this post is rather OT for this list. Kevin Kinsey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re[2]: too many illegal connection attempts through ssh
Hi Ed, Wednesday, April 13, 2005, 10:46:07 PM, you wrote these comments: Forgive the top posting (long message) ;) A quick way to make that crap go away is to run your ssh on a different port. quick, simple, effective. I used to have those brute force attacks every day and fill my logs and I would go in and create and entry that that entire Netmask in the ipfw and hosts.allow files but that got tedious real quick. Changing the port made my life easier. ssh -p 99 -l yournamehere 192.168.1.10 or, if Edwin uses pf, he can use my bruteforceblocker.pl, which is daemonized process that checks for these login attempts and ads given IPs to the pf's table. it's located at: http://danger.rulez.sk/projects/bruteforceblocker/ PS: it seems like Edwin will have to little bit adjust the regexp in my script, since my regexp checks for Failed password attempts, but to do so is trivial thing... On Wed, 2005-04-06 at 07:15 +, Edwin D. Vinas wrote: hello, shown below is snapshot of too many illegal attempts to login to my server from a suspicious hacker. this is taken from the /var/log/auth.log. my question is, how do i automatically block an IP address if it is attempting to guess my login usernames? can i configure the firewall to check the instances a certain IP has attempted to access/ssh the sevrer, and if it has failed to login for about x number of attempts, it will be blocked automatically? thank you in advance! -edwin Mar 26 05:00:00 pawikan newsyslog[11879]: logfile turned over due to size100K Mar 26 22:49:29 pawikan sshd[66637]: Illegal user test from 211.176.33.46 Mar 26 22:49:32 pawikan sshd[66639]: Illegal user guest from 211.176.33.46 Mar 26 22:49:35 pawikan sshd[66641]: Illegal user admin from 211.176.33.46 -- Best Regards, +--==/\/\==--+ (__) FreeBSD | DanGer [EMAIL PROTECTED] |\\\'',) The | [EMAIL PROTECTED] ICQ261701668 | \/ \ ^Power | http://danger.rulez.sk | .\._/_)To +--==\/\/==--+ Serve [ Oh, what is it now? Can't you leave me in Peace? - Basil Fawlty ] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: too many illegal connection attempts through ssh
On Wed, 2005-04-06 at 07:15 +, Edwin D. Vinas wrote: hello, shown below is snapshot of too many illegal attempts to login to my server from a suspicious hacker. this is taken from the /var/log/auth.log. my question is, how do i automatically block an IP address if it is attempting to guess my login usernames? can i configure the firewall to check the instances a certain IP has attempted to access/ssh the sevrer, and if it has failed to login for about x number of attempts, it will be blocked automatically? thank you in advance! -edwin Mar 26 05:00:00 pawikan newsyslog[11879]: logfile turned over ...etc. This is one of those things we all have to live with. I once had the idea to start an Open Source Project for making an administrators' tool that would work as follows. The tool would collect these records and send the information to a central server. I would be willing to donate and administer that server. The server would then track where these attacks are coming from. If it becomes apparent that the attacks are coming from a lone idiot doing one or two amateurish crack attempts, nothing further need be done. On the other hand, if it becomes apparent that the source is making repeated attacks on many machines, then a co-ordinate message would go out to all administrators using the tool. This could be automated. We could hope that many tens of thousands of BSD administrators would be using this tool (on many hundreds of thousands of BSD machines). All the machines administered by users of this tool would then launch a concerted Denial Of Service attack on the cracker address. Now, how about that? Of course, we could also try to do this nicely; for example, we could send automated notifications to the ISPs servicing the offending machines, or to ICANN, or to the police and other authorities in the countries where this kind of behavior is illegal, and so on. However, that would certainly be quite ineffective, and much less fun. Or we could combine these strategies. We could notify the ISPs that the attacks are coming from one of their clients, informing them that a Tsunami DOS shall follow if they do not put a stop to the attacks. Just an idea... Benjamin Rossen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re[2]: too many illegal connection attempts through ssh
On Wed, 2005-04-06 at 07:15 +, Edwin D. Vinas wrote: hello, shown below is snapshot of too many illegal attempts to login to my server from a suspicious hacker. this is taken from the /var/log/auth.log. my question is, how do i automatically block an IP address if it is attempting to guess my login usernames? can i configure the firewall to check the instances a certain IP has attempted to access/ssh the sevrer, and if it has failed to login for about x number of attempts, it will be blocked automatically? thank you in advance! -edwin Mar 26 05:00:00 pawikan newsyslog[11879]: logfile turned over ...etc. This is one of those things we all have to live with. I once had the idea to start an Open Source Project for making an administrators' tool that would work as follows. The tool would collect these records and send the information to a central server. I would be willing to donate and administer that server. The server would then track where these attacks are coming from. If it becomes apparent that the attacks are coming from a lone idiot doing one or two amateurish crack attempts, nothing further need be done. On the other hand, if it becomes apparent that the source is making repeated attacks on many machines, then a co-ordinate message would go out to all administrators using the tool. This could be automated. We could hope that many tens of thousands of BSD administrators would be using this tool (on many hundreds of thousands of BSD machines). All the machines administered by users of this tool would then launch a concerted Denial Of Service attack on the cracker address. Now, how about that? Of course, we could also try to do this nicely; for example, we could send automated notifications to the ISPs servicing the offending machines, or to ICANN, or to the police and other authorities in the countries where this kind of behavior is illegal, and so on. However, that would certainly be quite ineffective, and much less fun. Or we could combine these strategies. We could notify the ISPs that the attacks are coming from one of their clients, informing them that a Tsunami DOS shall follow if they do not put a stop to the attacks. Just an idea... Benjamin Rossen - Sounds fun but opens the door for every local user with ssh access to DOS the machine he is on. I am not that found of the idea. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: too many illegal connection attempts through ssh
On Wednesday 13 April 2005 23:55, Hexren wrote: Just an idea... Benjamin Rossen - Sounds fun but opens the door for every local user with ssh access to DOS the machine he is on. I am not that found of the idea. Not at all. Let us say that a trusted authority were to operate the central server. The central server would not authorize a coordinated defensive DOS unless there were to be evidence that the cracker had been attacking many machines - perhaps the criterion could be framed to trigger a defensive DOS only if it were established that the cracker had been attacking many disparate machines in different parts of the world. Who is tracking this kind of thing centrally? No one. When you find that someone is trying to get into one of your servers you have no idea of what else that individual may be doing. A central trusted authority would know. Benjamin Rossen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Self Defense thourg DoS... ? (was: too many illegal connection attempts through ssh)
On Wednesday 13 April 2005 23:55, Hexren wrote: Just an idea... Benjamin Rossen - Sounds fun but opens the door for every local user with ssh access to DOS the machine he is on. I am not that found of the idea. Not at all. Let us say that a trusted authority were to operate the central server. The central server would not authorize a coordinated defensive DOS unless there were to be evidence that the cracker had been attacking many machines - perhaps the criterion could be framed to trigger a defensive DOS only if it were established that the cracker had been attacking many disparate machines in different parts of the world. Who is tracking this kind of thing centrally? No one. When you find that someone is trying to get into one of your servers you have no idea of what else that individual may be doing. A central trusted authority would know. Benjamin Rossen - Central _trusted_ authority leaves a bitter taste in my mouth... but then I may be paranoid. Anyway if I am a local user on a machine and I have access to an ssh binary (that is what I meant with ssh access) and bash, I can churn out connections with the only limit beeing my bandwith and system limits on the number of processes I can run at one time. But even with these set to sensible defaults say 10 processes and 1/10 of site bw. I am able to attack many disparate machines in different parts of the world therefore I am able to trigger a _defensive_ DoS against the machine in that I am. Regards Hexren ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Routing question?
All, I have a FreeBSD 5.3 box running postfix/amavisd-new/spamassassin/clamav. Currently, we have two entrances to our network, one is the Watchguard FBIII for our T1, the other is a PC running Win2k and Winproxy, serving our DSL line. The PC is starting to flake out, and I'd like to replace it with a Wachguard SOHO that we have laying around. The default gateway for the FreeBSD box is pointed at the WG FBIII, as that's the way most of our email comes through. What the PC with Winproxy does is accept inbound email connections to our secondary MX, and presents them to the FreeBSD box. I'm assuming that the Winproxy program was doing something funky to make all of this happen, but I'm really set on replacing it. This has been working for a year or two, but lately the Winproxy program on the PC is falling over several times a day. It's not a hardware error - all other programs on the machine work just fine, but Winproxy is dieing. When I hook up the SOHO, I can't get emails through the DSL line. Does anyone out there know what I can do to set up the FreeBSD box so that email coming through on the DSL line can be handled? One other detail that might affect the answers given - there are two IP addresses on the NIC in the FreeBSD box. One of those addresses handles the inbound emails (applying all of the savvy of amavis/spamassassin/clamav) and the other handles outbound mail, and no mail scanning happens to mail through that IP address. Thoughts? Sneers? Kurt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)
Edgar Martinez wrote: All, I cant begin to tell you how horrible of a time I have had trying to get this system installed and running. Sysinstall kept throwing up a privilege fault kernel error randomly (7sed...4m.7m..etc), and after I go fast enough to get lucky to an install complete..the system then spends its time periodically rebooting.this is the first venture into AMD64 turf as I historically stick with i386.so any pointers.gotchas.tweaks or tips.. please let me know..I really don't want to give up, so I want to see what can be done to stabilize this. MSI K8T Neo AMD64 3000 w/1MB I was just reading the archives this week at freebsd.org and it leads me to believe msi make crap boards. They can not handle tough loads or lots of ram. I think it was in the amd64 list under a heading that mentioned 8gig of ram. There were several developers that just trashed there msi boards and all the rest of there hardware worked fine in a new board. You should look it up. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Routing question?
Looks like I sent the first copy from an old address. Sorry if this dupes... All, I have a FreeBSD 5.3 box running postfix/amavisd-new/spamassassin/clamav. Currently, we have two entrances to our network, one is the Watchguard FBIII for our T1, the other is a PC running Win2k and Winproxy, serving our DSL line. The PC is starting to flake out, and I'd like to replace it with a Wachguard SOHO that we have laying around. The default gateway for the FreeBSD box is pointed at the WG FBIII, as that's the way most of our email comes through. What the PC with Winproxy does is accept inbound email connections to our secondary MX, and presents them to the FreeBSD box. I'm assuming that the Winproxy program was doing something funky to make all of this happen, but I'm really set on replacing it. This has been working for a year or two, but lately the Winproxy program on the PC is falling over several times a day. It's not a hardware error - all other programs on the machine work just fine, but Winproxy is dieing. When I hook up the SOHO, I can't get emails through the DSL line. Does anyone out there know what I can do to set up the FreeBSD box so that email coming through on the DSL line can be handled? One other detail that might affect the answers given - there are two IP addresses on the NIC in the FreeBSD box. One of those addresses handles the inbound emails (applying all of the savvy of amavis/spamassassin/clamav) and the other handles outbound mail, and no mail scanning happens to mail through that IP address. Thoughts? Sneers? Kurt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)
On Wed, Apr 13, 2005 at 08:20:23PM -0400, jason henson wrote: snip MSI K8T Neo AMD64 3000 w/1MB I was just reading the archives this week at freebsd.org and it leads me to believe msi make crap boards. They can not handle tough loads or lots of ram. I think it was in the amd64 list under a heading that mentioned 8gig of ram. There were several developers that just trashed there msi boards and all the rest of there hardware worked fine in a new board. You should look it up. There was/is an issue with 4GB RAM, but I don't recall it being only with MSI boards. And since 4GB is the limit for 32-bit addressing, I would rather suspect a 32/64-bitness issue. Personally I've used MSI motherboards in my last four desktops, running Linux or FreeBSD, and have never had issues with them. I'm using a MSI K8T NEO FSR (MS-6702) in my current amd64 box without problems. Roland -- R.F. Smith /\ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ /No HTML/RTF in e-mail http://www.xs4all.nl/~rsmith/ X No Word docs in e-mail public key: http://www.keyserver.net / \Respect for open standards pgpVZaj0wBIHI.pgp Description: PGP signature
Re: Can't remove empty directory
I suffered the same problem with 2 ports, I couldn't delete them, nor make clean. I decide to rename (mv) the port. I build the ports and when I rebooted the box, when it cames to the part of checking the filesystem; it automagically fix the corruption. And I deleted the renamed ports :) When I tried to delete the ports it says something like: #foo.bar: bad file descriptor. On 4/12/05, Kris Kennaway [EMAIL PROTECTED] wrote: On Tue, Apr 12, 2005 at 05:42:14PM -0500, Guillermo Garcia-Rojas wrote: After moving the directory, the system will prompt for a corruption on the filesystem and a simple fsck, as you say, will fix the problem :) I don't know what you mean by prompt for a corruption. Kris -- --- Guillermo García Rojas Covarrubias Director General SoloBSD http://www.solobsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Affiliate/ Reseller
Dear Sir, Kindly advice me how to get affiliate/ reseller account to FreeBSD.org and OR its partners. my web site: http://bite-a-byte.com Regards, Mustaffa Ali -- Your Buddy ... http://bite-a-byte.com/mje ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Routing question?
In the last episode (Apr 13), Kurt Buff said: I have a FreeBSD 5.3 box running postfix/amavisd-new/spamassassin/clamav. Currently, we have two entrances to our network, one is the Watchguard FBIII for our T1, the other is a PC running Win2k and Winproxy, serving our DSL line. The PC is starting to flake out, and I'd like to replace it with a Wachguard SOHO that we have laying around. It might be easier to just hang your DSL line off your External or Optional network, so you can enable the FBIII's SMTP filtering on both your DSL and T1 lines. Hanging it off a SOHO in your Trusted network is a bit less secure (but no worse than your winproxy setup). The default gateway for the FreeBSD box is pointed at the WG FBIII, as that's the way most of our email comes through. What the PC with Winproxy does is accept inbound email connections to our secondary MX, and presents them to the FreeBSD box. I'm assuming that the Winproxy program was doing something funky to make all of this happen, but I'm really set on replacing it. This has been working for a year or two, but lately the Winproxy program on the PC is falling over several times a day. It's not a hardware error - all other programs on the machine work just fine, but Winproxy is dieing. When I hook up the SOHO, I can't get emails through the DSL line. What fails? Do you get connection refused? Maybe you just need to open port 25 incoming on the SOHO and redirect it to the FreeBSD box's IP (set up an alias IP in the SOHO's default 192.168.111/24 network if you can't get the SOHO to use your exisitng Trusted network as its trusted network). I have a Firebox 1000 and a SOHO at work but don't have the SOHO's password on me so I can't tell you exactly what to set where :) -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
about traffic/routes generator
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi folks, I'm searching a traffic and routes (ospf, bgp, ...) generator for my lab. Any advice will be appreciated Best Regards Andrea -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Darwin) iD8DBQFCXctuMakHrsrHP9wRAoRDAJ9FuTRa8+ZzPIbnOdXbGcxGKTsWVgCeIV4A d6WUm9/9m1FD8B4akDntuX0= =oNE8 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Meta-ports like KDE and Gnome, WindowMaker?
I know there is the meta-port, KDE. And you have Gnome and its major ports like Fifth-Toe etc. Are there things similar but for WindowMaker? -- Best regards, Chris If you've got them by the balls, their hearts and minds will follow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)
I think I have nailed it...somewhat... So I set it up so I could ssh to it from my office and try to mess with it...ran solid as a rock...I think got home tonight and checked my logs...nothing bad...so I THEN rebooted went into BIOS and enabled the cache...BAM...errors out every time...threw in ubuntu...craptastic...DISABLED the CACHE...everything smooth...sooo the question now is...MB or CPU?? The CPU is listed as DTR...OMFG WTF is DTR?? (acro-cursing intended..) Model: AMD Athlon 64 3000+ DTR Core: ClawHammer Operating Frequency: 1.8 GHz FSB: Integrated into Chip Cache: L1/64K+64K; L2/1MB Voltage: 1.5V Process: 0.13Micron Socket: Socket 754 Multimedia Instruction: MMX, SSE, SSE2, 3DNOW!, 3DNOW!+ Packaging: OEM(Processor Only) -Original Message- From: jason henson [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 13, 2005 7:20 PM To: [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install) Edgar Martinez wrote: All, I cant begin to tell you how horrible of a time I have had trying to get this system installed and running. Sysinstall kept throwing up a privilege fault kernel error randomly (7sed...4m.7m..etc), and after I go fast enough to get lucky to an install complete..the system then spends its time periodically rebooting.this is the first venture into AMD64 turf as I historically stick with i386.so any pointers.gotchas.tweaks or tips.. please let me know..I really don't want to give up, so I want to see what can be done to stabilize this. MSI K8T Neo AMD64 3000 w/1MB I was just reading the archives this week at freebsd.org and it leads me to believe msi make crap boards. They can not handle tough loads or lots of ram. I think it was in the amd64 list under a heading that mentioned 8gig of ram. There were several developers that just trashed there msi boards and all the rest of there hardware worked fine in a new board. You should look it up. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to interpret ipfw log?
On 2005-04-13, Ed Stover [EMAIL PROTECTED] wrote: On Tue, 2005-04-12 at 23:28 -0400, [EMAIL PROTECTED] wrote: Your ipfw rule 2500 is denying those outbound packets 192.168.0.200:65117 is your ip address: port number 65.87.165.45:5800 is the remote target ip address and port number and this is leaving your pc on NIC named tx0 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Sergei Gnezdov Sent: Tuesday, April 12, 2005 11:08 PM To: freebsd-questions@freebsd.org Subject: How to interpret ipfw log? The following firewall log seems to make very little sense to me. What could it possibly mean? Apr 11 04:27:05 name kernel: ipfw: 2500 Deny TCP 192.168.0.200:65117 65.87.165.45:5800 out via tx0 Apr 11 04:27:05 name kernel: ipfw: 2500 Deny TCP 192.168.0.200:49761 65.87.165.45:1003 out via tx0 Apr 11 04:27:05 name kernel: ipfw: 2500 Deny TCP 192.168.0.200:50116 65.87.165.45:1362 out via tx0 Apr 11 04:27:05 name kernel: ipfw: 2500 Deny TCP 192.168.0.200:50055 65.87.165.45:6101 out via tx0 Apr 11 04:27:05 name kernel: ipfw: 2500 Deny TCP 192.168.0.200:62352 65.87.165.45:888 out via tx0 Apr 11 04:27:05 name kernel: ipfw: 2500 Deny TCP 192.168.0.200:61272 65.87.165.45:969 out via tx0 Apr 11 04:27:05 name kernel: ipfw: 2500 Deny TCP 192.168.0.200:58267 65.87.165.45:471 out via tx0 Apr 11 04:27:05 name kernel: ipfw: 2500 Deny TCP 192.168.0.200:54164 65.87.165.45:1496 out via tx0 Apr 11 04:27:05 name kernel: ipfw: 2500 Deny TCP 192.168.0.200:61306 65.87.165.45:5716 out via tx0 Apr 11 04:27:05 name kernel: ipfw: 2500 Deny TCP 192.168.0.200:64970 65.87.165.45:281 out via tx0 Apr 11 04:27:05 name kernel: ipfw: 2500 Deny TCP 192.168.0.200:64115 65.87.165.45:106 out via tx0 Apr 11 04:27:05 name kernel: ipfw: 2500 Deny TCP 192.168.0.200:62007 65.87.165.45:284 out via tx0 looks like nmap ;) I don't remember running nmap. What are the chances that machine is compromised? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
cvs lock files
is there an elegant solution to this problem titan# cvs -d :pserver:[EMAIL PROTECTED]:/PubWare checkout python/PubWare.py cvs server: failed to create lock directory for `/PubWare/python' (/PubWare/python/#cvs.lock): Permission denied cvs server: failed to obtain dir lock in repository `/PubWare/python' cvs [server aborted]: read lock failed - giving up i did some googling and it turns ou the problem is in the cvsroot anonymous doesn't have access, chmoding everything stikes me as a bit problematic. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Exim-4.50FreeBSD-5.4-STABLE
Hi ALL! I have a some problem with Exim-4.50. I create Local/Makefile with some options(MySQL including) but it's not so important. After that I do next steps... and there is result of steps: worm# cd /var/tmp/exim-4.50 worm# make ../scripts/Configure-Makefile: ../scripts/os-type: Permission denied *** Error code 1 Stop in /var/tmp/exim-4.50. Can any know what is mean and how solve this problem? Senks! ___ http://www.bigmir.net - ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
syslogd will be removed from freebsd???
I found this info on www.syslog.org http://www.syslog.org -- http://www.syslog.org/Article28.phtml Saying that Linux and BSD variants are going to remove syslog in the next months. This is true for Freebsd? I normally read my syslog file, but if it's true, you are going change for something new? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: syslogd will be removed from freebsd???
perikillo on 2005-04-13 22:37:44 -0700: I found this info on www.syslog.org http://www.syslog.org -- http://www.syslog.org/Article28.phtml Posted by: mutex on Apr 01, 2005 - 10:44 AM pgpM30G0NQgeI.pgp Description: PGP signature
Re: syslogd will be removed from freebsd???
perikillo wrote: I found this info on www.syslog.org http://www.syslog.org -- http://www.syslog.org/Article28.phtml Saying that Linux and BSD variants are going to remove syslog in the next months. This is true for Freebsd? I normally read my syslog file, but if it's true, you are going change for something new? ___ look at the date on the article. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)
Edgar Martinez wrote: I think I have nailed it...somewhat... So I set it up so I could ssh to it from my office and try to mess with it...ran solid as a rock...I think got home tonight and checked my logs...nothing bad...so I THEN rebooted went into BIOS and enabled the cache...BAM...errors out every time...threw in ubuntu...craptastic...DISABLED the CACHE...everything smooth...sooo the question now is...MB or CPU?? The CPU is listed as DTR...OMFG WTF is DTR?? (acro-cursing intended..) Model: AMD Athlon 64 3000+ DTR Core: ClawHammer Operating Frequency: 1.8 GHz FSB: Integrated into Chip Cache: L1/64K+64K; L2/1MB Voltage: 1.5V Process: 0.13Micron Socket: Socket 754 Multimedia Instruction: MMX, SSE, SSE2, 3DNOW!, 3DNOW!+ Packaging: OEM(Processor Only) -Original Message- From: jason henson [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 13, 2005 7:20 PM To: [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install) Edgar Martinez DTR stands for desktop replacement notebook. You have a cpu for a powerful notebook, but I think it would still be a low powered desktop cpu. Maybe you could try a bios update, but I would you need to rma that cpu. Sounds like it has some bad cache on it? http://www.hothardware.com/viewarticle.cfm?articleid=642 http://www.voodoopc.com/boards/messages.aspx?topic=32296forum=2 http://www.theregister.co.uk/2003/07/29/amd_cuts_opteron_prices_by/ http://www.amd.com/us-en/Processors/ProductInformation/0,,30_118_10220_9486,00.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
