|
||||||||
There's an issue I've seen with freebsd and icmp pings. FreeBSD (well 4.9 at least) doesn't do a very good job NATting multiple hosts pinging the same address. It may be that this same issue arises when the machine doing the natting pings a host that a machine behind it is also pinging. See here for more details on what I've seen: http://m0n0.ch/wall/list/?action=show_msg&actionargs[]=73&actionargs[]=12 -bmd On Tue, 2004-08-17 at 14:27, Joe Lagreca wrote: > I am continuously pinging an IP address about 3 hops away from me from > my internally NAT'ed PC. When I try to ping that same address from > the m0n0wall ping page, it returns nothing. That is, until I stop > pinging from my internal machine. Then when I ping from m0n0 it goes > just fine. Is this normal behavior (some weird NAT characteristic)? > > By the way, my stupid mistake from earlier didn't fully clear up all > of the problems I have been having. I'm still trying to determine if > it is a local configuration problem or an ISP problem. My ping times > are all over the place for hosts only 3 hops away (still on my ISP's > private network)! > > They claim everything looks good from their end, but then every other > day they find a problem, fix it, and ask if I'm doing ok now. I am > starting to think it may be a config problem on their network > somewhere. They just switched backbone providers, and the problem may > have occured near that time (I'm not possitive on the timing). > > Thanks for your help! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch > For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch > |