Date: Sun, 12 Jan 2003 00:59:14 +0100 From: "Nikolaj Farrell" <nikk@home.se> To: <stacey@vickiandstacey.com> Cc: <freebsd-questions@freebsd.org> Subject: Re: Problems w NIC Message-ID: <00c301c2b9cd$71a44360$0100a8c0@athlon> References: <001701c2b987$9fdf72e0$0100a8c0@athlon> <1042300066.51041.227.camel@localhost> <002a01c2b989$f2099e90$1200a8c0@gsicomp.on.ca> <000b01c2b98a$df9981c0$0100a8c0@athlon> <1042301568.51041.233.camel@localhost> <001201c2b98e$063311e0$0100a8c0@athlon> <1042303096.51041.237.camel@localhost> <000301c2b993$55e70610$0100a8c0@athlon> <20030111171152.GH25529@sub21-156.member.dsl-only.net> <001b01c2b995$0dbf6d30$0100a8c0@athlon> <1042305860.51041.240.camel@localhost> <001801c2b999$95567000$0100a8c0@athlon> <1042310110.51041.250.camel@localhost> <002b01c2b9c3$56722e40$0100a8c0@athlon> <1042325630.51041.257.camel@localhost> <003701c2b9c4$db6e6950$0100a8c0@athlon> <1042328202.51041.268.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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 majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00c301c2b9cd$71a44360$0100a8c0>