NAS-Post in Netgear Accounting-Packet
Hi list, please have a look at this Accounting-Request. It was sent by a netgear WG102 WLAN-Access-Point: rad_recv: Accounting-Request packet from host 192.168.1.133 port 1033, id=48, length=194 Service-Type = Framed-User Acct-Status-Type = Stop User-Name = "burgerw" Framed-MTU = 1488 Acct-Session-Id = " 2" Acct-Authentic = RADIUS Acct-Session-Time = 159 Acct-Terminate-Cause = User-Request Acct-Delay-Time = 0 Called-Station-Id = "061B2F76F3B6:MPIIB-Guests" Calling-Station-Id = "0019E3D7B020" Framed-IP-Address = 192.168.20.34 NAS-Identifier = "netgear3" NAS-Port-Type = Wireless-802.11 Connect-Info = "CONNECT 54Mbps 802.11g" NAS-IP-Address = 192.168.1.133 NAS-Port = 0 NAS-Port-Id = "STA port # 0" The output of "radwho -R": User-Name = "burgerw" Acct-Session-Id = " 2" NAS-IP-Address = 192.168.1.133 NAS-Port = 1 Service-type = Login-User Framed-IP-Address = Acct-Session-Time = 359 Calling-Station-Id = "0019E3D7B020" The error: rlm_radutmp: Logout for NAS netgear3 port 0, but no Login record Is the Access-Point sending the wrong NAS-Port? If so, I would contact Netgear. I just want to confirm what`s the problem. Thanks and best regards Wolfgang Burger Mit freundlichen Grüßen Wolfgang Burger <burgerw@immunbio.mpg.de> Max-Planck-Institut fuer Immunbiologie Scientific Data Processing Unit (+00 49) 761 / 5108 461 Stuebeweg 51 D-79108 Freiburg Germany
Am 01.07.2008 um 11:42 schrieb Ivan Kalik:
Is the Access-Point sending the wrong NAS-Port?
Have a look at more accounting packets. It's quite likely that AP is sending port 0 for all of them.
Ivan Kalik Kalik Informatika ISP
In the "Start"-Packets and "Interim-Update"-Packets it seems to be right. But ALL the "Stop"-Packets have 0 as NAS-Port. So, you agree that this is a bug of the Access-Point? Thank you for your reply. Wolfgang Burger
participants (2)
-
Ivan Kalik -
Wolfgang Burger