Re: Firefox keeps beeping at me ...
Per olof Ljungmark skrev: Glenn Becker wrote: All - I've been away from FreeBSD for some time and have been updating my installation, getting used to the ways of portupgrade, etc. Have noticed that Firefox keeps emitting what sound like console beeps - I haven't established much of a pattern for these though it always happens when I close the app. Is there a way to kill these? Apologies in advance if this is a dopey question. Obviously more an annoyance than anything. perhaps -questions is more appropriate... Anyway, that makes two of us - mine beeps too - when sending and reading mails. No idea why though, sorry. Anyone? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] The beeping can be avoided by recompiling without the debug option. (I am clueless on how to disable it if debug is on though). Sorry for the crosspost-reply. /Nikolaj ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems w NIC
I guess this thread is dead by now. Just thought I should tell all of you who have tried to help me that I bought a new NIC yesterday with a different chipset. Everything works like a charm! I am not going to bother further testing with the Cnet-card- even though it was brand new. If anyone happens to remember the thread and possibly found a solution, I will consider sticking the card in a different machine and see what happens. I am now thinking either driver problem or some setting problem(like memory adressing). I very much doubt that the card is broken, since it is brand new. (and works in windows). Anyways, thanks for all your help and avoid the Cnet pro200 with the Davicom DM9102A chipset... /Nikolaj 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: 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: 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
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
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: 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: 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
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
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: 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
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
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: 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
