Bug 30966 - TCPdump repeating on Radius accounting packets
Summary: TCPdump repeating on Radius accounting packets
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: Bill Fenner
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-01 20:20 UTC by jsuter
Modified: 2005-08-30 11:10 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jsuter 2001-10-01 20:20:00 UTC
Athlon 700 socket, Intel 10/100 PCI (FXP).  Running Cistron 1.6.3 radius and Lucent PM3 w/ comos 3.9.1
Repeatedly posts "NAS_port_type".  Somewhere around 4.3 -> 4.4 change the problem manifested itself by causing grep to swell to 500+MB.  An open tcpdump will show:

13:59:25.471963 pm1.intrastar.net.1026 > moon.intrastar.net.1646:  rad-account-req 194 [id 47] Attr[  Acct_session_id{3500B78C} User{sandyland} NAS_ipaddr{pm1.intrastar.net} NAS_port{26} NAS_port_type NAS_port_type NAS_port_type NAS_port_type NAS_port_type NAS_port_type NAS_port_type NAS_port_type NAS_port_type NAS_port_type NAS_port_type NAS_port_type NAS_port_type NAS_port_type NAS_port_type NAS_port_type NAS_port_type NAS_port_type NAS_port_type NAS_port_type NAS_port_type NAS_port_type

It will repeat the NAS_port_type "forever"

Fix: 

working on that...
How-To-Repeat: For me all I have to do is tcpdump an ethernet segment with radius traffic.  I have not been able to change radius servers to see if its a server related issue.
Comment 1 Kris Kennaway freebsd_committer freebsd_triage 2001-10-05 06:51:20 UTC
Responsible Changed
From-To: freebsd-bugs->fenner

Bill is a tcpdump maintainer
Comment 2 Bill Fenner 2001-10-05 20:13:36 UTC
Jacob,

  Can you capture me a couple of these packets?  Maybe use something
like "tcpdump -c 2 -w badpkts udp port radius" and send me the
"badpkts" file, after verifying that "tcpdump -r badpkts" causes
the loop?

Thanks,
  Bill
Comment 3 Bill Fenner freebsd_committer freebsd_triage 2001-10-15 20:47:52 UTC
State Changed
From-To: open->feedback

Waiting for a dump file with the bad packets 
so I can replicate the problem locally
Comment 4 Matteo Riondato freebsd_committer freebsd_triage 2005-08-30 11:09:47 UTC
State Changed
From-To: feedback->closed

feedback timeout