From: Ferenc Wagner <wferi@niif.hu>
To: netdev@vger.kernel.org
Subject: ipv6 debugging
Date: Mon, 18 Feb 2008 15:06:19 +0100 [thread overview]
Message-ID: <87zltyjr50.fsf@tac.ki.iif.hu> (raw)
Hi,
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.
--
Thanks for your thoughts,
Feri.
next reply other threads:[~2008-02-18 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 14:06 Ferenc Wagner [this message]
2008-02-18 15:02 ` ipv6 debugging Jorge Boncompte [DTI2]
2008-02-18 21:46 ` Ferenc Wagner
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=87zltyjr50.fsf@tac.ki.iif.hu \
--to=wferi@niif.hu \
--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