Some ISPs require EAPOL on the WAN interface.
I made a very basic implementation, right now it just takes a wpa_supplicant config as an argument to get it working.
cat /opt/vyatta/share/vyatta-cfg/templates/interfaces/ethernet/node.tag/eapol/node.def priority: 382 type: txt help: wpa_supplicant config file for EAPOL create: sudo /sbin/wpa_supplicant -B -d -Dwired -i$VAR(../@) \ -c$VAR(@) \ -f/var/log/wpa_supplicant-$VAR(../@).log \ -P/var/run/wpa_supplicant-$VAR(../@).pid delete: sudo kill `cat /var/run/wpa_supplicant-$VAR(../@).pid` update: sudo kill `cat /var/run/wpa_supplicant-$VAR(../@).pid` sudo /sbin/wpa_supplicant -d -Dwired -i$VAR(../@) \ -c$VAR(@) \ -f/var/log/wpa_supplicant-$VAR(../@).log \ -P/var/run/wpa_supplicant-$VAR(../@).pid
I suppose a proper implementation needs to write the wpa_supplicant config instead of taking a file argument.
Is it possible to use the new xml method, when the rest of the interface is using the old method?
I only know the options needed for EAP-TLS, so I'm not sure of all the options that need to be included.
Let me know if I should submit it as a PR.