Setting Framed-MTU in Freeradius
Kat
Kaz at t-tec.com.au
Fri Feb 27 05:24:20 UTC 2026
Gday,
Google Gemini is insisting quite strongly that, after changing fragment
size in the /etc/raddb/mods-enabled/eap, I also need to put something in
the post-auth part.
The problem is that sometimes AI can be wrong and I cannot find
alternate sources that back this claim up. My Google-fu may be weak.
Google Gemini wants me to copy and paste this snippet:
post-auth {
update reply {
Framed-MTU := 1024
}
}
into /etc/raddb/sites-enabled/default in the post-auth section. Gemini
points to a comment block that says: "# Please do not put "unlang"
configurations into the "authenticate"
# section. Put them in the "post-auth" section instead. That's what
# the post-auth section is for."
is Google Gemini correct? Does this belong in the post-auth and is
perfectly fine to do?
In a previous email,
https://lists.freeradius.org/pipermail/freeradius-users/2022-March/101630.html,
to this list, it sounds like it could be in sites-available/default
Aren't they symlinks?
I can't find anything specific to comment or uncomment, and I would have
thought it would have been there, as an example. This makes me hesitant.
The example is for a State attribute when I want to set a configuration.
Even if the syntax is the same.
So it would look like this:
# Post-Authentication
# Once we KNOW that the user has been authenticated, there are
# additional steps we can take.
post-auth {
#
# If you need to have a State attribute, you can
# add it here. e.g. for later CoA-Request with
# State, and Service-Type = Authorize-Only.
#
# if (!&reply:State) {
# update reply {
# State := "0x%{randstr:16h}"
# }
# }
update reply {
Framed-MTU := 1024
}
Yay or Nay?
Kat
More information about the Freeradius-Users
mailing list