From: Ferenc Wagner <wferi@niif.hu>
To: "Jorge Boncompte [DTI2]" <jorge@dti2.net>
Cc: <netdev@vger.kernel.org>
Subject: Re: ipv6 debugging
Date: Mon, 18 Feb 2008 22:46:50 +0100 [thread overview]
Message-ID: <87mypygcol.fsf@szonett.ki.iif.hu> (raw)
In-Reply-To: <3740A925537C481CAA40DE393FA0D00E@intranet.dti2.net> (Jorge Boncompte's message of "Mon, 18 Feb 2008 16:02:05 +0100")
"Jorge Boncompte [DTI2]" <jorge@dti2.net> writes:
> Ferenc Wagner <wferi@niif.hu> writes:
>
>> I'm kindly asking for some debugging tips with the following problem:
>> a machine is running Linux 2.6.24.2, several 802.1q VLAN-s over
>> active/backup bonding over two physical interfaces. Everything is
>> allright, except for after a reboot, there's no IPv6, while IPv4
>> works. The router's ARP(6) table is empty, the machine doesn't answer
>> ping6. However, if I start tcpdump -i bond0 ip6, everything is
>> allright again. There are some indications that after some period
>> without IPv6 traffic, the same can happen again. Are there known
>> issues which can exhibit themselves like this? Other very similar
>> setups don't show this erratic behaviour.
>>
>> I know that the above doesn't give a fully detailed picture, but
>> thought that I'd better ask before taking the setup into pieces.
>
> This sounds to me like the same problem that I was having with
> OSPF, I think ARP(6) uses multicast ethernet address too. Can you try
> if the patch below, that I sent Patrick McHardy some days ago, fixes
> your problem?
Hi Jorge,
Thank you very much! Your patch indeed fixes my problem. I hope the
fix will make it into a stable release soon!
--
Regards,
Feri.
prev parent reply other threads:[~2008-02-18 21:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 14:06 ipv6 debugging Ferenc Wagner
2008-02-18 15:02 ` Jorge Boncompte [DTI2]
2008-02-18 21:46 ` Ferenc Wagner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mypygcol.fsf@szonett.ki.iif.hu \
--to=wferi@niif.hu \
--cc=jorge@dti2.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox