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.
----- 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
> 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
> Everything else in the network, except for fawlty machine 192.168.0.1,
> problem-free and have done so in over two years. the computer 192.168.0.1
> brand new and is set up on the same physical location and the same
> 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?).
> 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