* [LARTC] IPv6 routing question - corrected
@ 2004-09-20 1:57 filipe abrantes
2004-09-20 2:08 ` [LARTC] IPv6 routing question - corrected - again filipe abrantes
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: filipe abrantes @ 2004-09-20 1:57 UTC (permalink / raw)
To: lartc
* 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/
^ permalink raw reply [flat|nested] 6+ messages in thread
* [LARTC] IPv6 routing question - corrected - again
2004-09-20 1:57 [LARTC] IPv6 routing question - corrected filipe abrantes
@ 2004-09-20 2:08 ` filipe abrantes
2004-09-20 2:11 ` [LARTC] IPv6 routing question - corrected Alexander Samad
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: filipe abrantes @ 2004-09-20 2:08 UTC (permalink / raw)
To: lartc
* sorry for the 2 previous schemas, they 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/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [LARTC] IPv6 routing question - corrected
2004-09-20 1:57 [LARTC] IPv6 routing question - corrected filipe abrantes
2004-09-20 2:08 ` [LARTC] IPv6 routing question - corrected - again filipe abrantes
@ 2004-09-20 2:11 ` Alexander Samad
2004-09-20 2:40 ` filipe abrantes
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Alexander Samad @ 2004-09-20 2:11 UTC (permalink / raw)
To: lartc
[-- Attachment #1: Type: text/plain, Size: 2820 bytes --]
what do you get when you try
ip r g 3030::254
A
On Mon, Sep 20, 2004 at 02:57:17AM +0100, filipe abrantes wrote:
> * 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 ttl=64 time=0.175 ms
> 64 bytes from 192.168.30.254: icmp_seq=1 ttl=64 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/
>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [LARTC] IPv6 routing question - corrected
2004-09-20 1:57 [LARTC] IPv6 routing question - corrected filipe abrantes
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
4 siblings, 0 replies; 6+ messages in thread
From: filipe abrantes @ 2004-09-20 2:40 UTC (permalink / raw)
To: lartc
[-- Attachment #1: Type: text/plain, Size: 2918 bytes --]
hi and thanks for replying,
#ip r g 3030::254
3030::254 via 3030::254 dev eth0 src 2020::2 metric 0
cache mtu 1500 advmss 1440
Alexander Samad wrote:
>what do you get when you try
>
>
>ip r g 3030::254
>
>A
>
>On Mon, Sep 20, 2004 at 02:57:17AM +0100, filipe abrantes wrote:
>
>
>>* 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 ttl=64 time=0.175 ms
>>64 bytes from 192.168.30.254: icmp_seq=1 ttl=64 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/
>>
>>
>
>
>
[-- Attachment #2: Type: text/html, Size: 3778 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [LARTC] IPv6 routing question - corrected
2004-09-20 1:57 [LARTC] IPv6 routing question - corrected filipe abrantes
` (2 preceding siblings ...)
2004-09-20 2:40 ` filipe abrantes
@ 2004-09-20 3:00 ` Alexander Samad
2004-09-20 10:54 ` filipe abrantes
4 siblings, 0 replies; 6+ messages in thread
From: Alexander Samad @ 2004-09-20 3:00 UTC (permalink / raw)
To: lartc
[-- Attachment #1: Type: text/plain, Size: 4352 bytes --]
Hi
Sorry having a bit of a problem reading your diagram but is the
destination on the wire or is routed via box B
have you tried a tcpdump on B to see what it sees ?
A
On Mon, Sep 20, 2004 at 03:40:39AM +0100, filipe abrantes wrote:
> hi and thanks for replying,
>
> #ip r g 3030::254
> 3030::254 via 3030::254 dev eth0 src 2020::2 metric 0
> cache mtu 1500 advmss 1440
>
>
>
> Alexander Samad wrote:
> what do you get when you try
>
>
> ip r g 3030::254
>
> A
>
> On Mon, Sep 20, 2004 at 02:57:17AM +0100, filipe abrantes wrote:
> * 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 ttl=64 time=0.175
> ms
> 64 bytes from 192.168.30.254: icmp_seq=1 ttl=64 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 / _\bL_\bA_\bR_\bT_\bC_\b@_\bm_\ba_\bi_\bl_\bm_\ba_\bn_\b._\bd_\bs_\b9_\ba_\b._\bn_\bl
> _\bh_\bt_\bt_\bp_\b:_\b/_\b/_\bm_\ba_\bi_\bl_\bm_\ba_\bn_\b._\bd_\bs_\b9_\ba_\b._\bn_\bl_\b/_\bm_\ba_\bi_\bl_\bm_\ba_\bn_\b/_\bl_\bi_\bs_\bt_\bi_\bn_\bf_\bo_\b/_\bl_\ba_\br_\bt_\bc HOWTO: _\bh_\bt_\bt_\bp_\b:_\b/
> _\b/_\bl_\ba_\br_\bt_\bc_\b._\bo_\br_\bg_\b/
>
> _______________________________________________
> LARTC mailing list / _\bL_\bA_\bR_\bT_\bC_\b@_\bm_\ba_\bi_\bl_\bm_\ba_\bn_\b._\bd_\bs_\b9_\ba_\b._\bn_\bl
> _\bh_\bt_\bt_\bp_\b:_\b/_\b/_\bm_\ba_\bi_\bl_\bm_\ba_\bn_\b._\bd_\bs_\b9_\ba_\b._\bn_\bl_\b/_\bm_\ba_\bi_\bl_\bm_\ba_\bn_\b/_\bl_\bi_\bs_\bt_\bi_\bn_\bf_\bo_\b/_\bl_\ba_\br_\bt_\bc HOWTO: _\bh_\bt_\bt_\bp_\b:_\b/
> _\b/_\bl_\ba_\br_\bt_\bc_\b._\bo_\br_\bg_\b/
>
>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [LARTC] IPv6 routing question - corrected
2004-09-20 1:57 [LARTC] IPv6 routing question - corrected filipe abrantes
` (3 preceding siblings ...)
2004-09-20 3:00 ` Alexander Samad
@ 2004-09-20 10:54 ` filipe abrantes
4 siblings, 0 replies; 6+ messages in thread
From: filipe abrantes @ 2004-09-20 10:54 UTC (permalink / raw)
To: lartc
[-- Attachment #1: Type: text/plain, Size: 4628 bytes --]
Hi,
It's like this:
A eth0 ====== eth3 B eth1
eth0:
192.168.0.2/24
2020::2/128
eth3
192.168.0.254/24
2020::254/128
eth1
192.168.30.254
3030::254/128
I'm trying to ping B's eth1 address from A, but it only works in IPv4,
in IPv6 it does not work, unless i put a route via eth3's address.
regards
Filipe
Alexander Samad wrote:
>Hi
>
>Sorry having a bit of a problem reading your diagram but is the
>destination on the wire or is routed via box B
>
>have you tried a tcpdump on B to see what it sees ?
>
>A
>
>
>On Mon, Sep 20, 2004 at 03:40:39AM +0100, filipe abrantes wrote:
>
>
>>hi and thanks for replying,
>>
>>#ip r g 3030::254
>>3030::254 via 3030::254 dev eth0 src 2020::2 metric 0
>> cache mtu 1500 advmss 1440
>>
>>
>>
>>Alexander Samad wrote:
>> what do you get when you try
>>
>>
>> ip r g 3030::254
>>
>> A
>>
>> On Mon, Sep 20, 2004 at 02:57:17AM +0100, filipe abrantes wrote:
>> * 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 ttl=64 time=0.175
>> ms
>> 64 bytes from 192.168.30.254: icmp_seq=1 ttl=64 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 / _\bL_\bA_\bR_\bT_\bC_\b@_\bm_\ba_\bi_\bl_\bm_\ba_\bn_\b._\bd_\bs_\b9_\ba_\b._\bn_\bl
>> _\bh_\bt_\bt_\bp_\b:_\b/_\b/_\bm_\ba_\bi_\bl_\bm_\ba_\bn_\b._\bd_\bs_\b9_\ba_\b._\bn_\bl_\b/_\bm_\ba_\bi_\bl_\bm_\ba_\bn_\b/_\bl_\bi_\bs_\bt_\bi_\bn_\bf_\bo_\b/_\bl_\ba_\br_\bt_\bc HOWTO: _\bh_\bt_\bt_\bp_\b:_\b/
>> _\b/_\bl_\ba_\br_\bt_\bc_\b._\bo_\br_\bg_\b/
>>
>> _______________________________________________
>> LARTC mailing list / _\bL_\bA_\bR_\bT_\bC_\b@_\bm_\ba_\bi_\bl_\bm_\ba_\bn_\b._\bd_\bs_\b9_\ba_\b._\bn_\bl
>> _\bh_\bt_\bt_\bp_\b:_\b/_\b/_\bm_\ba_\bi_\bl_\bm_\ba_\bn_\b._\bd_\bs_\b9_\ba_\b._\bn_\bl_\b/_\bm_\ba_\bi_\bl_\bm_\ba_\bn_\b/_\bl_\bi_\bs_\bt_\bi_\bn_\bf_\bo_\b/_\bl_\ba_\br_\bt_\bc HOWTO: _\bh_\bt_\bt_\bp_\b:_\b/
>> _\b/_\bl_\ba_\br_\bt_\bc_\b._\bo_\br_\bg_\b/
>>
>>
>>
>
>
>
[-- Attachment #2: Type: text/html, Size: 5082 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2004-09-20 10:54 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-09-20 1:57 [LARTC] IPv6 routing question - corrected filipe abrantes
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
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.