1
Sítě / Re:Netflix po IPv6 od Metronetu
« kdy: 17. 01. 2021, 08:17:48 »
V "/ipv6 dhcp-client" má být pool-prefix-length=64 ?
Já tam mám 56.
prefix-hint=::/56 mám také.
Já tam mám 56.
prefix-hint=::/56 mám také.
Zobrazit příspěvky
Tato sekce Vám umožňuje zobrazit všechny příspěvky tohoto uživatele. Prosím uvědomte si, že můžete vidět příspěvky pouze z oblastí Vám přístupných.
Stran: [1]
2
Sítě / Re:Netflix po IPv6 od Metronetu
« kdy: 16. 01. 2021, 12:51:10 »Zatím to vypadá funkčně, ale to občas vypadalo i při špatném MTU. Budu to chvíli testovat a uvidím.
Ještě jsem si všiml, že mám hodnotu L2 MTU všude o 2 nižší oproti vám. Nemohlo by to taky dělat problémy?
Tak to fakt nevím.Jsem amater.
Nastavení Mikrotiku dělám podle toho co najdu na internetu.
3
Sítě / Re:Netflix po IPv6 od Metronetu
« kdy: 16. 01. 2021, 12:39:24 »A teď vidím že máte /interface vlan MTU 1492.
Já tam mám 1500.
Takže na PPPoE klienta mám dát Max MTU 1454, a na VLAN + všechny ethernety dát 1500?
Já to tak mám.
Vyskoušejteto.
Flags: D - dynamic, X - disabled, R - running, S - slave
# NAME TYPE ACTUAL-MTU L2MTU
0 R ether1 ether 1500 1598
1 RS ether2 ether 1500 1598
2 RS ether3 ether 1500 1598
3 RS ether4 ether 1500 1598
4 S ether5 ether 1500 1598
5 R VLAN 848 vlan 1500 1594
6 R ;;; defconf
bridge bridge 1500 1598
7 R ;;; VDSL_METRONET
pppoe-out1 pppoe-out 1454
4
Sítě / Re:Netflix po IPv6 od Metronetu
« kdy: 16. 01. 2021, 12:32:07 »
A teď vidím že máte /interface vlan MTU 1492.
Já tam mám 1500.
Já tam mám 1500.
5
Sítě / Re:Netflix po IPv6 od Metronetu
« kdy: 16. 01. 2021, 12:22:16 »
Mám IPv6/IPv4 VDSL Metronet - terminátor - mikrotik.
Na pppoe interface mám MTU 1454.Netflix jede.
https://www.dslreports.com/forum/r25398349-Optimal-MTU-size-for-ADSL-make-your-internet-faster
Optimal MTU size for ADSL -- make your internet faster.
There is often an incorrect assumption that bigger is always better. The maximum allowable packet size (MTU) for a PPPoE connection is 1492 bytes, however, the optimal MTU is actually 1454 bytes.
The protocol overhead (TCP, IP, PPP, PPPoE, Ethernet, AAL5, and ATM) of using a 1492 byte MTU is 16.80%.
By contrast, the protocol overhead using a 1454 byte MTU is 16.20%.
Although not a staggering difference, using a lower MTU actually reduces ATM overhead by about 0.6% and will thus yield a corresponding increase in user thoroughput: .06% * 1.5Mbps = ~+90Kbps
If you want to understand the details of exactly why overhead is lower, read on:
PPPoE 1492 byte Frame:
Portion Bytes
TCP/IP Payload 1492
PPP Headers +2
PPPoE Headers +6
Ethernet Headers +18
Total Frame Size 1518
Thus the total frame size when using a 1492 byte MTU, is actually 1518 bytes.
When a packet is converted to an ATM cell stream it is broken down into multiple cells of 53bytes each (48 bytes of user data and bytes of ATM header information).
1518 / 48 bytes= 31 cells plus a 30 byte remainder
Unlike Ethernet, ATM cells are fixed length...they must ALWAYS be 53 bytes long. Thus, the first 31 cells will contain 48 bytes of user data, however, the last cell will only be partially filled with 30 bytes of data. The last cell will also hold the Segmentation and Reassmbly (SAR) Trailer which is 8 bytes long. The SAR Trailer tells your ASDL modem how to reassmble the 32 cells back into the 1518 byte packet. Since the last cell will only have 30 data bytes, plus 8 SAR Trailer bytes, the remaining 10 bytes will simply be marked as cell padding (and is thus, wasted space).
The 10 bytes of cell padding is precisely where the 0.6% overhead comes from (10 bytes / 1452 bytes) = 0.68%
Note: When using a 1492 byte MTU, TCP and IP headers account for 40 bytes, thus the amount of user data is 1452 bytes (hence, we use 1452 bytes in the above calculations).
By contrast, here's what happens when we reduce our MTU to 1454 bytes:
PPPoE 1454 byte Frame:
Portion Bytes
TCP/IP Payload 1454
PPP Headers +2
PPPoE Headers +6
Ethernet Headers +18
Total Frame Size 1480
1480 / 48 bytes= 30 cells plus a 40 byte remainder
Thus, the first 30 cells will contain 48 bytes of user data, and the last cell will 40 bytes of data, plus the 8 byte SAR Trailer. Since the frame and associated ATM overhead fit exactly in to 31 cells, a 1454 byte MTU eliminates all ATM cell padding overhead.
Na pppoe interface mám MTU 1454.Netflix jede.
https://www.dslreports.com/forum/r25398349-Optimal-MTU-size-for-ADSL-make-your-internet-faster
Optimal MTU size for ADSL -- make your internet faster.
There is often an incorrect assumption that bigger is always better. The maximum allowable packet size (MTU) for a PPPoE connection is 1492 bytes, however, the optimal MTU is actually 1454 bytes.
The protocol overhead (TCP, IP, PPP, PPPoE, Ethernet, AAL5, and ATM) of using a 1492 byte MTU is 16.80%.
By contrast, the protocol overhead using a 1454 byte MTU is 16.20%.
Although not a staggering difference, using a lower MTU actually reduces ATM overhead by about 0.6% and will thus yield a corresponding increase in user thoroughput: .06% * 1.5Mbps = ~+90Kbps
If you want to understand the details of exactly why overhead is lower, read on:
PPPoE 1492 byte Frame:
Portion Bytes
TCP/IP Payload 1492
PPP Headers +2
PPPoE Headers +6
Ethernet Headers +18
Total Frame Size 1518
Thus the total frame size when using a 1492 byte MTU, is actually 1518 bytes.
When a packet is converted to an ATM cell stream it is broken down into multiple cells of 53bytes each (48 bytes of user data and bytes of ATM header information).
1518 / 48 bytes= 31 cells plus a 30 byte remainder
Unlike Ethernet, ATM cells are fixed length...they must ALWAYS be 53 bytes long. Thus, the first 31 cells will contain 48 bytes of user data, however, the last cell will only be partially filled with 30 bytes of data. The last cell will also hold the Segmentation and Reassmbly (SAR) Trailer which is 8 bytes long. The SAR Trailer tells your ASDL modem how to reassmble the 32 cells back into the 1518 byte packet. Since the last cell will only have 30 data bytes, plus 8 SAR Trailer bytes, the remaining 10 bytes will simply be marked as cell padding (and is thus, wasted space).
The 10 bytes of cell padding is precisely where the 0.6% overhead comes from (10 bytes / 1452 bytes) = 0.68%
Note: When using a 1492 byte MTU, TCP and IP headers account for 40 bytes, thus the amount of user data is 1452 bytes (hence, we use 1452 bytes in the above calculations).
By contrast, here's what happens when we reduce our MTU to 1454 bytes:
PPPoE 1454 byte Frame:
Portion Bytes
TCP/IP Payload 1454
PPP Headers +2
PPPoE Headers +6
Ethernet Headers +18
Total Frame Size 1480
1480 / 48 bytes= 30 cells plus a 40 byte remainder
Thus, the first 30 cells will contain 48 bytes of user data, and the last cell will 40 bytes of data, plus the 8 byte SAR Trailer. Since the frame and associated ATM overhead fit exactly in to 31 cells, a 1454 byte MTU eliminates all ATM cell padding overhead.
Stran: [1]
