On Wed, 24 Dec 2008 13:49:53 -0900
Ken Irving fn...@uaf.edu wrote:
On Wed, Dec 24, 2008 at 02:16:26PM -0800, ow...@netptc.net wrote:
From: fn...@uaf.edu
On Wed, Dec 24, 2008 at 10:25:07PM +0200, Micha Feigin wrote:
Ken Irving fn...@uaf.edu wrote:
...
A too-big MTU setting can
On Sat, 27 Dec 2008 16:16:00 +0200
Micha Feigin mi...@post.tau.ac.il wrote:
On Wed, 24 Dec 2008 13:49:53 -0900
Ken Irving fn...@uaf.edu wrote:
On Wed, Dec 24, 2008 at 02:16:26PM -0800, ow...@netptc.net wrote:
From: fn...@uaf.edu
On Wed, Dec 24, 2008 at 10:25:07PM +0200, Micha Feigin
On Sat, 27 Dec 2008, Micha Feigin wrote:
On Wed, 24 Dec 2008 13:49:53 -0900
Ken Irving fn...@uaf.edu wrote:
What can make the mtu drop on a running system?
The DHCP server (if you are using dhcp).
# Update on 12/13/2007
# -M Prevents dhcpcd from setting the MTU provided by the
On Sun, 21 Dec 2008 22:10:46 +
Bob Cox debian-u...@lists.bobcox.com wrote:
On Sun, Dec 21, 2008 at 23:51:02 +0200, Micha Feigin (mi...@post.tau.ac.il)
wrote:
[...]
I have no idea on how to read this. It seems that regular traceroute fails
(-n) tcp traceroute works (-n -T) and
On 12/24/08 10:28, Micha Feigin wrote:
[snip]
vivalunalitshi:tuxonice-head# traceroute -I www.yahoo.com
traceroute to www.yahoo.com (87.248.113.14), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 f1.us.www.vip.ird.yahoo.com
On Wed, Dec 24, 2008 at 06:28:01PM +0200, Micha Feigin wrote:
On Sun, 21 Dec 2008 22:10:46 +
Bob Cox debian-u...@lists.bobcox.com wrote:
Just a thought... what does traceroute -I www.yahoo.com (as root) give
you?
It seems that this works, ping works telnet www.yahoo.com 80 mostly
On Wed, 24 Dec 2008 10:38:23 -0900
Ken Irving fn...@uaf.edu wrote:
On Wed, Dec 24, 2008 at 06:28:01PM +0200, Micha Feigin wrote:
On Sun, 21 Dec 2008 22:10:46 +
Bob Cox debian-u...@lists.bobcox.com wrote:
Just a thought... what does traceroute -I www.yahoo.com (as root) give
you?
On Wed, Dec 24, 2008 at 10:25:07PM +0200, Micha Feigin wrote:
On Wed, 24 Dec 2008 10:38:23 -0900
Ken Irving fn...@uaf.edu wrote:
On Wed, Dec 24, 2008 at 06:28:01PM +0200, Micha Feigin wrote:
On Sun, 21 Dec 2008 22:10:46 +
Bob Cox debian-u...@lists.bobcox.com wrote:
Just a
Original Message
From: fn...@uaf.edu
To: debian-user@lists.debian.org
Subject: Re: tcpip stops working after some time
Date: Wed, 24 Dec 2008 11:44:45 -0900
On Wed, Dec 24, 2008 at 10:25:07PM +0200, Micha Feigin wrote:
On Wed, 24 Dec 2008 10:38:23 -0900
Ken Irving fn...@uaf.edu
On Wed, Dec 24, 2008 at 02:16:26PM -0800, ow...@netptc.net wrote:
From: fn...@uaf.edu
On Wed, Dec 24, 2008 at 10:25:07PM +0200, Micha Feigin wrote:
Ken Irving fn...@uaf.edu wrote:
...
A too-big MTU setting can give odd results in some cases.
but how would it change on a running
On Wednesday 2008 December 24 16:16:26 ow...@netptc.net wrote:
AFAIK the MTU is set by the initiator of the IP connection and any
intermediate router can't change it.
Larry
Not exactly. The MTU is really a link-level property that's immutable.
However, path MTU discovery is not required for
On Sun, Dec 21, 2008 at 23:51:02 +0200, Micha Feigin (mi...@post.tau.ac.il)
wrote:
[...]
I have no idea on how to read this. It seems that regular traceroute fails
(-n)
tcp traceroute works (-n -T) and telnet www.yahoo.com 80 fails (same with
google and a few others I testes)
Any
On Fri, 19 Dec 2008 12:37:44 -0800 (PST)
Jeff D fixedo...@gmail.com wrote:
On Fri, 19 Dec 2008, Micha Feigin wrote:
On Sat, 13 Dec 2008 01:07:12 +0200
subscriptions subscripti...@rdegraaf.nl wrote:
On Fri, 2008-12-12 at 22:10 +0100, Micha Feigin wrote:
For some reason after a
On Sat, 13 Dec 2008 01:07:12 +0200
subscriptions subscripti...@rdegraaf.nl wrote:
On Fri, 2008-12-12 at 22:10 +0100, Micha Feigin wrote:
For some reason after a few days of uptime , tcp stops working on my
machine.
Ping and dns lookups work, tcp doesn't. I tried both wired and
On Fri, 19 Dec 2008, Micha Feigin wrote:
On Sat, 13 Dec 2008 01:07:12 +0200
subscriptions subscripti...@rdegraaf.nl wrote:
On Fri, 2008-12-12 at 22:10 +0100, Micha Feigin wrote:
For some reason after a few days of uptime , tcp stops working on my
machine.
Ping and dns lookups
For some reason after a few days of uptime , tcp stops working on my machine.
Ping and dns lookups work, tcp doesn't. I tried both wired and wireless,
removing the firewall and unloading all firewall related modules but nothing
seems to change.
Only restarting seems to help
Any ideas what else
On 12/12/08 15:10, Micha Feigin wrote:
For some reason after a few days of uptime , tcp stops working on my machine.
Ping and dns lookups work, tcp doesn't. I tried both wired and wireless,
removing the firewall and unloading all firewall related modules but nothing
seems to change.
Only
On Fri, 2008-12-12 at 22:10 +0100, Micha Feigin wrote:
For some reason after a few days of uptime , tcp stops working on my
machine.
Ping and dns lookups work, tcp doesn't. I tried both wired and
wireless,
removing the firewall and unloading all firewall related modules but
nothing
seems
18 matches
Mail list logo
