SOLVED: Unsupported protocol (80fd) with SLiRP

Thread View: comp.os.os2.networking.tcp-ip

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by Ivan Yanasak Mon, 11 Sep 1995 00:00

#237

Author: Ivan Yanasak
Date: Mon, 11 Sep 1995 00:00

24 lines
1428 bytes

Just thought that I'd pass along my solution for the above problem (that
has been hosing me for the past couple of months).  Turns out that I 
didn't have a "conservative" enough entry for asyncmap.  I was originally
using 

  slirp -b 19200 -P "asyncmap a0000" "escape 11,13" "mru 1006" "mtu 1006"

but at ran across the following "worst case" slirp settings on one of the
SLiRP pages:

  slirp -b 19200 -P "mtu 552" "mru 552" "asyncmap FFFFFFFF" "escape 0,11,13,1D,FF"

This got everything working.  Later, bumping up mtu and mru back to 1006 was
okay, but returning asyncmap back to its former value caused the above error
message to return.  (I didn't go into any further debugging, and didn't
bother to play with the escaped characters list.)

Just one more thing to try.  Thanks to all for the pointers...

-Ivan

-- 
					
					-Ivan Yanasak (yanasak@cc.gatech.edu)

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads