So are you saying you don't need the script to create a netgraph interface in pfSense if you are doing wpa_supplicant?Skip the script and do
sudo /sbin/wpa_supplicant -dd -Dwired -ieth0 -c wpa_supplicant.conf
on the command line, should tell you where it's hanging. Make sure you didn't get any 0-byte .cer files, it seems the 210 linux doesn't unmount the partition correctly. Running sync before unmounting might help.
Not sure - I'm not running pfsense. But the wpa_supplicant alone should tell you why it hangs. I think the netgraph had something to do with vlan 0 on bsd, so you probably need it to actually access the internet.So are you saying you don't need the script to create a netgraph interface in pfSense if you are doing wpa_supplicant?
reg add “HKEY_LOCAL_MACHINE\SYSTEM\CURRENTControlSet\Services\vmsmp\parameters” /v 8021xEnabled /t REG_DWORD /d 1 /f
well that's quite the development...I was really wanting to terminate ATT's fiber right on my ICX6610's so I don't need another linux box/vm and all that crap just to terminate it - the brocades will take a GPON SFP and will do 802.1x authentication and termination right onboard - however I ruled it out because they will not allow you to tag packets on vlan 0. Your discovery makes me wonder if it's worth trying now - the big question is fastiron's treatment of packets coming in tagged with vlan0. only one way to find out I guessThankfully AT&T doesn't seem to care if you send the outgoing packets untagged.