On 24/11/2011 10:07, Kees Jan Koster wrote:
> This seems to be local to my machine. Here is another reason why I
> say that: I can reliably transmit data when I bind to the aliased IP
> address: If I use mtr to measure packet loss from saffron (the stricken
> machine) to cumin (another machine in a
Dear All,
Thank you so much for the excellent suggestions. I can tell some of you have a
lot of experience troubleshooting this issue.
At this stage I ruled out hardware or network issues. These are server grade
network interfaces, new cables and the ifconfig configuration seems in order.
nets
Dear Mike,
>> I am stuck with a machine that shows serious packet loss (about 1% of all
>> traffic is dropped). I tried the obvious (new network cable, different
>> switch port, different ethernet interface on the machine), but the problems
>> remain.
>
> What is the output of
> sysctl -a dev.
On 11/22/2011 3:33 PM, Kees Jan Koster wrote:
> Dear All,
>
> I am stuck with a machine that shows serious packet loss (about 1% of all
> traffic is dropped). I tried the obvious (new network cable, different switch
> port, different ethernet interface on the machine), but the problems remain.
Cc: Michael Sierchio; Gary Gatten; freebsd-questions@freebsd.org
Subject: Re: Diagnosing packet loss
On Tue, Nov 22, 2011 at 4:11 PM, Kees Jan Koster
mailto:kjkos...@gmail.com>> wrote:
[kjkoster@saffron ~]$ ifconfig bge0
bge0: flags=8843 metric 0 mtu 1500
options=8009b
ether
Matthew suggests turning off hardware checksums - it won't hurt to
give that a try:
ifconfig bge0 media 100baseTX mediaopt -txcsum
On Tue, Nov 22, 2011 at 2:26 PM, Adam Vande More wrote:
> On Tue, Nov 22, 2011 at 4:11 PM, Kees Jan Koster wrote:
>>
>> [kjkoster@saffron ~]$ ifconfig bge0
>> bge0
On Tue, Nov 22, 2011 at 4:11 PM, Kees Jan Koster wrote:
> [kjkoster@saffron ~]$ ifconfig bge0
> bge0: flags=8843 metric 0 mtu 1500
>
> options=8009b
>ether 00:e0:81:32:ed:b4
>inet 91.196.169.165 netmask 0xfff8 broadcast 91.196.169.167
>inet 91.196.169.166 netmask 0xff
Dear Michael,
[kjkoster@saffron ~]$ ifconfig bge0
bge0: flags=8843 metric 0 mtu 1500
options=8009b
ether 00:e0:81:32:ed:b4
inet 91.196.169.165 netmask 0xfff8 broadcast 91.196.169.167
inet 91.196.169.166 netmask 0x broadcast 91.196.169.166
media:
On Tue, Nov 22, 2011 at 9:33 PM, Kees Jan Koster wrote:
> Dear All,
>
> I am stuck with a machine that shows serious packet loss (about 1% of all
> traffic is dropped). I tried the obvious (new network cable, different switch
> port, different ethernet interface on the machine), but the problems
On 22/11/2011 20:33, Kees Jan Koster wrote:
> I am stuck with a machine that shows serious packet loss (about 1% of
> all traffic is dropped). I tried the obvious (new network cable,
> different switch port, different ethernet interface on the machine),
> but the problems remain.
>
> Another machi
On Tue, Nov 22, 2011 at 1:58 PM, Kees Jan Koster wrote:
> Thank you for your reply. Your comment about dupe IP triggered something that
> I failed to mention: the interface is aliased. It has two IP addresses. IP
> address a and it has an alias IP address b. I just tested binding mtr to each
>
Dear Gary,
Thank you for your reply. Your comment about dupe IP triggered something that I
failed to mention: the interface is aliased. It has two IP addresses. IP
address a and it has an alias IP address b. I just tested binding mtr to each
of these interfaces separately to measure packet loss
Well, 1% is not good but I've seen worse for sure! Sounds like you tried the
obvious. I would recommend a different IP to rule out a dupe ip; else it must
be NIC related - either hardware or driver. Also, perhaps swap cables and
ports with a working machine and see if the problem follows or s
13 matches
Mail list logo
