Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
docs:guide-user:network:wan:isp-configurations [2021/12/27 19:40] huj3rdocs:guide-user:network:wan:isp-configurations [2024/08/26 10:51] – [Aruba FTTH] Again option ipv6 '1' bit for OpenWrt 19.07 andreabravetti
Line 26: Line 26:
         option username 'YOURADSLUSERNAME'         option username 'YOURADSLUSERNAME'
         option password 'YOURADSLPASSWORD'         option password 'YOURADSLPASSWORD'
-        option mtu '1492' 
         list dns '8.8.8.8'         list dns '8.8.8.8'
         list dns '8.8.4.4'         list dns '8.8.4.4'
Line 130: Line 129:
         option firmware '/lib/modules/vr9-B-dsl.bin'         option firmware '/lib/modules/vr9-B-dsl.bin'
 </code> </code>
 +
 +==== Fonira with static IPv4 and fixed IPv6 prefix ====
 +
 +Fonira provides the option to get rid of carrier-grade NAT by purchasing a static (and non-NATed) IPv4 address, and then also provides a fixed IPv6 prefix.
 +
 +<code>
 +# /etc/config/network
 +config interface 'wan'
 +        option proto 'pppoe'
 +        option username '******@fonira.at'  # The PPPoE username provided by Fonira.
 +        option password '******'  # The PPPoE password provided by Fonira.
 +        option device 'eth<X>.31'  # The VLAN with the ID 31 has to be used.
 +        option delegate '0'
 +        option ipv6 '1'
 +
 +config interface 'wan6'
 +        option device '@wan'
 +        option proto 'dhcpv6'
 +        option reqaddress 'try'
 +        option reqprefix 'no'
 +        option ip6prefix '.....::/60'  # The IPv6 prefix provided by Fonira.
 +        option delegate '1'
 +</code>
 +
 +Using the settings above, the static IPv4 address and a dynamic IPv6 address is provided to the router's WAN port by the ISP, and the fixed IPv6 prefix is used on the LAN side.
 +
 +Setting ''reqprefix'' to ''no'' is needed to prevent the router from requesting an additional (dynamic) IPv6 prefix from the ISP. However, with this option set to ''no'', no IPv6 route to the internet is set. This can be worked around by adding a source-route for the fixed IPv6 prefix:
 +
 +<code>
 +# /etc/config/network
 +config route6
 +        option interface 'wan6'
 +        option target '::/0'
 +        option source '.....::/60'  # The IPv6 prefix provided by Fonira.
 +</code>
 +
 +More details and discussions on this topic can be found in [[https://www.lteforum.at/mobilfunk/statisches-ipv6-netz-mit-fonira.13760/|this thread at LTEForum.at]] (in german).
  
  
Line 155: Line 191:
 </code> </code>
  
 +
 +==== EDPnet (Fiber) ====
 +EDPnet provides Fiber services through PPPoE and VLAN tagging as well. The state monopolist (Proximus) still manages the backbone, as with VDSL, and will install an ONT to which you connect your router of choice (!) directly.
 +
 +The following works on a [[toh:mikrotik:rb5009ug_s_in|MikroTik RB5009UG+S+IN]] with OpenWrt 22.03 and **DSA**. At this point `/etc/config/network` makes a distinction between 'device' and 'interface' definitions (the latter relying on the former). I am using port 8 as WAN port and am using 'fiber' as a fancy recognisable name instead of the mundane 'p8.10' (which would be default based on the port being port 8 tagged with VLAN 10).
 +
 +<code>
 +config device                                                            
 +        option name 'p8'                                                 
 +                                                                         
 +config device                                                            
 +        option type '8021q'                                              
 +        option ifname 'p8'                                               
 +        option vid '10'                                                  
 +        option name 'fiber'
 +
 +config interface 'wan'
 + option proto 'pppoe'
 + option username 'blabla@EDPNET'
 + option password '..............'
 + option ipv6 '1'
 + option device 'fiber'
 +
 +config interface 'wan6'
 + option proto 'dhcpv6'
 + option device '@wan'
 +</code>
 +
 +If you are using swconfig rather than DSA, the following is an example configuration working on an [[toh:tp-link:archer_c7|TP-Link Archer C7]]:
 +
 +<code>
 +config interface 'wan'
 +        option device 'eth0.10'
 +        option proto 'pppoe'
 +        option username 'xxx'
 +        option password 'xxx'
 +
 +config interface 'wan6'
 +        option device '@wan'
 +        option proto 'dhcpv6'
 +
 +config switch
 +        option name 'switch0'
 +        option reset '1'
 +        option enable_vlan '1'
 +
 +config switch_vlan
 +        option device 'switch0'
 +        option vlan '1'
 +        option ports '2 3 4 5 0t'
 +
 +config switch_vlan
 +        option device 'switch0'
 +        option vlan '10'
 +        option ports '1t 6t'
 +</code>
 +
 +===== Bosnia and Herzegovina =====
 +
 +==== BH Telecom ====
 +BH Telecom provides a combination of Internet, IPTV and VoIP xDSL services via copper twisted pair.
 +
 +=== ADSL2(+) ===
 +The following was tested on TP-Link TD-W8980 OpenWRT v22.03.4, using "MojaTV povremeno 1" plan via ADSL2+ connection, using default annex A xDSL firmware.
 +
 +Internet PPPoE over 8/60 ATM bridge
 +<code>
 +config dsl 'dsl'
 +    option annex 'a'
 +    option tone 'av'
 +    option ds_snr_offset '0'
 +
 +config atm-bridge 'atm'
 +    option encaps 'llc'
 +    option payload 'bridged'
 +    option nameprefix 'dsl'
 +    option vci '60'
 +    option vpi '8'
 +    option atmdev '0'
 +    option unit '0'
 +
 +config device
 +    option name 'dsl0'
 +
 +config interface 'wan'
 +    option device 'dsl0'
 +    option proto 'pppoe'
 +    option username 'name.surname'
 +    option password '**********'
 +    option ipv6 'auto'
 +</code>
 +
 +IPTV ATM 8/40 bridge
 +<code>
 +# Remove some switch ports from br-lan so they can be used for bridge to IPTV STB device(s)
 +config device
 +    option name 'br-lan'
 +    option type 'bridge'
 +    list ports 'lan1'
 +    list ports 'lan2'
 +    option stp '1'
 +    option igmp_snooping '1'
 +
 +config atm-bridge
 +    option encaps 'llc'
 +    option payload 'bridged'
 +    option nameprefix 'dsl'
 +    option vci '40'
 +    option vpi '8'
 +    option atmdev '0'
 +    option unit '1'
 +
 +config device
 +    option name 'dsl1'
 +    option ipv6 '0'
 +
 +config device
 +    option name 'iptv'
 +    option type 'bridge'
 +    list ports 'dsl1'
 +    list ports 'lan3'
 +    list ports 'lan4'
 +    option multicast '1'
 +    option multicast_querier '1'
 +    option promisc '0'
 +    option ipv6 '0'
 +</code>
 +
 +=== VDSL2 ===
 +The following was tested on TP-Link TD-W8980 OpenWRT v22.03.4, using "MojaTV povremeno 2" plan over VDSL2 connection, using default annex A xDSL firmware.
 +
 +The VLAN tagging is as follows:
 +  * Internet: PPPoE over VLAN 100.
 +  * IPTV: Bridge to STB via VLAN 930.
 +  * VoIP: Bridge via uknown VLAN id.
 +
 +Internet PPPoE VLAN 100
 +<code>
 +config dsl 'dsl'
 +    option line_mode 'vdsl'
 +    option ds_snr_offset '0'
 +    option annex 'a'
 +
 +config device
 +    option name 'dsl0'
 +
 +config interface 'wan'
 +    option device 'dsl0.100'
 +    option proto 'pppoe'
 +    option username 'name.surname'
 +    option password '**********'
 +    option ipv6 'auto'
 +</code>
 +
 +IPTV VLAN 930
 +<code>
 +# Remove some switch ports from br-lan so they can be used for bridge to IPTV STB device(s)
 +config device
 +    option name 'br-lan'
 +    option type 'bridge'
 +    option stp '1'
 +    option igmp_snooping '1'
 +    list ports 'lan1'
 +    list ports 'lan2'
 +
 +config device
 +    option name 'iptv'
 +    option type 'bridge'
 +    list ports 'lan3'
 +    list ports 'lan4'
 +    list ports 'dsl0.930'
 +    option multicast '1'
 +    option multicast_querier '1'
 +    option promisc '0'
 +    option ipv6 '0'
 +</code>
  
 ===== Canada ===== ===== Canada =====
Line 234: Line 446:
  
 Both of these procedures should really work for any operator using PPPoE. Both of these procedures should really work for any operator using PPPoE.
 +
 +===== Cyprus =====
 +
 +==== Epic (VDSL2+) ====
 +
 +Epic provides VDSL2+ services through PPPoE and VLAN tagging (''VLAN 35'', but to be sure sniff for a while with ''tcpdump -e'' option).
 +
 +Example configuration for AVM FritzBox 7360 V2: 
 +
 +<code>
 +config dsl 'dsl'
 +        option annex 'b'
 +        option ds_snr_offset '0'
 +        option firmware '/lib/firmware/vr9-B-dsl.bin' # Annex B Firmware for this device
 +        option tone 'av'
 +config interface 'wan'
 + option proto 'pppoe'
 + option ifname 'dsl0.35'
 + option username 'bits*****@home'
 + option password '*******'
 +</code>
 +
 +==== Cyta (Fiber) ====
 +
 +Besides ADSL2+ and VDSL, Cyta provides Fiber services through PPPoE and VLAN tagging (''VLAN 42'', but to be sure sniff for a while with ''tcpdum -e'' option). For connection following devices are used:
 +
 +  * ONT like Huawei OptiXstar HG8245X6
 +  * GPON Terminal like Huawei OptiXstar HG8010HV6 and provider's device like ZTE ZXHN H268A or your own device
 +
 +Example configuration for [[:toh:xiaomi:mi_router_ac2100|Xiaomi Mi Router AC2100]] with OpenWrt 21.02.1, DSA and settings missed in [[https://www.cyta.com.cy/mp/informational/docs/settingforthirdpartymodem.pdf|guide]] (''username'' and ''password'' are really dummy but not empty fields):
 +
 +<code>
 +config interface 'wan'
 + option proto 'dhcp'
 + option hostname '*'
 + option device 'wan'
 + option delegate '0'
 +
 +config device
 + option name 'wan'
 + option ipv6 '0'
 +
 +config device
 + option type '8021q'
 + option ifname 'wan'
 + option vid '42'
 + option name 'wan.42'
 +
 +config interface 'cyta_eth'
 + option proto 'pppoe'
 + option device 'wan.42'
 + option username 'cyta'
 + option password 'cyta'
 + option ipv6 '0'
 + option peerdns '0'
 + list dns '1.1.1.1'
 + option delegate '0'
 +</code>
 +
 +==== Cablenet (Fiber) ====
 +
 +Cablenet most probably is renting Cyta's GPON to provide Fiber services through PPPoE and VLAN tagging (''VLAN 42'', but to be sure sniff for a while with ''tcpdump -e'' option). For connection following devices are used:
 +
 +  * GPON Terminal like Huawei OptiXstar HG8010HV6 and provider's device like Mikrotik RB750Gr3 (provider doesn't announce usage of your own device and doesn't provide any settings as Cyta does)
 +
 +As PPPoE ''username'' and ''password'' are not dummy and not empty fields it may require to intercept them using a sniffer, setting up the VLAN and the PPPoE server on a device connected to the router's WAN port. Usually, the login is the same as the Subscription Number (SLA).
 +
 +Example configuration for [[:toh:mkirotik:rb750gr3|MikroTik RB750Gr3]] with OpenWrt 22.03.5 and DSA:
 +
 +<code>
 +config interface 'wan'
 + option proto 'dhcp'
 + option hostname '*'
 + option device 'wan'
 + option delegate '0'
 +
 +config device
 + option name 'wan'
 + option ipv6 '0'
 +
 +config device
 + option type '8021q'
 + option ifname 'wan'
 + option vid '42'
 + option name 'wan.42'
 +
 +config interface 'cablenet_eth'
 + option proto 'pppoe'
 + option device 'wan.42'
 + option username '<username>'
 + option password '<password>'
 + option ipv6 '0'
 + option peerdns '0'
 + list dns '1.1.1.1'
 + option delegate '0'
 +</code>
 +
 +==== Primetel (Fiber) ====
 +
 +Primetel most probably is renting Cyta's GPON to provide Fiber services through PPPoE and VLAN tagging (''VLAN 42'', but to be sure sniff for a while with ''tcpdump -e'' option). For connection following devices are used:
 +
 +  * GPON Terminal like Huawei OptiXstar HG8010HV6 and provider's device like ZTE ZXHN H268Q (provider doesn't announce usage of your own device and doesn't provide any settings as Cyta does)
 +
 +As PPPoE ''username'' and ''password'' are not dummy and not empty fields it may require to intercept them using a sniffer, setting up the VLAN and the PPPoE server on a device connected to the router's WAN port. Usually, the login looks like ''provider's_router_mac_address@cpe.prime-tel.com''.
 +
 +
 +Example configuration for [[:toh:xiaomi:mi_router_ac2100|Xiaomi Mi Router AC2100]] with OpenWrt 21.02.1 and DSA:
 +
 +<code>
 +config interface 'wan'
 + option proto 'dhcp'
 + option hostname '*'
 + option device 'wan'
 + option delegate '0'
 +
 +config device
 + option name 'wan'
 + option ipv6 '0'
 +
 +config device
 + option type '8021q'
 + option ifname 'wan'
 + option vid '42'
 + option name 'wan.42'
 +
 +config interface 'cablenet_eth'
 + option proto 'pppoe'
 + option device 'wan.42'
 + option username '<provider's_router_mac_address>@cpe.prime-tel.com'
 + option password '<password>'
 + option ipv6 '0'
 + option peerdns '0'
 + list dns '1.1.1.1'
 + option delegate '0'
 +</code>
  
 ===== Czech Republic ===== ===== Czech Republic =====
Line 257: Line 604:
                  
 config dsl 'dsl' config dsl 'dsl'
-        option annex 'a'+        option annex 'b'
         option ds_snr_offset '0'         option ds_snr_offset '0'
         option line_mode 'vdsl'         option line_mode 'vdsl'
-        option tone 'av       +        option tone 'bv' 
 +        option xfer_mode 'ptm       
 </code> </code>
  
Line 297: Line 645:
         option vid '835'         option vid '835'
         option ports '6t 0'                 option ports '6t 0'        
-</code> 
- 
-===== Cyprus ===== 
- 
-==== Epic (previously MTN) ==== 
- 
-==== VDSL2+ ==== 
- 
-  * Internet: PPPoE over VLAN 35. 
- 
- Example configuration on AVM FritzBox 7360 V2  using dsl  
-<code> 
-config dsl 'dsl' 
-        option annex 'b' 
-        option ds_snr_offset '0' 
-        option firmware '/lib/firmware/vr9-B-dsl.bin' # Annex B Firmware for this device 
-        option tone 'av' 
-config interface 'wan' 
- option proto 'pppoe' 
- option ifname 'dsl0.35' 
- option username 'bits*****@home' 
- option password '*******' 
 </code> </code>
  
Line 352: Line 678:
 ==== Bouygues Telecom ==== ==== Bouygues Telecom ====
 === FTTH === === FTTH ===
 +== IPv4 ==
  
-You have to use VLAN 100 and spoofing the bbox MAC address.+You have to use VLAN 100 and spoof the bbox MAC address.
 <code> <code>
 +config device
 + option name 'wan'
 + option macaddr '01:23:45:67:89:ab'
 +
 +config device
 + option type '8021q'
 + option ifname 'wan'
 + option vid '100'
 + option name 'wan.100'
 + option macaddr '01:23:45:67:89:ab'
 +
 config interface 'wan' config interface 'wan'
  option proto 'dhcp'  option proto 'dhcp'
- option ifname 'eth0.100'+ option ifname 'wan.100'
  option clientid '0123456789AB'  option clientid '0123456789AB'
  option vendorid 'BYGTELIAD'  option vendorid 'BYGTELIAD'
 + option hostname '*'
  option macaddr '01:23:45:67:89:ab'  option macaddr '01:23:45:67:89:ab'
 +</code>
 +
 +== IPv6 ==
 +you can get a ipv6 /60 prefix with IPv6-PD.
 +<code>
 +config interface 'wan6'
 + option proto 'dhcpv6'
 + option reqaddress 'try'
 + option macaddr '01:23:45:67:89:ab'
 + option clientid '0123456789AB'
 + option device 'wan.100'
 + option reqprefix 'auto'
 + option ip6assign '64'
 + list ip6class 'wan6'
 +
 +config interface 'lan'
 + […]
 + option ip6assign '64'
 + option delegate '0'
 +</code>
 +
 +<code>
 +config dhcp 'wan6'
 + option interface 'wan6'
 + option master '1'
 + option ra 'hybrid'
 + option dhcpv6 'hybrid'
 + option ndp 'hybrid'
 +
 +config dhcp 'lan'
 + option interface 'lan'
 + […]
 + option ra 'hybrid'
 + option dhcpv6 'hybrid'
 + option ndp 'hybrid'
 + list ra_flags 'managed-config'
 + list ra_flags 'other-config'
 + option ra_default '1'
 </code> </code>
  
Line 562: Line 939:
 </code> </code>
  
 +==== Deutsche Glasfaser ====
 +
 +Deutsche Glasfaser locally known as **DG** and in English the **German Fiber** uses IPoE for private customers with the support of **DHCPv4** (RFC 2131) and **DHCPv6** (RFC 8415) for all new connections.
 +
 +If you are an OpenWrt user means that you are using your own router (Kundeneigener Router) whose WAN interface is connected to the DG's **ONT** (Optical Network Terminal) directly.
 +
 +The minimal **wan4** and **wan6** configuration needed is shown below. The DG supplies a CG-NAT IPv4 address and a public IPv6 address in addition to the ''/56'' IPv6 prefix for further delegation.
 +
 +<code>
 +config interface 'wan4'
 + option proto 'dhcp'
 + option device 'eth1'
 +
 +config interface 'wan6'
 + option proto 'dhcpv6'
 + option device 'eth1'
 + option reqaddress 'try'
 + option reqprefix 'auto'
 + option norelease '1' # optional
 +</code>
 +
 +Note: ''eth1'' is your WAN interface and the optional option ''option norelease '1' '' is supported by OpenWrt version **23.05.2** and above and can be used to avoid missing PD for some hours after often restarts.
 +
 +==== Vodafone ====
 +
 +=== FTTH ===
 +
 +/etc/config/network
 +<code>
 +config interface 'wan'
 +        option device 'eth0.7'
 +        option proto 'pppoe'
 +        option username 'vodafone-ftth.komplett/***'
 +        option password '***'
 +        option ipv6 '1'
 +
 +config interface 'wan6'
 +        option proto 'dhcpv6'
 +        option reqaddress 'try'
 +        option reqprefix 'auto'
 +        option device 'pppoe-wan'
 +
 +config interface 'wan4'
 +        option proto 'dslite'
 +        option peeraddr '::'
 +        option encaplimit 'ignore'
 +</code>
 +
 +/etc/config/firewall
 +
 +<code>
 +config zone
 +        option name 'wan'
 +        option input 'REJECT'
 +        option output 'ACCEPT'
 +        option forward 'REJECT'
 +        option masq '1'
 +        option mtu_fix '1'
 +        list network 'wan'
 +        list network 'wan4'
 +        list network 'wan6'
 +</code>
 +
 +===== Greece =====
 +==== Nova ====
 +This ISP is little more involved to set up. Users who wish to use their own CPEs need to get ahold of:
 +  * The PPPoE credentials
 +  * The telephony credentials
 +
 +This can either be done by formally requesting the credentials from the ISP or by acquiring them from the router that the ISP provides.
 +
 +The ISP provides internet connectivity on VLAN 835 (PPPoE) and voip telephony on VLAN 837 (DHCP).
 +
 +For internet access, one must create a VLAN 835 and tag CPU and WAN. Then create a PPPoE interface, bind it on the 835 VLAN device, enter the credentials and enable "Use default gateway".
 +
 +Example configuration for internet access:
 +<code>
 +config device
 +        option name 'eth0.835'
 +        option type '8021q'
 +        option ifname 'eth0'
 +        option vid '835'
 +
 +config interface 'wan'
 +        option device 'eth0.835'
 +        option proto 'pppoe'
 +        option username '{pppoe_username}'
 +        option password '{pppoe_password}'
 +        option ipv6 '0'
 +</code>
 +
 +For telephony, one must create a VLAN 837 and tag CPU and WAN. Then create a DHCP interface, bind it on the 837 VLAN, disable "Use default gateway" and provide the client id for dhcp option 61 (this is usually //30xxxxxxxxxx_cid.ims.wind.gr// where //xxxxxxxxxx// is the phone number). Please note that it has to be converted to HEX (and remove any separator) in order for OpenWRT to understand it.
 +
 +Example configuration for telephony:
 +<code>
 +config device
 +        option name 'eth0.837'
 +        option type '8021q'
 +        option ifname 'eth0'
 +        option vid '837'
 +        option ipv6 '0'
 +        
 +config interface 'wan_voip'
 +        option proto 'dhcp'
 +        option device 'eth0.837'
 +        option clientid '{30xxxxxxxxxx_cid.ims.wind.gr or the option 61 they emailed you converted to hex and removing spaces}'
 +        option delegate '0'
 +        option defaultroute '0'
 +</code>
 +
 +The DHCP client will fetch the ip and the proper classless routes.
 +
 +**Make sure you disable Rebind protection. Whitelisting the sip service domain will not suffice.**
 +
 +**Additionally for this method you have to clone the original routers MAC if using the original credentials**
 +
 +SIP Configuration:
 +
 +Depending on whether you have fetched the credentials from the ISP's original router or whether you have applied for a "bring your own device" configuration, the settings will differ. For the first case, the SIP client configuration should be:
 +
 +  * Domain: `sip-voice.forthnet.gr`
 +  * Username: Your phone number (`30xxxxxxxxxx`)
 +  * Password: Your voip password (as fetched from the ISP's router)
 +  * Server: `sip-voice.forthnet.gr`
 +  * Port: `5060`
 +  * SIP Transport: `UDP`
 +  * SIP Address: `30xxxxxxxxxx@sip-voice.forthnet.gr`
 +  * Registry Server: `sip-voice.forthnet.gr`
 +
 +For the second case the following is what needs to be the client configuration
 +
 +  * Domain: `byod.nova.gr`
 +  * Username: Your phone number (`30xxxxxxxxxx`)
 +  * Password: Your voip password (from the email)
 +  * Server: `byod.nova.gr`
 +  * Port: `5060`
 +  * SIP Transport: `UDP`
 +  * SIP Address: `30xxxxxxxxxx@byod.nova.gr`
 +  * Registry Server: `byod.nova.gr`
 +  * Audio Codec: `PCMA` ONLY
 +
 +**Caution, the byod.nova.gr domain is only configured on the DNS servers of the telephony VLAN, **
 +
 +Alternatively you can do a custom DNS record if you don't want to use the ISP DNS
 +the IPv4 for byod.nova.gr is 10.50.131.150
  
 ===== Ireland ===== ===== Ireland =====
  
-=== Vodafone SIRO 1G ===+==== Vodafone SIRO 1G ====
  
 * igmpproxy need to be installed for TV * igmpproxy need to be installed for TV
Line 623: Line 1145:
  
 ''/etc/config/igmpproxy'' ''/etc/config/igmpproxy''
 +
 <code> <code>
 config igmpproxy config igmpproxy
Line 638: Line 1161:
  option zone lan  option zone lan
  option direction downstream  option direction downstream
 +</code>
 +
 +==== Pure Telecom 100Mb SIRO FTTC ====
 +
 +<code>
 +config atm-bridge 'atm'
 +        option vpi '1'
 +        option vci '32'
 +        option encaps 'llc'
 +        option payload 'bridged'
 +        option nameprefix 'dsl'
 +
 +config dsl 'dsl'
 +        option annex 'a'
 +        option line_mode 'vdsl'
 +        option ds_snr_offset '0'
 +        option xfer_mode 'ptm'
 +
 +config interface 'wan'
 +        option device 'dsl0.10'
 +        option proto 'pppoe'
 +        option username 'puretelecom@puretel.ie'
 +        option password 'broadband1'
 +        option ipv6 '0'
 +        option service 'internet'
 </code> </code>
  
 ===== Italy ===== ===== Italy =====
 +==== Aruba FTTH ====
 +This ISP in Italy is pretty easy to set up, and it is compliant to Italian law about the utilization of your own (compatible) modem/router. Also ipv6 works and ipv4.
 +The only thig to setup is a PPPoE connection with a 835 VLAN on the WAN port. Note that user and password are not necessary for authentication and can be whatever.
 +
 +With **OpenWrt 21.02** (with DSA):
 +
 +<code>
 +config interface 'wan'
 + option proto 'pppoe'
 + option username 'aruba'
 + option password 'aruba'
 + option ipv6 '1'
 + option device 'wan.835'
 +
 +config interface 'wan6'
 +    option proto 'dhcpv6'
 +    option reqaddress 'try'
 +    option reqprefix 'auto'
 +    option ifname '@wan'
 +</code>
 +
 +
 +With **OpenWrt 19.07** (with swconfig):
 +
 +<code>
 +config interface 'wan'
 +    option ifname 'eth0.835'
 +    option proto 'pppoe'
 +    option username 'aruba'
 +    option password 'aruba'
 +    option ipv6 '1'
 +
 +config interface 'wan6'
 +    option proto 'dhcpv6'
 +    option reqaddress 'try'
 +    option reqprefix 'auto'
 +    option ifname '@wan'
 +</code>
 +
 +==== TIM ====
 +TIM (a.k.a. Telecom Italia) uses the following PPPoE connection settings: [[https://www.tim.it/assistenza/assistenza-tecnica/guide-manuali/modem-generico#specifiche-tecniche-di-configurazione]].
 +VLAN 835 is required on your WAN port. In the following example, the phisical name of WAN interface is 'eth0' so with VLAN 835 will be 'eth0.835', but with different device can be somewhat like 'eth1.835'.
 +
 +Configuration with **OpenWrt 21.02** (with DSA):
 +
 +<code>
 +config interface 'wan'
 +    option ifname 'eth0.835'
 +    option proto 'pppoe'
 +    option username '[replace with your phone number]'
 +    option password 'timadsl'
 +    option ipv6 'auto'
 +</code>
 +
 ==== Tiscali ==== ==== Tiscali ====
 Tiscali uses the following ADSL PPPoA connection settings: [[https://assistenza.tiscali.it/internet-telefono/modem/guida/parametri-connessione]]. In order to configure the connection and bring up the dsl port after having flashed the firmware you have to follow these steps: Tiscali uses the following ADSL PPPoA connection settings: [[https://assistenza.tiscali.it/internet-telefono/modem/guida/parametri-connessione]]. In order to configure the connection and bring up the dsl port after having flashed the firmware you have to follow these steps:
Line 719: Line 1321:
 </code> </code>
 **IMPORTANT**: in the aforementioned configuration there`s a LAN bridge between two entries. This bridge has been created during the openWrt firmware installation because the target device is a Netgear DM200 modem/router with only one dsl interface and only one LAN port. **IMPORTANT**: in the aforementioned configuration there`s a LAN bridge between two entries. This bridge has been created during the openWrt firmware installation because the target device is a Netgear DM200 modem/router with only one dsl interface and only one LAN port.
 +
 ===== Netherlands ===== ===== Netherlands =====
-==== Many ISP's ====+ 
 +==== KPN FTTH ==== 
 + 
 +You can connect the WAN port of your router directly to the fiber termination box delivered by KPN using RJ-45. Internet will be delivered on VLAN 6 using PPPoE. The username/password combination is internet/internet. To get 1500 MTU (PPPoE is 1492 default due to 8 bytes overhead) you need to set the WAN port'MTU to 1508 bytes and then set the PPPoE interface to 1500 bytes. KPN is compliant with [[https://datatracker.ietf.org/doc/html/rfc4638|RFC4638]]. 
 + 
 +This is an example configuration of /etc/config/network with eth1 as the WAN port: 
 + 
 +<code> 
 +config device 
 + option name 'eth1' 
 + option mtu '1508' 
 + 
 +config device 
 + option type '8021q' 
 + option ifname 'eth1' 
 + option vid '6' 
 + option name 'eth1.6' 
 + 
 +config interface 'wan' 
 + option proto 'pppoe' 
 + option device 'eth1.6' 
 + option username 'internet' 
 + option password 'internet' 
 + option mtu '1500' 
 + option peerdns '0' 
 + list dns '8.8.8.8' 
 + list dns '8.8.4.4' 
 + option ipv6 '1' 
 + option metric '1' 
 + 
 +config interface 'wan6' 
 + option proto 'dhcpv6' 
 + option device 'pppoe-wan' 
 + option reqaddress 'try' 
 + option reqprefix 'auto' 
 + option peerdns '0' 
 + list dns '2001:4860:4860::8888' 
 + list dns '2001:4860:4860::8844' 
 + option metric '0' 
 +</code> 
 + 
 +==== KPN: OpenWrt behind the supplied kpn Box 12 modem ==== 
 + 
 +If you have the OpenWrt router's WAN port connected to your kpn Box 12 modem, you will notice that it's behind NAT and as such you won't be able to enjoy a proper internet experience. 
 + 
 +Don't get sad, though! You can set up the kpn Box 12 so that OpenWrt can automatically expose all ports through the NAT and also get IPv6 addresses for all your devices, without the modem or its firewall getting in your way. 
 + 
 +WARNING: This configuration will expose other devices you directly connect to the modem to the internet without any firewall! This won't be a problem if you connect other devices via your OpenWrt router. 
 +Especially IPv6-enabled devices would be at risk, as the following modem configuration allows any IPv6 device connected to it to expose any port to the internet. IPv4 devices will be stuck behind NAT, and all NAT ports will be reserved for the OpenWrt router. 
 + 
 +If you use a custom DNS on your computer, consider finding out the IP address of your KPN modem, which can be done by logging into your OpenWrt router -> ''Status'' -> ''Overview'' and scroll down until ''Network'' where the ''Gateway'' value in ''IPv4 Upstream'' is the IP address of your KPN modem. 
 +You can add this IP address to your computer's ''/etc/hosts'' file like so: 
 +<code> 
 +192.168.2.254  mijnmodem.kpn 
 +</code> 
 +where you replace ''192.168.2.254'' with the actual IP address of your KPN modem. 
 + 
 +Now you can go into your modem's settings page by going to http://mijnmodem.kpn and do the following: 
 +  - Log into the modem. 
 +  - If this is the first time logging into the modem, it's going to ask you to change the admin password. DO NOT AT ANY TIME click outside this dialog or cancel, as doing so will soft-brick your modem! If you do soft-brick it, either call KPN, or use a needle to push the reset switch on the device. 
 +  - Log back into the modem using the new password. 
 +  - Click ''My Modem''
 +  - Go to the ''LAN IPv4'' tab. 
 +  - Scroll down and click ''Add Reserved Address'' in the ''DHCP'' section. 
 +  - Select your OpenWrt router's MAC address in the ''Device Name'' column. 
 +  - Enter a simple IP address within the DHCP range, for example ''192.168.2.1''
 +  - Click ''Apply'' at the bottom of the page. 
 +  - Go back to the home page by clicking the kpn logo in the top left. 
 +  - Click ''Access Control''
 +  - Go to the ''IPv6 Pin-holing'' tab. 
 +  - Set ''Name'' to whatever you like, in my case ''All''
 +  - Set ''Device'' to ''Other''
 +  - Leave ''MAC address'' empty. Inserting any invalid value into this field will soft-brick the modem, so LEAVE IT EMPTY! 
 +  - Turn on the ''DMZv6'' toggle. 
 +  - Click ''Add'' 
 +  - Now go to the ''DMZ'' tab. 
 +  - Turn on the ''Enable'' toggle. 
 +  - Select your OpenWrt router from the MAC address dropdown menu. 
 +  - Your OpenWrt router's IP address should automatically appear in the ''Local host'' input field. 
 +  - Click ''Apply''
 + 
 +Now that we're done with the modem, we can set up OpenWrt. 
 +Here's the important snippet from ''/etc/config/network'': 
 +<code> 
 +config interface 'lan' 
 + option device 'br-lan' 
 + option proto 'static' 
 + option ipaddr '192.168.1.1' 
 + option netmask '255.255.255.0' 
 + option ip6assign '60' 
 + 
 +config interface 'wan' 
 + option proto 'dhcp' 
 + option device 'eth0' 
 + option hostname '*' 
 + option peerdns '0' 
 + list dns '8.8.8.8' 
 + list dns '8.8.4.4' 
 + 
 +config interface 'wan6' 
 + option device 'eth0' 
 + option proto 'dhcpv6' 
 + option reqaddress 'try' 
 + option reqprefix 'auto' 
 + option peerdns '0' 
 + list dns '2001:4860:4860::8888' 
 + list dns '2001:4860:4860::8844' 
 +</code> 
 +Note that OpenWrt can't get a prefix through Prefix Delegation, so you may disable it. It's there in the hopes that KPN someday adds Prefix Delegation support to the kpn Box 12, which would greatly simplify the configuration. 
 +Until KPN fixes this issue, we must relay DHCPv6, RA, and NDP with the following ''/etc/config/dhcp'' snippet: 
 +<code> 
 +config dhcp 'lan' 
 + option interface 'lan' 
 + option start '100' 
 + option limit '150' 
 + option leasetime '12h' 
 + option dhcpv4 'server' 
 + option dhcpv6 'relay' 
 + option ra 'relay' 
 + option ndp 'relay' 
 + 
 +config dhcp 'wan' 
 + option interface 'wan' 
 + option master '1' 
 + option ra 'relay' 
 + option dhcpv6 'relay' 
 + option ndp 'relay' 
 +</code> 
 +The important thing to take away from this config is that we essentially set up ''lan'' DHCPv6, Router Advertisements, and Neighbor Discovery to be relayed, where ''wan'' is the master. 
 + 
 +And now you should have a proper internet connection again, like you would expect after installing OpenWrt appliances in your network. The kpn Box 12 inserts a '':1'' after the prefix that you got assigned with your subscription. Besides that quirk, everything should work. 
 + 
 +==== Many ISPs ====
 Many DSL and Fiber ISPs use these settings. At least Telfort, Oxxio and Tweak use these. KPN, XS4ALL and Ziggo don't. Many DSL and Fiber ISPs use these settings. At least Telfort, Oxxio and Tweak use these. KPN, XS4ALL and Ziggo don't.
 Tweak [[https://www.tweak.nl/support/apparatuur-configureren.html|provides settings]] for xDSL and glassfiber. Tweak [[https://www.tweak.nl/support/apparatuur-configureren.html|provides settings]] for xDSL and glassfiber.
Line 900: Line 1635:
   - open the Device combo box and type 'eth0.6'   - open the Device combo box and type 'eth0.6'
   - enter PPP/CHAP username '98-42-xx-xx-xx-xx@internet' (use your KPN router MAC address), PPP/CHAP password 'ppp'   - enter PPP/CHAP username '98-42-xx-xx-xx-xx@internet' (use your KPN router MAC address), PPP/CHAP password 'ppp'
-  - hit Save, then Save&Apply+  - hit Save 
 +  - in the Devices tab change the MAC address of eth0.6 to match your KPN router MAC address (this might be optional) 
 +  - hit Save&Apply
   - if the WAN interface is in error state then reboot the modem   - if the WAN interface is in error state then reboot the modem
  
 The WAN MTU will be 1492, don't try to change it, no other values work. The WAN MTU will be 1492, don't try to change it, no other values work.
 A WAN_6 virtual dynamic interface will appear upon successful connection; you can delete any other WAN device and reset any other unused eth0 virtual device. A WAN_6 virtual dynamic interface will appear upon successful connection; you can delete any other WAN device and reset any other unused eth0 virtual device.
 +
 +==== Ziggo ====
 +
 +First put the modem in bridge mode (disabled routing options) via [[https://www.ziggo.nl/klantenservice/internet-wifi/bridge-modus/stappenplan-bridge-modus|this website]]. Then use the following network config:
 +
 +<code>
 +config interface 'wan'
 + option proto 'dhcp'
 + option device 'eth1'
 + option hostname '*'
 + option peerdns '0'
 + list dns '8.8.8.8'
 + list dns '8.8.4.4'
 +
 +config interface 'wan6'
 + option proto 'dhcpv6'
 + option device 'eth1'
 + option reqaddress 'try'
 + option reqprefix 'auto'
 + option peerdns '0'
 + list dns '2001:4860:4860::8888'
 + list dns '2001:4860:4860::8844'
 +</code>
 +
 +Remove the 'peerdns' and 'list dns' if you want to use Ziggo's DNS servers. These servers, however, do impose censorship on certain domains.
 +
 +===== New Zealand =====
 +==== Slingshot Fibre ====
 +
 +<code>
 +config interface 'wan'
 +        option proto 'dhcp'
 +        option device 'wan.10'
 +        option hostname '*'
 +
 +config interface 'wan6'
 +        option proto 'dhcpv6'
 +        option device 'wan.10'
 +        option reqaddress 'try'
 +        option reqprefix 'auto'
 +
 +config device
 +        option type '8021q'
 +        option ifname 'wan'
 +        option vid '10'
 +        option name 'wan.10'
 +</code>
 +
  
 ===== Portugal ===== ===== Portugal =====
Line 941: Line 1726:
  option target 'SNAT'  option target 'SNAT'
 </code> </code>
 +
 +
 +===== Slovakia =====
 +
 +==== Orange Slovensko ====
 +
 +[[https://www.orange.sk/|Orange Slovensko]] (the owner is France-based multinational telecommunications company [[https://www.orange.com/|Orange S.A.]]) offers FTTH service for their customers through the end CPE device.
 +
 +=== FTTH (Fiber) ===
 +Orange Slovensko uses the same IPv6 /64 prefix delegation method as AT&T does.
 +
 +At the present moment (August 2022) there is no known way to get a /60 or /62 IPv6 prefix delegated from the LAN port of the operator's CPE device. It is only possible to send a multiple PD requests, and to get a pool of multiple /64 blocks to have them assigned into different LAN interfaces on the downstream device. So, it is possible to use these obtained /64 subnets within your OpenWrt configuration and downstream client subnets or VLANs.
 +
 +Initial discussion and working OpenWrt configuration with the Orange Slovensko CPE device can be found in this post: [[https://forum.openwrt.org/t/ipv6-pd-60-for-downstream-openwrt-router-after-orange-slovensko-fiber/131707/8?u=alexq|Link to owrt forum]].
 +
 +Сonfiguration details are similar to the [[:docs:guide-user:network:wan:isp-configurations#fiber|AT&T ISP configuration]]:
 +all the 'magic' will be achieved by the ''kmod-macvlan'' that allows to create multiple //wan6// virtual interfaces (hence to request and obtain multiple IPv6 /64 blocks), and to assign these virtual //wan6// interfaces into appropriate DHCPv6 clients via ''ip6class'' and ''ip6assign 64'' settings. 
 +
 +
 +===== Spain =====
 +
 +==== DIGI ====
 +
 +DIGI uses PPPoE for FTTH connections, just need to call to their support number and ask for the authentication data. They offer optionaly VoIP but at the date they don't provide a way to configure, you must use the provided router if you want to have VoIP.
 +
 +=== FTTH (Fiber) ===
 +These settings are over a DSA switch and then over swconfig. You just need to, set VLAN 20 over WAN port and then configure the VLAN in the wan interface with PPPoE and the authentication data provided by technical support. No need to clone MAC address.
 +
 +== DSA: ==
 +Just set a VLAN 20 device over the wan port and then set the device for wan interface with the PPPoE authentication data.
 +<code>
 +config device
 + option type '8021q'
 + option ifname 'wan'
 + option vid '20'
 + option name 'wan.20'
 +
 +config interface 'wan'
 + option device 'wan.20'
 + option proto 'pppoe'
 + option username '*********@digi'
 + option password '********'
 + option ipv6 'auto'
 +
 +</code>
 +
 +With ipv6 auto a virtual interface wan_6 is spawned. If you want to rename it to wan6 or configure specific settings there is a way but out of scope in this page so you can refer to [[:docs:guide-user:network:ipv6:configuration#native_ipv6_connection|Native IPv6 connection]].
 +
 +== swconfig: ==
 +You must check the switch name and also the eth# you have for the wan port, in this example switch0 and eth0:
 +<code>
 +config interface 'wan'
 + option device 'eth0.20'
 + option proto 'pppoe'
 + option username '*********@digi'
 + option password '********'
 + option ipv6 'auto'
 +
 +config switch_vlan
 + option device 'switch0'
 + option vlan '3'
 + option ports '1t 6t'
 + option vid '20'
 +
 +</code>
 +
 +With ipv6 auto a virtual interface wan_6 is spawned. If you want to rename it to wan6 or configure specific settings there is a way but out of scope in this page so you can refer to [[:docs:guide-user:network:ipv6:configuration#native_ipv6_connection|Native IPv6 connection]].
 +
 +
 +==== Vodafone ====
 +WIP: Vodafone doesn't provide PPPoE data, you must, capture it by factory resetting the router, accessing it with generic auth data over internet, configuring port mirroring for the ppp interface to lan1 port and then with wireshark or the tool you want get the autoconfiguration data when you plug the ont rj45 or fiber cable to the router. This can be done for their non-integrated and integrated ont actual routers.
  
  
Line 961: Line 1817:
  option username '***************@turk.net'  option username '***************@turk.net'
  option password '****'  option password '****'
- option mtu '1492' 
  option ifname 'dsl0.35'  # VLAN ID: 35  option ifname 'dsl0.35'  # VLAN ID: 35
  
Line 984: Line 1839:
  option username '***************@turk.net'  option username '***************@turk.net'
  option password '****'  option password '****'
- option mtu '1492' 
  option ifname 'dsl0'   option ifname 'dsl0' 
  
 </code> </code>
  
 +==== Turk Telekom ====
 +Turk Telekom (a major ISP in Turkey, also known with the name TTNET) provides FTTH and FTTB services through PPPoE with VLAN tagging. You can ask customer support for your PPPoE username and password.
  
 +VLAN tagging is usually as follows:
  
 +  * VoIP: VLAN 46
 +  * Internet: PPPoE over VLAN 35
 +  * IPTV: VLAN 55 for [[https://www.tivibu.com.tr|tivibu]]
 +
 +A sample config should look like on OpenWrt 21.02 (with DSA):
 +
 +<code>
 +config interface 'wan'
 +    option device 'wan.35'
 +    option proto 'pppoe'
 +    option username 'xxxxxxx'
 +    option password 'xxxxxxx'
 +    option ipv6 'auto'
 +
 +config device
 +    option name 'wan.35'
 +    option type '8021q'
 +    option ifname 'wan'
 +    option vid '35'
 +</code>
 +
 +==== Turkcell Superonline ====
 +Turkcell Superonline provides FTTH and FTTB services through PPPoE with VLAN tagging. In addition, you have to spoof the WAN MAC address of the stock router.
 +
 +VLAN tagging is usually as follows:
 +
 +  * Internet: PPPoE (They only allow registered MAC addresses to authenticate with PPPoE. So you need to clone the WAN MAC address of the stock router)
 +  * IPTV: VLAN 103 (Priority 4) for [[https://tvplus.com.tr|TV+]]
 +
 +A basic WAN config should look like on OpenWrt 21.02 and up w/ DSA:
 +
 +<code>
 +config interface 'wan'
 + option device 'wan'
 + option proto 'pppoe'
 + option username 'xxxxxxxxxxxx@fiber'
 + option password 'xxxxxxx'
 + option ipv6 'auto'
 + option peerdns '0'
 + list dns '8.8.8.8'
 + list dns '8.8.4.4'
 +
 +config device
 + option name 'wan'
 + option macaddr 'XX:XX:XX:XX:XX:XX'
 +</code>
 +
 +**Note:** Turkcell Superonline does not share PPPoE credentials with you. So you have to capture them yourself from the stock router first.
 +
 +==== Turksat Kablonet ====
 +
 +Kablonet uses DHCP for Docsis and PPPoE for FTTH services.
 +
 +Basic WAN configs should look like:
 +=== DOCSIS ===
 +<code>
 +config interface 'wan'
 + option device 'wan'
 + option proto 'dhcp'
 + option ipv6 'auto'
 + option peerdns '0'
 + option dns '1.1.1.1'
 + option dns '1.0.0.1'
 +</code>
 +=== FTTH ===
 +<code>
 +config interface 'wan'
 + option device 'wan'
 + option proto 'pppoe'
 + option username 'xxxxxxxx@kablofiber'
 + option password 'xxxxxxxx'
 + option ipv6 'auto'
 + option peerdns '0'
 + option dns '1.1.1.1'
 + option dns '1.0.0.1'
 +</code>
 +**Note(FTTH):** If you are using the stock modem that was given make sure it's connected to your openwrt router on LAN1.
  
 +**Note2(FTTH):** PPPoE credentials can be acquired from [[https://online.turksatkablo.com.tr/|TurksatKablo Customer Web Interface]] or by calling them.
 ===== United Kingdom ===== ===== United Kingdom =====
  
-The information below is reproduced from the 'OpenWrt/LEDE Installation Guide for the BT Home Hub 5A', which can be downloaded from: +The information below is reproduced from the '1-OpenWrt/LEDE Installation Guide for the BT Home Hub 5A', which can be downloaded from: 
-[[https://openwrt.ebilan.co.uk/viewtopic.php?f=7&t=266|Ebilan forum]] +[[https://www.dropbox.com/sh/c8cqmpc6cacs5n8/AAA2f8htk1uMitBckDW8Jq88a?dl=0|Dropbox]]
-[[https://www.dropbox.com/sh/c8cqmpc6cacs5n8/AAA2f8htk1uMitBckDW8Jq88a?dl=0|Dropbox mirror]]+
  
  
Line 1067: Line 2001:
   * PTM (Packet Transfer Mode)   * PTM (Packet Transfer Mode)
   * Annex B, Tone A   * Annex B, Tone A
-  * VLAN 101+  * VLAN 101 (GEA lines use VLAN 2 for voice) 
 + 
 +[[https://support.aquiss.net/en/knowledgebase/article/generic-fttc-broadband-setup-and-router-settings|Aquiss]] uses the PPPoE protocol with authentication required. 
 + 
 +IPv6 is supported but disabled by default. Once a line goes active, you will need to enable IPv6 within the Aquiss ebilling area and wait for a prefix to be assigned. 
 +<code> 
 +config dsl 'dsl' 
 +    option annex 'b' 
 +    option tone 'a' 
 + 
 +config interface 'wan' 
 +    option ifname 'dsl0.101' 
 +    # option ifname 'ptm0.101' # for LEDE 17.01 
 +    option proto 'pppoe' 
 +    option ipv6 '1' # Aquiss has IPv6 but it needs to be enabled on your line first. Replace '0' to disable IPv6 
 +    option mtu '1458' 
 +    option username 'abb-username@aquiss.com' 
 +    option password 'XXXXXXX' # Provided by email or avaiable in Aquiss ebilling area (Circuit information) 
 +</code>
  
 [[https://www.bt.com/broadband/fibre|BT Broadband]] uses PPPoE protocol. [[https://www.bt.com/broadband/fibre|BT Broadband]] uses PPPoE protocol.
Line 1084: Line 2036:
     option username 'bthomehub@btinternet.com'     option username 'bthomehub@btinternet.com'
     option password ' ' # Apparently requires any non-empty password such as a space character or 'BT'.     option password ' ' # Apparently requires any non-empty password such as a space character or 'BT'.
 +</code>
 +For 22.03.X/23.X builds.
 +<code>
 +config atm-bridge 'atm'
 + option vpi '0'
 + option vci '38'
 + option encaps 'vc'
 + option payload 'bridged'
 + option nameprefix 'dsl'
 +
 +config dsl 'dsl'
 + option annex 'b'
 +        option tone 'a'
 + option ds_snr_offset '0'
 + option xfer_mode 'ptm'
 + option line_mode 'vdsl'
 +
 +config device
 + option name 'dsl0.101'
 + option type '8021q'
 + option ifname 'dsl0'
 + option vid '101'
 +
 +config interface 'wan'
 + option device 'dsl0.101'
 + option proto 'pppoe'
 + option username 'bthomehub@btbroadband.com'
 +        option password 'BT' # Apparently requires any non-empty password such as a space character or 'BT'.
 + option ipv6 '1' # BT Broadband has IPv6. Replace '0' to disable IPv6
 +        option multicast '1' # For BT TV, Remember to install imgproxy.
 +        
 +config interface 'wan6'
 +        option proto 'dhcpv6'
 +        option reqaddress 'try'
 +        option reqprefix 'auto'
 +        option ifname 'dsl0.101'
 </code> </code>
  
Line 1098: Line 2086:
     option proto 'pppoe'     option proto 'pppoe'
     option ipv6 '0' # EE has no IPv6. Replace '1' to enable IPv6     option ipv6 '0' # EE has no IPv6. Replace '1' to enable IPv6
-    option mtu '1492' 
     option username '56@fs' ' # see https://ee.co.uk/help/help-new/broadband-and-landline/home-broadband/what-are-my-home-broadband-internet-settings     option username '56@fs' ' # see https://ee.co.uk/help/help-new/broadband-and-landline/home-broadband/what-are-my-home-broadband-internet-settings
     option password 'XXXXX' # password that came with your EE router     option password 'XXXXX' # password that came with your EE router
Line 1104: Line 2091:
  
  
-[[https://www.shellenergy.co.uk/broadband|Shell Energy *fibre* (G.993.2=VDSL2)]] uses the PPPoE protocol:+[[http://web.archive.org/web/20210505225223/https://help.shellenergy.co.uk/hc/en-us/articles/360001044438-What-if-I-want-to-use-my-own-router-|Shell Energy *fibre* (G.993.2=VDSL2)]] uses the PPPoE protocol:
  
 <code> <code>
Line 1178: Line 2165:
     option proto 'pppoe'     option proto 'pppoe'
     option ipv6 '0' # Vodafone UK has no IPv6. Replace '1' to enable IPv6     option ipv6 '0' # Vodafone UK has no IPv6. Replace '1' to enable IPv6
-    option mtu '1492' 
     option username 'XXX@broadband.vodafone.co.uk'     option username 'XXX@broadband.vodafone.co.uk'
     #option username 'XXXX@businessbroadband.vodafone.co.uk # for business customers     #option username 'XXXX@businessbroadband.vodafone.co.uk # for business customers
Line 1202: Line 2188:
 </code> </code>
  
-====== General xDSL configuration (step by step) ======+==== Fibre Optic ==== 
 + 
 +=== Openreach Full Fibre (FTTP) === 
 + 
 +Openreach (a subsidiary owned by BT plc) provides fibre optic broadband to the home, [[https://www.openreach.com/fibre-broadband/fttp-providers|with various ISPs reselling Openreach services to end users]]. Any provider using the Openreach FTTP network requires an ONT (Optical Network Terminal) device fitted by Openreach to provide the fibre connection to the premises. This acts as the modem that will then connect to some form of CPE or router at the customer end via ethernet. 
 + 
 +== Aquiss == 
 + 
 +Aquiss uses PPPoE and DHCPv6. A standard PPPoE network interface with your Aquiss abb-xxxxxx@aquiss.com and password should get you connected with your IPv4 address. IPv6 (if enabled) will be automatically configured by a virtual interface with Obtain IPv6 address set to Automatic. You can alternatively set this to manual and create your own alias interface if required. 
 + 
 +IPv6 must be enabled on the broadband line within the Aquiss ebilling system with a prefix delegated before configuring IPv6. 
 + 
 +=== Alternative networks === 
 + 
 +Outside of Openreach other connection providers in the UK are referred to as alternative networks (alt-nets), these include: 
 + 
 +  * City Fibre 
 +  * Community Fibre 
 +  * HyperOptic 
 +  * Giganet 
 +  * Virgin Media (Uses both HFC and FTTP in some areas with DOCSIS) 
 + 
 +== City Fibre == 
 + 
 +City Fibre provide fibre networks to business and residential customers, with selected ISPs reselling the connection to end users. These include ISPs such as Vodafone, Giganet, TalkTalk and Zen Internet. 
 + 
 +VLAN: all traffic on the CityFibre network must be tagged as VLAN 911 or traffic will not flow. 
 + 
 +== Giganet == 
 + 
 +Giganet are a CityFibre and BT Openreach fibre reseller. They provide IPv4 and IPv6 connectivity to business and residential customers. They provide a static IPv4 address and a static IPv6 router address, with a /48 prefix for the client's network. 
 + 
 +DHCPv6 is used to IPv6 prefix delegation, but the IPv6 prefix must be released by the router before the prefix will be issued again to either the same router or to another router. If this doesn't happen, an error of NoPrefixAvail during DHCPv6 negotiation, and odhcpd will complain that there is a local route, but no prefix, so it doesn't issue IPv6 addresses to LAN clients. 
 + 
 +== Gigabit Networks == 
 +Gigabit networks provide residential broadband through Cityfibre. They operate CGNat and operate a DHCP based service. Their requirements web pag is here: [[https://support.gigabitnetworks.co.uk/portal/en/kb/articles/can-i-use-my-own-router-with-your-service]] You need to contact their order desk to confirm the required VLAN. They do filter based on the MAC address and you need to contact their support team to clear this binding. The engineer called this "Clear the DHCP Binding process for the ONT interface." 
 + 
 +These are a set of working steps with a Belkin RT3200. 
 +  * WAN VLAN tagging on the appropriate VLAN 
 +  * Disabled IPv6 
 +  * No hostname required. 
 +  * Contact their support and ask for "Clear the DHCP Binding process for the ONT interface." 
 + 
 + 
 +== Community Fibre == 
 + 
 +The Adtran ONT connects to any DHCP enabled router. Recommended to spoof the MAC of your router so it follows the provider one. 
 + 
 + 
 + 
 +===== United States ===== 
 + 
 +==== AT&T ==== 
 + 
 +[[https://www.att.com/internet/|AT&T Internet]] no longer offers DSL connections, but is offering FTTH service in certain markets. 
 + 
 +=== Fiber === 
 + 
 +These settings based on this post [[https://forum.openwrt.org/t/configure-dhcpv6c-on-wan-for-multiple-pd-requests-for-at-t-fiber/99371/39?u=_failsafe|Link to owrt forum]] 
 + 
 +AT&T Fiber connectivity with OpenWrt is most easily achieved via setting the AT&T gateway device into "IP passthrough" mode. The IP passthrough mode type should be set as //DHCPS-fixed// with the passthrough fixed MAC address set to the MAC address of the WAN interface to which your OpenWrt device is connected to the AT&T gateway device. In this configuration you will not be operating in a double-NAT mode as you would if you use the //DHCPS-dynamic// type of passthrough. 
 + 
 +Additionally, if you intend for the AT&T gateway device to act as transparently as possible while allowing your OpenWrt device to perform all typical firewall, NAT, and routing functions, you will also want to disable packet filters and turn off all firewall advanced features within your AT&T gateway device's Firewall settings sections. This may vary by AT&T gateway model, so please refer to available guides online as to how to disable those features for your particular AT&T gateway device. 
 + 
 +By default, AT&T enables IPv6 connectivity, but AT&T's IPv6 handling is suboptimal in that while it is DHCPv6-PD, the IPv6 subnet they provide to each customer is a /60 instead of a more desireable /56 (or even /48). Further, the AT&T gateway device is assigned the /60 prefix delegation (PD) and it does not pass that /60 PD down to the passthrough connected device. The AT&T gateway reserves eight (8) of the sixteen (16) /64 subnets within the /60 (64 - 60 = 4, so 2^4 = 16) for its own purposes. However, while certainly not as straight-forward as a true /56 PD granted to the OpenWrt WAN interface, it is possible to still use the remaining eight (8) /64 subnets within your OpenWrt configuration and downstream client subnets. 
 + 
 +In order to achieve the goal of requesting the additional /64 subnets from the PD, a separate /64 PD request must be sent to the AT&T gateway device, with a unique MAC address, for each /64 you wish to obtain. To meet this objective with odhcp6c, you need to create additional devices and interfaces stemming from the OpenWrt WAN interface. This requires **kmod-macvlan**: 
 + 
 +<code> 
 +opkg update && opkg install kmod-macvlan 
 +</code> 
 + 
 +With kmod-macvlan installed, in your /etc/config/network file create a 'macvlan' type device for each /64 subnet you wish to pull from the AT&T gateway. In this example, we will pull and use three /64 subnets, each for a separate client VLAN/subnet that OpenWrt handles: 
 + 
 +//Note: The 'macaddr' values in this example are arbitrary and can be set to any MAC address you choose. The key is to ensure each is unique within your entire OpenWrt device.// 
 + 
 +<code> 
 +config device 'vwan1' 
 + option name 'vwan1' 
 + option type 'macvlan' 
 + option ifname 'eth0' 
 + option macaddr '70:e7:cf:ae:f2:00' 
 + 
 +config device 'vwan2' 
 + option name 'vwan2' 
 + option type 'macvlan' 
 + option ifname 'eth0' 
 + option macaddr '70:e7:cf:ae:f2:01' 
 + 
 +config device 'vwan3' 
 + option name 'vwan3' 
 + option type 'macvlan' 
 + option ifname 'eth0' 
 + option macaddr '70:e7:cf:ae:f2:02' 
 +</code> 
 + 
 +The next step is to create a corresponding interface for each of the newly added devices. Again, in this example we are creating three where one is for 'LAN', one is for 'GUEST', and the third is for 'IOT': 
 + 
 +<code> 
 +config interface 'WAN6LAN' 
 + option proto 'dhcpv6' 
 + option peerdns '0' 
 + option device 'vwan1' 
 + option reqprefix '64' 
 + option reqaddress 'none' 
 + 
 +config interface 'WAN6GUEST' 
 + option proto 'dhcpv6' 
 + option device 'vwan2' 
 + option reqprefix '64' 
 + option peerdns '0' 
 + option reqaddress 'none' 
 + 
 +config interface 'WAN6IOT' 
 + option proto 'dhcpv6' 
 + option device 'vwan3' 
 + option reqaddress 'none' 
 + option reqprefix '64' 
 + option peerdns '0' 
 +</code> 
 + 
 +Finally, each of the client subnet interfaces needs to be set to hand out IPv6 addresses from its corresponding WAN6* IPv6 pool. This is achieved by using the //list ip6class// setting and //option ip6assign// option for a client facing interface in /etc/config/network: 
 + 
 +<code> 
 +config interface 'LAN' 
 + option proto 'static' 
 + option netmask '255.255.255.0' 
 + option ipaddr '192.168.1.1' 
 + option device 'eth1' 
 + list ip6class 'WAN6LAN' 
 + option ip6assign '64' 
 + 
 +config interface 'GUEST' 
 + option proto 'static' 
 + option netmask '255.255.255.0' 
 + option ipaddr '192.168.9.1' 
 + option device 'eth1.9' 
 + list ip6class 'WAN6GUEST' 
 +        option ip6assign '64' 
 + 
 +config interface 'IOT' 
 + option proto 'static' 
 + option netmask '255.255.255.0' 
 + option ipaddr '192.168.99.1' 
 + option device 'eth1.99' 
 + list ip6class 'WAN6IOT' 
 +        option ip6assign '64' 
 +</code> 
 + 
 +Bonus step: Because you no longer will be assigning addresses based on your WAN interface's PD, you can disable the request to pull a PD on your WAN interface by adding this to your /etc/config/network file (on your WAN interface): 
 + 
 +<code> 
 +option reqprefix 'no' 
 +</code> 
 + 
 +Your WAN interface will still request a usable IPv6 (SLAAC) address from the AT&T gateway for OpenWrt purposes. 
 + 
 +===== General xDSL configuration (step by step) =====
  
   - Connect to box:<code>ssh root@192.168.1.1</code>   - Connect to box:<code>ssh root@192.168.1.1</code>
  • Last modified: 2024/12/06 04:47
  • by simtcrom