home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!wupost!cs.utexas.edu!sun-barr!ames!purdue!news.cs.indiana.edu!umn.edu!noc.msc.net!uc.msc.edu!shamash!easyaspi.udev.cdc.com!gsa
- From: gsa@easyaspi.udev.cdc.com (gary s anderson)
- Newsgroups: comp.protocols.tcp-ip
- Subject: Re: Raw IP
- Message-ID: <46458@shamash.cdc.com>
- Date: 14 Aug 92 15:46:02 GMT
- References: <1992Aug14.120245.8688@news.uit.no>
- Sender: usenet@shamash.cdc.com
- Reply-To: gsa@easyaspi.udev.cdc.com (gary s anderson)
- Lines: 28
-
- In article <1992Aug14.120245.8688@news.uit.no>, rune@regina.itek.norut.no (Rune Hamnvik (Stud IT)) writes:
- |> Hello
- |> We are using Berkeley sockets and we wish for some reason to use
- |> raw sockets, but we have a problem. We can not send packets greater
- |> than about 1500 - 2000 bytes. Why is that ?
- |> Does the protocol spesify this or is it only the implementation that
- |> has this limitation ?
- |> I have read that IP can do fragmentation and that the maximum
- |> size of an IP datagram is 65536 bytes. Is this true ?
- |>
- |> Can someone please help us ?
- |>
- |> Rune Hamnvik
-
- Here are two possible reasons:
-
- 1) The socket send and/or receive buffers are not large enough.
- A nominal value used in BSD code is 2048 bytes. You can use
- the getsockopt to check the sizes and the setsockopt to
- change the sizes.
-
- 2) You are going between network solutions and the don't fragment
- option is set (e.g. when going from FDDI to Ethernet). Unless
- you have control over the IP headers you may be SOL (NOTE - if
- you're lucky you might be able to configure the FDDI MTU size).
-
- My guess is that issue "1" is the problem, however, one is always
- humbled by new findings.
-