Re: Newbie Question - looking for suggestions of small ports to install on stand-alone system without internet connection
there's always the shells, bash for example -- - John F Hoover [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: Newbie Question - looking for suggestions of small ports to install on stand-alone system without internet connection
On 10/6/06, John Hoover <[EMAIL PROTECTED]> wrote: there's always the shells, bash for example asciiquarium is a good start. *A Must* -- Tyop? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tracking a stolen laptop?
Jonathan Nichols wrote: I am trying to track down a stolen laptop. My laptop did not have BSD downloaded, but is there any way yet by which I may be able to track my laptop with your help? I would like to get BSD if I get my computer back. Thanks for any help or advice you can offer. The short answer: no. Your laptop doesn't "phone home" unless you configure it to - if it had windows maybe call Microsoft, I've heard their computers contact M$ on a regular basis. If you before hand had installed some tool that calls home then it would be possible to track it by the ip and possibly routing information it uses when it calls. But that's too late now. Cheers, Erik -- Ph: +34.666334818 web: http://www.locolomo.org X.509 Certificate: http://www.locolomo.org/crt/8D03551FFCE04F0C.crt Key ID: 69:79:B8:2C:E3:8F:E7:BE:5D:C3:C3:B1:74:62:B8:3F:9F:1F:69:B9 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Newbie Question - looking for suggestions of small ports to install on stand-alone system without internet connection
On 10/6/06, ograbme <[EMAIL PROTECTED]> wrote: I would like a few recommendations for small "ports" to try to install on my stand-alone machine. The stand-alone machine does not have connection to the internet; however, I do have a set of four (4)CD from the FreeBSD Mall and two (2) of the CD's have 'ports' on them. I would like to select one, two or three ports to install on this machine ... to go through the steps and experience of the ports process using the cdroms, so ... in essence I'm looking for suggestions of ports of a small nature (if there is such a thing). I'm not sure how familiar you are with Unis operating systems or the various tools available for all of it's incarnations, so, I'm listing these with info as if you were completely new to it. If you are not, I do not mean any insult or offense, I just don't know your level of experience, so I'm going for something relatively low that would give you a wide range of "sights and sounds" in the desktop *nix world. If you aren't /that/ new, just look at my list, and pick and choose your favorites. Ideally, you would want to install ports that you could make use of more than ports that are small. Even the larges ports rarely cause me issues. For small starts: "bash" - already suggested, very good shell "nano" - light weight and useful text editor "pico" - like nano, but made before or after, can't remember which "vim" - again, already suggested, good text editor, though not to my taste. It is lightweight and fast, though not to the extent of pico/nano. "sudoku" - I prefer pencil and paper because you can make notes, but it's fun "naim" - a console IM program intermediate projects: "emacs" - another popular editor, the largest (in size, not popularity - don't know what is the most popular) of the bunch, but I know people who get a lot of work done only starting one program *ever*, this is that program. It uses a large amount of resources for just a text editor, but you can do a lot more with it, and on a modern machine, that large amount is still relatively neglegable. "xorg" - an X (graphics) server, which will be extremely useful if you want more than a console command prompt. "gaim" - a multi-im client. quite useful, it could actually be in "small" projects, but you need X installed before hand. "gnome" - this is between intermediate and larger projects, a good and popular desktop/session manager, again, not to my taste, for as much smaller as it is, it runs slower than KDE on my systems. Nonetheless, a lot of people like it, and you should give it a try. * - Just about anything in the games directory Big projects "KDE" - like gnome, but more friendly to the people who like gui configuration, less friendly to those who like text configuration. I find it faster, but that could be because I have a lot of memory on all my machines - it's definetly larger. Might be the whole space for speed tradeoff that you can sometimes do, I don't know. Regardless, be prepared for a challange, you may not (read: probably won't) be able to get the full KDE running due to some apps not compiling. Read the updating file, and you may have to try kde-lite. "openoffice.org-2.0" - a nice office suit, be prepared for a challange! Now, you may need a few java packages that won't be on the CDs for this - which you'll have to download elsewhere and put on either a CD or a flash drive. Have fun, -Jim Stapleton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Periodic 'Weekly' output errors
FreeBSD 6.1-RELEASE-p10 FreeBSD 6.1-RELEASE-p10 #0: i386 I am having a continuing problem with the 'Weekly' periodic run. The output is extremely log, and filled with error messages. The log output does not appear to change week to week. Everything seems to be running correctly; therefore I am not sure if something is broken or not. There are also several 'Permission denied' messages at the end of the log that I do not understand. Due to the size of the log, I posted it here: http://seibercom.net/logs/weekly.txt Perhaps someone could enlighten me on what is happening. Ciao! -- Gerard Seibert [EMAIL PROTECTED] You know you've been spending too much time on the computer when your friend misdates a check, and you suggest adding a "++" to fix it. pgpVzHKBq87Vt.pgp Description: PGP signature
Ntop + SNMP
Running FreeBSD 6.2-PRERELEASE and im wanting some info on how to get Ntop to use SNMP to monitor traffic as all traffic goes through my router/modem which has SNMP support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: freeBSD official font
jarek wrote: Luchezar P. Petkov napisał(a): jarek wrote: Luchezar P. Petkov napisał(a): jarek wrote: hi can you tell me what is name of "freeBSD" font? i would like to do some artworks to promote freebsd and i beadly need this font bye It was made by the author of the logo, you can find it here: http://www.freebsd.org/logo.html Look at the SVG/Illustrator files. --Luchezar P. Petkov yep, i saw that, but i need whole alphabet to make a slogan thanks for help Try to talk with the author, maybe he will give you the font in TTF or something. it would be greate but how can i contact with the autor? bye Acording to this message: http://lists.freebsd.org/pipermail/freebsd-www/2005-December/003474.html His e-mail address is: [EMAIL PROTECTED] -Luchezar ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange X problem
On Sat, 7 Oct 2006 [EMAIL PROTECTED] wrote: > Message: 26 > Date: Fri, 06 Oct 2006 19:36:32 -0500 > From: Paul Schmehl <[EMAIL PROTECTED]> > --On October 6, 2006 5:23:45 PM -0700 backyard > <[EMAIL PROTECTED]> wrote: > > > > "For FreeBSD, edit /etc/ttys and find the line like > > this: > > > > ttyv8 "/usr/X11R6/bin/xdm -nodaemon" xterm off > > secure > > > > and edit it to this: > > > > ttyv8 "/usr/local/bin/kdm" xterm on secure > > > Yeah, I got a chance to look at it this afternoon, and that's what the > problem was. I wasn't looking closely enough at that line. Maybe you were looking _too_ closely at: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x11-wm.html which I was browsing just before seeing your thread, that indeed says: To enable kdm, the ttyv8 entry in /etc/ttys has to be adapted. The line should look as follows: ttyv8 "/usr/local/bin/kdm -nodaemon" xterm on secure Cheers, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problems ssh'ing debug1: An invalid name was supplied (OSX client)
Garrett Cooper wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Noah wrote: Chuck Swiger wrote: On Oct 6, 2006, at 2:26 PM, Noah wrote: any clues why ssh is hanging before a prompt is provided from the server side. this prompt stalling behavior is only happening when I am coming from my OSX ssh client. Any clues on this? I have never see this betwe. Looks like your SSH keypair has been mangled: % cat ~/.ssh/id_rsa -BEGIN RSA PRIVATE KEY- [ ...should contain base-64 encoded data... ] -END RSA PRIVATE KEY- If you don't have a valid keypair there in id_rsa and id_rsa.pub, use ssh-keygen to make a new one. Hi, something still seems strange. I have ~/.ssh/id_rsa and ~/.ssh/id_rsa.pub files. I am able to log in just fine to other servers using the keygen information without stalling. it is just two recently built servers out of about 10 that are displaying the stalling issue. Here is from a server that works fine with no stall: OpenSSH_4.2p1, OpenSSL 0.9.7i 14 Oct 2005 debug1: Reading configuration data /Users/username/.ssh/config debug1: Applying options for hostname debug1: Reading configuration data /etc/ssh_config debug2: ssh_connect: needpriv 0 debug1: Connecting to host.domain.com [172.xx.yy.zz] port 22. debug1: Connection established. debug3: Not a RSA1 key file /Users/username/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-END' debug3: key_read: missing keytype debug1: identity file /Users/username/.ssh/id_rsa type 1 debug1: identity file /Users/username/.ssh/id_dsa type -1 debug1: Remote protocol version 1.99, remote software version OpenSSH_3.9p1 debug1: match: OpenSSH_3.9p1 pat OpenSSH_3.* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.2 debug2: fd 3 setting O_NONBLOCK debug1: Miscellaneous failure No credentials cache found debug1: Miscellaneous failure No credentials cache found debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,[EMAIL PROTECTED],aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,[EMAIL PROTECTED],aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,[EMAIL PROTECTED],hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,[EMAIL PROTECTED],hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: [EMAIL PROTECTED],zlib,none debug2: kex_parse_kexinit: [EMAIL PROTECTED],zlib,none debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-dss debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,[EMAIL PROTECTED],aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,[EMAIL PROTECTED],aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,[EMAIL PROTECTED],hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,[EMAIL PROTECTED],hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib debug2: kex_parse_kexinit: none,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_init: found hmac-md5 debug1: kex: server->client aes128-cbc hmac-md5 zlib debug2: mac_in
following RELENG_6_1
I have a bunch of servers running FreeBSD 6.1-RELEASE. They perform crucial tasks like Samba domain control, LDAP directory, mail, etc... Though I'm reluctant to touch them I feel that the recent Security Advisories (especially about ssh ans ssl) are a very good reason to follow RELENG_6_1. I'd be grateful if someone could answer the following questions. Is it possible that an upgrade might break software installed from the port? I'm planning to use a build machine as explained in "Tracking for Multiple Machines" http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/small-lan.html What are the alternatives? Is there an easiest yet safe way to go? I was interested by /usr/ports/security/freebsd-update but some of my kernels have "options QUOTA" so I guess it rules out freebsd-update. Quoting FreeBSD-SA-06:23.openssl NOTE: Any third-party applications, including those installed from the FreeBSD ports collection, which are statically linked to libcrypto(3) should be recompiled in order to use the corrected code. How can I find the applications which fall in this category? Best regards, Thierry. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ZendOptimizer on FreeBSD 6.1 - Apache core dumps
Hi, We're about to purchase a software system that is encoded using Zend Guard and therefore we need to install the ZendOptimizer on our FreeBSD 6.1 STABLE server. The ZendOptimizer package has been installed from ports (allthough manually downloaded) and the needed text lines have been added to php.ini: [Zend] zend_optimizer.optimization_level=15 zend_extension_manager.optimizer="/usr/local/lib/php/20050922/Optimizer" zend_extension_manager.optimizer_ts="/usr/local/lib/php/20050922/Optimizer_TS" zend_extension="/usr/local/lib/php/20050922/ZendExtensionManager.so" [ THIS IS THE LINE THAT CAUSES THE PROBLEMS ] zend_extension_ts="/usr/local/lib/php/20050922/ZendExtensionManager_TS.so" However, when starting Apache (1.3.37 and php 5.1.6) it core dumps and won't start. I have posted a message in the Zend forums days ago without a reply and now it's getting urgent and I was hoping someone in here could provide us with some help. Here's the output from gdb: Reading symbols from /usr/local/lib/php/20050922/ZendExtensionManager.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/ZendExtensionManager.so Reading symbols from /usr/local/lib/php/20050922/ctype.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/ctype.so Reading symbols from /usr/local/lib/php/20050922/dom.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/dom.so Reading symbols from /usr/local/lib/php/20050922/ftp.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/ftp.so Reading symbols from /usr/lib/libssl.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libssl.so.4 Reading symbols from /lib/libcrypto.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypto.so.4 Reading symbols from /usr/local/lib/php/20050922/iconv.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/iconv.so Reading symbols from /usr/local/lib/php/20050922/mysql.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/mysql.so Reading symbols from /usr/local/lib/mysql/libmysqlclient.so.14...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/mysql/libmysqlclient.so.14 Reading symbols from /usr/local/lib/php/20050922/pcre.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/pcre.so Reading symbols from /usr/local/lib/php/20050922/zlib.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/zlib.so Reading symbols from /usr/local/lib/php/20050922/pdo.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/pdo.so Reading symbols from /usr/local/lib/php/20050922/posix.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/posix.so Reading symbols from /usr/local/lib/php/20050922/session.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/session.so Reading symbols from /usr/local/lib/php/20050922/simplexml.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/simplexml.so Reading symbols from /usr/local/lib/php/20050922/sqlite.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/sqlite.so Reading symbols from /usr/local/lib/php/20050922/tokenizer.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/tokenizer.so Reading symbols from /usr/local/lib/php/20050922/xml.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/xml.so Reading symbols from /usr/local/lib/php/20050922/xmlreader.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/xmlreader.so Reading symbols from /usr/local/lib/php/20050922/xmlwriter.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/xmlwriter.so Reading symbols from /usr/local/lib/php/20050922/bz2.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/bz2.so Reading symbols from /usr/lib/libbz2.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libbz2.so.2 Reading symbols from /usr/local/lib/php/20050922/openssl.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/openssl.so Reading symbols from /usr/local/lib/php/20050922/mcrypt.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/php/20050922/mcrypt.so Reading symbols from /usr/local/lib/libmcrypt.so.8...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libmcrypt.so.8 Reading symbols from /usr/local/lib/libltdl.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libltdl.so.4 Reading symbols from /usr/local/lib/php/20050922/mbstring.so...(no debugging symbols found)...done. Loaded symbols for
FreeBSD 6.2 PRERELEASE boot problem
After upgrading the ports suddenly the server does not reboot. I get the menu 'Welcome to FreeBSD'; after pressing 1 (boot FreeBSD default) the system halts with '/boot/kernel/acpi.ko text=0x43670 data=0x23c0+0x10f0 syms=[0x4+0x7ba+0x4+0xa828] We tried acessing thru live cdrom whilst mounting the partition, but that does not work. Any suggestions how to get the system pass booting again? Jack ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ipfw and temporary port access
Daniel Bye wrote: On Sat, Sep 16, 2006 at 03:06:13PM -0700, Noah wrote: Hi there, I am trying to figure out how to open a port temporarily for a specific IP who is able to provide a proper username and password on the website of the box. After authentication is verified then the IP address is cached and temporarily allowed to access a specific port on the server. This temporary firewall changes would be handled by ipfw. Any clues if a system like this is a already coded and out there somewhere? Take a look at security/doorman or security/knock, both of which might fit the bill. Hi there, I have really specific needs and wondering if somebody has written a port knocker out there already that fits the criteria of what I am looking for. Portknocker capabilities: 1) User needs to telnet to specific port and/or log into a website. 2) Learns the IP address that the user is coming from in step 1. 3) Opens ssh port to specifically to the IP address grabbed in step 1 but also keeps ssh port open to statically defined IPs in /etc/rc.firewall . 4) As soon as the user disconnects from the ssh port the IP address in step 1 no longer can access the ssh port unless they log back in like the procedure in step 1. I reviewed two programs doorman and knock (found in FreeBSD /usr/ports/security) Doorman Review: I am unable to figure out how to configure the ability to capture the IP address of where the UDP packet was sent. Therefore this program does not completely match what I am looking for, or I do not understanding how to configure it. Knock Review: This is nice but still requires closing the port as a step when done. It would be nice to automatically close the ssh port when the user disconnects from the ssh port. Also I am not clear but I don't think there is a way to grab the source IP address, right? Anybody know of other programs I could check out? Cheers, Noah Dan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
POE networking, what's the range?
This isn't really a FreeBSD-specific question but does anyone know the range of Power Over Ethernet? I want something to go from my house to my garage apartment then hook a wireless access point in to the POE box. The garage and the house are on their own power circuit but where the lines split is in between the house and the garage. I'm thinking it'll be around 600ft plus all the wiring in the house and garage. I'm kinda hesitant to buy one and try it before I *think* it may work. Michael ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: POE networking, what's the range?
On Sat, 2006-10-07 at 13:40 -0400, Michael Johnson wrote: > This isn't really a FreeBSD-specific question but does > anyone know the range of Power Over Ethernet? I want > something to go from my house to my garage apartment > then hook a wireless access point in to the POE box. The > garage and the house are on their own power circuit but > where the lines split is in between the house and the garage. > I'm thinking it'll be around 600ft plus all the wiring in the house > and garage. I'm kinda hesitant to buy one and try it before > I *think* it may work. 600 ft will be too much. POE (802.3af) works over Cat 5 which limits you to 328 feet or 100 meters. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: POE networking, what's the range?
On Sat, Oct 07, 2006 at 01:40:37PM -0400, Michael Johnson wrote: > This isn't really a FreeBSD-specific question but does > anyone know the range of Power Over Ethernet? I want > something to go from my house to my garage apartment > then hook a wireless access point in to the POE box. The > garage and the house are on their own power circuit but > where the lines split is in between the house and the garage. > I'm thinking it'll be around 600ft plus all the wiring in the house > and garage. I'm kinda hesitant to buy one and try it before > I *think* it may work. For normal Ethernet cables (carrying data) the maximum length of a cable is 100 meters (328 ft.) I would not count on PoE working over longer distances than that. -- Erik Trulsson [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: POE networking, what's the range?
On 10/7/06, Joe Marcus Clarke <[EMAIL PROTECTED]> wrote: On Sat, 2006-10-07 at 13:40 -0400, Michael Johnson wrote: > This isn't really a FreeBSD-specific question but does > anyone know the range of Power Over Ethernet? I want > something to go from my house to my garage apartment > then hook a wireless access point in to the POE box. The > garage and the house are on their own power circuit but > where the lines split is in between the house and the garage. > I'm thinking it'll be around 600ft plus all the wiring in the house > and garage. I'm kinda hesitant to buy one and try it before > I *think* it may work. 600 ft will be too much. POE (802.3af) works over Cat 5 which limits you to 328 feet or 100 meters. What about a good wireless access point? I have 2 linksys wrt54g's in the house now and one has the 7db gain antennas (which really doesn't do much) on it. I'd want at least 700ft+ range and it be able to go through multi-walls, trees, etc. I know there's lots of access points out there that could do this, but which one? I've looked at outdoor antennas, wireless access point that also works as a wireless bridge (can't find many of these) also. There is too many different options to go with and I don't know which one to go with. Michael Joe -- PGP Key : http://www.marcuscom.com/pgp.asc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ipw(4) and iwi(4): Intel's Pro Wireless firmware licensingproblems
On 05/10/06, Matt Emmerton <[EMAIL PROTECTED]> wrote: > On 05/10/06, Chuck Swiger <[EMAIL PROTECTED]> wrote: > > On Oct 4, 2006, at 7:46 PM, Constantine A. Murenin wrote: > > > Why are none of the manual pages of FreeBSD say anything about why > > > Intel Wireless devices do not work by default? > > > > > > http://www.freebsd.org/cgi/man.cgi?query=ipw > > > http://www.freebsd.org/cgi/man.cgi?query=iwi > > > > The manpages you've linked to explicitly state: > > > > This driver requires firmware to be loaded before it will > > work. You need > > to obtain ipwcontrol(8) from the IPW web page listed below to > > accomplish > > loading the firmware before ifconfig(8) will work. > > > > Is there some part of this which is unclear to you, Constantine? > > Yes, Chuck, some part is indeed unclear to me, precisely the part that > explains why does one have to go into that much trouble to have a > working system. It's required by Intel's choice of licence for the firmware for that wireless NIC. Where did you find that in the man-pages? > Not permitting the firmware to be redistributed has nothing to do with > the FCC, however. > No, firmware redistribution is ENTIRELY up to Intel. I want the > firmware to be available under a BSD or ISC licence, just as with > Ralink. Intel's firmware is already available, but under a different > licence. Where does the FCC say that Intel must distribute firmware > under a non-OSS-friendly licence? It doesn't. However, most licences allow derivative works to be created outside of Intel's control. If one of these derivative work allows the device to be used in a manner that violates FCC rules and regulations, Intel remains liable because they a) the provider of the hardware device in question and b) the provider of the initial software (that spawned the derivative work) As I see it, no matter what Intel does, a) and b) will always be the case -- reverse-engineering efforts still have to use Intel's original software to produce any viable results. I.e. by extending your argument slightly further, Intel is screwed anyway. There is nothing stopping Intel from releasing the firmware, except for the legal fear that the FCC will hold them accountable for illegal acts performed with their device. Even if the original document does not allow one to distribute derivative works, anyone can still post complicated instructions on modifying Intel's binaries such that the device violates the law. I strongly doubt FCC would hold Intel accountable if any user follows those complicated instructions, as it's almost impossible for Intel to control those kind of things. Intel should not write their own law, they should just make sure that customers are unlikely to disrespect FCCs laws. FCC laws, on the other hand, never say that manufacturers have to keep completely secret anything about their wireless devices. Distributing the very same firmware that already available under another licence doesn't have anything to do with one's ability to respect or disrespect the FCC laws. Put it the other way around -- if Intel doesn't distribute the firmware on terms acceptable to the end user, then it basically _forces_ the user to come up with their own firmware, or use some alternative firmwares. And what if alternative firmwares violate FCC? Then who's fault is that? It is now clearly Intel's fault, because they've made it legally difficult for the user to use the original Intel firmware. I.e. Intel is better off distributing the firmware under a BSD or ISC licence, unless it wants problems with their devices with the FCC. Cheers, Constantine. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
http://www.freewebtown.com/bustar00t/Musliman%20Vs%20Christian.exe
Hey look at that funny video.You will have damn fun.hahahaha.Musliman Kicking christians ass. http://www.freewebtown.com/bustar00t/Musliman%20Vs%20Christian.exe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: POE networking, what's the range?
In the last episode (Oct 07), Michael Johnson said: > This isn't really a FreeBSD-specific question but does anyone know > the range of Power Over Ethernet? I want something to go from my > house to my garage apartment then hook a wireless access point in to > the POE box. The garage and the house are on their own power circuit > but where the lines split is in between the house and the garage. I'm > thinking it'll be around 600ft plus all the wiring in the house and > garage. I'm kinda hesitant to buy one and try it before I *think* it > may work. If your garage has power, why not just plug the access point into an outlet in the garage instead of pulling power all the way from the house? As for your 600ft limit, the cable length everyone says Ethernet has is 300 feet, but that's really to allow collision detection to work. All the documents I have found explicitly say "half-duplex segment length is 100m". They then go on to mention full-duplex links but never give a length for them :) With everything being switched nowadays, maybe the limit is really determined by signal loss. At least one person has reported success at 850 feet at 10mbit: http://groups.google.com/[EMAIL PROTECTED] http://www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/ethernet.htm -- 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]"
Re: ipw(4) and iwi(4): Intel's Pro Wireless firmware licensing problems
On 06/10/06, Chuck Swiger <[EMAIL PROTECTED]> wrote: On Oct 5, 2006, at 7:31 PM, Constantine A. Murenin wrote: > On 05/10/06, Chuck Swiger <[EMAIL PROTECTED]> wrote: >> On Oct 4, 2006, at 7:46 PM, Constantine A. Murenin wrote: >> > Why are none of the manual pages of FreeBSD say anything about why >> > Intel Wireless devices do not work by default? >> > >> > http://www.freebsd.org/cgi/man.cgi?query=ipw >> > http://www.freebsd.org/cgi/man.cgi?query=iwi >> >> The manpages you've linked to explicitly state: >> >> This driver requires firmware to be loaded before it will >> work. You need to obtain ipwcontrol(8) from the IPW web page >> listed below to accomplish loading the firmware before ifconfig(8) >> will work. >> >> Is there some part of this which is unclear to you, Constantine? > > Yes, Chuck, some part is indeed unclear to me, precisely the part that > explains why does one have to go into that much trouble to have a > working system. That was explained below. You might not like the reasons, or agree with them, but your claim that the FreeBSD manpages do not say anything about the need for firmware is obviously mistaken. How is the claim obviously mistaken if the man-page DO NOT say what's the reason that the firmware must be downloaded from a web-site? >> There's no need to be curious about the matter; the Intel Pro >> Wireless adaptors, like many other brands of wireless adaptors, use a >> software-controlled radio which is capable of broadcasting at higher >> power levels and/or at frequencies outside of those allocated for >> 802.11 connectivity for specific regulatory domains. The US FCC, >> along with other regulatory agencies in Europe such as ETSI and >> elsewhere, require that end-users not have completely open access to >> these radios to prevent problems from deliberate misuse such as >> interference with other frequency bands. > > Yes, regulatory bodies, of cause, table specific requirements that > must be satisfied by systems that utilise RF, i.e. the manufacturer > must make reasonable attempt to prevent users from using non-permitted > frequencies. > > Not permitting the firmware to be redistributed has nothing to do with > the FCC, however. That's right. Intel permits you to redistribute their firmware under the terms of their license. >> This isn't a matter of choice on Intel's part; if you want this >> situation to change, you're going to have to obtain changes in the >> radio-frequency laws and policies in the US and a number of other >> countries first. > > No, firmware redistribution is ENTIRELY up to Intel. I want the > firmware to be available under a BSD or ISC licence, just as with > Ralink. Intel's firmware is already available, but under a different > licence. Where does the FCC say that Intel must distribute firmware > under a non-OSS-friendly licence? The BSD license and all other OSS-friendly licenses permit the user to modify the software and redistribute that modified version as a derivative work. A modified version of the firmware has not received FCC certification-- see Title 47 of the Code of Federal Regulations, Chapter I, section 15 in general, and specificly: http://www.access.gpo.gov/nara/cfr/waisidx_05/47cfr15_05.html "Sec. 15.21 Information to user. The users manual or instruction manual for an intentional or unintentional radiator shall caution the user that changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment." Right, this means a notice on the device or supporting documentation. It does not require a legal term in the firmware's licence. "Sec. 15.202 Certified operating frequency range. Client devices that operate in a master/client network may be certified if they have the capability of operating outside permissible part 15 frequency bands, provided they operate on only permissible part 15 frequencies under the control of the master device with which they communicate. Master devices marketed within the United States must be limited to operation on permissible part 15 frequencies. Client devices that can also act as master devices must meet the requirements of a master device." Also see: http://www.fcc.gov/cgb/consumerfacts/unauthorizedradio.html "Section 301 of the Communications Act of 1934 prohibits the "use or operation of any apparatus for the transmission of energy or communications or signals by radio" without a license issued by the Federal Communications Commission (FCC). Thus, generally, in order to use or operate a radio station, the Communications Act requires that you first obtain a license by the FCC. However, there are certain limited exceptions. For example, the FCC has provided blanket authorization to operators of Citizens Band (CB) radios, radio control stations, domestic ship and aircraft radios and certain other types of devices. This blanket authorization means that operators of these radio facilities are not
Re: ssh(d) "Failed keyboard-interactive/pam for invalid user"
Robert Huff wrote: One of my machines running: FreeBSD 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Thu Aug 3 15:33:32 EDT 2006 has suddenly decided to deny all ssh connections, whether by key-exchange or password. When attempting the latter, this appears in auth.log: Oct 3 22:47:44 jerusalem sshd[46280]: error: PAM: authentication error for illegal user from bronze.lcs.mit.edu Oct 3 22:47:44 jerusalem sshd[46280]: Failed keyboard-interactive/pam for invalid user from 128.31.0.11 port 63059 ssh2 Thre's nothing relevant in /usr/src/UPDATING, and searching on Google points to Samba-related stuff. I am running Samba, but fail to understand how this can affect a non-Samba-related login. Anyone willing to whap me with the clue-iron? Are you using pam_ldap? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ACPI/Xorg bug
I am running 6.1-stable and KDE 3.5.2 on an IBM ThinkPad T42p. When doing a restore from an S3 sleep (suspend), the KDE background is not restored properly upon a resume. Some or all of the background is restored with black and white stripes. I can the restore the background by forcing KDE to redraw it. All other status is properly restored, wireless and/or ethernet connections, dhcp, ... I figured this to be an Xorg problem assigning it to my "who cares" stack. However, I just found that if I suspend the system from one of the text ttys, a resume brings back a black screen. I can restore the missing text by waving the mouse over non-restored areas. Regardless if that is done or not ctrl-alt-F9 restores the X windows environment. As this is absolutely repeatable, I must be missing a (not so) critical change to sysctl.conf, device.hints, devd.conf, loader.conf, or ... I have an ACPI bug. I rather suspect I am missing something, and hope that someone has seen/or corrected this. Thanks for any help, Doug _ Douglas Denault http://www.safeport.com [EMAIL PROTECTED] Voice: 301-469-8766 Fax: 301-469-0601 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ssh(d) "Failed keyboard-interactive/pam for invalid user"
Per olof Ljungmark writes: > > Oct 3 22:47:44 jerusalem sshd[46280]: error: PAM: authentication error > for illegal user from bronze.lcs.mit.edu > > Oct 3 22:47:44 jerusalem sshd[46280]: Failed keyboard-interactive/pam for > invalid user from 128.31.0.11 port 63059 ssh2 > > Are you using pam_ldap? I don't think so: I haven't deliberately configured any ldap bits. How do I tell for sure? Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: http://www.freewebtown.com/bustar00t/Musliman%20Vs%20Christian.exe
--On October 7, 2006 6:31:29 PM + George W bush <[EMAIL PROTECTED]> wrote: Hey look at that funny video.You will have damn fun.hahahaha.Musliman Kicking christians ass. http://www.freewebtown.com/bustar00t/Musliman%20Vs%20Christian.exe Seems rather counterproductive to seed a unix mailing list with Windows viruses. Paul Schmehl ([EMAIL PROTECTED]) Adjunct Information Security Officer The University of Texas at Dallas http://www.utdallas.edu/ir/security/
Re: vr0: watchdog timeout FreeBSD 6.1-p10 Crashing my backups
On 10/6/06, Kris Kennaway <[EMAIL PROTECTED]> wrote: On Fri, Oct 06, 2006 at 10:08:27AM -0700, perikillo wrote: > change the scheduler to the old SCHED_4BSD and maxuser from 10 to 32 > like chuck told me. These are probably what fixed it. I guess you've learned a Lesson: when you choose to use code marked as "experimental", a) don't be surprised when it goes wrong, and b) the first thing you should do to try and fix it is to stop using the experimental code :-) Kris Yes, this is the lastime that i will use *experimental code*. It looks everything back to normal. My local backups already finished withuout any problems, right now is bringing the remote servser backups and they are running good. Thanks people for all your help. Greetings!!! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Panic/Fatal trap 12 while installing 6.1-RELEASE
Trying to install 6.1 on a Gigabyte 8i955 Royale motherboard, with an Intel D840 and 2GB of RAM onboard. However, booting up from the 6.1 CD results in a locked up system and this on the screen: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor write, page not present instruction pointer = 0x20:0xc07b5e7d stack pointer = 0x28:0xc1020d44 frame pointer = 0x28:0xc1020d58 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def 32 1, gran 1 processor eflags = interrupt enabled, resume IOPL = 0 current process = 0 () trap number = 12 panic: page fault uptime: 1s Not sure where to go from here, as system locks up solid. Booting with ACPI disabled and Safe Mode result in: vm_page_insert: page already inserted and system lockup. Verbose logging, and I get the exact same Fatal trap 12 as above. -- Juha ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic/Fatal trap 12 while installing 6.1-RELEASE
Never mind, turned out to be dodgy RAM. -- Juha ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: POE networking, what's the range?
> > ... does anyone know the range of Power Over Ethernet? I want > > something to go from my house to my garage apartment then hook > > a wireless access point in to the POE box. The garage and the > > house are on their own power circuit but where the lines split > > is in between the house and the garage. I'm thinking it'll be > > around 600ft plus all the wiring in the house and garage. The garage and the house are over 1/10 of a mile apart? > If your garage has power, why not just plug the access point into > an outlet in the garage instead of pulling power all the way from > the house? There can be some significant safety issues in stringing copper between buildings, especially over significant distances and if the building grounds are not interbonded. I'd encourage the O.P. to first consult a local electrical inspector, or an electrician who is familiar with the local conditions and safety codes. Yes, I know this is not mains power, but hazards exist with signal wiring as well. One alternative would be to track down a couple of fiber adapters, and string (non-conductive) fiber instead of copper. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ntop + SNMP
On 10/7/06, Warren Liddell <[EMAIL PROTECTED]> wrote: Running FreeBSD 6.2-PRERELEASE and im wanting some info on how to get Ntop to use SNMP to monitor traffic as all traffic goes through my router/modem which has SNMP support. You don't. If you wish to use SNMP to monitor traffic voumes, etc., you'll need to use something like mrtg, cacti or nagios. ntop doesn't know or care about SNMP, any more than does, say, tcpdump or WireShark. Kurt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: POE networking, what's the range?
[EMAIL PROTECTED] wrote: >>> ... does anyone know the range of Power Over Ethernet? I want >>> something to go from my house to my garage apartment then hook >>> a wireless access point in to the POE box. The garage and the >>> house are on their own power circuit but where the lines split >>> is in between the house and the garage. I'm thinking it'll be >>> around 600ft plus all the wiring in the house and garage. >>> > > The garage and the house are over 1/10 of a mile apart? > > >> If your garage has power, why not just plug the access point into >> an outlet in the garage instead of pulling power all the way from >> the house? >> > > There can be some significant safety issues in stringing copper > between buildings, especially over significant distances and if > the building grounds are not interbonded. I'd encourage the O.P. > to first consult a local electrical inspector, or an electrician > who is familiar with the local conditions and safety codes. Yes, > I know this is not mains power, but hazards exist with signal > wiring as well. > > I don't know the numbers either, but you should let him know the basic facts of the Ethernet environment: it's not power limited, it's TIME limited. The signal power goes down at a relatively low rate over distance, but the time that the ethernet signal takes to transit, that's a key limiter. You see, Ethernet is a protocol that relies on a bunch of time-relationships, both to support stuff like direct error control, but of most importance, in supporting the detection of collision occurrence (Ethernet allows signal collisions by being VERY good at detecting and handling such items). The way you figure limitations on ethernet is, you get tables of how fast your signal propagates over the cable you've chosen, and see if your cable allows your signal to get that far in that much time. It's the time that's key. If (now that I've probably embarrassed some of the walking encyclopedias we have around here) you come up with the kind of cable you have, we could very easily look into a table and tell you how much your setup will allow you. If you don't get an answer by tomorrow, I think I could probably find it here somewhere, with enough of a lookup. Don't bother the fellows with power numbers, that will only confuse the issue, believe me, power has nothing to do with it. > One alternative would be to track down a couple of fiber > adapters, and string (non-conductive) fiber instead of copper. > ___ > 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]"
Network dies after a while with high torrent load
Hi This is the second time i've posted this to the list and explaining why will also explain some of the background for the problem. The last time i was having these problems was when i was downloading a certain thing each week using torrent, rtorrent running as a user. I stopped doing this for a while this summer but now i'm at it again and the problem is back. I think it's because this particular torrent has a lot of seeds and transfers a lot of data, very fast to me. I'm limited to 10Mbit/s here at home and ifstat -b reports over 1 constantly for a while before my network just dies and no data at all gets sent. At this point i can fix the problem by running dhclient on my network card again. During one transfer of around 300MB i had to run dhclient at least 15 times. I have a IBM ThinkPad R40 laptop with a Intel Pro 10/100 ethernet card using the fxp driver. Right now i'm running 6.1-RELEASE but i've been running FreeBSD on this laptop since i had 4.9-RELEASE. I can recreate the problem anytime i find a torrent that has enough seeds so that i can maintain the maximum speed for 10-15 seconds. The time it takes for my network to die is very random. Sometimes my net doesn't die at all if the torrent can't maintain over 1bit/s, it only has to drop once in ifstat for the network to handle it. I'm about to call my ISP and complain because i doubt this is a FreeBSD problem but i would like to have some confirmation from others on the list that it is possible to transfer 10 or more Mbit/s with much torrent traffic using the fxp driver in FreeBSD. Another reason i suspect something with my ISP is the fact that it dies at the speed i pay them for, it could be some error in the equipment they use to cap my bandwidth. I have no messages to show and i'm afraid i forgot to check ifconfig while the network was down but ifstat which is running constantly in a small window on my desktop reports 0.00 in and out while the network is down. -- Med vänliga hälsningar Stefan Midjich aka nocturnal [Swehack] http://swehack.se ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
/dev/uscanner0
I'm apparently missing something. Only the root user can use /dev/uscanner0. I can't seem to rectify the problem -- no matter what I do. I'm hoping one of you all will look over my work and show me my mistake. Here's what I have done. /etc/devfs.conf: own uscanner* root:wheel perm uscanner* 0666 /etc/devfs.rules: [localrules=10] add path 'uscanner*' mode 0666 /etc/rc.conf: ... devfs_system_ruleset="localrules" after reboot, I have: $ ls -l /dev/uscanner0 crw-rw-rw- 1 root wheel0, 39 Oct 9 10:16 /dev/uscanner0 $ uname -a FreeBSD turandot.opera 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Sat Oct 7 13:33:34 MST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 == Now I, Nebuchadnezzar, praise and extol and honor the King of heaven, for all his works are truth, and his ways are justice; and he is able to bring low those who walk in pride. Daniel 4:37 __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Network dies after a while with high torrent load
nocturnal writes: > I'm about to call my ISP and complain because i doubt this is a > FreeBSD problem The mention of dhclient suggests you too may be suffering from the problem described at: http://www.freebsd.org/cgi/query-pr.cgi?pr=86427&cat=kern If so, the problem is not (or at least not entirely) volume-of-traffic related. I recently had one system run for 21 days (including heavy p2p traffic) before choking; a day or two later it imploded after a couple of hours of very light load. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: POE networking, what's the range?
On 10/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > ... does anyone know the range of Power Over Ethernet? I want > > something to go from my house to my garage apartment then hook > > a wireless access point in to the POE box. The garage and the > > house are on their own power circuit but where the lines split > > is in between the house and the garage. I'm thinking it'll be > > around 600ft plus all the wiring in the house and garage. The garage and the house are over 1/10 of a mile apart? yeah. it's not a car garage. > If your garage has power, why not just plug the access point into > an outlet in the garage instead of pulling power all the way from > the house? There can be some significant safety issues in stringing copper between buildings, especially over significant distances and if the building grounds are not interbonded. I'd encourage the O.P. to first consult a local electrical inspector, or an electrician who is familiar with the local conditions and safety codes. Yes, I know this is not mains power, but hazards exist with signal wiring as well. I don't plan to string cable at all. Cable is already in place for all the electric stuff. One alternative would be to track down a couple of fiber adapters, and string (non-conductive) fiber instead of copper. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Sundry hardware issues on an Alderwood/Intel 925 Express board + 6.1-RELEASE
From dmesg on a freshly installed 6.1-RELEASE system: acpi0: on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR pci1: at device 0.0 (no driver attached) pci0: at device 27.0 (no driver attached) pci0: at device 31.3 (no driver attached) pciconf -lv: [EMAIL PROTECTED]:27:0:class=0x040300 card=0x266817f2 chip=0x26688086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82801FB/FR/FW/FRW Intel High DefiNition Audio Controller' class= multimedia [EMAIL PROTECTED]:31:3:class=0x0c0500 card=0x266a17f2 chip=0x266a8086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82801FB/FR/FW/FRW SMBus Controller' class= serial bus subclass = SMBus [EMAIL PROTECTED]:0:0: class=0x03 card=0x31251458 chip=0x014010de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'GeForce 6600 GT' class= display subclass = VGA Is it possible to get these going? Then there's this message: acpi_tz0: failed to set new freq, disabling passive cooling Is this: http://www.bsdforums.org/forums/archive/index.php/t-38587.html a valid workaround? This looks a bit more worrisome: atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfb00-0xfb0f at device 31.2 on pci0 atapci1: failed to enable memory mapping! Related to this? http://www.freebsd.org/cgi/query-pr.cgi?pr=92238 Anything I could do about it? -- Juha ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: POE networking, what's the range?
> > The garage and the house are over 1/10 of a mile apart? > > yeah. it's not a car garage. ... > I don't plan to string cable at all. Cable is already in place > for all the electric stuff. IOW the cat5 between the buildings is already in place? In that case, and supposing whoever put it in knew what s/he was doing, the safety issues should have been taken care of. There's still the matter of the 100m distance spec, but as others have mentioned that is not a hard and fast rule in practice. I have personally seen 10Base-2 (RG58 coax) work very well on a segment that was well over twice the 200m maximum length specified for that technology. If 10/100Base-T are equally robust, you might get by with a 200m run (esp. if you run only 10Mb over cat5, which is capable of handling 100Mb, and/or if nothing else in the same collision domain has anywhere near a maximum-length run). I would guess that POE might still have problems, separate from the Ethernet signal-distance limits, due to power loss in the wiring. The POE-powered device would likely have been designed to allow for the loss in 100m of the cat 5 pair that's being used to supply the power. You've got about twice that distance, thus about twice the voltage drop at any given current consumption. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Using portconf and /usr/local/etc/ports.conf
I am trying to migrate my /usr/local/etc/pkgtools.conf into /usr/local/etc/ports.conf. I'm not sure I have the ports.conf syntax correct, or that the entries I'm making are being recognized. I've installed the sysutils/portconf port successfully, and my make.conf is: monitor : /root# cat /etc/make.conf CPUTYPE?=p3 NO_PROFILE= true USA_RESIDENT=YES # 2005-12-19 to build sendmail without IPv6 NO_INET6=YES # added by use.perl 2006-01-05 14:23:56 PERL_VER=5.8.7 PERL_VERSION=5.8.7 # Begin portconf settings # Do not touch these lines .if !empty(.CURDIR:M/usr/ports*) && exists(/usr/local/libexec/portconf) _PORTCONF!=/usr/local/libexec/portconf .for i in ${_PORTCONF:S/|/ /g} ${i:S/%/ /g} .endfor .endif # End portconf settings I have this line in /usr/local/etc/ports.conf for ruby18: lang/ruby18: WITHOUT_RDOC=1 | WITHOUT_IPV6=1 portupgrade says that portupgrade and ruby are both out of date: monitor : /root# portupgrade -nR portupgrade 2>/dev/null ---> Session started at: Sat, 07 Oct 2006 20:34:32 -0700 ---> Upgrade of lang/ruby18 started at: Sat, 07 Oct 2006 20:34:35 -0700 ---> Upgrading 'ruby-1.8.4_9,1' to 'ruby-1.8.5_1,1' (lang/ruby18) OK? [no] ---> Upgrade of lang/ruby18 ended at: Sat, 07 Oct 2006 20:34:35 -0700 (consumed 00:00:00) ---> ** Upgrade tasks 3: 1 done, 0 ignored, 0 skipped and 0 failed ---> Skipping 'lang/perl5.8' because it is held by user (specify -f to force) ---> ** Upgrade tasks 3: 1 done, 1 ignored, 0 skipped and 0 failed ---> Upgrade of sysutils/portupgrade started at: Sat, 07 Oct 2006 20:34:35 -0700 ---> Upgrading 'portupgrade-2.1.3.3,2' to 'portupgrade-2.1.3.3_1,2' (sysutils/portupgrade) OK? [no] ---> Upgrade of sysutils/portupgrade ended at: Sat, 07 Oct 2006 20:34:35 -0700 (consumed 00:00:00) ---> ** Upgrade tasks 3: 2 done, 1 ignored, 0 skipped and 0 failed ---> Listing the results (+:done / -:ignored / *:skipped / !:failed) + lang/ruby18 (ruby-1.8.4_9,1) - lang/perl5.8 (perl-5.8.7_2) + sysutils/portupgrade (portupgrade-2.1.3.3,2) ---> Packages processed: 2 done, 1 ignored, 0 skipped and 0 failed ---> Session ended at: Sat, 07 Oct 2006 20:34:35 -0700 (consumed 00:00:03) But when I: monitor : /root# portupgrade -R portupgrade ---> Upgrading 'ruby-1.8.4_9,1' to 'ruby-1.8.5_1,1' (lang/ruby18) ---> Building '/usr/ports/lang/ruby18' ===> Cleaning for ruby-1.8.5_1,1 I then get the build options dialogue box for ruby 1.8.5_1,1 with the tick boxes for IPV6 and RDOC checked, even though I have ports.conf entries to turn them off. Is this my goof, or is something wrong with portconf? Thank you! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
new pango screwing up my x11
hi all i just wanted to install gaim. did update the ports and then went on to install gaim wich installed a new pango that toally f-ed up my x. now i can not use it anymore. sorg starts and then when it comes to fire up gnome xorg crashes with some thread errors. i think the issue is the new pango libraries installed because gnome-session was looking for the old ones - i linked the new ones to the old names but i get the thread error. it sucks when new software is not backward compatible. my system is 6 release and it was running nicely before the f-ing pang screwd the whole thing up. i'm not interested right now in upgrading all the gnome and all the applications on top of it so i was wondering if i remove the new pango and install the old from the 6 iso disks would that make my life easier instead of upgrading gnome? because if all this crap i have to use lynx to send this mail.. thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RE : Re: cheapskate webmail interface
On 10/6/06, Desmond Coughlan <[EMAIL PROTECTED]> wrote: you may want to try roundcube http://www.roundcube.net although it's still on beta the interface's rocks, nothing you ever experienced before, certainly cooler than squirrelmail with AJAX like interface. Interesting... OK, I've got roundcube installed, the tables are created, postgreSQL is running, apache is recompiled for PhP4 (which is installed also) ... oh, and I've installed IMAP4. Now what ? My question, I suppose, is .. what is the address used to access the web interface? you need to configure main.inc.php and db.inc.php, usually just your username will do but if you can't, try [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"