remove references to pre/post proxy

diff --git a/doc/antora/modules/reference/pages/raddb/sites-available/copy-acct-to-home-server.adoc b/doc/antora/modules/reference/pages/raddb/sites-available/copy-acct-to-home-server.adoc
index 4425d4537daf0dcf3f23c6c122b9a555e23b394a..a8e99d3099796864068e0006591d687ff97ee0d5 100644 (file)
--- a/doc/antora/modules/reference/pages/raddb/sites-available/copy-acct-to-home-server.adoc
+++ b/doc/antora/modules/reference/pages/raddb/sites-available/copy-acct-to-home-server.adoc
@@ -150,50 +150,6 @@ locally.  Ensure that the accounting section
 ```
                   ok
        }
-
-```
-
-When the server decides to proxy a request to a home server,
-the proxied request is first passed through the pre-proxy
-stage.  This stage can re-write the request, or decide to
-cancel the proxy.
-
-Only a few modules currently have this method.
-
-```
-       pre-proxy {
-
-```
-If you want to have a log of packets proxied to a home
-server, uncomment the following line, and the
-'detail pre_proxy_log' section in radiusd.conf.
-pre_proxy_log
-```
-       }
-
-```
-
-When the server receives a reply to a request it proxied
-to a home server, the request may be massaged here, in the
-post-proxy stage.
-
-```
-       post-proxy {
-```
-
-
-If you want to have a log of replies from a home
-server, uncomment the following line, and the
-'detail post_proxy_log' section in radiusd.conf.
-post_proxy_log
-
-Uncomment the following line if you want to filter
-replies from remote proxies based on the rules
-defined in the 'attrs' file.
-
-attr_filter
-```
-       }
 }
 ```
 
@@ -202,5 +158,5 @@ attr_filter
 ```
 ```
 
-// Copyright (C) 2025 Network RADIUS SAS.  Licenced under CC-by-NC 4.0.
+// Copyright (C) 2026 Network RADIUS SAS.  Licenced under CC-by-NC 4.0.
 // This documentation was developed by Network RADIUS SAS.

diff --git a/doc/antora/modules/reference/pages/raddb/sites-available/robust-proxy-accounting.adoc b/doc/antora/modules/reference/pages/raddb/sites-available/robust-proxy-accounting.adoc
index 93346da2431487299651d5c2aaeea7192ebfe6b9..83d259d6e8ce184b5f7614df748c946ba23e001f 100644 (file)
--- a/doc/antora/modules/reference/pages/raddb/sites-available/robust-proxy-accounting.adoc
+++ b/doc/antora/modules/reference/pages/raddb/sites-available/robust-proxy-accounting.adoc
@@ -110,48 +110,6 @@ realm acct_realm.example.com {
 (5) Define a virtual server to handle pre/post-proxy re-writing
 ```
 server home.example.com {
-       pre-proxy {
-```
-Insert pre-proxy rules here
-```
-       }
-
-       post-proxy {
-```
-Insert post-proxy rules here
-
-This will be called when the CURRENT packet failed
-to be proxied.  This may happen when one home server
-suddenly goes down, even though another home server
-may be alive.
-
-i.e. the current request has run out of time, so it
-cannot fail over to another (possibly) alive server.
-
-We want to respond to the NAS, so that it can stop
-resending the packet.  We write the packet to the
-"detail" file, where it will be read, and sent to
-another home server.
-
-```
-               Post-Proxy-Type Fail-Accounting {
-                       detail.example.com
-               }
-
-```
-
-This section is run when there are problems
-proxying Access-Request packets
-
-```
-               Post-Proxy-Type Fail-Authentication {
-```
-add policies here
-```
-               }
-
-       }
-
 ```
 Read accounting packets from the detail file(s) for
 the home server.

diff --git a/raddb/sites-available/copy-acct-to-home-server b/raddb/sites-available/copy-acct-to-home-server
index eb63d88de19f2f317bd6fdcace749f4bec21f416..b0bb770f522da9c97fb3ea6f0f355f80daa8a257 100644 (file)
--- a/raddb/sites-available/copy-acct-to-home-server
+++ b/raddb/sites-available/copy-acct-to-home-server
@@ -133,42 +133,4 @@ server copy-acct-to-home-server {
                   #  "succeeds" by forcing an "ok" return.
                   ok
        }
-
-
-       #
-       #  When the server decides to proxy a request to a home server,
-       #  the proxied request is first passed through the pre-proxy
-       #  stage.  This stage can re-write the request, or decide to
-       #  cancel the proxy.
-       #
-       #  Only a few modules currently have this method.
-       #
-       pre-proxy {
-
-               #  If you want to have a log of packets proxied to a home
-               #  server, uncomment the following line, and the
-               #  'detail pre_proxy_log' section in radiusd.conf.
-       #       pre_proxy_log
-       }
-
-       #
-       #  When the server receives a reply to a request it proxied
-       #  to a home server, the request may be massaged here, in the
-       #  post-proxy stage.
-       #
-       post-proxy {
-               #
-
-               #  If you want to have a log of replies from a home
-               #  server, uncomment the following line, and the
-               #  'detail post_proxy_log' section in radiusd.conf.
-       #       post_proxy_log
-
-
-               #  Uncomment the following line if you want to filter
-               #  replies from remote proxies based on the rules
-               #  defined in the 'attrs' file.
-
-       #       attr_filter
-       }
 }

diff --git a/raddb/sites-available/robust-proxy-accounting b/raddb/sites-available/robust-proxy-accounting
index 8efa6e0fbabad749b83192bc15a066d278679b0b..3654927eb91d862e63857d751192fce3cc3baa11 100644 (file)
--- a/raddb/sites-available/robust-proxy-accounting
+++ b/raddb/sites-available/robust-proxy-accounting
@@ -87,41 +87,6 @@ realm acct_realm.example.com {
 
 #  (5) Define a virtual server to handle pre/post-proxy re-writing
 server home.example.com {
-       pre-proxy {
-               #  Insert pre-proxy rules here
-       }
-
-       post-proxy {
-               #  Insert post-proxy rules here
-
-               #  This will be called when the CURRENT packet failed
-               #  to be proxied.  This may happen when one home server
-               #  suddenly goes down, even though another home server
-               #  may be alive.
-               #
-               #  i.e. the current request has run out of time, so it
-               #  cannot fail over to another (possibly) alive server.
-               #
-               #  We want to respond to the NAS, so that it can stop
-               #  resending the packet.  We write the packet to the
-               #  "detail" file, where it will be read, and sent to
-               #  another home server.
-               #
-               Post-Proxy-Type Fail-Accounting {
-                       detail.example.com
-               }
-
-               #
-               #  This section is run when there are problems
-               #  proxying Access-Request packets
-               #
-               Post-Proxy-Type Fail-Authentication {
-                       #  add policies here
-               }
-
-       }
-
-
        #  Read accounting packets from the detail file(s) for
        #  the home server.
        #