v12.2: RADIUS source+pfconnector is not working in admin context

[nqb]

Describe the bug
If you use a RADIUS source with authorization rules (admin context) and your source is configured with "Use connector" enabled, RADIUS response will be ignored.

If you disable "Use Connector", everything works as expected.

I tried to use same source (with "Use connector" enabled) on captive portal and it works.

To Reproduce
Steps to reproduce the behavior:

1. Configure a RADIUS server
2. Create your RADIUS source with "Use Connector" enabled
3. Create an administration rule on that source
4. Try to authenticate on webadmin using an account on your RADIUS server

=> Following message will appear in logs:

Feb 23 11:20:14 pfdeb11localdev pfperl-api-docker-wrapper[2050]: pfperl-api(16) ERROR: [mac:[undef]] Unable to perform RADIUS authentication on any server: ETIMEOUT (pf::Authentication::Source::RADIUSSource::_handle_radius_request)

Expected behavior
Access to web admin granted

Additional context
I captured traffic on port use by pfconnector and I can see that RADIUS server is returning an Access-Accept.

[nqb]

I put a dump after that line

and I got this:

# use connector=enabled
{'authenticator' => '<C6><8F><88><82><E2><82>;<CB><A5><BB>jE<9B><F6><BB>%','localaddr' => undef,'error' => 'ETIMEOUT',
     'sock' => bless( \*Symbol::GEN308, 'IO::Socket::INET' ),
     'attributes' => '^A^Ebob^B^R<FB>d<FF><C6><A9><FF><A1><FF><E7>h<BB><D1><CC><D3><CF>^M^D^F<AC>^R<8C>^O',
     'error_comment' => '',
     'secret' => 'testing123',
     'timeout' => '1',
     'node_addr_a' => '100.64.0.1:41575',
     'message_auth' => undef},
    'Authen::Radius' )

# use connector=disabled
    {'secret' => 'testing123',
         'timeout' => '1',
         'node_addr_a' => '172.18.140.102:1812',
         'message_auth' => undef,
         'error' => 'ENONE',
         'authenticator' => '̡% J%vڃ',
         'localaddr' => undef,
         'sock' => bless( \*Symbol::GEN426, 'IO::Socket::INET' ),
         'attributes' => 'Hello, bob',
         'error_comment' => ''},
    'Authen::Radius' )

[nqb]

@jrouzierinverse, same behaviour with your fix.

[fdurand]

The reply is coming from the wrong ip address, it send to 100.64.0.1 but the return is coming from the mgmt ip of the server.