Proxy EAP packets between network interfaces. Compatible with:
- Ubiquiti Networks EdgeRouter™ products
- UniFi® Security Gateway
- Generic Linux systems
1x_prox posted to the “AT&T Residential Gateway Bypass - True bridge mode!” discussion in the “AT&T U-verse” DSLReports forum.
IF_ROUTER for your router's interfaces. The
DAEMON_OPTIONS should not normally need adjusting.
Please see https://blog.taylorsmith.xyz/att-uverse-modem-bypass-unifi-usg/
Instruction (Generic Linux)
Sorry, you're on your own for now, but see #21 for hints.
EdgeRouter Sample Configuration
Here's an excerpt of my EdgeRouter configuration:
set interfaces ethernet eth0 description WAN
set interfaces ethernet eth0 duplex auto
set interfaces ethernet eth0 firewall in name WAN_IN
set interfaces ethernet eth0 firewall local name WAN_LOCAL
set interfaces ethernet eth0 speed auto
set interfaces ethernet eth0 vif 0 address dhcp
set interfaces ethernet eth0 vif 0 description 'WAN VLAN 0'
set interfaces ethernet eth0 vif 0 dhcp-options default-route update
set interfaces ethernet eth0 vif 0 dhcp-options default-route-distance 210
set interfaces ethernet eth0 vif 0 dhcp-options name-server update
set interfaces ethernet eth0 vif 0 firewall in name WAN_IN
set interfaces ethernet eth0 vif 0 firewall local name WAN_LOCAL
set interfaces ethernet eth0 vif 0 mac 'aa:bb:cc:dd:ee:ff'
set interfaces ethernet eth1 address 192.168.1.1/24
set interfaces ethernet eth1 description LAN
set interfaces ethernet eth1 duplex auto
set interfaces ethernet eth1 speed auto
set interfaces ethernet eth2 description 'AT&T router'
set interfaces ethernet eth2 duplex auto
set interfaces ethernet eth2 speed auto
set service nat rule 5010 description 'masquerade for WAN'
set service nat rule 5010 outbound-interface eth0.0
set service nat rule 5010 protocol all
set service nat rule 5010 type masquerade
set system offload ipv4 vlan enable
Update the MAC address for
eth0 vif 0 to that of your AT&T router, or let
eap_proxy do it with the
--set-mac option. I prefer to set it in my router config.
set system offload ipv4 vlan enable command or you'll have horrible routing performance.
Don't forget to update the rest of your config to reference
eth0.0 as your WAN interface as needed.
I previously had IPv6 working via 6rd before my area was on native dual-stack. Here's the relevant 6rd configuration from that time:
set interfaces tunnel tun0 6rd-prefix '2602:300::/28'
set interfaces tunnel tun0 6rd-default-gw '::22.214.171.124'
set interfaces tunnel tun0 address '2602:30x:xxxx:xxxx::1/60'
set interfaces tunnel tun0 description 'AT&T 6rd tunnel'
set interfaces tunnel tun0 encapsulation sit
set interfaces tunnel tun0 firewall in ipv6-name WAN6_IN
set interfaces tunnel tun0 firewall local ipv6-name WAN6_LOCAL
set interfaces tunnel tun0 local-ip YY.YY.YY.YY
set interfaces tunnel tun0 multicast disable
set interfaces tunnel tun0 ttl 255
set service dhcp-server use-dnsmasq enable
set service dns forwarding options enable-ra
set service dns forwarding options 'dhcp-range=::1,constructor:eth1,ra-names,86400'
set system offload ipv6 forwarding enable
6rd-default-gw should be the same for all AT&T customers that are using 6rd. The
local-ip is your DHCP-issued WAN IP. The
tun0 address is your 6rd delegated prefix. It is based on your WAN IP and can be computed with this bit of python:
python -c 'import sys;a,b,c,d=map(int,sys.argv.split("."));print "2602:30%x:%x%02x%x:%x%02x0::1/60" % (a>>4,a&15,b,c>>4,c&15,d)' 126.96.36.199
If you aren't already using
dnsmasq for DHCP, you might want to use
radvd instead. See the example here (it's the
For configuring IPv6 in areas that are on native dual-stack, please see the discussion in https://github.com/jaysoffian/eap_proxy/issues/3. FWIW, though I was able to get IPv6 to work correctly, I eventually disabled it for a couple reasons. First, AT&T's IPv6 network was flakey for me, and sometimes sites would randomly become unreachable. Second, even when IPv6 was working correctly, the latency for me to many sites was always significantly higher than over IPv4. YMMV.
Good luck. This proxy continues to work well for me. I originally developed it for use on an EdgeRouter Lite running EdgeOS v188.8.131.52. As of Sep 2018, I'm using it on an EdgeRouter 4 running EdgeOS v1.10.5. I know that it has also been used successfully on the ER-X and USG.
usage: eap_proxy [-h] [--ping-gateway] [--ping-ip PING_IP]
[--ignore-when-wan-up] [--ignore-start] [--ignore-logoff]
[--restart-dhcp] [--set-mac] [--vlan-id VLAN_ID] [--daemon]
[--pidfile PIDFILE] [--syslog] [--run-as USER[:GROUP]]
[--promiscuous] [--debug] [--debug-packets]
IF_WAN interface of the AT&T ONT/WAN
IF_ROUTER interface of the AT&T router
-h, --help show this help message and exit
checking whether WAN is up:
--ping-gateway normally the WAN is considered up if the IF_WAN VLAN
has an address; this option additionally requires that
there is a route via IF_WAN with a gateway (next-hop)
that responds to a ping
--ping-ip PING_IP normally the WAN is considered up if the IF_WAN VLAN
has an address; this option additionally requires that
PING_IP responds to a ping
ignoring router packets:
--ignore-when-wan-up ignore router packets when WAN is up (see --ping-
--ignore-start always ignore EAPOL-Start from router
--ignore-logoff always ignore EAPOL-Logoff from router
configuring IF_WAN VLAN:
--restart-dhcp check whether WAN is up after receiving EAP-Success on
IF_WAN VLAN (see --ping-gateway); if not, restart
dhclient on IF_WAN VLAN
--set-mac set IF_WAN VLAN MAC (ether) address to router's MAC
--vlan-id VLAN_ID set IF_WAN VLAN ID (default is 0)
--daemon fork into background and attempt to run forever until
killed; implies --syslog
--pidfile PIDFILE record pid to PIDFILE
--syslog log to syslog instead of stderr
switch to USER[:GROUP] after opening sockets;
incompatible with --daemon
--promiscuous place interfaces into promiscuous mode instead of
--debug enable debug-level logging
--debug-packets print packets in hex format to assist with debugging;