On Fri, 10 May 2002, Justin Hawkins wrote:
Well thanks to Archie, I had mpd connecting me to my works 2500 quite
successfully. 'Had' being the operative word :-)
snip
In the way that only a cry for help on a large mailing list can do, I
found the problem myself.
It seems that lowering the
Anyway, now I have a legitimate question, how can I setup mpd
to change the MTU on the ng0 interface when it brings it up?
I do this via mpd's set iface up-script, using a manually chosen MTU.
I'd be nice if mpd would do this automatically, based on the MTU of the
underlying interface and
Lars Eggert writes:
Anyway, now I have a legitimate question, how can I setup mpd
to change the MTU on the ng0 interface when it brings it up?
I do this via mpd's set iface up-script, using a manually chosen MTU.
I'd be nice if mpd would do this automatically, based on the MTU of the
On Mon, 18 Feb 2002, Archie Cobbs wrote:
Unfortunately, there is no fix for this yet. However you can
try one trick, which is to set up a host route to the remote
IP address via your default gateway. I'm not sure if this will
work but it might (please report success/failure if you try it).
Justin Hawkins writes:
Unfortunately, there is no fix for this yet. However you can
try one trick, which is to set up a host route to the remote
IP address via your default gateway. I'm not sure if this will
work but it might (please report success/failure if you try it).
Very happy to
Justin,
glad this worked for you!
How did you stop the Cisco box from stupidly trying to hand its own IP
address to the clients over and over? I don't even get past negotiation,
since the Cisco won't hand out any other addresses... (It also doesn't
help that the box isn't under my direct
Lars Eggert writes:
How did you stop the Cisco box from stupidly trying to hand its own IP
address to the clients over and over? I don't even get past negotiation,
since the Cisco won't hand out any other addresses... (It also doesn't
help that the box isn't under my direct administration,
Archie,
Archie Cobbs wrote:
Newer versions of mpd will not even finish negotiation with a box
that uses the same IP address inside out... this was added as a
safety check.. to disable this behavior and allow such negotiation,
apply the patch below.
you put created that patch in repsonse to
Lars Eggert writes:
If I take out the NAK patch, I believe I'll see kernel panics again; or
were you saying that adding a host route can prevent this?
Adding a host route should prevent the kernel panic. However, there
was also a fix made to ng_ksocket(4) that eliminates the panic from
ever
Lars Eggert writes:
this doesn't look like the same bug described in the link you posted.
The other bug caused negotiation to completely fail, while it succeeds
in your case.
Looks like there's something else wring. What does your ifconfig look
like after the link is up?
I'm trying to
On Mon, 18 Feb 2002, Archie Cobbs wrote:
Yes, this is the same problem. Mpd and the kernel have both
been modified since that posting:
- mpd will disallow the 'fatal' scenario
- the 'fatal' scenario is no longer fatal, i.e., instead of the
kernel panicing, it will just return the
Justin Hawkins writes:
Yes, this is the same problem. Mpd and the kernel have both
been modified since that posting:
- mpd will disallow the 'fatal' scenario
- the 'fatal' scenario is no longer fatal, i.e., instead of the
kernel panicing, it will just return the 'deadlock avoided'
Hi,
this doesn't look like the same bug described in the link you posted.
The other bug caused negotiation to completely fail, while it succeeds
in your case.
Looks like there's something else wring. What does your ifconfig look
like after the link is up?
Lars
--
Lars Eggert [EMAIL
13 matches
Mail list logo
