[SOLVED] Having problem with LAN interface after MultiWAN setup

[bobbythomas]

Hi,

I am facing some problem with the LAN interface after the MultiWAN implementation. Previously I have configured Radius server for 802.1x authentication along with my openwrt wireless AP. It was working fine, but after the MultiWAN setup firewall is not processing the Radius packets. When I do a packet capture, I can see that the packets are hitting the LAN interface, but nothing happens. I have checked the LAN rules and I don't see anything unusual. I have configured MutiWAN according to the user manual. I am only seeing these messages in the Radius.log.

Tue Aug 15 01:55:13 2017 : Warning: No 'ipaddr' or 'ipv4addr' or 'ipv6addr' field found in client 192.168.xxx.xxx/32. Please fix your configuration
Tue Aug 15 01:55:13 2017 : Warning: Support for old-style clients will be removed in a future release
Tue Aug 15 01:55:13 2017 : Info: Debugger not attached
Tue Aug 15 01:55:13 2017 : Warning: [/usr/local/etc/raddb/mods-config/attr_filter/access_reject]:11 Check item "FreeRADIUS-Response-Delay"  found in filter list for realm "DEFAULT".
Tue Aug 15 01:55:13 2017 : Warning: [/usr/local/etc/raddb/mods-config/attr_filter/access_reject]:11 Check item "FreeRADIUS-Response-Delay-USec"      found in filter list for realm "DEFAULT".
Tue Aug 15 01:55:13 2017 : Info: Loaded virtual server <default>
Tue Aug 15 01:55:13 2017 : Warning: Ignoring "sql" (see raddb/mods-available/README.rst)
Tue Aug 15 01:55:13 2017 : Warning: Ignoring "ldap" (see raddb/mods-available/README.rst)
Tue Aug 15 01:55:13 2017 : Info:  # Skipping contents of 'if' as it is always 'false' -- /usr/local/etc/raddb/sites-enabled/inner-tunnel:330
Tue Aug 15 01:55:13 2017 : Info: Loaded virtual server inner-tunnel
Tue Aug 15 01:55:13 2017 : Info: Loaded virtual server default
Tue Aug 15 01:55:13 2017 : Info: Ready to process requests

Below is the capture output:

Capture output
01:57:10.973401 IP WirelessAP.57234 > Firewall.1812: UDP, length 197
01:57:10.980459 IP WirelessAP.57234 > Firewall.1812: UDP, length 211
01:57:10.987020 IP WirelessAP.57234 > Firewall.1812: UDP, length 380
01:57:11.000092 IP WirelessAP.57234 > Firewall.1812: UDP, length 211
01:57:11.010126 IP WirelessAP.57234 > Firewall.1812: UDP, length 211
01:57:11.022018 IP WirelessAP.57234 > Firewall.1812: UDP, length 341
01:57:11.028065 IP WirelessAP.57234 > Firewall.1812: UDP, length 211
01:57:12.682297 IP WirelessAP.57234 > Firewall.1812: UDP, length 197
01:57:12.687066 IP WirelessAP.57234 > Firewall.1812: UDP, length 211
01:57:12.693453 IP WirelessAP.57234 > Firewall.1812: UDP, length 380
01:57:12.706031 IP WirelessAP.57234 > Firewall.1812: UDP, length 211
01:57:12.712632 IP WirelessAP.57234 > Firewall.1812: UDP, length 211
01:57:12.724334 IP WirelessAP.57234 > Firewall.1812: UDP, length 341
01:57:12.730127 IP WirelessAP.57234 > Firewall.1812: UDP, length 211
01:57:15.425568 IP WirelessAP.57234 > Firewall.1812: UDP, length 197
01:57:15.430630 IP WirelessAP.57234 > Firewall.1812: UDP, length 211
01:57:15.436427 IP WirelessAP.57234 > Firewall.1812: UDP, length 380
01:57:15.448784 IP WirelessAP.57234 > Firewall.1812: UDP, length 211
01:57:15.455262 IP WirelessAP.57234 > Firewall.1812: UDP, length 211
01:57:15.467295 IP WirelessAP.57234 > Firewall.1812: UDP, length 341
01:57:15.472934 IP WirelessAP.57234 > Firewall.1812: UDP, length 211

Any idea?

Thanks in advance.
Regards,
Bobby Thomas

[bobbythomas]

Hi,

Radius is now working after reinstalling the package. Please mark this thread as solved.

Thank you,
Regards,
Bobby Thomas

[franco]

Done, thanks!