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 :-)
In the way that only a cry for help on a large mailing list can do, I
found the problem myself.
It seems that
Well thanks to Archie, I had mpd connecting me to my works 2500 quite
successfully. 'Had' being the operative word :-)
Unfortunately, the 2500 recently had some configuration changes.
Specifically related to the MTU settings. This fixed some other clients,
but broke me :-(
Symptoms, the connect
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)
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 'd
Hi folks,
I'm trying to setup a VPN connection to my work's staff network. I think
I'm running into the problem described here:
http://www.geocrawler.com/mail/msg.php3?msg_id=7311422&list=165
IE: The physical IP address of the cisco device is the same as the tunnel
endpoint address, and packet
