Urgent 4.9 networking problems

[JJB]

Your symptoms are typical of DNS time outs.
Ping ip address does no DNS lookups.
Ping freebsd.org will not work either.

With out a lot more detail about your network environment, the best
I can say is look at how your network resolves DNS lookups.

Some times a ISP will change the ip address of their DNS or DHCP
servers and if you have their ip address hard coded in your firewall
rules your network will just stop talking to the public internet.
Start your research there.




-----Original Message-----
From: owner-freebsd-questions at freebsd.org
[mailto:owner-freebsd-questions at freebsd.org]On Behalf Of Dave Raven
Sent: Thursday, June 24, 2004 4:54 PM
To: freebsd-questions at freebsd.org
Subject: Urgent 4.9 networking problems

Hi all,
        I really need some urgent help with this I'm completely
confused. I
have a FreeBSD 4.9 machine running ipfilter ipnat vrrp and a few
other
services, today is the first time I tried to access through the
specific
method but now every interface and every local address I try has the
same
problem. I can ping anything - but any other kind of traffic waits
for about
2 minutes before transmitting - this is true with tcp and udp. I'm
trying to
access machines on the same network - and if I ping -R you can see
the same
effect - pasted below. I've also included the interface that I'm
trying to
do this on although it seems to be happening on all my other
interfaces..
I try to telnet to a cisco router that's on a switch I'm plugged in
and I
see the same behaviour - it just waits then suddenly responds very
quickly.
My IpFilter rules don't log anything until it responds at which time
they
pass it - and tethereal + tcpdump also see if perfectly AFTER the
long
delay.

It appears that its sitting on the kernel for 2 minutes??? It just
does
NOTHING then all of a sudden responds. The only thing I can find
that works
is icmp - and perfectly. I'm sorry for the urgency but its very high
priority

Thanks in advance
Dave

# ifconfig fxp1
fxp1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet x.y.186.3 netmask 0xffffff00 broadcast x.y.186.255
        inet x.y.186.1 netmask 0xffffffff broadcast x.y.186.1
        inet x.y.186.15 netmask 0xffffffff broadcast x.y.186.15
        inet x.y.186.14 netmask 0xffffffff broadcast x.y.186.14
        inet x.y.186.142 netmask 0xffffffff broadcast x.y.186.142
        inet x.y.186.33 netmask 0xffffffff broadcast x.y.186.33
        inet x.y.186.124 netmask 0xffffffff broadcast x.y.186.124
        inet x.y.186.250 netmask 0xffffffff broadcast x.y.186.250
        inet x.y.186.122 netmask 0xffffffff broadcast x.y.186.122
        inet x.y.186.25 netmask 0xffffffff broadcast x.y.186.25
        inet x.y.186.127 netmask 0xffffffff broadcast x.y.186.127

# date ; ping -R -c1 x.y.186.253 ; date
Thu Jun 24 22:43:13 SAST 2004
PING x.y.186.253 (152.110.186.253): 56 data bytes
64 bytes from x.y.186.253: icmp_seq=0 ttl=255 time=0.414 ms
RR:     x.y.186.253
        x.y.186.253
        x.y.186.3

--- x.y.186.253 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.414/0.414/0.414/0.000 ms
Thu Jun 24 22:46:58 SAST 2004

_______________________________________________
freebsd-questions at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribe at freebsd.org"