Multiple Interfaces, Not Seeing Requests

[A.L.M.Buxey at lboro.ac.uk]

Hi,

> When requests are made locally using radtest and eapol_test (with the
> EAP-MSCHAPv2 file,) the service responds just fine.  I've done both

right. so service is working.

> packet-capture on the local router and a tcp dump showing packets
> arriving on the server.  My guess is that the service isn't listening
> to the correct interface, but it is configured to listen to all
> interfaces (from what I can tell).

netstat -anp  

look to verify the server is listening.


you have a firewall running - firewalld service running?  use the tools to verify what the
rules on the firewall are

>     Listening on auth address * port 1812 as server default
>     Listening on acct address * port 1813 as server default
>     Listening on auth address :: port 1812 as server default
>     Listening on acct address :: port 1813 as server default
>     Listening on auth address 127.0.0.1 port 18120 as server inner-tunnel
>     Opening new proxy socket 'proxy address * port 0'
>     Listening on proxy address * port 35952
>     Ready to process requests

..and no further debug output?  even if you hadnt configured a client you'd get output - unknown client! ;-)

> Proof packet is arriving:
> 23:20:50.935823 IP 10.xxx.xxx.205.1645 > 10.xxx.xxx.253.1812: RADIUS,
> Access Request (1), id: 0x55 length: 49

arriving to the doorstep of the server...theres still plenty that can stop that packet getting to
a daemon. 

alan