"Brian Andrus" <[EMAIL PROTECTED]> wrote: > And when I start freeradius up, it grabs 1812 and 1813 for listening. The > odd thing is that it seems to grab the first non-priviledged port for > sending out responses.
The server *should* send response FROM the port that the NAS sent packets TO. If it doesn't, something is seriously wrong. In fact, I don't see how it *can* send packets from the wrong port. Nothing in the send/receive packet code knows about ports. It just receives a packet on a socket, and sends replies back out that socket. The kernel takes care of putting on the UDP header, with src/dst port information. I'd suggest using checking if there's a firewall between the RADIUS sever and the NAS. If so, it's the one screwing things up. Also, run tcpdump on the radius server, to see the port from which the reply packet is sent. If it's 1812, then the problem isn't the RADIUS server, it's something else in the network. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
