*BSD News Article 80794


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!spool.mu.edu!howland.erols.net!newsfeed.internetmci.com!hunter.premier.net!netaxs.com!socko.cdnow.com!heller
From: heller@socko.cdnow.com (A. Karl Heller)
Newsgroups: comp.unix.bsd.freebsd.misc,comp.unix.solaris
Subject: named/Connection lags on Solaris..
Date: 15 Oct 1996 20:22:18 GMT
Organization: CDnow - The World's Largest Online Music Store http://cdnow.com
Lines: 76
Distribution: inet
Message-ID: <540rpq$rhj@netaxs.com>
Reply-To: heller@cdnow.com
NNTP-Posting-Host: socko.cdnow.com
X-Newsreader: TIN [version 1.2 PL2]
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:29302 comp.unix.solaris:85990


  Strange topic to post here but its related... trust me..


I've got a Solaris 2.5.1 box that is running as a secondary name server
to a FreeBSD 2.1.5 box primary name server.

  I'm experiencing connection lags to and from the solaris box to other
machines.  The connection eventually will go through but will sit for
a very long time before connecting.  It is also random ( or so ) and I 
can't reproduce it other than when someone screams why they can't get to
some machine.

  You can telnet to some host and it will just sit there.. then go through.
This lag can be a few seconds to over 30.  I am assuming that this is some
kind of Solaris problem as it existed when it was the primary name server.

  Now, here comes the FreeBSD part.  I monitored the data between the S2.5.1
and the Freebsd box.  This is what troubles me:


320 126.88002 freebsd -> solaris    DNS R port=45251 
321 126.88079    solaris -> freebsd ICMP Destination unreachable (Bad port)
322 132.77982 freebsd -> solaris    DNS R port=45252 
323 132.78025    solaris -> freebsd ICMP Destination unreachable (Bad port)
324 142.36503    solaris -> freebsd DNS C port=45376 
325 155.36887    solaris -> freebsd DNS C port=45379 
326 161.68358    solaris -> freebsd DNS C port=45393 
327 162.66785    solaris -> freebsd DNS C port=45400 

342 190.57529    solaris -> freebsd SMTP C port=34426 
343 190.58283 freebsd -> solaris    DNS R port=45400 
344 190.58326    solaris -> freebsd ICMP Destination unreachable (Bad port)
345 190.59207 freebsd -> solaris    AUTH C port=2961 
346 190.60053    solaris -> freebsd AUTH R port=2961 

 These bad ports are showing up all over the place!

  And you'll notice that solaris can go to port 45400 on freebsd but
not vice versa...

  If you look at one of these packets you can see more:

   Packet 344 in detail says:
 
ETHER:  Packet size = 113 bytes

IP:   Flags = 0x4
IP:         .1.. .... = do not fragment
IP:         ..0. .... = last fragment
ICMP:UDP:  Length = 51 (Not all data contained in this fragment)
ICMP:UDP:  Checksum = BAFA 

  Why is this fragmented if the packet is not allowed to be?

ICMP:  ----- ICMP Header -----
ICMP:  
ICMP:  Type = 3 (Destination unreachable)
ICMP:  Code = 3 (Bad port)
ICMP:  Checksum = 60a5

ICMP:UDP:  Source port = 53
ICMP:UDP:  Destination port = 45400 
ICMP:UDP:  Length = 51 (Not all data contained in this fragment)
ICMP:UDP:  Checksum = BAFA 




  So, whats going on here? 

  Solaris:  Whats broken with 2.5.1 that lets this lag happen? Is it
related at all to this DNS problem? Any help would be greatly appreciated. =)

Thanks, Karl