Ethereal-dev: [ethereal-dev] non-standard UDP ports for standard protocolls ???

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: "Hannes R. Boehm" <hannes@xxxxxxxxx>
Date: Sun, 10 Jan 1999 16:02:33 +0100
Hi,

I just captured a new packet type which is not yet supported by
ethereal:

RADIUS - (Remote Athentication for Dial In User Service)

the problem is:

Many radius implementations do not use the
standard UDP port (1812 (formely: 1645)) but nonstandarized ports.

What should we do with those packets ?

I am thinking about analyzing the packet within packet-udp.c
-> if a packet to an unknown UDP port turns out to be a RADIUS packet,
   then dissect_radius() is called

-> since this step is only performed for unknown UDP ports, this should
   not increase the time needed to open a standard tracefile (unless
   of course, there are many UDP packets to unknown ports....

-> If this does not perform well, we could limit the ports we are checking
   for radius packets (e.g. user configurable within the config file)


Any other ideas ?

waiting for comments or suggestions 

    Hannes


-- 
--
"The nice thing about standards is that there's so many to choose from." 
        -- Andrew S. Tanenbaum
!------------------------------------------------------------------!
  Hannes R. Boehm
        email   : hannes@xxxxxxxxx
        www     : http://hannes.boehm.org
        PGP-key : http://hannes.boehm.org/hannes-pgp.asc
!------------------------------------------------------------------!