This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ipv6-wg@ripe.net/

[ipv6-wg] Re: not announcing IXP IPv6 peering lan prefixes in global BGP table possibly breaks PMTUD

Previous message (by thread): [ipv6-wg] not announcing IXP IPv6 peering lan prefixes in global BGP table possibly breaks PMTUD
Next message (by thread): [ipv6-wg] Re: not announcing IXP IPv6 peering lan prefixes in global BGP table possibly breaks PMTUD

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Christian Seitz chris at in-berlin.de
Tue Jul 26 09:05:25 CEST 2011

Hello Florian,

On Mon, 25 Jul 2011, Florian Weimer wrote:

> * Christian Seitz:
>
>> 5) ?
>
> Send those ICMP messages from a globally reachable IP address.  The 
> source address doesn't matter, after all.

so Level3 should fix the problem in this case? I notified them about the 
problem last week, but since today nothing happened. I still see

>From 2001:7f8:4::d1c:1 icmp_seq=1 Packet too big: mtu=1450

when sending big packets. free.fr still has many IPv6 customers online and 
I hope that more and more access providers will enable IPv6. These issues 
have to be fixed in the own network first. Waiting for the big carriers to 
do anything can take some time... :-/

Regards,

Chris

Previous message (by thread): [ipv6-wg] not announcing IXP IPv6 peering lan prefixes in global BGP table possibly breaks PMTUD
Next message (by thread): [ipv6-wg] Re: not announcing IXP IPv6 peering lan prefixes in global BGP table possibly breaks PMTUD

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ ipv6-wg Archives ]