Destination port invalid
Hello, i have an issue with the response packet sended from my freeradius server to the NAS, a tcpdump on NAS side give this error message: The accounting response message is unfound,The message destination port invalid.ServerIP:0xac193c27 0x00000000 0x00000000 0x00000000,DstPort:31686,Correct Range:31671<=Port<=31685 Do you have any idea why freeradius choose this range port for response packet? Thanks Bassem
Hi,
On 20/02/2020, at 10:53 PM, Bassem Mettichi <mettichi@gmail.com> wrote:
Hello, i have an issue with the response packet sended from my freeradius server to the NAS, a tcpdump on NAS side give this error message:
The accounting response message is unfound,The message destination port invalid.ServerIP:0xac193c27 0x00000000 0x00000000 0x00000000,DstPort:31686,Correct Range:31671<=Port<=31685
Do you have any idea why freeradius choose this range port for response packet?
This is the destination port of the reply packet, which means it was the source port of the request. FreeRADIUS did not choose this port, your NAS did. If you look at a packet capture with the request and response, you will be able to verify this. -- Nathan Ward
Hello Nathan, thanks a lot for your response, i know that my Nas has chosen this port to send the request to my freeradius server, but the question why my radius server doesn't accept to use this port as a destination for sending packet response, the problem is on radius server not on NAS side, i don't really undertand this behavior. Thanks Bassem Le jeu. 20 févr. 2020 à 13:00, Nathan Ward <lists+freeradius@daork.net> a écrit :
Hi,
On 20/02/2020, at 10:53 PM, Bassem Mettichi <mettichi@gmail.com> wrote:
Hello, i have an issue with the response packet sended from my freeradius server to the NAS, a tcpdump on NAS side give this error message:
The accounting response message is unfound,The message destination port invalid.ServerIP:0xac193c27 0x00000000 0x00000000 0x00000000,DstPort:31686,Correct Range:31671<=Port<=31685
Do you have any idea why freeradius choose this range port for response packet?
This is the destination port of the reply packet, which means it was the source port of the request. FreeRADIUS did not choose this port, your NAS did.
If you look at a packet capture with the request and response, you will be able to verify this.
-- Nathan Ward
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi Bassem, Without the FreeRADIUS output is pretty complicated to help you. Please https://wiki.freeradius.org/guide/radiusd-X <https://wiki.freeradius.org/guide/radiusd-X> and share with us. -- Jorge Pereira jpereira@freeradius.org > On 20 Feb 2020, at 10:40, Bassem Mettichi <mettichi@gmail.com> wrote: > > Hello Nathan, > > thanks a lot for your response, i know that my Nas has chosen this port to > send the request to my freeradius server, but the question > why my radius server doesn't accept to use this port as a destination for > sending packet response, the problem is on radius server not on NAS side, i > don't really undertand this behavior. > > Thanks > Bassem > > Le jeu. 20 févr. 2020 à 13:00, Nathan Ward <lists+freeradius@daork.net> a > écrit : > >> Hi, >> >>> On 20/02/2020, at 10:53 PM, Bassem Mettichi <mettichi@gmail.com> wrote: >>> >>> Hello, >>> i have an issue with the response packet sended from my freeradius server >>> to the NAS, a tcpdump on NAS side give this error message: >>> >>> >>> The accounting response message is unfound,The message destination port >>> invalid.ServerIP:0xac193c27 0x00000000 0x00000000 >>> 0x00000000,DstPort:31686,Correct Range:31671<=Port<=31685 >>> >>> Do you have any idea why freeradius choose this range port for response >>> packet? >> >> >> This is the destination port of the reply packet, which means it was the >> source port of the request. >> FreeRADIUS did not choose this port, your NAS did. >> >> If you look at a packet capture with the request and response, you will be >> able to verify this. >> >> -- >> Nathan Ward >> >> - >> List info/subscribe/unsubscribe? See >> http://www.freeradius.org/list/users.html > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Feb 20, 2020, at 2:40 PM, Bassem Mettichi <mettichi@gmail.com> wrote:
thanks a lot for your response, i know that my Nas has chosen this port to send the request to my freeradius server, but the question why my radius server doesn't accept to use this port as a destination for sending packet response, the problem is on radius server not on NAS side, i don't really undertand this behavior.
In your original message, you say that tcpdump on the NAS says that the destination port is invalid. This is not a FreeRADIUS issue. tcpdump isn't FreeRADIUS. The NAS isn't FreeRADIUS. And even if the NAS is seeing an ICMP "destination unreachable" packet, that packet comes from the OS, not from FreeRADIUS. I don't see why there's an issue here, or what the issue is. The message you're worried about comes from the NAS, not FreeRADIUS. So don't ask on the FreeRADIUS list why the NAS is producing the message. Ask the NAS vendor what the message is, and what it means. Alan DeKok.
participants (4)
-
Alan DeKok -
Bassem Mettichi -
Jorge Pereira -
Nathan Ward