after fiddling around with the settings for the provider WIND in Greece I wanted to share with you the config for the Turris Omnia as VDSL router:
There is an ISP router (branded CPE from ZTE, Modell H288A).
It was originally set up as VDSL Router with the following details:
Link Encapsulation: G.993.2_Annex_K_PTM
DSL Transfer Mode: PTM
IP Version: IPv4
Link Type: PPP
PPP Transfer Mode: PPPoE
VLAN ID: 835
My wonderful Turris Omnia was plugged as LAN client and set up with simple DHCP setup (double NAT so to say).
Turris OS version: 5.1.10
Turris OS branch: HBS
Kernel version: 4.14.222
Here is the config I used to get it working with the Turris Omnia to log in as DSL router via PPPoE and keep the ZTE H288A as VOIP client for the phone line. This has to stay that way, at least for now (ISP says VOIP only with the ZTA H288A).
On the ZTE H288A:
- delete the VDSL internet connection
- keep the VOIP connection and DSL synchronization running
- Set up a bridge connection with DSL Transfer Mode PTM and VLAN on with VLAN ID 835
- Set up port binding for the bridge connection on port LAN2 (where the Turris is plugged as WAN client in my case)
Then set up the Turris OS as WAN client with PPPoE.
Here is the config:
$ cat /etc/config/network
config interface 'loopback' option ifname 'lo' option proto 'static' option ipaddr '127.0.0.1' option netmask '255.0.0.0' config globals 'globals' option ula_prefix '***' config interface 'lan' option type 'bridge' option proto 'static' option netmask '255.255.255.0' option ip6assign '60' option bridge_empty '1' list ifname 'lan0' list ifname 'lan1' list ifname 'lan2' list ifname 'lan3' option _turris_mode 'managed' option ipaddr '***' config interface 'guest_turris' option enabled '1' option type 'bridge' option proto 'static' option ipaddr '***' option netmask '255.255.255.0' option bridge_empty '1' list ifname 'lan4' config interface 'wan' option ifname 'eth2' option proto 'pppoe' option password '***' option ipv6 'auto' option mtu '1492' option username '***' option type 'bridge' config interface 'wan6' option ifname '@wan' option proto 'dhcpv6'
Note that the ZTE H288A is taking care of tagging the packets with VLAN ID 835. No VLAN tagging needed from Turris OS / openwrt.
Here is my netperf results:
$ speedtest-netperf.sh [date/time] Starting speedtest for 60 seconds per transfer session. Measure speed to netperf.bufferbloat.net (IPv4) while pinging gstatic.com. Download and upload sessions are sequential, each with 5 simultaneous streams. .............................................................. Download: 83.47 Mbps Latency: [in msec, 62 pings, 0.00% packet loss] Min: 43.500 10pct: 43.600 Median: 44.300 Avg: 46.250 90pct: 51.500 Max: 67.600 CPU Load: [in % busy (avg +/- std dev), 60 samples] cpu0: 16.4 +/- 16.5 cpu1: 20.0 +/- 21.0 Overhead: [in % used of total CPU available] netperf: 5.4 .............................................................. Upload: 9.42 Mbps Latency: [in msec, 51 pings, 0.00% packet loss] Min: 43.700 10pct: 44.000 Median: 46.200 Avg: 85.882 90pct: 49.900 Max: 1089.000 CPU Load: [in % busy (avg +/- std dev), 60 samples] cpu0: 16.1 +/- 14.5 cpu1: 18.5 +/- 15.9 Overhead: [in % used of total CPU available] netperf: 0.5