Broken proxy requests with 3.2.6 Docker Container image?

Rahman DURAN rahman.duran at erzurum.edu.tr
Tue Dec 24 12:12:43 UTC 2024


Thank you for the confirmation Nick, any ETA about 3.2.7?

Regards,

Rahman Duran
Bilgi İşlem Daire Başkanlığı
Erzurum Teknik Üniversitesi
444 5 388 - 2730


<freeradius-users-request at lists.freeradius.org> adresine sahip kullanıcı 24
Ara 2024 Sal, 15:00 tarihinde şunu yazdı:

> Send Freeradius-Users mailing list submissions to
>         freeradius-users at lists.freeradius.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.freeradius.org/mailman/listinfo/freeradius-users
> or, via email, send a message with subject or body 'help' to
>         freeradius-users-request at lists.freeradius.org
>
> You can reach the person managing the list at
>         freeradius-users-owner at lists.freeradius.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Freeradius-Users digest..."
>
>
> Today's Topics:
>
>    1. Re: Broken proxy requests with 3.2.6 Docker Container image?
>       (Nick Porter)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 24 Dec 2024 10:54:07 +0000
> From: Nick Porter <nick at portercomputing.co.uk>
> To: freeradius-users at lists.freeradius.org
> Subject: Re: Broken proxy requests with 3.2.6 Docker Container image?
> Message-ID:
>         <a664b346-db56-4f04-b752-1b640c97d0a5 at portercomputing.co.uk>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
> On 24/12/2024 10:46, Rahman DURAN via Freeradius-Users wrote:
> > It just disables unused things and copies over my custom config from my
> git
> > repo. It was working without any problem until version 3.2.6. After I
> > upgraded to 3.2.6 outgoing eduroam proxy requests all started to fail
> with
> > same error:
> >
> > "Tue Dec 24 06:05:10 2024 : Auth: (1) Login incorrect (No Auth-Type
> found:
> > rejecting the user via Post-Auth-Type = Reject): [test08 at artvin.edu.tr]
> > (from client etu_wifi_rektorluk port 0 cli 7e8623ae0401)"
> >
> > Returning back to the 3.2.5 version container fixes the problem.
> >
> > I just tried to debug the problem and started the 3.2.6 version container
> > with "-X" but surprisingly it works ok in debug mode. It is reproducible
> > every time. If I run the container normally without "-X" it all fails
> with
> > the above error. If I run the same container with the same config with
> "-X"
> > it all works as expected.
> >
> > Is this a known problem? I tried the official "freeradius/freeradius-dev"
> > image with "v3.2.x" tag to see if the development image works and it
> works
> > without any problem too in normal mode (without debug mode).
>
> There is a known issue in 3.2.6 where proxying uses Home-Server-Pool or
> Home-Server-Name to direct the proxying - using Proxy-To-Realm works as
> expected.
>
> The issue will be resolved in 3.2.7 - hence the dev image working.
>
> Nick
>
> --
> Nick Porter
>
> Porter Computing Ltd
> Registered in England No 12659380
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: OpenPGP_signature.asc
> Type: application/pgp-signature
> Size: 665 bytes
> Desc: OpenPGP digital signature
> URL: <
> http://lists.freeradius.org/pipermail/freeradius-users/attachments/20241224/cf689990/attachment-0001.sig
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
>
>
> ------------------------------
>
> End of Freeradius-Users Digest, Vol 236, Issue 28
> *************************************************
>


More information about the Freeradius-Users mailing list