Re: Drgenius with gnome2
On Fri, 2003-01-10 at 12:02, P. U. Kruppa wrote: Hi again! In the meantime I played around a little bit with DrGenius. (As I teach maths and physics - ) I think it is quite a valuable tool for visualization and exploration of geometry and and vector geometry. It seems to be competitive to commercial systems like dynageo's Euklid and it is part of the gnome project. Thus it would be a good idea if someone - who knows about these things - could write a port for it, to make it easily accessible for students and teachers. The port has been added under the math category. I set the maintainer to ports@ since I did enough geometry to get a math minor then got the hell out :-). If someone that has a special fondness for this port wants to step up, I'll be happy to adjust the maintainer. Joe Thanks, Uli. On Thu, 9 Jan 2003, P. U. Kruppa wrote: DrGenius is an intuitive geometry system, that might be interesting for students (More information on http://www.ofset.org/drgenius/ml.html ). How does it fail? Before I can run # ./configure I have to # ln -s /usr/X11R6/bin/gtk12-config /usr/X11R6/bin/gtk-config because drgenius needs gtk12. Then I run # ./gmake which ends with FreeBSD doesn't have or need crypt.h. You can remove it from the source file. This should be something that's checked by configure. Indeed, I uncommented # include crypt.h and now it seems to install and run. *---* *Peter Ulrich Kruppa* * - Wuppertal - * * Germany * *---* -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Problems installing 5.0 RC2 on a Compaq Amarda M700 (acpi problems)
Hi, I'm having a problem installing 5.0 RC2 from cd onto my Compaq amarda M700 laptop. I get errors from acpi on boot that look like: ACPI-1287: *** Method execution failed. AE_AML_BUFFER_LIMIT And a complaint about tempurature. Then it tries to mount the memory file system and hangs. If I use unset acpi_load it boots up, (lots of unknown pci problems) but it boots and will install. After installation the system will not boot as it can't mount the root file system. I get : setrootbyname failed ffs_mountroot: can't find rootvp root mount failed: 6 If I again do a unset acpi_load, the system boots and I can log in. I've tried set hw.acpi.ec.event_driven=1 and that didn't make a different. I've captured acpidump and dmesg if you want to look at that. http://chaotic.oz.org/other/bsd-5.0/erwin-5.0RC2-acpidump.txt http://chaotic.oz.org/other/bsd-5.0/erwin-5.0RC2-dmesg.txt Any ideas? -- Simon Coggins (SAGE-AU Member)Email: [EMAIL PROTECTED] Network and System Management Officer Phone: +61-2-4221-3775 Information Technology Systems (ITS) Mobile: 0408 115861 University of Wollongong, 2522, Australia Fax: +61-2-4229-1985 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
newbie questions about pppoe and netgraph
attempting to run pppoe on freebsd 4.7 over cable/dsl connection. manual says kernel recompilation unnecessary for this release in order to run pppoe. however, netgraph does not seem to be loading at boot time. additionally, pppoe seems unable to get past lcp when connecting. how can i tell if netgraph is active after boot? if not, can netgraph modules be loaded at boot by adding necessary lines into loader.conf? or is recompiling kernel a preferred method? stephen To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
ext3 - fbsd
I want to change my debian linux server into a FreeBSD one. All's quite set up to do this fast and easy, except for one thing: in my linux machine I have a large LAN-shared drive, using the EXT3 filesystem. This drive must not be down too long, otherwise I get into lots of trouble w/ my homemates :-)) (wife, children..) I think FreeBSD does _not_ support the linux ext2 / ext3 What is the best way to change the filesystem on that drive? Use another one and copy the files, sure, but how, when fbsd doesn't understand ext2/ext3 ? -- dick -- http://www.nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.7 ++ Debian GNU/Linux (Woody) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: newbie questions about pppoe and netgraph
ok here is what i get www# /usr/sbin/ppp Working in interactive mode Using interface: tun0 tun0: Command: default: add default HISADDR tun0: Command: default: enable DNS tun0: Command: default: set ifaddr 10.0.0.1/0 10.0.0.0/2 255.255.255 0.0.0.0 tun0: Command: default: set authname ** tun0: Command: default: set authkey ** tun0: Command: default: set login tun0: Command: default: set dial tun0: Command: default: set timeout 0 tun0: Command: default: open tun0: Phase: bundle: Establish tun0: Phase: closed - opening tun0: Phase: PPP started (interactive) tun0: Phase: deflink: Connected! tun0: Phase: deflink: opening - dial tun0: Chat: deflink: Dial attempt 1 of 1 tun0: Phase: deflink: dial - carrier ppp ON www tun0: Phase: deflink: Disconnected! tun0: Phase: deflink: carrier - hangup tun0: Phase: deflink: Connect time: 5 secs: 0 octets in, 0 octets out tun0: Phase: total 0 bytes/sec, peak 0 bytes/sec on Sat Jan 11 tun0: Phase: deflink hangup - closed tun0: Phase: bundle: Dead i imagine that some of this is unnecessary, but it appears that i am not even getting to authentication before disconnecting. thank you stephen On Sat, 11 Jan 2003, Matthew Emmerton wrote: attempting to run pppoe on freebsd 4.7 over cable/dsl connection. manual says kernel recompilation unnecessary for this release in order to run pppoe. however, netgraph does not seem to be loading at boot time. additionally, pppoe seems unable to get past lcp when connecting. how can i tell if netgraph is active after boot? if not, can netgraph modules be loaded at boot by adding necessary lines into loader.conf? or is recompiling kernel a preferred method? If netgraph and pppoe support are not present in your kernel (or not loaded from modules automatically), the ppp program will complain loudly. Can you post part of your ppp log file so that we can determine if the lack of pppoe is your problem or if it's something else? -- Matt Emmerton To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Strange behavior with /dev/null
Strange behavior I'm getting since I last did a mergemaster and MAKEDEV in /dev: cannot create /dev/null: permission denied $ cat ConfigFvwmMenus /dev/null -bash: /dev/null: Permission denied $ ls -l /dev/null crw--- 1 root wheel2, 2 Jan 11 10:00 /dev/null $ file /dev/null /dev/null: character special (2/2) I am running 4.6.2-RELEASE #5. What did I miss here? I'm beginning to wonder if this may be causing some of my other problems with fvwm menu/keystroke xterm execution. TIA Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ You know you've landed gear-up when it takes full power to taxi. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: ext3 - fbsd
dick hoogendijk wrote: I want to change my debian linux server into a FreeBSD one. All's quite set up to do this fast and easy, except for one thing: in my linux machine I have a large LAN-shared drive, using the EXT3 filesystem. This drive must not be down too long, otherwise I get into lots of trouble w/ my homemates :-)) (wife, children..) I think FreeBSD does _not_ support the linux ext2 / ext3 What is the best way to change the filesystem on that drive? Use another one and copy the files, sure, but how, when fbsd doesn't understand ext2/ext3 ? FreeBSD _does_ understand ext2. See the mount_ext2fs command for details. Unfortunately, ext3 isn't supported yet AFAIK. So I guess you could reformat the filesystem as ext2 (do a dump/restore) and you'll be in business. Any reason why you can't copy the contents of this partition to another computer (via network) and then reformat it UFS while installing FreeBSD and copy everything back? -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Strange behavior with /dev/null
Louis LeBlanc wrote: Strange behavior I'm getting since I last did a mergemaster and MAKEDEV in /dev: cannot create /dev/null: permission denied $ cat ConfigFvwmMenus /dev/null -bash: /dev/null: Permission denied $ ls -l /dev/null crw--- 1 root wheel2, 2 Jan 11 10:00 /dev/null My /dev/null is crw-rw-rw-. Don't know how it happened, but it sure seems like a simple permission problem. chmod 666 /dev/null should fix it (I would think). $ file /dev/null /dev/null: character special (2/2) I am running 4.6.2-RELEASE #5. What did I miss here? I'm beginning to wonder if this may be causing some of my other problems with fvwm menu/keystroke xterm execution. Obviously, it will cause problems any time someone other than root tries to write to /dev/null -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Strange behavior with /dev/null
On Sat, 11 Jan 2003 10:27:23 -0500 Louis LeBlanc [EMAIL PROTECTED] wrote: Strange behavior I'm getting since I last did a mergemaster and MAKEDEV in /dev: cannot create /dev/null: permission denied $ cat ConfigFvwmMenus /dev/null -bash: /dev/null: Permission denied $ ls -l /dev/null crw--- 1 root wheel2, 2 Jan 11 10:00 /dev/null $ file /dev/null /dev/null: character special (2/2) I am running 4.6.2-RELEASE #5. What did I miss here? I'm beginning to wonder if this may be causing some of my other problems with fvwm menu/keystroke xterm execution. Louis, My 4.7-STABLE system shows: BSD1# ls -la /dev/null crw-rw-rw- 1 root wheel2, 2 Jan 11 09:31 /dev/null Regards, Stephen Hilton [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: newbie questions about pppoe and netgraph
attempting to run pppoe on freebsd 4.7 over cable/dsl connection. manual says kernel recompilation unnecessary for this release in order to run pppoe. however, netgraph does not seem to be loading at boot time. additionally, pppoe seems unable to get past lcp when connecting. how can i tell if netgraph is active after boot? if not, can netgraph modules be loaded at boot by adding necessary lines into loader.conf? or is recompiling kernel a preferred method? If netgraph and pppoe support are not present in your kernel (or not loaded from modules automatically), the ppp program will complain loudly. Can you post part of your ppp log file so that we can determine if the lack of pppoe is your problem or if it's something else? -- Matt Emmerton To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Problems w NIC
Help... My NIC is found during boot-up and everything appears to be correct setup, except the darn thing won't work. I can ping 192.168.0.1 (computers local ip - see below), but no other computers on my LAN. However, from other computers on my LAN, I can ping this computer and get a response. Clearly the NIC is working in some manner, but I have given up on ideas now The computer is a brand new machine, set up as dual-boot. NIC works perfectly in other OS. BIOS is set to non-plug and play OS Any ideas? dmesg: Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.7-RELEASE #0: Wed Oct 9 15:08:34 GMT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz CPU: AMD Athlon(tm) XP 2000+ (1666.74-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x662 Stepping = 2 .. dc0: Davicom DM9102A 10/100BaseTX port 0xec00-0xecff mem 0xdf00-0xdfff irq 10 at device 8.0 on pci0 dc0: Ethernet address: 00:08:a1:2c:28:fa miibus0: MII bus on dc0 .. ifconfig: dc0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.0.1 netmask 0xff00 broadcast 192.168.0.255 inet6 fe80::208:a1ff:fe2c:28fa%dc0 prefixlen 64 scopeid 0x1 ether 00:08:a1:2c:28:fa media: Ethernet autoselect (10baseT/UTP) status: active lp0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 faith0: flags=8002BROADCAST,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff00 ppp0: flags=8010POINTOPOINT,MULTICAST mtu 1500 sl0: flags=c010POINTOPOINT,LINK2,MULTICAST mtu 552 Any help much appreciated /Nikolaj To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Strange behavior with /dev/null
On 01/11/03 09:43 AM, Bill Moran sat at the `puter and typed: Louis LeBlanc wrote: Strange behavior I'm getting since I last did a mergemaster and MAKEDEV in /dev: cannot create /dev/null: permission denied $ cat ConfigFvwmMenus /dev/null -bash: /dev/null: Permission denied $ ls -l /dev/null crw--- 1 root wheel2, 2 Jan 11 10:00 /dev/null My /dev/null is crw-rw-rw-. Don't know how it happened, but it sure seems like a simple permission problem. chmod 666 /dev/null should fix it (I would think). That did the trick, and now my menus are working as expected. Thanks a bunch! Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ The function of the expert is not to be more right than other people, but to be wrong for more sophisticated reasons. -- Dr. David Butler, British psephologist To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Rebuild database - login.conf
At 12:46 AM 1.11.2003 -0800, you wrote: it's already been answered on the list, but i thought i might add: /usr/src/etc/login.conf: randall@isber[~]% cat /usr/src/etc/login.conf # login.conf - login class capabilities database. # # Remember to rebuild the database after each change to this file: # # cap_mkdb /etc/login.conf ;) -randall At 12:46 AM 1.11.2003 -0800, randall ehren wrote: it's already been answered on the list, but i thought i might add: /usr/src/etc/login.conf: randall@isber[~]% cat /usr/src/etc/login.conf # login.conf - login class capabilities database. # # Remember to rebuild the database after each change to this file: # # cap_mkdb /etc/login.conf Thanks for the reminder of where that darn file was. Lots of tweaking needed after that late-night upgrade -- FrontPage extensions broke and have to do triage! BTW, has anyone run into this FP error after updating (on another server, I had no problem) Note the Undefined symbol __stderrp Never saw that one before: [Sat Jan 11 00:00:30 2003] [notice] SIGHUP received. Attempting to restart [Sat Jan 11 00:00:31 2003] [notice] Apache/1.3.26 (Unix) FrontPage/5.0.2.2510 PHP/4.2.3 configured -- resuming normal operations [Sat Jan 11 00:00:31 2003] [notice] suEXEC mechanism enabled (wrapper: /usr/local/sbin/suexec) [Sat Jan 11 00:00:31 2003] [notice] Accept mutex: flock (Default: flock) /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol __stderrp [Sat Jan 11 09:00:29 2003] [error] [client 192.168.0.3] Premature end of script headers: /usr/local/frontpage/version5.0/apache-fp/_vti_bin/fpexe Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: newbie questions about pppoe and netgraph
What does your ppp.conf look like? For PPPoE, it you should have a line like this: [ dang email client ] set device PPPoE:ed1 where ed1 is the network card that is hooked up to your DSL modem. -- Matt www# /usr/sbin/ppp Working in interactive mode Using interface: tun0 tun0: Command: default: add default HISADDR tun0: Command: default: enable DNS tun0: Command: default: set ifaddr 10.0.0.1/0 10.0.0.0/2 255.255.255 0.0.0.0 tun0: Command: default: set authname ** tun0: Command: default: set authkey ** tun0: Command: default: set login tun0: Command: default: set dial tun0: Command: default: set timeout 0 tun0: Command: default: open tun0: Phase: bundle: Establish tun0: Phase: closed - opening tun0: Phase: PPP started (interactive) tun0: Phase: deflink: Connected! tun0: Phase: deflink: opening - dial tun0: Chat: deflink: Dial attempt 1 of 1 tun0: Phase: deflink: dial - carrier ppp ON www tun0: Phase: deflink: Disconnected! tun0: Phase: deflink: carrier - hangup tun0: Phase: deflink: Connect time: 5 secs: 0 octets in, 0 octets out tun0: Phase: total 0 bytes/sec, peak 0 bytes/sec on Sat Jan 11 tun0: Phase: deflink hangup - closed tun0: Phase: bundle: Dead i imagine that some of this is unnecessary, but it appears that i am not even getting to authentication before disconnecting. thank you stephen On Sat, 11 Jan 2003, Matthew Emmerton wrote: attempting to run pppoe on freebsd 4.7 over cable/dsl connection. manual says kernel recompilation unnecessary for this release in order to run pppoe. however, netgraph does not seem to be loading at boot time. additionally, pppoe seems unable to get past lcp when connecting. how can i tell if netgraph is active after boot? if not, can netgraph modules be loaded at boot by adding necessary lines into loader.conf? or is recompiling kernel a preferred method? If netgraph and pppoe support are not present in your kernel (or not loaded from modules automatically), the ppp program will complain loudly. Can you post part of your ppp log file so that we can determine if the lack of pppoe is your problem or if it's something else? -- Matt Emmerton To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
What does a netstat -finet -rn show? It sound like you don't have a default route set up. Matt Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default192.168.0.2UGSc10dc0 127.0.0.1 127.0.0.1 UH 00lo0 192.168.0 link#1 UC 10dc0 192.168.0.2link#1 UHLW20dc0 192.168.0.2 is my BSD-router. I have done 'route add default 192.168.0.2' and I have even tried flushing the tables, but w/o success. regards /Nikolaj To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: ext3 - fbsd
On 11 Jan Bill Moran wrote: FreeBSD _does_ understand ext2. See the mount_ext2fs command for details. Unfortunately, ext3 isn't supported yet AFAIK. So, if I switch this drive to another (fbsd) box I could copy form one (ext2) drive to another UFS drive preserving all persmission? Or would it be better to tar the drive onto the new one; reformat the old drive as UFS and untar back? Any reason why you can't copy the contents of this partition to another computer (via network) and then reformat it UFS while installing FreeBSD and copy everything back? Network too slow (for a transfer of approx 35G), plus _space_ :) -- dick -- http://www.nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.7 ++ Debian GNU/Linux (Woody) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
Hi, On Sat, 2003-01-11 at 16:02, Nikolaj Farrell wrote: What does a netstat -finet -rn show? It sound like you don't have a default route set up. Matt Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default192.168.0.2UGSc10dc0 127.0.0.1 127.0.0.1 UH 00lo0 192.168.0 link#1 UC 10dc0 192.168.0.2link#1 UHLW20dc0 192.168.0.2 is my BSD-router. I have done 'route add default 192.168.0.2' and I have even tried flushing the tables, but w/o success. Are the other hosts (with which you are testing) defined in /etc/hosts (on this box) or the BSD-router? They should appear here, if only when switched on. What does /var/log/messages /var/log/sedurity show? Regards, Stacey regards /Nikolaj To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: dhclient: no memory for option buffer ?
[EMAIL PROTECTED] writes: I'm getting this weird message reported by syslogd: dhclient: no memory for option buffer. Obviously this means that dhclient is reporting some sort of memory error, but what exactly? It just started reporting this error reecntly after I had a power outage, but everything else seems OK. I did some searching in the archives but couldn't find anything on this. Can anyone enlighten me? That error goes all the way back to malloc(), so it sounds like something got mangled on your system. Despite the fact that nothing else seems to be having problems, I'd suspect the system libraries first, but it could well be dhclient as well. If you keep your system up-to-date on any kind of regular basis, now might be a good time for an upgrade. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
XFree86 on Alpha and FreeBSD 4.7
Hello, I have installed FreeBSD 4.7 on an AlphaServer 1200 box with zero problems except I can't get X to run. The Alpha has the standard PowerStorm 4D10T PCI video card which is a 3DLabs Permedia2 chipset and TI TVP4020C RAMDAC. I have configured XF86Config with the appropriate card description and driver via sysinstall. When I try to start X the system bombs back to SRM and I have to reboot. I have installed RedHat Linux 7.2 w/ X support in the past and it ran X/KDE with no problem so the system will run X. The BSD I am using is the two disk ISO from the FTP site. Thanks for the help! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
On Sat, Jan 11, 2003 at 06:03:16PM +0100, Nikolaj Farrell wrote: snip and the ping outputs: # ping 192.168.0.2 PING 192.168.0.2 (192.168.0.2): 56 data bytes ping: sendto: Host is down ... repeated .. --- 192.168.0.2 ping statistics --- 7 packets transmitted, 0 packets received, 100% packet loss # ping speedy PING speedy.mydomain.se (192.168.0.2): 56 data bytes ping: sendto: Host is down ... repeated... --- speedy.mydomain.se ping statistics --- 9 packets transmitted, 0 packets received, 100% packet loss slight correction on problem-description: I can not ping the computer from other computers. I must have been dreaming or something regards /Nikolaj The fact that the other machines on the LAN cannot ping 192.168.0.1 is a big difference. At this point I would start checking you network cabling and possibly the hub/switch. Nathan -- GPG Public Key ID: 0x4250A04C gpg --keyserver pgp.mit.edu --recv-keys 4250A04C http://63.105.21.156/gpg_nkinkade_4250A04C.asc msg15122/pgp0.pgp Description: PGP signature
Re: Problems w NIC
The fact that the other machines on the LAN cannot ping 192.168.0.1 is a big difference. At this point I would start checking you network cabling and possibly the hub/switch. Nathan well yes, but as stated before this machine is a dual-boot and works perfectly in the other OS, so cables and hub must be working /Nikolaj To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
Hi, On Sat, 2003-01-11 at 16:25, Nikolaj Farrell wrote: Are the other hosts (with which you are testing) defined in /etc/hosts (on this box) or the BSD-router? They should appear here, if only when switched on. What does /var/log/messages /var/log/sedurity show? Regards, Stacey Yes, all boxes on my LAN are defined in /etc/hosts. The router has the same definitions. All 4 boxes are switched on and they all behave correctly. Well, except for this one of course ;) Please post:- /etc/hosts /etc/rc.conf Actual output from: ping other_host_by_name ping other_host_by_IP Regards, Stacey regards /Nikolaj -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: ipfilter/ipmon log msgs
On Fri, 10 Jan 2003, JoeB wrote: I am using ipfilter for my firewall and ipmon to capture firewall error msgs. Where can I find description of the format of the ipmon msg text so I can decipher what the msgs are saying? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message man ipmon Marco Radzinschi E-Mail: [EMAIL PROTECTED] Sat Jan 11 11:50:58 EST 2003 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Apache_fp Port install problem
On Sat, Jan 11, 2003 at 11:31:22AM -0600, Jack L. Stone wrote: I just updated from FBSD-4.5 to 4.7 on a server running apache_fp.1.26. The update somehow has broken the FP extensions (ugh!). I have tried a number of fixes, including portupgrade, but get a checksum error there. Have tried to rerun the present install of FP using fp_install.sh, but get this error: Who should own web root web on port 80 [www]: What should the group for web root web on port 80 be [www]: /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol __stderrp ERROR: Unable to chown web root web in port 80 Hit enter to continue I'm also seeing the __stderrp error in my httpd-error.log whenever I try to login to FP. So, something has changed in the FBSD-4.5-4.7 update and I've never seen this error, so don't know what needs to be fixed. I have another server running apache_fp.1.27 on FBSD.4.7 just fine. It's looking like an uninstall/reinstall completely for apache+fp didn't want to have to do that on a box with a bunch of virtual hosts. Has anyone seen the above problem on similar installs...??? /usr/src/UPDATING says: 20021110: The definitions of the standard file streams (stdio, stdout, and stderr) have changed so that they are no longer compile-time constants. Some older binaries may require updated 3.X compatability libraries (for example, by setting COMPAT3X=yes for a buildworld/installworld). Alternatively to doing a buildworld with COMPAT3X=yes, you could install the misc/compat3x port. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
Perhaps at this point, it's a good point for you to give us a descriptive picture of what the network layout is like there. What is between each host, and they are logically. Regards, Stacey Okidoki ;) Basically I have a home network connected to a DSL. The connection is negotiated by a FreeBSD machine with dual NICs. One NIC connected to the internet and the other to my hub. I also have a mail server connected to the hub and a workstation and a laptop. DSL | 192.168.0.2 | 192.168.0.5 - Hub - 192.168.0.4 | 192.168.0.1 well this picture will certainly not come out right, but the idea is that all machines except .0.2 have one NIC connected to the hub. 0.2 has two NICs and is gateway/firewall. This machine also does all the necessary port forwarding and such. Actually, I have had this setup successfully for a little over two years, and I recently bought a new computer and I gave it the same physical location as the old desktop. (i.e. same TP-cable and the same place on hub). I can't quite see the physical setup of the network as cause of the current problems. Thank you for all your help so far, I have to leave for a few hours, but am still thankful for all your efforts regards /Nikolaj To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
Hi, On Sat, 2003-01-11 at 17:15, Nikolaj Farrell wrote: The fact that the other machines on the LAN cannot ping 192.168.0.1 is a big difference. At this point I would start checking you network cabling and possibly the hub/switch. Nathan well yes, but as stated before this machine is a dual-boot and works perfectly in the other OS, so cables and hub must be working /Nikolaj Perhaps at this point, it's a good point for you to give us a descriptive picture of what the network layout is like there. What is between each host, and they are logically. Regards, Stacey To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: XFree86 on Alpha and FreeBSD 4.7
[EMAIL PROTECTED] wrote: Hello, I have installed FreeBSD 4.7 on an AlphaServer 1200 box with zero problems except I can't get X to run. The Alpha has the standard PowerStorm 4D10T PCI video card which is a 3DLabs Permedia2 chipset and TI TVP4020C RAMDAC. I have configured XF86Config with the appropriate card description and driver via sysinstall. When I try to start X the system bombs back to SRM and I have to reboot. I have installed RedHat Linux 7.2 w/ X support in the past and it ran X/KDE with no problem so the system will run X. The BSD I am using is the two disk ISO from the FTP site. Thanks for the help! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message Check your /var/log/XFree86.0.log lots of usefull info there, maybe it will help you identifying the problem Rob To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
Yes, right. Sorry, I somehow missed that point in the original post! When you ping, do you see any activity at all on your hub/switch? I suppose that this would minimally let you know that the card is transmittig something. Nathan No, I have a small light on the hub that says packet. This packet-light blinks when I try to ping the troublesome computer, but remains off when trying to ping from this computer. I am thinking perhaps driver problems? /Nikolaj To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: freebsd curiosity
On Thu, 9 Jan 2003, James Hicks wrote: require any kind of defrag? I was told by my UNIX instructor that freebsd had hardware recognition trouble. Is this true and if so has it been fixed? of the 3 or 4 linux distros I have experience with, one 1 has not required me to manually add a device driver or two. despite the lack of prettyness of freebsd's installer, I find freebsd to be by far quicker and easier to install. I have also found that freebsd's ports are easier to install and maintain that linux's rpms. to use freebsd. What is the problem that I'm hearing that linux has? Do you believe the berkeley system to have code that has better stability than the GNU systems? I look forward to your reply. Thanks you aren't really going to get a truly partial answer to that question on this mailing list, I think just about everyone will tell you that freebsd wins in the stability department. but in all my dealings with linux, i never once heard someone say linux was more stable than freebsd :) erik To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Apache_fp Port install problem
At 05:44 PM 1.11.2003 +, Matthew Seaman wrote: On Sat, Jan 11, 2003 at 11:31:22AM -0600, Jack L. Stone wrote: I just updated from FBSD-4.5 to 4.7 on a server running apache_fp.1.26. The update somehow has broken the FP extensions (ugh!). I have tried a number of fixes, including portupgrade, but get a checksum error there. Have tried to rerun the present install of FP using fp_install.sh, but get this error: Who should own web root web on port 80 [www]: What should the group for web root web on port 80 be [www]: /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol __stderrp ERROR: Unable to chown web root web in port 80 Hit enter to continue I'm also seeing the __stderrp error in my httpd-error.log whenever I try to login to FP. So, something has changed in the FBSD-4.5-4.7 update and I've never seen this error, so don't know what needs to be fixed. I have another server running apache_fp.1.27 on FBSD.4.7 just fine. It's looking like an uninstall/reinstall completely for apache+fp didn't want to have to do that on a box with a bunch of virtual hosts. Has anyone seen the above problem on similar installs...??? /usr/src/UPDATING says: 20021110: The definitions of the standard file streams (stdio, stdout, and stderr) have changed so that they are no longer compile-time constants. Some older binaries may require updated 3.X compatability libraries (for example, by setting COMPAT3X=yes for a buildworld/installworld). Alternatively to doing a buildworld with COMPAT3X=yes, you could install the misc/compat3x port. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way Good grief! I read the UPDATING as always, but this one did NOT sink in! Thank you so much for pointing me in the right direction before I shot myself in the foot If I go the misc/compat3x port route, I assume I need to redo the buildword?? If so, then I might as well include the COMPAT3X=yes in the make.conf. Sorry, a little dense after 3 hours sleep Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: rcp documentation
mike svejk [EMAIL PROTECTED] writes: I like to know where I can find the rcp protocol documented. I'm It basically isn't. It is part of the rlogin stuff (which is briefly described in RFC 1282), but you're best off looking at the source. implmenting a scp server and believe that rcp is used has the protocol after ssh has set up the secure channel. Um, no. *ssh* is the protocol used by scp. The relevant IETF working group is: http://www.ietf.org/html.charters/secsh-charter.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
On Sat, Jan 11, 2003 at 06:15:34PM +0100, Nikolaj Farrell wrote: The fact that the other machines on the LAN cannot ping 192.168.0.1 is a big difference. At this point I would start checking you network cabling and possibly the hub/switch. Nathan well yes, but as stated before this machine is a dual-boot and works perfectly in the other OS, so cables and hub must be working /Nikolaj Yes, right. Sorry, I somehow missed that point in the original post! When you ping, do you see any activity at all on your hub/switch? I suppose that this would minimally let you know that the card is transmittig something. Nathan -- GPG Public Key ID: 0x4250A04C gpg --keyserver pgp.mit.edu --recv-keys 4250A04C http://63.105.21.156/gpg_nkinkade_4250A04C.asc msg15134/pgp0.pgp Description: PGP signature
Apache_fp Port install problem
I just updated from FBSD-4.5 to 4.7 on a server running apache_fp.1.26. The update somehow has broken the FP extensions (ugh!). I have tried a number of fixes, including portupgrade, but get a checksum error there. Have tried to rerun the present install of FP using fp_install.sh, but get this error: Who should own web root web on port 80 [www]: What should the group for web root web on port 80 be [www]: /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol __stderrp ERROR: Unable to chown web root web in port 80 Hit enter to continue I'm also seeing the __stderrp error in my httpd-error.log whenever I try to login to FP. So, something has changed in the FBSD-4.5-4.7 update and I've never seen this error, so don't know what needs to be fixed. I have another server running apache_fp.1.27 on FBSD.4.7 just fine. It's looking like an uninstall/reinstall completely for apache+fp didn't want to have to do that on a box with a bunch of virtual hosts. Has anyone seen the above problem on similar installs...??? Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
Please post:- /etc/hosts /etc/rc.conf Actual output from: ping other_host_by_name ping other_host_by_IP Regards, Stacey /etc/hosts: 127.0.0.1 localhost.mydomain.se localhost 192.168.0.1 athlon.mydomain.se athlon 192.168.0.1 athlon.mydomain.se. 192.168.0.2 speedy.mydomain.se speedy 192.168.0.4 mail.mydomain.se mail 192.168.0.5 laptop.mydomain.se laptop /etc/rc.conf defaultrouter=192.168.0.2 hostname=athlon.mydomain.se ifconfig_dc0=inet 192.168.0.1 netmask 255.255.255.0 kern_securelevel_enable=NO keymap=swedish.iso linux_enable=YES moused_enable=YES nfs_client_enable=YES nfs_reserved_port_only=YES sendmail_enable=YES sshd_enable=YES usbd_enable=YES and the ping outputs: # ping 192.168.0.2 PING 192.168.0.2 (192.168.0.2): 56 data bytes ping: sendto: Host is down ... repeated .. --- 192.168.0.2 ping statistics --- 7 packets transmitted, 0 packets received, 100% packet loss # ping speedy PING speedy.mydomain.se (192.168.0.2): 56 data bytes ping: sendto: Host is down ... repeated... --- speedy.mydomain.se ping statistics --- 9 packets transmitted, 0 packets received, 100% packet loss slight correction on problem-description: I can not ping the computer from other computers. I must have been dreaming or something regards /Nikolaj To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re[2]: Problems w NIC
Do you have IPFW or IPFilter compiled into the kernel? If so what do `ipfw list` and/or `ipfstat -ion` show? -- Benmailto:[EMAIL PROTECTED] Saturday, January 11, 2003, 12:53:49 PM, you wrote: Yes, right. Sorry, I somehow missed that point in the original post! When you ping, do you see any activity at all on your hub/switch? I suppose that this would minimally let you know that the card is transmittig something. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
Hi, On Sat, 2003-01-11 at 17:48, Nikolaj Farrell wrote: Perhaps at this point, it's a good point for you to give us a descriptive picture of what the network layout is like there. What is between each host, and they are logically. Regards, Stacey Okidoki ;) Basically I have a home network connected to a DSL. The connection is negotiated by a FreeBSD machine with dual NICs. One NIC connected to the internet and the other to my hub. I also have a mail server connected to the hub and a workstation and a laptop. DSL | 192.168.0.2 | 192.168.0.5 - Hub - 192.168.0.4 | 192.168.0.1 well this picture will certainly not come out right, but the idea is that all machines except .0.2 have one NIC connected to the hub. 0.2 has two NICs and is gateway/firewall. This machine also does all the necessary port forwarding and such. Thanks for getting back with the funky art:-) Question on the network though, you mentioned: but the idea is that all machines except .0.2 have one NIC connected to the hub So according to your diagram, the FreeBSD box has two nics - 1 to Internet (?) and the other connected to , what? Which interface on the FreeBSD box has the IP address of 192.168.0.2? If of all the machines, .0.2 connect to the hub, how do the others then see the FreeBSD box? You also mention: 0.2 has two NICs and is gateway/firewall What packet filter do you have? For whichever you are using, please post the fw logs. Looking forward to hearing more on the information I asked for here. Regards, Stacey Actually, I have had this setup successfully for a little over two years, and I recently bought a new computer and I gave it the same physical location as the old desktop. (i.e. same TP-cable and the same place on hub). I can't quite see the physical setup of the network as cause of the current problems. Thank you for all your help so far, I have to leave for a few hours, but am still thankful for all your efforts regards /Nikolaj -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: ext3 - fbsd
dick hoogendijk [EMAIL PROTECTED] writes: I think FreeBSD does _not_ support the linux ext2 / ext3 I think I read (a couple years ago) that the ext2 and ext3 filesystems look the same on the disk; the difference is all in the kernel's handling of the data. If that's true (and you should check with Linux people) then FreeBSD should be able handle it. Again, a couple years ago, I couldn't get the two OSes to even read each others FSs without a few errors, so I resorted to transfering data by using a raw partition as a tar _T_ape _AR_chive. Report your success or failure, please. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: DNS and DHCPD
On Thu, 9 Jan 2003 [EMAIL PROTECTED] wrote: I would like to configure my dhcpd server (isc-dhcpd3 from ports). I would also like to have the options domainnameservers (or somewhat similar) to be dynamic, as my fBSD box is my own router. (I run a local network). The WAN side is DHCP'd, so my IP and DNS servers are set differently each time. I was wondering how to set the domainname servers option in my dhcpd.conf dynamically. Like, it would get edited each time upon bootup, and before dhcpd even loads. I don't know how to even start approaching this problem, except for asking you guys. Thanks so much, lattera Forget your ISP's DNS servers and run your own. I use bind on my firewall, and have the DHCP server hand out the firewall address as the DNS server. Not what you asked originally, but it works like a charm, especially when Comcast's DNS servers suddenly stop working. Try running /usr/sbin/named to get started. Otherwise, man named. Marco Radzinschi E-Mail: [EMAIL PROTECTED] Sat Jan 11 11:38:01 EST 2003 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
Nikolaj Farrell wrote: Yes, right. Sorry, I somehow missed that point in the original post! When you ping, do you see any activity at all on your hub/switch? I suppose that this would minimally let you know that the card is transmittig something. No, I have a small light on the hub that says packet. This packet-light blinks when I try to ping the troublesome computer, but remains off when trying to ping from this computer. I am thinking perhaps driver problems? Could well be. You say that it works fine under another OS? What other OS? What, also, is the make/model of the NIC? Check ifconfig and compare the media line to the actual capibilities of the system. If it's not negiotiating properly (could a driver cause that?) you might be able to get it working by manually specifying the media type in an ifconfig command. I'm grasping at straws here, but hopefully it will be helpful. -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: ext3 - fbsd
dick hoogendijk wrote: On 11 Jan Bill Moran wrote: FreeBSD _does_ understand ext2. See the mount_ext2fs command for details. Unfortunately, ext3 isn't supported yet AFAIK. So, if I switch this drive to another (fbsd) box I could copy form one (ext2) drive to another UFS drive preserving all persmission? Or would it be better to tar the drive onto the new one; reformat the old drive as UFS and untar back? Yup. Use 'cp -Rp /old/part /new/part' to maintain as many perms as possible. Any reason why you can't copy the contents of this partition to another computer (via network) and then reformat it UFS while installing FreeBSD and copy everything back? Network too slow (for a transfer of approx 35G), plus _space_ :) Ouch, didn't know that you had that much data! You should be able to copy off an ext2 filesystem, though. -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: adding some new IPs from a different subnet
Kevin Stevens [EMAIL PROTECTED] writes: On Saturday, Jan 11, 2003, at 08:28 US/Pacific, Lowell Gilbert wrote: I think this is it: net.link.ether.inet.log_arp_wrong_iface Check whether yours is off or on and change it the other way. It would be better to fix the actual problem than to just make the error message go away. In this case, specifying a correct subnet mask on the alias configuration should solve the problem. [I think.] I saw the note about the incorrect mask on the second 10. address; and agree that it needs fixing, but I don't think that was the source of the log messages. I ran into the same thing when I had different NICS on different IP subnets on the same physical network some time ago - that's how I remembered the setting. That's why there's a sysctl for it - depending on your configuration, it isn't actually an error. The incorrect netmask would be enough to cause the message. And I happen to think that the message *always* indicates an error. In many cases, it indicates an ISP error that you (downstream) can't do anything about, but it's always an error. [My logic is: within the window of a single ARP timeout, an IP address should not be used on the link by a different Ethernet address. Let's see what the OP discovers. I'm sure that one way or another, he's fine. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: ext3 - fbsd
On Sat, Jan 11, 2003 at 08:36:22AM -0800, Gary W. Swearingen wrote: dick hoogendijk [EMAIL PROTECTED] writes: I think FreeBSD does _not_ support the linux ext2 / ext3 I think I read (a couple years ago) that the ext2 and ext3 filesystems look the same on the disk; the difference is all in the kernel's handling of the data. If that's true (and you should check with Linux Ext3 is Ext2 + journal file. Let me quote the documentation: ext3 filesystems may still be mounted by ext2 as long as they have been cleanly unmounted. ext2 will refuse to mount ext3 filesystems which have not been cleanly shut down, because there is live data still in the journal which ext2 does not know how to deal with. So you should have no trouble mounting ext3 partitions. -- Nimrod. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: MAC address trouble
I did an upgrade of my LAN this morning from 10Mbits to 100Mbits (full duplex). To do so i bought to Sitecom Fast Ethernet LAN cards (sitecom chipset). After installation i found out that freebsd gave both the cards the same MAC address (here is my arp output) 192.168.0.2 08-00-08-00-08-00 dynamic 192.168.0.3 08-00-08-00-08-00 dynamic i also found out that these are not the MAC adresses they are supposed to have (the DOS tool shows other MAC addresses). The driver both cards use is dc Can anyone tell me what is going on and if i can change the MAC of one of the cards during boot. I know i can change them using ifconfig dc0 lladdr newmac but i need to do this at boot cause having the same MAC address i lose contact to both servers. I've resolved the issue currently using /etc/rc.local i also found that this error is already discussed about on freebsd-stable an explanation of the error can be found here. http://groups.google.com/groups?hl=nllr=ie=UTF-8oe=UTF-8threadm=amjkrm%241ke4%241%40FreeBSD.csie.NCTU.edu.twrnum=4prev=/groups%3Fq%3DADM983%2B%252B%2Bfreebsd%26hl%3Dnl%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26selm%3Damjkrm%25241ke4%25241%2540FreeBSD.csie.NCTU.edu.tw%26rnum%3D4%26filter%3D0 Marcel To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: MAC address trouble
ifconfig dc0 lladdr newmac but i need to do this at boot cause having the same MAC address i lose contact to both servers. friend of mine helped me out here, he found an eeprom tool to change the MAC one can download it here http://www.admtek.com.tw/download/AN983B.htm Marcel To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
MAC address trouble
Hi all, I did an upgrade of my LAN this morning from 10Mbits to 100Mbits (full duplex). To do so i bought to Sitecom Fast Ethernet LAN cards (sitecom chipset). After installation i found out that freebsd gave both the cards the same MAC address (here is my arp output) 192.168.0.2 08-00-08-00-08-00 dynamic 192.168.0.3 08-00-08-00-08-00 dynamic i also found out that these are not the MAC adresses they are supposed to have (the DOS tool shows other MAC addresses). The driver both cards use is dc Can anyone tell me what is going on and if i can change the MAC of one of the cards during boot. I know i can change them using ifconfig dc0 lladdr newmac but i need to do this at boot cause having the same MAC address i lose contact to both servers. Marcel -- It's no surprise that things are so screwed up: everyone that knows how to run a government is either driving taxicabs or cutting hair. -- George Burns To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Cisco Aironet PCI card - The Fix
Hi all, Just a note for anyone wanting to try a Cisco Aironet PCI card under FreeBSD. I had problems getting mine to work, but a firmware upgrade to the latest Cisco firmware appears to have solved my problems. Regards, -- - Wayne Pascoe You cannot apply a technological solution to a sociological problem. (Edwards' Law) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: adding some new IPs from a different subnet
On Saturday, Jan 11, 2003, at 14:15 US/Pacific, Josh Brooks wrote: Ok, I toggled net.link.ether.inet.log_arp_wrong_iface - I set it to zero ... and I am still getting those error messages ... Any thoughts ? Did you change thea 10. alias mask at Lowell suggested? KeS To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
HI, On Sat, 2003-01-11 at 22:46, Nikolaj Farrell wrote: Hello again everyone, I will try to clearify below; Thanks for getting back with the funky art:-) Question on the network though, you mentioned: but the idea is that all machines except .0.2 have one NIC connected to the hub More appropriate description would be All machines except 192.168.0.2 have one NIC. 192.168.0.2 has two NICs, where one NIC is connected to hub and the other to DSL modem. I am sorry if this caused confusion. So according to your diagram, the FreeBSD box has two nics - 1 to Internet (?) and the other connected to , what? Which interface on the FreeBSD box has the IP address of 192.168.0.2? If of all the machines, .0.2 connect to the hub, how do the others then see the FreeBSD box? Actually all my computers are FreeBSD. The gateway with two NICs has one NIC connected to the hub. Me writing 0.2 was simple laziness and meant 192.168.0.2. I was not trying to indicate an ip-range or anything similar. You also mention: 0.2 has two NICs and is gateway/firewall What packet filter do you have? For whichever you are using, please post the fw logs. 192.168.0.2 is running natd/ipfw. The only thing forwarded aimed specifically at one machine is pop and smtp which both redirect to my mailserver. Otherwise the following rule is all I have; (apart from firewalling on external NIC and there are no rules for the internal network) 00100 divert 8668 ip from any to any via xl0 These rules work perfectly for all other fbsd-boxes on my LAN. Looking forward to hearing more on the information I asked for here. Regards, Stacey I hope this makes things a little more clear. I can also add that I, in all frustration, did a complete reinstall. I repartioned/sliced the disk and then installed again from cd-rom. (The installer wouldn't allow ftp, since it couldn't find any servers responding... ;) ). This did, naturally, not help at all. Thanks for clarifying things. I think I understand now. Here's what I (and others as well) believe is the root of the problem - its ipfw. By default its got a rule that reads DENY EVERYTHING. If you run ipfw show then it'll be right at the bottom. Unless you expressly allow traffic with ipfw statements, then you'll get packets not being forwarded onto respective destinations. Also if you've not actually configured the rule-set (E.G. for logging) then that explains why nothing appears in the logs. You mentioned that you've not configured any rules for the internal network, so you've answered you own questions here. Post the output from the above ipfw cmd, and I'm sure there'll be lots of assistance for you. Regards, Stacey regards /Nikolaj -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
Could well be. You say that it works fine under another OS? What other OS? What, also, is the make/model of the NIC? Check ifconfig and compare the media line to the actual capibilities of the system. If it's not negiotiating properly (could a driver cause that?) you might be able to get it working by manually specifying the media type in an ifconfig command. I'm grasping at straws here, but hopefully it will be helpful. -- Bill Moran Potential Technologies http://www.potentialtech.com Hello, The make and model of the card are Cnet pro200 with Davicom DM9102A chipset. I bought this card because it actually claims to work under FreeBSD. The included floppy has a driver for FreeBSD and the following text: This driver is being supplied as a supplement to FreeBSD 3.2, 3.3, and 3.4, which is due to be released very soon. Unfortunately, the FreeBSD 3.4 code freeze went into effect before this driver clould be included with the 3.4 distribution. Note that FreeBSD 4.0, which is supposed to be released in January of next year, will include support for the Davicom DM9102 chip using the if_dc driver. You do not need this driver for FreeBSD 4.0. This driver (and the one on FreeBSD 4.0) should work on both FreeBSD/x86 and FreeBSD/alpha. This clearly indicates that it shouldn't be a driver problem after all. Unless the driver changed? Media type seems to be correct. regards /Nikolaj To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Ports checksum errors
I know there's been a lot of questions lately about broken ports and now I'm stuck. I cannot find this specific problem in the past recent archives. I' trying to upgrade Apache+Frontpage and keep getting this error no matter what trick I try. root@sageman make === Extracting for apache_fp-1.3.27 Checksum mismatch for apache_1.3.27.tar.gz. Checksum OK for powerlogo.gif. Checksum OK for fplogo.gif. Make sure the Makefile and distinfo file (/usr/ports/www/apache13-fp/distinfo) are up to date. If you are absolutely sure you want to override this check, type make NO_CHECKSUM=yes [other args]. *** Error code 1 Can anyone shed some light. What is the cure??? Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
Thanks for clarifying things. I think I understand now. Here's what I (and others as well) believe is the root of the problem - its ipfw. By default its got a rule that reads DENY EVERYTHING. If you run ipfw show then it'll be right at the bottom. Unless you expressly allow traffic with ipfw statements, then you'll get packets not being forwarded onto respective destinations. Also if you've not actually configured the rule-set (E.G. for logging) then that explains why nothing appears in the logs. You mentioned that you've not configured any rules for the internal network, so you've answered you own questions here. Post the output from the above ipfw cmd, and I'm sure there'll be lots of assistance for you. Regards, Stacey Actually... I have compiled ipfw _default to accept_.. and besides, no other computers on my LAN would work otherwise either. Just for the sake of it though, here is my ruleset su-2.05b# ipfw list 00190 divert 8668 ip from any to any via xl0 00301 deny log logamount 100 tcp from any to any 515 in recv xl0 00310 allow tcp from 212.181.54.2 53 to any in recv xl0 00311 allow tcp from 212.181.54.3 53 to any in recv xl0 00320 allow log logamount 100 tcp from any to any 22 in recv xl0 00321 allow log logamount 100 tcp from any to any 21 in recv xl0 00322 allow log logamount 100 tcp from any to any 113 in recv xl0 setup 00323 allow log logamount 100 tcp from any to any 80 in recv xl0 00324 allow tcp from any to any 25 via xl0 00325 allow tcp from any to any 995 via xl0 00395 deny log logamount 100 tcp from any to any 0-1024 in recv xl0 setup 00396 deny log logamount 100 tcp from any to any 2049 in recv xl0 00400 allow udp from 212.181.54.2 53 to any in recv xl0 00401 allow udp from 212.181.54.3 53 to any in recv xl0 00410 allow udp from any to any 123 in recv xl0 00499 deny log logamount 100 udp from any to any in recv xl0 00610 allow icmp from 212.181.54.2 to any in recv xl0 00611 allow icmp from 212.181.54.3 to any in recv xl0 00620 allow log logamount 100 icmp from any to any in recv xl0 icmptype 3 00621 allow log logamount 100 icmp from any to any in recv xl0 icmptype 8 65535 allow ip from any to any regards /Nikolaj To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Netatalk - Mac OS X connection problem
I am running netatalk-1.6.0_1,1 from the FreeBSD ports systems on two
boxes and connecting from Mac OS X 10.2.3.
Now when I connect from one box I get the following error on the mac:
Connection failed
An AppleShare system error occurred.
I can connect to the other box without any problems. Netatalk is
configured the same on both boxes. This problem came on suddenly.
Below is the log file showing netatalk starting up.
This is a stumper.
Please also cc me on any email as I can no longer subscribe to the list.
Thanks,
Jim
Jan 11 17:37:32 atalkd[88690][logger.c:409]: I:Logger: doing
syslog_setup, type 0, level 50
Jan 11 17:37:32 atalkd[88690][logger.c:434]: D7:Logger:
log_file_arr[0] now contains: {log_filename:, log_file:0x0,
log_level: 50}
Jan 11 17:37:32 atalkd[88690][logger.c:437]: D5:Logger: syslog_setup[0] done
Jan 11 17:37:32 atalkd[88690][main.c:1090]: I:ATalkDaemon: restart (1.6.0)
Jan 11 17:37:34 atalkd[88690][zip.c:910]: I:ATalkDaemon: zip_getnetinfo for dc0
Jan 11 17:37:44 atalkd[88690][zip.c:910]: I:ATalkDaemon: zip_getnetinfo for dc0
Jan 11 17:37:54 atalkd[88690][zip.c:910]: I:ATalkDaemon: zip_getnetinfo for dc0
Jan 11 17:38:04 atalkd[88690][main.c:278]: I:ATalkDaemon: config for no router
Jan 11 17:38:06 atalkd[88690][main.c:659]: I:ATalkDaemon: ready 0/0/0
Jan 11 17:38:06 afpd[88691][logger.c:409]: I:Logger: doing
syslog_setup, type 0, level 50
Jan 11 17:38:06 afpd[88691][logger.c:434]: D7:Logger: log_file_arr[0]
now contains: {log_filename:, log_file:0x0, log_level: 50}
Jan 11 17:38:06 afpd[88691][logger.c:437]: D5:Logger: syslog_setup[0] done
--
Jim Arnold - Ohio.com - [EMAIL PROTECTED]
Cell: 330.730.0797 Voice: 330.572.2822
AOL IM: instantjim/Yahoo: jim0266
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Re: adding some new IPs from a different subnet
Actually that was already correct - it was a typo in bringing it over to email form. On the system itself it has the correct .255 mask. On Sat, 11 Jan 2003, Kevin Stevens wrote: On Saturday, Jan 11, 2003, at 14:15 US/Pacific, Josh Brooks wrote: Ok, I toggled net.link.ether.inet.log_arp_wrong_iface - I set it to zero ... and I am still getting those error messages ... Any thoughts ? Did you change thea 10. alias mask at Lowell suggested? KeS To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Re[2]: Problems w NIC
Yeah, this is a classic example of ipfw enabled but not configured. Since the default rule is 'Deny all', you need to add allow statements to the config to see the network, or build a non-ipfw config (Being the internal box, you have no need for ipfw on it) --Adam Nope. Kernel compiled IPFIREWALL_DEFAULT_TO_ACCEPT. Also see my previous mail. /Nikolaj To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Ports checksum errors
Jack L. Stone [EMAIL PROTECTED] writes: I know there's been a lot of questions lately about broken ports and now I'm stuck. I cannot find this specific problem in the past recent archives. It's not a broken port. I' trying to upgrade Apache+Frontpage and keep getting this error no matter what trick I try. Try removing (or moving out of the way) your existing /usr/ports/distfiles/apache_1.3.27.tar.gz To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Netatalk - Mac OS X connection problem
On Sat, 2003-01-11 at 18:00, Jim Arnold wrote: I am running netatalk-1.6.0_1,1 from the FreeBSD ports systems on two boxes and connecting from Mac OS X 10.2.3. Now when I connect from one box I get the following error on the mac: Connection failed An AppleShare system error occurred. I can connect to the other box without any problems. Netatalk is configured the same on both boxes. This problem came on suddenly. Below is the log file showing netatalk starting up. This is a stumper. Please also cc me on any email as I can no longer subscribe to the list. The log isn't too helpful, but a sniffer trace might be. Can you capture the client connection to the bad server with tcpdump, and send me the raw capture file. I recommend the following command line: tcpdump -s 1518 -w /tmp/outfile host IP address of client Note, this assumes you're connecting over TCP (which you really should be with OS X). Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: Ports checksum errors
At 06:08 PM 1.11.2003 -0500, Lowell Gilbert wrote: Jack L. Stone [EMAIL PROTECTED] writes: I know there's been a lot of questions lately about broken ports and now I'm stuck. I cannot find this specific problem in the past recent archives. It's not a broken port. I' trying to upgrade Apache+Frontpage and keep getting this error no matter what trick I try. Try removing (or moving out of the way) your existing /usr/ports/distfiles/apache_1.3.27.tar.gz Thanks, Lowell. It was that simple as I had an October copy sitting there. Appreciate the help. Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
Hi, On Sat, 2003-01-11 at 22:57, Nikolaj Farrell wrote: Thanks for clarifying things. I think I understand now. Here's what I (and others as well) believe is the root of the problem - its ipfw. By default its got a rule that reads DENY EVERYTHING. If you run ipfw show then it'll be right at the bottom. Unless you expressly allow traffic with ipfw statements, then you'll get packets not being forwarded onto respective destinations. Also if you've not actually configured the rule-set (E.G. for logging) then that explains why nothing appears in the logs. You mentioned that you've not configured any rules for the internal network, so you've answered you own questions here. Post the output from the above ipfw cmd, and I'm sure there'll be lots of assistance for you. Regards, Stacey Actually... I have compiled ipfw _default to accept_.. and besides, no other computers on my LAN would work otherwise either. Just for the sake of it though, here is my ruleset su-2.05b# ipfw list 00190 divert 8668 ip from any to any via xl0 00301 deny log logamount 100 tcp from any to any 515 in recv xl0 00310 allow tcp from 212.181.54.2 53 to any in recv xl0 00311 allow tcp from 212.181.54.3 53 to any in recv xl0 00320 allow log logamount 100 tcp from any to any 22 in recv xl0 00321 allow log logamount 100 tcp from any to any 21 in recv xl0 00322 allow log logamount 100 tcp from any to any 113 in recv xl0 setup 00323 allow log logamount 100 tcp from any to any 80 in recv xl0 00324 allow tcp from any to any 25 via xl0 00325 allow tcp from any to any 995 via xl0 00395 deny log logamount 100 tcp from any to any 0-1024 in recv xl0 setup 00396 deny log logamount 100 tcp from any to any 2049 in recv xl0 00400 allow udp from 212.181.54.2 53 to any in recv xl0 00401 allow udp from 212.181.54.3 53 to any in recv xl0 00410 allow udp from any to any 123 in recv xl0 00499 deny log logamount 100 udp from any to any in recv xl0 00610 allow icmp from 212.181.54.2 to any in recv xl0 00611 allow icmp from 212.181.54.3 to any in recv xl0 00620 allow log logamount 100 icmp from any to any in recv xl0 icmptype 3 00621 allow log logamount 100 icmp from any to any in recv xl0 icmptype 8 65535 allow ip from any to any So, you're saying that with this configuration, you: 1] Cannot ping any hosts on the internal network 2] No internal hosts can ping the internal IP address of the g'way. Do this for me:- 1] tail /var/log/security 2] Back-up your current ipfw ruleset - and disconnect (physically) from the internet 3] create a new rule set that reads ipfw add allow log ip any to any 4] reload the new ruleset into place 5] Try connecting to and from other internal hosts 6] Post logs here. Regards, Stacey regards /Nikolaj To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
So, you're saying that with this configuration, you: 1] Cannot ping any hosts on the internal network 2] No internal hosts can ping the internal IP address of the g'way. Do this for me:- 1] tail /var/log/security 2] Back-up your current ipfw ruleset - and disconnect (physically) from the internet 3] create a new rule set that reads ipfw add allow log ip any to any 4] reload the new ruleset into place 5] Try connecting to and from other internal hosts 6] Post logs here. Regards, Stacey Summary so far; Actually what I am saying is: 1] Computer with problems cant ping anything but itself 2] All internal computers can access the gw (and internet), except for computer with problems. 3] The gateway machine has no problems, neither do any of the other computers on the LAN. As for the stuff you want me to do; One of the first things I checked was the firewalling, and I then did an ipfw flush. (just to be sure) security logs show nothing, probably due to that firewall is completely open on the internal interface and firewall is default to accept. If you really really think the security-log can be of help I can post it, but please read on. Everything else in the network, except for fawlty machine 192.168.0.1, works problem-free and have done so in over two years. the computer 192.168.0.1 is brand new and is set up on the same physical location and the same tp-cable as the old computer. (which is not used anymore). When I ping from 192.168.0.1 to ANY host no packets leave the interface-card (according to hub). The only thing that so far has prevented me from throwing the NIC out the window is the fact that if I reboot the computer, and boot up WindowsXP instead, everything works perfectly. This also rules out problems set outside of 192.168.0.1. (or am I wrong?). regards /Nikolaj To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
Hi, Perhaps I misunderstood here. On Sat, 2003-01-11 at 23:59, Nikolaj Farrell wrote: So, you're saying that with this configuration, you: 1] Cannot ping any hosts on the internal network 2] No internal hosts can ping the internal IP address of the g'way. Do this for me:- 1] tail /var/log/security 2] Back-up your current ipfw ruleset - and disconnect (physically) from the internet 3] create a new rule set that reads ipfw add allow log ip any to any 4] reload the new ruleset into place 5] Try connecting to and from other internal hosts 6] Post logs here. Regards, Stacey Summary so far; Actually what I am saying is: 1] Computer with problems cant ping anything but itself 2] All internal computers can access the gw (and internet), except for computer with problems. 3] The gateway machine has no problems, neither do any of the other computers on the LAN. As for the stuff you want me to do; One of the first things I checked was the firewalling, and I then did an ipfw flush. (just to be sure) security logs show nothing, probably due to that firewall is completely open on the internal interface and firewall is default to accept. If you really really think the security-log can be of help I can post it, but please read on. Everything else in the network, except for fawlty machine 192.168.0.1, works problem-free and have done so in over two years. the computer 192.168.0.1 is brand new and is set up on the same physical location and the same tp-cable as the old computer. (which is not used anymore). I see. So there's this machine hanging off the hub that no-one else can see, and he cannot see anyone else. Yet when booted to WinXP, he is fine? Forgive me and post what you get from ifconfig -au, please. Regards, Stacey When I ping from 192.168.0.1 to ANY host no packets leave the interface-card (according to hub). The only thing that so far has prevented me from throwing the NIC out the window is the fact that if I reboot the computer, and boot up WindowsXP instead, everything works perfectly. This also rules out problems set outside of 192.168.0.1. (or am I wrong?). regards /Nikolaj To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
We're not referring to your gateway machine having firewall issues, but rather the machine with connectivity issues.It has all the symptoms of a non-configured ipfw firewall. --Adam - Original Message - From: Nikolaj Farrell [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Saturday, January 11, 2003 6:59 PM Subject: Re: Problems w NIC So, you're saying that with this configuration, you: 1] Cannot ping any hosts on the internal network 2] No internal hosts can ping the internal IP address of the g'way. Do this for me:- 1] tail /var/log/security 2] Back-up your current ipfw ruleset - and disconnect (physically) from the internet 3] create a new rule set that reads ipfw add allow log ip any to any 4] reload the new ruleset into place 5] Try connecting to and from other internal hosts 6] Post logs here. Regards, Stacey Summary so far; Actually what I am saying is: 1] Computer with problems cant ping anything but itself 2] All internal computers can access the gw (and internet), except for computer with problems. 3] The gateway machine has no problems, neither do any of the other computers on the LAN. As for the stuff you want me to do; One of the first things I checked was the firewalling, and I then did an ipfw flush. (just to be sure) security logs show nothing, probably due to that firewall is completely open on the internal interface and firewall is default to accept. If you really really think the security-log can be of help I can post it, but please read on. Everything else in the network, except for fawlty machine 192.168.0.1, works problem-free and have done so in over two years. the computer 192.168.0.1 is brand new and is set up on the same physical location and the same tp-cable as the old computer. (which is not used anymore). When I ping from 192.168.0.1 to ANY host no packets leave the interface-card (according to hub). The only thing that so far has prevented me from throwing the NIC out the window is the fact that if I reboot the computer, and boot up WindowsXP instead, everything works perfectly. This also rules out problems set outside of 192.168.0.1. (or am I wrong?). regards /Nikolaj To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
I see. So there's this machine hanging off the hub that no-one else can see, and he cannot see anyone else. Yet when booted to WinXP, he is fine? Forgive me and post what you get from ifconfig -au, please. Regards, Stacey Actually, I have to apologize. I shouldn't have answered with information that I myself could have ruled out as reasons for problem. I never meant to confuse and am still very thankful for the help. ifconfig -au: dc0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.0.1 netmask 0xff00 broadcast 192.168.0.255 inet6 fe80::208:a1ff:fe2c:28fa%dc0 prefixlen 64 scopeid 0x1 ether 00:08:a1:2c:28:fa media: Ethernet autoselect (10baseT/UTP) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff00 Do you think the problem possibly could be in media auto select? The network speed is 10Mbps, so 10baseT should be correct? Again thank you for your help so far. regards /Nikolaj To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
Hi, On Sun, 2003-01-12 at 00:17, Nikolaj Farrell wrote: I see. So there's this machine hanging off the hub that no-one else can see, and he cannot see anyone else. Yet when booted to WinXP, he is fine? Forgive me and post what you get from ifconfig -au, please. Regards, Stacey Actually, I have to apologize. I shouldn't have answered with information that I myself could have ruled out as reasons for problem. I never meant to confuse and am still very thankful for the help. 'skay, I should be paying more attention. ifconfig -au: dc0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.0.1 netmask 0xff00 broadcast 192.168.0.255 inet6 fe80::208:a1ff:fe2c:28fa%dc0 prefixlen 64 scopeid 0x1 ether 00:08:a1:2c:28:fa media: Ethernet autoselect (10baseT/UTP) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff00 Do you think the problem possibly could be in media auto select? The network speed is 10Mbps, so 10baseT should be correct? Not a problem. If the network is running at 10, then if the nic is set to auto-negotiate then it's *supposed* to return 10baseT. But I do have to ask again if there is a firewall running on the problem box itself. My reasons for asking again, is the fact that nothing hitting the hub, as you say, does indeed indicate that nothing leaves the box. In cases like this, its usually because data was not *allowed* to leave the box. I'd ask you again to check his for sure. Just so as to eliminate this, just run ipfw show on the box, please. Also check in /etc/rc.conf, as well in the kernel for IPFIREWALL definitions. Regards, Stacey Again thank you for your help so far. regards /Nikolaj To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
But I do have to ask again if there is a firewall running on the problem box itself. My reasons for asking again, is the fact that nothing hitting the hub, as you say, does indeed indicate that nothing leaves the box. In cases like this, its usually because data was not *allowed* to leave the box. I'd ask you again to check his for sure. Just so as to eliminate this, just run ipfw show on the box, please. Also check in /etc/rc.conf, as well in the kernel for IPFIREWALL definitions. Regards, Stacey See below for details, I just want to point out that the computer has a clean install from cd-rom. I have not compiled the kernel and AFAIK ipfw is not set default in the GENERIC kernel. And I would never intentionally activate ipfw on this computer. Anyways: # ipfw list ipfw: getsockopt(IP_FW_GET): Protocol not available # uname -a FreeBSD athlon.mydomain.se 4.7-RELEASE FreeBSD 4.7-RELEASE #0: Wed Oct 9 15:08:34 GMT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 # cat /etc/rc.conf defaultrouter=192.168.0.2 hostname=athlon.mydomain.se ifconfig_dc0=inet 192.168.0.1 netmask 255.255.255.0 kern_securelevel_enable=NO keymap=swedish.iso linux_enable=YES moused_enable=YES nfs_client_enable=YES nfs_reserved_port_only=YES sendmail_enable=YES sshd_enable=YES usbd_enable=YES and finally the contents of /usr/src/sys/i386/conf/GENERIC # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-confi g.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.48 2002/08/31 20:28:26 obrien Exp $ machine i386 cpu I386_CPU cpu I486_CPU cpu I586_CPU cpu I686_CPU ident GENERIC maxusers 0 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options UFS_DIRHASH #Improve performance on big directories options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O device isa device eisa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device fd1 at fdc0 drive 1 # # If you have a Toshiba Libretto with its Y-E Data PCMCIA floppy, # don't use the above line for fdc0 but the following one: #device fdc0 # ATA and ATAPI devices device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering # SCSI Controllers device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices device ahd # AHA39320/29320 and onboard AIC79xx devices device amd # AMD 53C974 (Tekram DC-390(T)) device isp # Qlogic family device mpt # LSI-Logic MPT/Fusion device ncr # NCR/Symbios Logic device sym # NCR/Symbios Logic (newer chipsets) options
Re: Netatalk - Mac OS X connection problem
On Sat, 2003-01-11 at 19:12, Jim Arnold wrote: The log isn't too helpful, but a sniffer trace might be. Can you capture the client connection to the bad server with tcpdump, and send me the raw capture file. I recommend the following command line: tcpdump -s 1518 -w /tmp/outfile host IP address of client Note, this assumes you're connecting over TCP (which you really should be with OS X). Attached is the outfile as run on the FreeBSD box with the command line from above. tcpdump -s 1518 -w /tmp/outfile host 192.168.0.4 .4 is the Mac OS X box I hope this is what you meant. :) Do you have a custom volume icon on this server? If so, try deleting it, then reconnection. Joe Thanks, Jim -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Audio problems with SDL games when using virtual sound chanels
I'm having trouble using applications which use sound trough SDL, especifically tuxracer-0.61, foobilliard-2.3 and gl-117-0.7 crash on startup. In fact the simple loopwa ve demo which comes with SDL gives trouble: It runs but the sound is choppy. Otherwise sound works fine. If I set the number of virtual chanels to 0 the demo works fine, but the games no longer work! (tuxracer works if I disable sound, there doesn't seem to be any way of di sabling sound in the others) At one time all these games worked. Furthermore, they worked while using virtual sound chanels but using Mesa's libraries instead of nVidia's libGL.so but in my current configuration they don't. Is this a known issue? and if not, where should I start looking? % uname -smr FreeBSD 4.7-20021204-STABLE i386 % sysctl -a hw.snd hw.snd.targetirqrate: 32 hw.snd.report_soft_formats: 1 hw.snd.verbose: 1 hw.snd.maxautovchans: 4 hw.snd.pcm0.buffersize: 4096 hw.snd.pcm0.vchans: 4 % dmesg | grep pcm pcm0: VIA VT8235 port 0xd800-0xd8ff irq 5 at device 17.5 on pci0 -- __ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup Meet Singles http://corp.mail.com/lavalife To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
Hi, On Sun, 2003-01-12 at 00:43, Nikolaj Farrell wrote: snipped See below for details, I just want to point out that the computer has a clean install from cd-rom. I have not compiled the kernel and AFAIK ipfw is not set default in the GENERIC kernel. And I would never intentionally activate ipfw on this computer. Anyways: # ipfw list ipfw: getsockopt(IP_FW_GET): Protocol not available Pretty much settles it, I'd say. # uname -a FreeBSD athlon.mydomain.se 4.7-RELEASE FreeBSD 4.7-RELEASE #0: Wed Oct 9 15:08:34 GMT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 # cat /etc/rc.conf defaultrouter=192.168.0.2 hostname=athlon.mydomain.se ifconfig_dc0=inet 192.168.0.1 netmask 255.255.255.0 kern_securelevel_enable=NO keymap=swedish.iso linux_enable=YES moused_enable=YES nfs_client_enable=YES nfs_reserved_port_only=YES sendmail_enable=YES sshd_enable=YES usbd_enable=YES and finally the contents of /usr/src/sys/i386/conf/GENERIC # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 snipped # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device dc # DEC/Intel 21143 and various workalikes device fxp # Intel EtherExpress PRO/100B (82557, 82558) device pcn # AMD Am79C97x PCI 10/100 NICs snipped Okay.., I see that there's no firewall support in the kernel. Well., at the end I'd ask for you to try reloading the nic (ifconfig dc0 down / ifconfig dc0 up) to see if that makes any difference - maybe booting to other OS leaves the nic is some sort of state.., but that's grasping at straws.., but I seem to recall hearing at least one instance of this.., somewhere.., Regards, Stacey To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
Okay.., I see that there's no firewall support in the kernel. Well., at the end I'd ask for you to try reloading the nic (ifconfig dc0 down / ifconfig dc0 up) to see if that makes any difference - maybe booting to other OS leaves the nic is some sort of state.., but that's grasping at straws.., but I seem to recall hearing at least one instance of this.., somewhere.., Regards, Stacey In your opinion, could it be worth buying a new network card? regards /Nikolaj To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
Hi, On Sun, 2003-01-12 at 00:58, Nikolaj Farrell wrote: Okay.., I see that there's no firewall support in the kernel. Well., at the end I'd ask for you to try reloading the nic (ifconfig dc0 down / ifconfig dc0 up) to see if that makes any difference - maybe booting to other OS leaves the nic is some sort of state.., but that's grasping at straws.., but I seem to recall hearing at least one instance of this.., somewhere.., Regards, Stacey In your opinion, could it be worth buying a new network card? I'd be weary of getting a new nic without having ruled everything else out at the moment. There is a simple thing you can try, which is to swap nics with another box, and see if you get anything different. If the box is okay with another nic, then you trash the current one. However, if switching nics changes nothing, then we're back to square one :-( Do the other boxes have other brands of nics in them? Regards, Stacey regards /Nikolaj To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
how do i setup my FreeBSD box to act like an RARP server?
unfortunately, there is no FreeBSD port for the Sparc32 machines, so I'm stuck with using NetBSD. since, i've been having problems with booting from CD, i am going to try to install the OS by using TFTP. in order for my to do this though, i need to be able to have my FreeBSD box act as an RARP server. can anyone tell me how to do this? __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Netatalk - Mac OS X connection problem
Do you have a custom volume icon on this server? If so, try deleting it, then reconnection. Nope. Nothing fancy. Just a straight install of Netatalk and I didn't change any of the icons. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re[2]: Drgenius with gnome2
Dear/Beste P., Thursday, January 9, 2003, 11:10:12 PM, you wrote: On 9 Jan 2003, Joe Marcus Clarke wrote: FreeBSD doesn't have or need crypt.h. You can remove it from the source file. This should be something that's checked by configure. Indeed, I uncommented # include crypt.h and now it seems to install and run. # That isn't a comment sign in C. But /* comment */ and (depending on you compiler) // comment newline is . -- Best regards/Met vriendelijke groet, Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems w NIC
I did have a similar problem with 5.0rc2 and my 3cSOHO 100BaseTX NIC, but I had it coming up in hw-loopback state rather than any actual link state from Autodetect. My solution was to replace the NIC with a 10baseT NE2000-PCI cheapo, since the box in question was simply a firewall/router for 3Mbit DSL. --Adam - Original Message - From: Nikolaj Farrell [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: FreeBSD Questions [EMAIL PROTECTED] Sent: Saturday, January 11, 2003 7:58 PM Subject: Re: Problems w NIC Okay.., I see that there's no firewall support in the kernel. Well., at the end I'd ask for you to try reloading the nic (ifconfig dc0 down / ifconfig dc0 up) to see if that makes any difference - maybe booting to other OS leaves the nic is some sort of state.., but that's grasping at straws.., but I seem to recall hearing at least one instance of this.., somewhere.., Regards, Stacey In your opinion, could it be worth buying a new network card? regards /Nikolaj To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Netatalk - Mac OS X connection problem
On Sat, 2003-01-11 at 20:40, Jim Arnold wrote: Do you have a custom volume icon on this server? If so, try deleting it, then reconnection. Nope. Nothing fancy. Just a straight install of Netatalk and I didn't change any of the icons. When exactly do you see the message? Right after you login? Can you send your AppleVolumes.default as well as your afpd.conf files? Does the user you're logging in as have a valid shell? Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: Netatalk - Mac OS X connection problem
When exactly do you see the message? Right after you login? As soon as I hit the connect button after typing in the IP address of the FreeBSD box or using the afp address. Can you send your AppleVolumes.default This just has the ~ (tilde) at the end so the home directory will get mounted as well as your afpd.conf files? Everything in this file is commented out. In the file this is noted: The simplest case is to not have an afpd.conf I've always run Netatalk without anything in this file without any problems. Does the user you're logging in as have a valid shell? Yes. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: how do i setup my FreeBSD box to act like an RARP server?
On Sat, 11 Jan 2003, at 17:28 [=GMT-0800], Bsd Neophyte wrote: in order for my to do this though, i need to be able to have my FreeBSD box act as an RARP server. can anyone tell me how to do this? man rarpd tells it all, but is a bit short to get it started (and to see if the machine you want to install can talk to the rarp server), make on the server a file /etc/ethers looking like this: 08:00:2B:27:7D:16 vax where the numbers are the MAC address of the network card (you should get that from it, or from its bios) of the client, and vax is the hostname for the machine. Then put in /etc/hosts (on the server) vax 10.0.0.123 where 10.0.0.123 is the IP address the client is to have This should let your client get the IP address from the rarp server. If you want rarpd to start always at boot, add to /etc/rc.conf rarpd_enable=YES # Run rarpd (or NO). rarpd_flags=-as # Flags to rarpd. Or start it manually (as root) rarpd -as Next stage is to do tftpboot, which depends on your architecture, the Vax I ran NetBSD on, did this through mopd. But that is something from DEC. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
load over 14 from make -j4
Hmm, this is odd. I noticed the load go through the roof on the laptop sitting next to me; not surprising during buildworld. But then I looked closer, starred, and called up top. The load was reported at 14.97. X is running, a portupgrade -arF was running, and there's an idle lyx. How in the rold did that many processes get launched from -j4? It's still there, above 12 or so for the right-hand 40% or so of my xload window. hawk -- Richard E. Hawkins, Asst. Prof. of Economics/\ ASCII ribbon campaign [EMAIL PROTECTED] Smeal 178 (814) 375-4700 \ / against HTML mail These opinions will not be those of Xand postings. Penn State until it pays my retainer. / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Netatalk - Mac OS X connection problem
On Sat, 2003-01-11 at 21:56, Jim Arnold wrote: When exactly do you see the message? Right after you login? As soon as I hit the connect button after typing in the IP address of the FreeBSD box or using the afp address. Can you send your AppleVolumes.default This just has the ~ (tilde) at the end so the home directory will get mounted as well as your afpd.conf files? Everything in this file is commented out. In the file this is noted: The simplest case is to not have an afpd.conf I've always run Netatalk without anything in this file without any problems. Does the user you're logging in as have a valid shell? Yes. This is baffling. I have a OS X 10.2.3 machine that can connect just fine (as do you). The sniffer traces are more or less identical. Since it looks like the OS X client is initiating the disconnect, can you bring up the OS X console under Applications-Utilities-Console, and see if any messages show up there? Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re[2]: Drgenius with gnome2
On Sun, 12 Jan 2003, Alex wrote: Dear/Beste P., Thursday, January 9, 2003, 11:10:12 PM, you wrote: On 9 Jan 2003, Joe Marcus Clarke wrote: Indeed, I uncommented # include crypt.h and now it seems to install and run. # That isn't a comment sign in C. But /* comment */ and (depending on you compiler) // comment newline is . Please excuse my lousy English: One has to say comment out not uncomment - hasn't one? Of course I did /* # include crypt.h */ Regards, Uli. -- Best regards/Met vriendelijke groet, Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message *---* *Peter Ulrich Kruppa* * - Wuppertal - * * Germany * *---* To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Netatalk - Mac OS X connection problem
This is baffling. I have a OS X 10.2.3 machine that can connect just fine (as do you). The sniffer traces are more or less identical. Since it looks like the OS X client is initiating the disconnect, can you bring up the OS X console under Applications-Utilities-Console, and see if any messages show up there? No messages are appearing under the console when I try to mount the volume in question. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Credit Card Fraud
Would you like to know more about credit card fraud on the internet and how to stop it? Simply reply to this email with Credit Card Fraud in the subject line for more infromation. Thank you for your time To be removed from our database simply reply to this email with the word Remove in the subject line. Thank you for your time To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Small Hdd
I have a 486 that I would like to run as a file server. I have installed fbsd but the harddirve is only 800 mb. I really would rather not change it. Not much will be stored on there but none the less would like to have it. Is there a way to use the current hdd would like to have ssh and samba running and the most space I can get for files..any Ideas Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Small Hdd
do the minimal install, thatll give u the bare minimum system usage, even after you do a Samba port, as long as you dont install X you'll have a lot of space left. If you really want to get every drop of disk u can, perhaps when doing fdisk do just a swap partition and a / partition. Bri - Original Message - From: Shawn Henderson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Saturday, January 11, 2003 10:40 PM Subject: Small Hdd I have a 486 that I would like to run as a file server. I have installed fbsd but the harddirve is only 800 mb. I really would rather not change it. Not much will be stored on there but none the less would like to have it. Is there a way to use the current hdd would like to have ssh and samba running and the most space I can get for files..any Ideas Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
