On Fri, 17 Dec 2004, roland whispered secretively:
> maybe this isn`t a networking problem but a problem with the UML process
> itself ?
> Keep in mind that a UML is a program which runs in userspace - and it`s no
> realtime
> application. So, under certain circumstances the response of that appl
On Friday 17 December 2004 01:21, roland wrote:
> Antoine,
> maybe this isn`t a networking problem but a problem with the UML process
> itself ? Keep in mind that a UML is a program which runs in userspace - and
> it`s no realtime application. So, under certain circumstances the response
> of that
From: "Antoine Martin" <[EMAIL PROTECTED]>
To: "User Mode Linux User" <[EMAIL PROTECTED]>
Sent: Thursday, December 16, 2004 7:53 PM
Subject: [uml-user] re: peculiar intermittent network seizures with
uml-2.4.27-1 on 2.4.28
> > Notably, the UML ceases
Yep, I realised after I sent it,
my packets were dropped when I had something I thought was similar.
Sorry for the noise.
On Fri, 2004-12-17 at 01:01 +, Nix wrote:
> On Thu, 16 Dec 2004, Antoine Martin spake:
> > Looks to me like this is a routing problem, check your arp tables and
> > your r
On Thu, 16 Dec 2004, Antoine Martin spake:
> Looks to me like this is a routing problem, check your arp tables and
> your routes. It may be that something is occasionally causing a packet
> to come out of the wrong interface/wrong mac, which confuses the lower
> network layers.
Alas, I don't think
> Notably, the UML ceases responding to network packets for up to a minute
> and a half at a time, then restarts again just as quietly: the
> console-on-network-port freezes at the same time. The UML continues
> running and packets get queued on either side of the... blockage, and
> are allowed thr
