Rick Thomas a écrit :
>
> My point is that by setting your MTU to 1280, you have done *your*
> part.
By doing that you have just used a side effect of the MTU as a
workaround to hide the problem originating at the other end, for TCP
connections only. Nothing has been fixed.
> At least you can
Rick Thomas writes:
On Jun 5, 2011, at 9:46 AM, Pascal Hambourg wrote:
Rick Thomas a écrit :
On Jun 3, 2011, at 10:46 AM, Jeffrey B. Green wrote:
The RFCs say that any conforming implementation MUST handle an MTU of
1280, and may not necessarily handle anything larger.
What is your point in me
On Jun 5, 2011, at 9:46 AM, Pascal Hambourg wrote:
Rick Thomas a écrit :
On Jun 3, 2011, at 10:46 AM, Jeffrey B. Green wrote:
The RFCs say that any conforming implementation MUST handle an MTU of
1280, and may not necessarily handle anything larger.
What is your point in mentionning this re
Rick Thomas a écrit :
> On Jun 3, 2011, at 10:46 AM, Jeffrey B. Green wrote:
>
> The RFCs say that any conforming implementation MUST handle an MTU of
> 1280, and may not necessarily handle anything larger.
Wha is your point in mentionning this requirement ? Do you mean that the
server should n
On Jun 3, 2011, at 10:46 AM, Jeffrey B. Green wrote:
On Fri, 03 Jun 2011 09:42:49 +0200
Pascal Hambourg wrote:
It could be an MTU/MSS issue. See the recent discussion in the
debian-ipv6 list with subject "schein.debian.org" [2001:4f8:8:36::6].
Many thanks. Changing the MTU to 1480 as sug
On Fri, 03 Jun 2011 09:42:49 +0200
Pascal Hambourg wrote:
> Hello,
>
> Jeffrey B. Green a écrit :
> >
> > I'm seeing if there is an alternate answer here before filing a
> > bug. (I believe) All of the servers here that have IPv6 configured
> > hang while attempting an update on security.debian
Hello,
Jeffrey B. Green a écrit :
>
> I'm seeing if there is an alternate answer here before filing a bug. (I
> believe) All of the servers here that have IPv6 configured hang while
> attempting an update on security.debian.org. If I turn off IPv6 by
> deconfiguring the IPv6 address, then the upd
On Wed, 1 Jun 2011 10:00:17 -0400
"Jeffrey B. Green" wrote:
>
> Doing the update from the firewall works, a conversation of 29 packets
> in the captured pcap file. There are still 404s but none of the out of
> sequence/lost sequence messages. Hmmm, now to see which of the packets
> are being dro
On Wed, 1 Jun 2011 10:00:17 -0400
"Jeffrey B. Green" wrote:
>
> Doing the update from the firewall works, a conversation of 29 packets
> in the captured pcap file. There are still 404s but none of the out of
> sequence/lost sequence messages. Hmmm, now to see which of the packets
> are being dro
On Wed, 01 Jun 2011 09:18:17 -0400
"Jeffrey B. Green" wrote:
> Chris Brennan writes:
> >
> > The 404's you were getting, I got them as well on my Debian 6 VPS.
> > No firewall in place on he VPS
> > (yet, as I am still setting it up) but every time I run an update,
> > I see the 404's against s
Chris Brennan writes:
On Tue, May 31, 2011 at 1:20 PM, Andrei Popescu
wrote:
On Ma, 31 mai 11, 09:50:48, Jeffrey B. Green wrote:
So, if anyone knows what going on here or whether this looks like
an official bug, then let me know.
This sounds like you might want to contact debian-admin
On Tue, May 31, 2011 at 1:20 PM, Andrei Popescu
wrote:
On Ma, 31 mai 11, 09:50:48, Jeffrey B. Green wrote:
> >
> > So, if anyone knows what going on here or whether this looks like
> > an official bug, then let me know.
>
> This sounds like you might want to contact debian-admin ;)
>
The 404
On Ma, 31 mai 11, 09:50:48, Jeffrey B. Green wrote:
>
> So, if anyone knows what going on here or whether this looks like
> an official bug, then let me know.
This sounds like you might want to contact debian-admin ;)
Regards,
Andrei
--
Offtopic discussions among Debian users and developers
On Tue, 31 May 2011 11:15:13 -0400
"Jeffrey B. Green" wrote:
> On Tue, 31 May 2011 09:50:48 -0400
> "Jeffrey B. Green" wrote:
> >
> > When I check with tcpdump to be sure the firewall isn't the
> > culprit, I find that all of the packets that reach the firewall
> > also make it to the server an
David Erwin writes:
On Tue, May 31, 2011 at 03:50:48PM CEST, "Jeffrey B. Green"
said:
Hi,
I'm seeing if there is an alternate answer here before filing a bug. (I
believe) All of the servers here that have IPv6 configured hang while
attempting an update on security.debian.org. If I turn off IP
On Tue, 31 May 2011 09:50:48 -0400, Jeffrey B. Green wrote:
> I'm seeing if there is an alternate answer here before filing a bug. (I
> believe) All of the servers here that have IPv6 configured hang while
> attempting an update on security.debian.org. If I turn off IPv6 by
> deconfiguring the IPv
On Tue, 31 May 2011 09:50:48 -0400
"Jeffrey B. Green" wrote:
>
> When I check with tcpdump to be sure the firewall isn't the culprit, I
> find that all of the packets that reach the firewall also make it to
> the server and a conversation of 20-22 packets occurs (20 on one
> server, 22 on a diffe
On Tue, May 31, 2011 at 03:50:48PM CEST, "Jeffrey B. Green"
said:
> Hi,
>
> I'm seeing if there is an alternate answer here before filing a bug. (I
> believe) All of the servers here that have IPv6 configured hang while
> attempting an update on security.debian.org. If I turn off IPv6 by
> decon
Hi,
I'm seeing if there is an alternate answer here before filing a bug. (I
believe) All of the servers here that have IPv6 configured hang while
attempting an update on security.debian.org. If I turn off IPv6 by
deconfiguring the IPv6 address, then the update goes through fine.
When I check with
I have some additional information to add to my previously reported problem which is
that "apt-get install whatever" often hangs. I have now experienced this problem on
three different computers and it makes upgrading packages nearly impossible so I
must find a solution.
I believe the problem is
20 matches
Mail list logo
