Paul Koning wrote: "gerry" == gerry <gerry77 at mail.com> writes: gerry> Really, we [1] had some problems with fragmented UDP packets, gerry> mostly due to some cheap IP routers bundled with local ADSL gerry> connections. Many of them seem to be unable to correctly gerry> manage UDP fragments and/or have memory leaks which in the end gerry> cause lockups and other nasty things after some DECnet-in-UDP gerry> traffic has passed thru them. In at least one case, the gerry> problem was even nailed down to some ISP apparatus sitting gerry> between two remote bridges of ours. Yikes. Yeah. "Yikes" is a good word for it. gerry> We still do not know how these UDP related problems would/will gerry> impact other protocols like LAT, LAD/LAST and MOP because we gerry> haven't experimented so much as with pure DECnet. Any gerry> contribution and suggestions on how to force reduced frame gerry> size for those protocols would be much appreciated. :-) I can't think of any. The general rule at DEC was that some basic level of design competence was assumed. Getting the Ethernet frame size right was certainly part of the basic IQ test. The only solution I can think of is to reduce the MTU of your local Ethernet on the machine doing the UDP encapsulation. That would force the packets to be fragmented at origination time, which means your defective routers will see small-enough packets. If I suspect right, that won't solve it. I haven't any direct experience with these kind of problems, but the few cases that I'm semi-aware of are actually of bridges/gateways/routers that can't handled IP fragments. Forcing a fragment even earlier won't help. And the problem stems from the fact that these stupid products look at the head of the packet to make some "intelligent" decision. However, in a fragmented packet, only the first packet have the header of the encapsulated protocol. So, for UDP, only the first IP fragment have the UDP header. Any of the other fragments don't. And stupid firewalls then get really confused, because they can't deal with this. A correct firewall will atleast remember the source and destination IP, along with the identification field of the packet, along with the decision taken for the first fragment. And then it takes the same decision for all the other fragments belonging to the same packet. That is still not perfect, but it's usually "good enough". The only way to avoid the problem, if you have one of those stupid products, is either to make sure all your frames are small enough to fit in inside a normal packet, or make the MTU larger. The first is what gerry have done for DECnet. The latter is what you might do with jumbo ethernet frames. However, if you run packets to non-local destinations, you'll probably still end up with fragmented packets. So my only solution is to get better hardware that can deal with IP fragmentation. Johnny -- Johnny Billquist || "I'm on a bus || on a psychedelic trip email: bqt at softjar.se || Reading murder books pdp is alive! || tryin' to stay hip" - B. Idol