public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: <Brian.Danilko@instech.com.au>
To: Jonathan Larmour <jlarmour@cygnus.co.uk>
Cc: Brian.Danilko@instech.com.au, ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Maximum size of Ping?
Date: Thu, 07 Dec 2000 21:01:00 -0000	[thread overview]
Message-ID: <14896.26059.682142.843225@elrond.instech.com.au> (raw)
In-Reply-To: <3A303EB4.A128BD34@cygnus.co.uk>

Jonathan Larmour writes:
 > Brian.Danilko@instech.com.au wrote:
 > > 
 > > Using the ecos tcp/ip stack I have noticed that it will only reply to
 > > pings of less then or equal to 3700 bytes (ie. ping -s 3042
 > > ecos_ip). Anything over this number gets dropped silently. Is this by
 > > design?
 > 
 > No. You need to update your TCP/IP stack to one from after the end of June.
 > Get it from anoncvs: http://sources.redhat.com/anoncvs.html although you'll
 > have to use anoncvs for everything then.
 >

Thanks for your swift reply. I have been using anoncvs and did my last 
checkout in November. I just checked to make sure that my networking
code was up to date and it is. 

Are there any settings that could be constraining the ICMP packet
size? Are the regression tests testing large ping packets?

Thanks,

Brian 

-- 
Brian Danilko - Software Design and Implementation
  @ Inspiration Technology P/L (Brian.Danilko@instech.com.au)
       Signal Processing Research & Design
  @ Formal Solutions (bdanilko@formalsolutions.com.au)
       Software Development, Technical Writing & Training

      reply	other threads:[~2000-12-07 21:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-07 17:36 Brian.Danilko
2000-12-07 17:52 ` Jonathan Larmour
2000-12-07 21:01   ` Brian.Danilko [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=14896.26059.682142.843225@elrond.instech.com.au \
    --to=brian.danilko@instech.com.au \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=jlarmour@cygnus.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).