Sending Access-Accept of id 14 to 148.85.32.5 port 1645

Luciano Afranllie listas.luafran at gmail.com
Thu Jan 22 15:30:05 CET 2009


On Thu, Jan 22, 2009 at 12:15 PM, Brian Ertel <bsertel at amherst.edu> wrote:
>
> Hi,
>
> I have freeradius configured to use port 1812 for auth.
>
>  #  Port on which to listen.
>         #  Allowed values are:
>         #       integer port number (1812)
>         #       0 means "use /etc/services for the proper port"
>         port = 1812
>
> I also have my Cisco Aironet 1230g configured to use 1812 and 1813:
>
> radius-server host 148.85.9.214 auth-port 1812 acct-port 1813
>
> ...but, the radius debug reads:
>
> Listening on authentication address * port 1812
> Listening on accounting address * port 1813
> Listening on command file /var/run/radiusd/radiusd.sock
> Listening on proxy address * port 1814
> Ready to process requests.
> rad_recv: Access-Request packet from host 148.85.32.5 port 1645, id=4,
> length=108
>         User-Name = "002241faecc3"
>         User-Password = "002241faecc3"
>         Called-Station-Id = "001a.6d6b.f080"
>         Calling-Station-Id = "0022.41fa.ecc3"
>         Service-Type = Login-User
>         NAS-Port-Type = Wireless-802.11
>         NAS-Port = 260
>         NAS-IP-Address = 148.85.32.5
>
> Sending Access-Accept of id 4 to 148.85.32.5 port 1645
>         Tunnel-Type:0 = VLAN
>         Tunnel-Medium-Type:0 = IEEE-802
>         Tunnel-Private-Group-Id:0 = "159"
>
> rad_recv on port 1645? and then sending access-accept port 1645?  Am I
> missing something?
>

1645 is the port being used by your radius client not by freeRADIUS.

Regards
Luciano



More information about the Freeradius-Users mailing list