netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Riccardo Losselli <riccardo@e4a.it>
To: netdev@vger.kernel.org
Subject: Problem on ipv6 side of the lan.
Date: Tue, 30 Sep 2008 17:26:46 +0200	[thread overview]
Message-ID: <48E24536.5040508@e4a.it> (raw)

Hi all, i would like to request a hint to sort out a problem is driving 
me crazy since the last two days..
i'm running a small network of 8 linux boxes, each one of them acting as 
a router.
I used a /64 as peering lan, configured the network interfaces, set up 
the peerings and all went smooth for about one week.
Two days ago one of the machines rebooted, and since then i have a very 
strange behaviour of the network.
Network is made of box1,2,3,4,5,6,7 and box200, which is a xen machine 
hosted by box5, box4 really is a Mikrotik box...

"Box1" and "Box200" can reach all other boxes as expected.
"Box2" can reach all boxes except 4,5 and 6
"box3" can reach all boxes except 4,5 and 6
"box4" can reach box1 and 200 only
"box5" can reach box1 and 200 only
"box6" can reach box 1 and 200 only
"box7" can reach all boxes except 4,5 and 6

i tried to check with tcpdump, pinging box7 from box6.. what i get is, 
from box6
14:13:57.662327 IP6 xxxx:xxxx::6 > xxxx:xxxx::7: ICMP6, echo request, 
seq 234, length 64
as expected, but  no reply..

ip neighbor shows

xxxx:xxxx::7 dev eth0 lladdr 00:0e:0c:b8:70:a4 router REACHABLE

On box7 tcpdump i see no requests coming..

If i try to ping from box7 to box6 i get, on box7

16:21:14.891742 IP6 xxxx:xxxx::7 > xxxx:xxxx::6: ICMP6, echo request, 
seq 47, length 64

and on box6

14:19:51.765354 IP6 xxxx:xxxx::7 > 2001:4c00::6: ICMP6, echo request, 
seq 2, length 64
14:19:51.765366 IP6 xxxx:xxxx::6 > 2001:4c00::7: ICMP6, echo reply, seq 
2, length 64

but i can see no reply on box7

ip neig , on box 7 reports no entry for box6

xxxx:xxxx::6 dev eth2 lladdr 00:30:48:98:5d:84 DELAY

network interfaces are correct.

or... i can se the echo request on both boxes (when pinging from the 
box) and no reply (but no "unreachable" either)

I'm pretty confused, as the same boxes work with ipv4 without problems 
and worked pretty fine with ipv6 too for about one week.


Any hint?
Thank you very much,
ricky

                 reply	other threads:[~2008-09-30 15:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=48E24536.5040508@e4a.it \
    --to=riccardo@e4a.it \
    --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;
as well as URLs for NNTP newsgroup(s).