Page MenuHomePhabricator

Add EAPOL login support
Open, Requires assessmentPublicFEATURE REQUEST

Description

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.

Details

Difficulty level
Unknown (require assessment)
Version
-
Why the issue appeared?
Will be filled on close

Event Timeline

mb300sd created this task.Jun 21 2019, 6:32 PM
mb300sd created this object in space S1 VyOS Public.

Trying to figure out how to do this via xml. Seems like it generates the .def files from the xml Does it require rebuilding the whole image to test?

mb300sd changed the subtype of this task from "Task" to "Feature Request".Jun 25 2019, 11:13 PM
pasik added a subscriber: pasik.Jun 26 2019, 8:46 PM