From: filipe abrantes <filipe_abrantes@netcabo.pt>
To: lartc@vger.kernel.org
Subject: [LARTC] IPv6 routing question - corrected
Date: Mon, 20 Sep 2004 01:57:17 +0000 [thread overview]
Message-ID: <414E38FD.3080003@netcabo.pt> (raw)
* sorry for the other schema, it came out a mess. I hope this one is
understandable.
hi:
I have this 2 boxes set up like this:
2020::2/128
2020::254/128 3030::254/128
192.168.0.2/24 192.168.0.254/24
192.168.30.254/24
+-------+ eth0 eth3
+-------+
| |============ | | eth1
| A
| | B | ----
|
| | |
+-------+ +-------+
A
# ip r l
192.168.30.254 dev eth0 scope link
192.168.0.0/24 dev eth0 scope link
169.254.0.0/16 dev lo scope link
127.0.0.0/8 dev lo scope link
# ip -6 r l
2020::254 dev eth0 metric 1024 mtu 1500 advmss 1440
3030::254 dev eth0 metric 1024 mtu 1500 advmss 1440
(...plus link local and multicast routes)
B
# ip r l
127.0.0.1 dev lo scope link
192.168.0.0/24 dev eth3 proto kernel scope link src 192.168.0.254
192.168.30.0/24 dev eth1 proto kernel scope link src 192.168.30.254
# ip -6 r l
2020::2 dev eth3 metric 1024 mtu 1500 advmss 1440 metric10 64
(...plus link local and multicast routes)
# cat /proc/sys/net/ipv4/ip_forward
1
#cat /proc/sys/net/ipv6/conf/all/forwarding
1
The problem is that i can ping 192.168.30.254 from A, but i can't ping
3030::254 from A, anyone has a clue why this happens? Is there any
feature i need to turn on or anything misconfigured? Why does it work
for IPv4 but not for IPv6?
A -> B
# ping 192.168.30.254
PING 192.168.30.254 (192.168.30.254) 56(84) bytes of data.
64 bytes from 192.168.30.254: icmp_seq=0 ttld time=0.175 ms
64 bytes from 192.168.30.254: icmp_seq=1 ttld time=0.122 ms
#ping6 3030::254
PING 3030::254(3030::254) 56 data bytes
From ::1 icmp_seq=0 Destination unreachable: Address unreachable
From ::1 icmp_seq=1 Destination unreachable: Address unreachable
Regards
Filipe Abrantes
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2004-09-20 1:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 1:57 filipe abrantes [this message]
2004-09-20 2:08 ` [LARTC] IPv6 routing question - corrected - again filipe abrantes
2004-09-20 2:11 ` [LARTC] IPv6 routing question - corrected Alexander Samad
2004-09-20 2:40 ` filipe abrantes
2004-09-20 3:00 ` Alexander Samad
2004-09-20 10:54 ` filipe abrantes
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=414E38FD.3080003@netcabo.pt \
--to=filipe_abrantes@netcabo.pt \
--cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.