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 ... 4 5 [6] 7 8 ... 31

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

spring

  • Reg Member
  • ***
  • Posts: 342
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #75 on: May 11, 2018, 04:34:26 PM »

Yeah, just for as long as the WAN connection held.
Logged
No one knows what is the taste of the void.

Weaver

  • Senior Kitizen
  • ******
  • Posts: 10274
  • Retd s/w dev; A&A; 3x7km lines; Firebrick; IPv6
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #76 on: May 11, 2018, 06:32:03 PM »

Damn that is such a total disappointment, sounds like the author has got some more work to do?

Could any kitizen fix it properly?
Logged

burakkucat

  • Global Moderator
  • Senior Kitizen
  • *
  • Posts: 34378
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #77 on: May 11, 2018, 06:54:17 PM »

The fix is for using a VMG1312-B10A in bridging modem mode.

No "fix" is required for a VMG1312-B10A in modem/router mode.
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.

spring

  • Reg Member
  • ***
  • Posts: 342
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #78 on: May 11, 2018, 07:32:02 PM »

Well if someone else could confirm my experience, it'd be something to work on for "the next" release.
Logged
No one knows what is the taste of the void.

johnson

  • Reg Member
  • ***
  • Posts: 787
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #79 on: May 11, 2018, 11:10:09 PM »

Damn that is such a total disappointment, sounds like the author has got some more work to do?

Could any kitizen fix it properly?

No, it appears this thread has confused spring.

The changed firmware is to make 1508 mtu work while the device is being used as a modem (as per thread title) in bridge mode. From his previous posts (setting ppp session parameters over telnet on the VMG1312) he is using it as a modem/router, in which case he only needed to set the MTU to 1500 in the web interface. His method of changing the ppp session is of course not persistent, just as changing it on your router by direct commands would not survive a reboot.

Maybe I should edit the OP to make it even clearer we are talking about bridge mode?
Logged

burakkucat

  • Global Moderator
  • Senior Kitizen
  • *
  • Posts: 34378
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #80 on: May 11, 2018, 11:34:59 PM »

Maybe I should edit the OP to make it even clearer we are talking about bridge mode?

Yes, please, that would be helpful.
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.

johnson

  • Reg Member
  • ***
  • Posts: 787
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #81 on: May 11, 2018, 11:54:17 PM »

Yes, please, that would be helpful.

I dont seem to be able to edit the first post, might I suggest this: If you dont mind doing the honours burakkucat.

Quote
The often suggested ZyXEL modems on this forum have great performance, but to my knowledge none support RFC 4638 with MTUs over 1492 for PPPoE connections in bridge mode. As far as I understand, all BT based FTTC connections should support it, but working examples to google are thin on the ground.

Other modems I am aware of with BCM63168 chipset:
Billion 8800nl
Netgear D6400
BT HH5B?

Does anyone have experience with one that can support over 1492 MTU when used as a modem in bridge mode?


And maybe add bridge mode to the title as well?
Logged

burakkucat

  • Global Moderator
  • Senior Kitizen
  • *
  • Posts: 34378
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #82 on: May 12, 2018, 12:20:58 AM »

I dont seem to be able to edit the first post, <snip>

And maybe add bridge mode to the title as well?

Ah, yes, the post has "aged" out of the time-frame, available to you, for its editing. Hopefully my modifications are appropriate!  ;)
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.

johnson

  • Reg Member
  • ***
  • Posts: 787
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #83 on: May 12, 2018, 12:25:23 AM »

That's perfect, thank you!
Logged

burakkucat

  • Global Moderator
  • Senior Kitizen
  • *
  • Posts: 34378
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #84 on: May 12, 2018, 12:33:11 AM »

That's perfect, thank you!

s/perfect/purrfect/

You are welcome.  :)
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.

spring

  • Reg Member
  • ***
  • Posts: 342
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #85 on: May 12, 2018, 04:47:25 AM »

No, it appears this thread has confused spring.

The changed firmware is to make 1508 mtu work while the device is being used as a modem (as per thread title) in bridge mode. From his previous posts (setting ppp session parameters over telnet on the VMG1312) he is using it as a modem/router, in which case he only needed to set the MTU to 1500 in the web interface. His method of changing the ppp session is of course not persistent, just as changing it on your router by direct commands would not survive a reboot.

Maybe I should edit the OP to make it even clearer we are talking about bridge mode?

Can this be changed? Don't think so.
Maybe I could upload a configuration file with 1492 edited to 1500, but I won't try that for now.
Next time take the time to test something before you pretend to know it for sure.
« Last Edit: May 12, 2018, 05:00:31 AM by spring »
Logged
No one knows what is the taste of the void.

Weaver

  • Senior Kitizen
  • ******
  • Posts: 10274
  • Retd s/w dev; A&A; 3x7km lines; Firebrick; IPv6
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #86 on: May 12, 2018, 06:05:45 AM »

I have now flashed that custom firmware in my VMG1312-B10A, modem-only mode. Tested with DF pings and MTU 1500 + 8 = 1508 joy! Very pleased with that.
Logged

johnson

  • Reg Member
  • ***
  • Posts: 787
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #87 on: May 12, 2018, 08:00:33 AM »

Can this be changed? Don't think so.
Maybe I could upload a configuration file with 1492 edited to 1500, but I won't try that for now.
Next time take the time to test something before you pretend to know it for sure.

My apologies! I admit I have not used the VMG1312 as a modem/router to test, but was going on other forum users use of it with 1500 MTU.

So when you issued:
Code: [Select]
ifconfig ppp2.1 mtu 1500
on a router with unmodified firmware it failed?

Seems unlikely as the changes were only to the switch driver to allow > 1500 byte MTU ethernet frames from another router, and to change the ptm session parameters to default to 1508.

Could you share the output of "ifconfig" from your modem/router currently?
Logged

spring

  • Reg Member
  • ***
  • Posts: 342
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #88 on: May 12, 2018, 02:02:51 PM »

Code: [Select]
bcmsw     Link encap:Ethernet  HWaddr
          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
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr:  Scope:Link
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:2048  Metric:1
          RX packets:259691 errors:0 dropped:0 overruns:0 frame:0
          TX packets:431812 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:23021480 (21.9 MiB)  TX bytes:557977520 (532.1 MiB)

eth0      Link encap:Ethernet  HWaddr
          inet6 addr:  Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:2048  Metric:1
          RX packets:34415 errors:0 dropped:0 overruns:0 frame:0
          TX packets:51871 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3206690 (3.0 MiB)  TX bytes:54580614 (52.0 MiB)


eth0.0    Link encap:Ethernet  HWaddr
          UP BROADCAST RUNNING MULTICAST  MTU:2048  Metric:1
          RX packets:34001 errors:0 dropped:0 overruns:0 frame:0
          TX packets:51249 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2562311 (2.4 MiB)  TX bytes:53360556 (50.8 MiB)

eth1      Link encap:Ethernet  HWaddr
          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
          inet6 addr:  Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:2048  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3489 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:1162228 (1.1 MiB)

eth2      Link encap:Ethernet  HWaddr
          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
          inet6 addr:  Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:2048  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3457 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:1159216 (1.1 MiB)

eth3      Link encap:Ethernet  HWaddr
          inet6 addr:  Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:2048  Metric:1
          RX packets:226139 errors:0 dropped:0 overruns:0 frame:0
          TX packets:384815 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:24552437 (23.4 MiB)  TX bytes:510288675 (486.6 MiB)


eth3.0    Link encap:Ethernet  HWaddr
          inet6 addr:  Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:2048  Metric:1
          RX packets:225695 errors:0 dropped:0 overruns:0 frame:0
          TX packets:383986 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:20459649 (19.5 MiB)  TX bytes:505773672 (482.3 MiB)

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:66 errors:0 dropped:0 overruns:0 frame:0
          TX packets:66 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4294 (4.1 KiB)  TX bytes:4294 (4.1 KiB)

ppp2.1    Link encap:Point-to-Point Protocol
          inet addr:  P-t-P:  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:431109 errors:0 dropped:0 overruns:0 frame:0
          TX packets:254197 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:552112647 (526.5 MiB)  TX bytes:21057615 (20.0 MiB)

ptm0      Link encap:Ethernet  HWaddr
          inet6 addr:  Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1508  Metric:1
          RX packets:427737 errors:0 dropped:0 overruns:0 frame:0
          TX packets:252047 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:556776733 (530.9 MiB)  TX bytes:25572463 (24.3 MiB)

ptm0.1    Link encap:Ethernet  HWaddr
          UP BROADCAST RUNNING MULTICAST  MTU:1508  Metric:1
          RX packets:431119 errors:0 dropped:0 overruns:0 frame:0
          TX packets:254209 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:555562051 (529.8 MiB)  TX bytes:26650346 (25.4 MiB)
Logged
No one knows what is the taste of the void.

johnson

  • Reg Member
  • ***
  • Posts: 787
Re: BCM63168 Modems that Support Baby Jumbo Frames (Bridge Mode)
« Reply #89 on: May 12, 2018, 03:19:58 PM »

So as you say the best course of action is to change the mtu value in an uploaded configuration. The ptm interfaces have their MTU set at 1508 as per the changes to the firmware, but this maybe unnecessary.

Would be good to see if you set the wan mtu to 1500 with cfg file and then change the ptm interfaces back to 1500 if packets get fragmented. That way we'd know if its just the nag from the web interface that needs to be circumvented and no need for the other changes when running as a modem/router.
Logged
Pages: 1 ... 4 5 [6] 7 8 ... 31