Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: 1 ... 16 17 [18] 19 20 ... 31

Author Topic: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)  (Read 66588 times)

j0hn

  • Kitizen
  • ****
  • Posts: 3155
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #255 on: January 17, 2019, 06:10:39 PM »

Need more details.

Is it being used as a bridge modem or full modem router?

If being used as a bridge modem please login to the Zyxel via telnet and run

Code: [Select]
ifconfig
and post the results here
Logged
BT FTTP 160/30 - BQM - speed test

GigabitEthernet

  • Kitizen
  • ****
  • Posts: 1987
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #256 on: January 17, 2019, 06:13:40 PM »

Thanks for the quick response. It's in bridge mode.


Code: [Select]
bcmsw     Link encap:Ethernet  HWaddr 04:BF:6D:AF:5D:00 
          UP BROADCAST RUNNING MULTICAST  MTU:2048  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Base address:0xda00


br0       Link encap:Ethernet  HWaddr 04:BF:6D:AF:5D:00 
          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::6bf:6dff:feaf:5d00/64 Scope:Link
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1508  Metric:1
          RX packets:2605 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2773 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:255798 (249.8 KiB)  TX bytes:1959116 (1.8 MiB)


eth0      Link encap:Ethernet  HWaddr 04:BF:6D:AF:5D:00 
          inet6 addr: fe80::6bf:6dff:feaf:5d00/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:2048  Metric:1
          RX packets:43518 errors:0 dropped:0 overruns:0 frame:0
          TX packets:84514 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8066813 (7.6 MiB)  TX bytes:101613799 (96.9 MiB)
         


eth0.0    Link encap:Ethernet  HWaddr 04:BF:6D:AF:5D:00 
          inet6 addr: fe80::6bf:6dff:feaf:5d00/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:2048  Metric:1
          RX packets:43178 errors:0 dropped:0 overruns:0 frame:0
          TX packets:83776 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:8973718 (8.5 MiB)  TX bytes:100310619 (95.6 MiB)


eth1      Link encap:Ethernet  HWaddr 04:BF:6D:AF:5D:00 
          UP BROADCAST MULTICAST  MTU:2048  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


eth1.0    Link encap:Ethernet  HWaddr 04:BF:6D:AF:5D:00 
          inet6 addr: fe80::6bf:6dff:feaf:5d00/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:2048  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:121 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:28422 (27.7 KiB)


eth2      Link encap:Ethernet  HWaddr 04:BF:6D:AF:5D:00 
          UP BROADCAST MULTICAST  MTU:2048  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
         


eth2.0    Link encap:Ethernet  HWaddr 04:BF:6D:AF:5D:00 
          inet6 addr: fe80::6bf:6dff:feaf:5d00/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:2048  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:118 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:28174 (27.5 KiB)


eth3      Link encap:Ethernet  HWaddr 04:BF:6D:AF:5D:00 
          UP BROADCAST MULTICAST  MTU:2048  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
         


eth3.0    Link encap:Ethernet  HWaddr 04:BF:6D:AF:5D:00 
          inet6 addr: fe80::6bf:6dff:feaf:5d00/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:2048  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:114 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:27790 (27.1 KiB)


lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:134 errors:0 dropped:0 overruns:0 frame:0
          TX packets:134 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:8208 (8.0 KiB)  TX bytes:8208 (8.0 KiB)


ptm0      Link encap:Ethernet  HWaddr 04:BF:6D:AF:5D:00 
          inet6 addr: fe80::6bf:6dff:feaf:5d00/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1508  Metric:1
          RX packets:87958 errors:0 dropped:0 overruns:0 frame:0
          TX packets:39340 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:95165230 (90.7 MiB)  TX bytes:8447363 (8.0 MiB)


ptm0.1    Link encap:Ethernet  HWaddr 04:BF:6D:AF:5D:00 
          UP BROADCAST RUNNING MULTICAST  MTU:1508  Metric:1
          RX packets:68683 errors:0 dropped:0 overruns:0 frame:0
          TX packets:35488 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:82295699 (78.4 MiB)  TX bytes:7730846 (7.3 MiB)
Logged

j0hn

  • Kitizen
  • ****
  • Posts: 3155
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #257 on: January 17, 2019, 06:54:21 PM »

It worked.
Just the router to look at.

What model is the router? Does it definitely support RFC4638 ?
Does it allow you to set 1500 MTU or only 1492?

What's the ISP?
Logged
BT FTTP 160/30 - BQM - speed test

GigabitEthernet

  • Kitizen
  • ****
  • Posts: 1987
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #258 on: January 17, 2019, 07:33:05 PM »

It's a TP-LINK Archer C7 running OpenWrt. I've set the MTU to 1508 in the web interface.

The ISP is BT.
Logged

underzone

  • Reg Member
  • ***
  • Posts: 356
Logged
Plusnet 80/20, Huawei 288, Zyxel VMG8924-B10A (bridge mode with 1500 MTU, thanks to johnson), Netgate SG-1100 (pfsense)

GigabitEthernet

  • Kitizen
  • ****
  • Posts: 1987
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #260 on: January 17, 2019, 09:23:47 PM »

Not Found

The requested URL /mtu-test.php was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Logged

burakkucat

  • Global Moderator
  • Senior Kitizen
  • *
  • Posts: 31041
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #261 on: January 17, 2019, 10:19:31 PM »

Not Found

The requested URL /mtu-test.php was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

That's very odd.  ???

http://www.letmecheck.it/my-ip.php works for me.
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.

GigabitEthernet

  • Kitizen
  • ****
  • Posts: 1987
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #262 on: January 17, 2019, 11:37:37 PM »

I'm on BT, it must be a BT issue with accessing that site.

Regardless.

Code: [Select]
ping -D -s 1472 www.bbc.co.uk
PING gtmlivelive-eu-c-1nlbwwwcouk-17e0f31403454351.elb.eu-central-1.amazonaws.com (3.120.156.170): 1472 data bytes
556 bytes from 192.168.1.1: frag needed and DF set (MTU 1492)
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
 4  5  00 dc05 dd69   0 0000  40  01 f586 192.168.1.102  3.120.156.170


Request timeout for icmp_seq 0
556 bytes from 192.168.1.1: frag needed and DF set (MTU 1492)
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
 4  5  00 dc05 6093   0 0000  40  01 725d 192.168.1.102  3.120.156.170


Request timeout for icmp_seq 1
556 bytes from 192.168.1.1: frag needed and DF set (MTU 1492)
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
 4  5  00 dc05 8dd9   0 0000  40  01 4517 192.168.1.102  3.120.156.170

Logged

j0hn

  • Kitizen
  • ****
  • Posts: 3155
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #263 on: January 18, 2019, 12:28:11 AM »

You need to disable ipv6 temporarily to use
http://www.letmecheck.it/my-ip.php

Technically the MTU is 1500, that's what I set in my router.
It's 1492 without this patch.

Perhaps Open-WRT want it set as 1508 I've no experience with that.

edit: should have asked earlier, can you run "ifconfig" on the router also and post the results.
« Last Edit: January 18, 2019, 12:33:07 AM by j0hn »
Logged
BT FTTP 160/30 - BQM - speed test

johnson

  • Reg Member
  • ***
  • Posts: 787
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #264 on: January 18, 2019, 07:47:01 AM »

I flashed the VMG1312 firmware from GitHub on my modem and 1500 MTU isn't working :(

It's a TP-LINK Archer C7 running OpenWrt. I've set the MTU to 1508 in the web interface.

If your router uses a switch with vlans for the wan and lan interfaces you need to set the root interface to 1508 then set it back to 1500 for the lan interface that inherits from it. See:

https://forum.archive.openwrt.org/viewtopic.php?id=51326

I have a BTHH5A and an x86 machine running openWRT which only required 1508 set in the web interface and a tp-link wdr3600 that needed the main switch set to 1508 then the subsequent 'lan' interface set back to 1500.

Have a look at your /etc/config/network file and if the interfaces for wan and lan have the form eth0.1 eth0.2 or similar then this should do the trick.
Logged

jhm

  • Member
  • **
  • Posts: 25
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #265 on: January 30, 2019, 08:17:18 AM »

A new version of the VMG3925-B10B firmware is now up on:

https://github.com/trejan/VMG3925-B10B

This contains (i) the jumbo frames patch; and (ii) a mechanism to sync the admin user password to supervisor + root.

The above now updated to the latest firmware - V5.13(AAVF.12)C0 - with the following:

Quote
Bootbase version : V1.63 | 05/25/2018 17:40:14
Firmware version : V5.13(AAVF.12)C0
Kernel version: 3.4.11
DSL mode code version: A2pv6F039x6
DSL driver version: d26s
WLAN code version: 7.14.164.20.cpe4.16L05.0-kdb
3G WWAN package version: 1.18
« Last Edit: January 30, 2019, 08:21:14 AM by jhm »
Logged

johnson

  • Reg Member
  • ***
  • Posts: 787
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #266 on: February 15, 2019, 11:07:16 AM »

Inspired by some PMs with snadge about getting full 1500 MTU on these devices when used as a router I have found a few things out after putting an 8324 on my line as a full router with stock firmware.

The commands required with unmodified firmware are as follows:

Code: [Select]
ifconfig ptm0 mtu 1508
ifconfig ptm0.1 mtu 1508

This will cause the ppp session to break, timeout and reconnect. The process takes 2.5 – 3 minutes and you will lose internet connectivity but not sync.

After the new ppp session is created it must be changed:

Code: [Select]
ifconfig ppp2.1 mtu 1500

At least with my testing (many times) this always resulted in successful 1500 byte pings. One caveat is that when quickly changing between them it is sometimes required to disable and re-enable your networking adapter to get accurate results with the ping test (on linux at least).

This leads me to the conclusion that even if using the devices as routers the modified firmware is desirable as no drop and wait for reconnect of the ppp session is required. Of the two modifications one is to bring up all the ptm interfaces with 1508 MTU by default, so only the instant “ifconfig ppp2.1 mtu 1500” is required, which is what I believe spring was talking about all along.

Given this single command that causes no loss of session or sync is all thats required with the baby jumbo frames patches applied I thought I would make a firmware with the most basic of scripts to check the current MTU and change if required:

Code: [Select]
#!/bin/bash

waitTime=60

interface="/sys/devices/virtual/net/ppp2.1/mtu"

sleep 50

while [ 1 ]
do

    if [ -f $interface ]
    then
        currentMtu=`cat $interface`
        if [ $currentMtu -eq 1492 ]
        then
            echo 1500 > $interface
        fi
    fi

    sleep $waitTime

done

Just tests the if the interface exists and if so checks for 1492 and changes to 1500. Couldnt be simpler.

I would have liked to change the ppp negotiation so it comes up at 1500 be default but after a decent amount of trying could not. I tried changing the GUI so 1500 was accepted and changing all references to the 1492 limit in the pppd program to no avail. I suspect (as always) that one of the closed source binarys supplied that takes the value from the web interface and supplies it to the pppd program/commits it to config has its own checks that default to 1492.

So, for anyone running an 8924/8324 as a full router (can make one for 1312s but doubt people are using them in this way) this firmware has the jumbo frames patches and the script above running from boot:

https://www.dropbox.com/s/b7b5gwzwteysk9t/8924-B10A-AAKL24-router1500.bin?dl=0

Have flashed to my 8324, connected to a line and it works as intended, but as always you are flashing at your own risk.

Any questions please ask!  :)
Logged

underzone

  • Reg Member
  • ***
  • Posts: 356
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #267 on: February 15, 2019, 11:45:17 AM »

Very clever. Great work!

 ;)
Logged
Plusnet 80/20, Huawei 288, Zyxel VMG8924-B10A (bridge mode with 1500 MTU, thanks to johnson), Netgate SG-1100 (pfsense)

snadge

  • Kitizen
  • ****
  • Posts: 1264
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #268 on: February 15, 2019, 05:32:39 PM »

Having tried this FW for Johnson I got some strange results.

I found that my connection worked on SOME websites, Kitz being one that doesn't work, this was with a windows MTU of 1500, I did ping 1742 tests and they worked also, TELNET access to the router is no longer possible? even though it was accessible shortly after the fw swap.

WINDOWS MTU VALUE:
1492 = working websites / Speedtest = 73Mbit / ping test 1472 = FAIL
1500 = partially working websites / Speedtest = 21Mbit / ping test 1472 = PASS

Iam at a loss as to why telnet access no longer works? or why the above settings give me the results they do

current windows MTU is 1492 as it only works properly with that and this is speedguides test results:

Quote
MTU = 1492
MTU is optimized for PPoE DSL broadband. If not, consider raising MTU to 1500 for optimal throughput.
MSS = 1452
MSS is optimized for PPPoE DSL broadband. If not, consider raising your MTU value.
Default TCP Receive Window (RWIN) = 262656
RWIN Scaling (RFC1323) = 8 bits (scale factor: 2^8=256)
Unscaled TCP Receive Window = 1026

In Windows 10, unless "TCP/IP Auto-Tuning" is disabled, only the Current TCP Window is displayed. Use the latest TCP Optimizer for tweaking.
You seem to be using Google Chrome. Note that Chrome can modify the TCP Window for sockets it creates under some OSes, and therefore servers may not get your OS-assigned RWIN value. FAQ
RWIN is not multiple of MSS. If your OS supports setting RWIN directly, consider changing it to a multiple of MSS for optimum performance.
Other RWIN values that might work well with your current MTU/MSS:
63888  (up to 2 Mbit lines, depending on latency. MSS * 44)
127776 (1-5 Mbit lines, depending on latency. MSS * 44 * 2)
255552 (2-15 Mbit lines, depending on latency. MSS * 44 * 2^2)
511104 (10-30 Mbit lines, depending on latency. MSS * 44 * 2^3)
1022208 (30-100 Mbit lines depending on latency. MSS * 44 * 2^4)
bandwidth * delay product (Note this is not a speed test):

Your current TCP Window limits you to: 10506 kbps (1313 KBytes/s) @ 200ms latency
Your current TCP Window limits you to: 4202 kbps (525 KBytes/s) @ 500ms latency
MTU Discovery (RFC1191) = ON
Time to live left = 48 hops
TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349) = 00000010 (2)
Precedence (priority) = 000 (routine)
Delay = 0 (normal delay)
Throughput = 0 (normal throughput)
Reliability = 0 (normal reliability)
Cost = 1 (low cost)
Check bit = 0 (correct, 8th checking bit must be zero)
 
DSCP (DiffServ) = CS0 000000 (0) - class 0, default traffic (RFC 2474).
« Last Edit: February 15, 2019, 05:37:17 PM by snadge »
Logged
Zyxel VMG8924-B10A <-> PlusNET <-> Eci DSLAM
Sync: 60,000k <-> Snr: 6dB <-> FTTP arriving soon :) 900Mbps

j0hn

  • Kitizen
  • ****
  • Posts: 3155
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #269 on: February 15, 2019, 06:01:46 PM »

Any reason you're tweaking the MTU value in Windows?
Logged
BT FTTP 160/30 - BQM - speed test
Pages: 1 ... 16 17 [18] 19 20 ... 31