home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!news.tek.com!ogicse!decwrl!concert!sas!mozart.unx.sas.com!torpid.unx.sas.com!sastdr
- From: sastdr@torpid.unx.sas.com (Thomas David Rivers)
- Newsgroups: comp.unix.bsd,ics.general
- Subject: Re: [386bsd]: SLIP woes (packetsize > 876)
- Message-ID: <BxJ4Bo.ArL@unx.sas.com>
- Date: 11 Nov 92 02:02:12 GMT
- Article-I.D.: unx.BxJ4Bo.ArL
- References: <2B005B3A.17158@ics.uci.edu>
- Sender: news@unx.sas.com (Noter of Newsworthy Events)
- Organization: SAS Institute Inc.
- Lines: 33
- Nntp-Posting-Host: torpid.unx.sas.com
-
-
- Just to follow up on this (since I happen to be SL/IP'd in right
- now).
-
- On 386bsd saying -
- /sbin/ping -s869 wherever [wherever is an HP PA-Risc box]
-
- I saw the modem go crazy; both the sending and receiving lights were
- pegged. However, no packet ever made it back to the 386bsd box;
- (i.e. 49 packets transmitted, 0 packets received, 100% packet loss)
-
- On the HP (wherever) pinging the 386bsd box:
- /etc/ping -s869 386bsd
-
- I never saw a single modem light twiddle.
-
- ping's with the default size work fine.
-
- Actually, let me describe the setup - I'm SL/IP'd into a XYPLEX,
- which handles the routing, etc... - so it could be any number of
- hops between the 386bsd box and the HP.
-
- Then, I did a quick search, and found the largest packet size I could
- ping back and forth was 876 bytes (using /sbin/ping -s 878). I took
- some time looking in the kernel sources for this magic number (i.e. mtu,
- or something like that) - but couldn't find it. However, it is a
- familiar number from somewhere...
-
- - Dave Rivers -
- (rivers@ponds.uucp (home))
- (sastdr@unx.sas.com (work))
- --
- UPDATE ALL INFORMATION AND POD INTO COSMOS - Federal Express
-