Re: Firefox keeps beeping at me ...

2007-01-24 Thread Nikolaj Farrell
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

Re: Problems w NIC

2003-01-28 Thread Nikolaj Farrell
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

Problems w NIC

2003-01-11 Thread Nikolaj Farrell
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.

Re: Problems w NIC

2003-01-11 Thread Nikolaj Farrell
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

Re: Problems w NIC

2003-01-11 Thread Nikolaj Farrell
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

Re: Problems w NIC

2003-01-11 Thread Nikolaj Farrell
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

Re: Problems w NIC

2003-01-11 Thread Nikolaj Farrell
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

Re: Problems w NIC

2003-01-11 Thread Nikolaj Farrell
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

Re: Problems w NIC

2003-01-11 Thread Nikolaj Farrell
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

Re: Problems w NIC

2003-01-11 Thread Nikolaj Farrell
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

Re: Re[2]: Problems w NIC

2003-01-11 Thread Nikolaj Farrell
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

Re: Problems w NIC

2003-01-11 Thread Nikolaj Farrell
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

Re: Problems w NIC

2003-01-11 Thread Nikolaj Farrell
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

Re: Problems w NIC

2003-01-11 Thread Nikolaj Farrell
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

Re: Problems w NIC

2003-01-11 Thread Nikolaj Farrell
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