Is RG_ETHER_ADDR needed in supplicant mode?
owenthewizard opened this issue · 6 comments
I use the attached script (slightly modified) for supplicant mode on OPNsense 21.7.1, and I just use EAP_SUPPLICANT_IDENTITY
for everything. Everything works fine.
99-opnatt.txt
Would like to know the answer to this as well, I didn't extract my certs I purchased them.
Would like to know the answer to this as well, I didn't extract my certs I purchased them.
You purchased them? So you paid someone to extract them for you? Sounds like you got scammed.
Would like to know the answer to this as well, I didn't extract my certs I purchased them.
You purchased them? So you paid someone to extract them for you? Sounds like you got scammed.
LOL
I too would like to know this, or if RG_ETHER_ADDR should be the same as EAP_SUPPLICANT_IDENTITY
I also purchased certificates (not a scam @owenthewizard , it's relatively common and it works great for me on Unifi)
I can deduce that EAP_SUPPLICANT_IDENTITY should be matching the certificates I received, what I don't know is if RG_ETHER_ADDR should also be this mac address, or if it should match my actual AT&T gateway
I can deduce that EAP_SUPPLICANT_IDENTITY should be matching the certificates I received, what I don't know is if RG_ETHER_ADDR should also be this mac address, or if it should match my actual AT&T gateway
EAP_SUPPLICANT_IDENTITY should match the certificates. RG_ETHER_ADDR should be the mac address of your current AT&T-provided residential gateway.
I can deduce that EAP_SUPPLICANT_IDENTITY should be matching the certificates I received, what I don't know is if RG_ETHER_ADDR should also be this mac address, or if it should match my actual AT&T gateway
EAP_SUPPLICANT_IDENTITY should match the certificates. RG_ETHER_ADDR should be the mac address of your current AT&T-provided residential gateway.
That is the conventional wisdom yes, but I use EAP_SUPPLICANT_IDENTITY
for both even though my certificates are not from my assigned RG, and everything still works.