I have a draytek130 configured as a router which is doing PPPoE to connect to my ISP. There was a suggestion to configure the draytek device as a bridge and have my openwrt device act as the PPPoE client in this thread.
I just spent a lot of time trying to get this to work, the closest thing I came to success was that the PPPoE session was established but it seems as if this is happening on the openwrt device:
OpenWrt sends: LCP Conf-Request id 1 (no Auth-Prot option!)
ISP sends: LCP Conf-Request id 218 (with Auth-Prot: PAP)
OpenWrt sends: LCP Conf-Ack id 1 (acknowledging OpenWrt's own request??)
OpenWrt keeps resending LCP Conf-Request id 1 (same one, over and over)
OpenWrt keeps sending LCP Conf-Ack id 1 but never acknowledges the ISP's Conf-Request!
You can see the summary of successufl and failed authentication pcaps here:
I tried a lot of different configurations; setting vigbrg on and off, using pppoe passthrough, different tagging mechanisms (on vigor, on openwrt, on both), but none of them seem to work. As you can see from the pppoe pcaps, my ISP is congstar. If there is anyone out there who was able to configure a draytek vigor130 along with an openwrt router to use the draytek as a transparent bridge, while openwrt does vlan tagging and PPPoE, I would really appreciate a comment on how you set it up.
Mmh, ard you sure the vigor passes your vlan on?
I opted for manually setting the VLAN tag on my bridged modem's dsl port, but I use VLANs to reach either the dsl bridge or tha lan dide with different VLANs...
No indeed I am not sure whether the vigor passes the vlan on or not, but I tried enabling and disabling it, configured the openwrt device with a vlan tagged wan interface but it does not work.
Not working: uci set network.wan.device='wan' uci set network.wan.proto='pppoe' uci set network.wan.username='vdsl/334697944@congstar.de' uci set network.wan.password='*****' uci set network.wan.ipv6='auto' uci delete network.wan.ipaddr 2>/dev/null uci delete network.wan.netmask 2>/dev/null uci delete network.wan.gateway 2>/dev/null uci delete network.wan.dns 2>/dev/null uci delete network.wan.mtu 2>/dev/null
Not working either:
uci set network.wan7.name='wan.7'
uci set network.wan7.type='8021q'
uci set network.wan7.ifname='wan'
uci set network.wan7.vid='7'
uci set network.wan7.mtu='1500'
uci set network.wan.device='wan.7'
uci set network.wan.proto='pppoe'
uci set network.wan.username='vdsl/334697944@congstar.de'
uci set network.wan.password='*****'
uci set network.wan.ipv6='auto'
uci delete network.wan.ipaddr 2>/dev/null
uci delete network.wan.netmask 2>/dev/null
uci delete network.wan.gateway 2>/dev/null
uci delete network.wan.dns 2>/dev/null
uci delete network.wan.mtu 2>/dev/null
Also tried adjusting mtu to 1492.
This is the only working configuration, which relies on the vigor to be configured as a router:
uci set network.wan.proto='static' uci set network.wan.device='wan' uci set network.wan.ipaddr='172.16.8.10' uci set network.wan.netmask='255.255.255.248' uci set network.wan.gateway='172.16.8.9' uci set network.wan.dns='8.8.8.8 8.8.4.4' uci delete network.wan.username 2>/dev/null uci delete network.wan.password 2>/dev/null uci delete network.wan.ipv6 2>/dev/null uci delete network.wan.mtu 2>/dev/null
It can do either - either taking care of all the tagging or passing through tagged connections. Personally I always did the later, doing the tagging on my router, not the modem.
Keep in mind, BNG is a relatively new development, originally 'Internet', VoIP and IPTV were often transported via different VLANs, in those situations your router needs to be able to get multiple different VLANs over the modem.
my guess is that bridge do not work as expected on the vigor side.
Even on attempt to connect you should see RX / TX bytes on the ifconfig wan.7 or wan dependent how bridge is set on vigor.
When I used a Vigor 130, it was important to configure MPoA bridge mode, because PPPoE passthrough was broken. Generally, the configuration linked by @slh looks good to me.
For debugging of the PPPoE connection you can use option pppd_options 'debug'. Then you can see what is going on without doing a packet capture.