Date: Sat, 24 Mar 2001 14:51:54 +0200 From: Tommi Harkonen <harkonen@mail.teliafi.net> To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Cc: freebsd-net@FreeBSD.ORG Subject: Re: RTM_LOSING: Kernel Suspects Partitioning: Message-ID: <20010324145154.A27634@teliafi.net> In-Reply-To: <200103231711.MAA42834@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Fri, Mar 23, 2001 at 12:11:06PM -0500 References: <20010322124742.A9984@teliafi.net> <200103221643.LAA30673@khavrinen.lcs.mit.edu> <20010323090102.B9984@teliafi.net> <200103231711.MAA42834@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 23, 2001 at 12:11:06PM -0500, Garrett Wollman wrote:
> <<On Fri, 23 Mar 2001 09:01:02 +0200, Tommi Harkonen <harkonen@mail.teliafi.net> said:
>
> >> This is perfectly natural. TCP will generate these messages whenever
> >> its retransmission timer goes off; they should correlate with packet
> >> losses.
>
> > Is it also natural that I cannot ftp from the box to anywhere
> > (eg. ftp.cdrom.com)?
>
> One goes in hand with the other. Your TCP connections are timing out,
> which causes the RTM_LOSING messages. Clearly, your packets are not
> getting anywhere. Perhaps you should carefully check your
> configuration.
Traceroute & ping works fine from the box and everything to the box (still)
works and I have checked, double checked and triple checked all settings
and I've discussed about this in EFnet's #FreeBSDhelp (without success) and
on #FreeBSD (and got a bit more help) and every setting/configuration seems
to be correct. I've even changed the hardware once to disable the probability
of broken hw and I've even tried another OS on the box (which worked just
fine).
Here's some settings/configurations so you can see everything is like
they're supposed to be.
$ ifconfig -a
vr0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 62.236.255.202 netmask 0xfffffff8 broadcast 62.236.255.207
inet 62.236.255.203 netmask 0xffffffff broadcast 62.236.255.203
inet 62.236.255.204 netmask 0xffffffff broadcast 62.236.255.204
inet 62.236.255.205 netmask 0xffffffff broadcast 62.236.255.205
ether 00:50:ba:0a:69:6e
media: autoselect (10baseT/UTP) status: active
supported media: autoselect 100baseTX <full-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP none
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
$ netstat -rn
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 62.236.255.201 UGSc 12 106117 vr0
62.236.255.200/29 link#1 UC 0 0 vr0 =>
62.236.255.201 0:0:c:41:b9:40 UHLW 13 0 vr0 277
62.236.255.202 0:50:ba:a:69:6e UHLW 0 6 lo0
62.236.255.203 0:50:ba:a:69:6e UHLW 0 4 lo0 =>
62.236.255.203/32 link#1 UC 0 0 vr0 =>
62.236.255.204 0:50:ba:a:69:6e UHLW 0 4 lo0 =>
62.236.255.204/32 link#1 UC 0 0 vr0 =>
62.236.255.205 0:50:ba:a:69:6e UHLW 0 4 lo0 =>
62.236.255.205/32 link#1 UC 0 0 vr0 =>
127.0.0.1 127.0.0.1 UH 0 22 lo0
$ ipfstat -io
empty list for ipfilter(out)
empty list for ipfilter(in)
$ ipfw show
ipfw: getsockopt(IP_FW_GET): Protocol not available
No errors nor complaints in dmesg and so on. Please ask if you need more
information.
--
th
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010324145154.A27634>