Craig Sanders via luv-talk <luv-talk@luv.asn.au> writes:
On Sat, Dec 14, 2019 at 04:55:55PM +1100, Brian May wrote:
My theory is that with a bridged/PPPOE setup I was getting a lot of queuing of outgoing packets, which led to large latencies, and that the routed setup is better. I did try solving this by setting up QOS, but with the speed changing so much this didn't work anymore, and I don't particularly want to have to keep monitoring this.
I never noticed anything like that with my bridged pppoe connection (also using a very old billion modem). I always had good performance. Was getting almost 16 Mbpbs down and 1.1 Mbps up until about a year or so ago when NBN contractors came to prepare the street for NBN (FTTC). They negligently disconnected me twice while doing that (several days outage both times). After that, I never got better than 11 Mbps down. Coincidentally, that was just good enough that I couldn't insist that it be fixed.
This is my router: https://www.ui.com/edgemax/edgerouter-pro/ I am not sure what its CPU is. I think though it should be able to cope with PPPOE at fast then 3Mbps. Unfortunately this company doesn't make anything that will terminate a ADSL/VDSL connection. Which is why I need the modem/router. In fact, I only noticed performance issues after the ADSL speed dropped, which is why I suspected queuing.
Did you reduce the MTU and MRU to account for the pppoe overhead? i had mine set to 1412.
Yes, did that.
BTW, you also have to set the MTU on all machines behind the pppoe router - if they send 1500 byte packets to the router, they'll just be fragmented anyway.
Good point. Although I still prefer to avoid PPPOE if possible.
My Cisco 877 is past end of life[*], so would like to replace it with something more recent (and capable of NBN speeds for when I eventually get FTTN). Currently looking at the Cisco Rv134w-e-k9-au it appears it supports things like DHCPv6 PD. Apparently it is suppose to be able to cope with NBN 100/40 speeds (confirmation of this would be good...). One review says it requires regular reboots. It also doesn't run IOS - although if it does what I want that isn't a big concern. Might be better actually, looks like firmware updates can be downloaded free of charge.
IMO, you'd be much better off with a good 2nd NIC in your linux box, and have linux handle the routing, firewalling, etc. a cheap realtek nic like mine(*) would do, or use something better like an intel or broadcom.
This isn't going to help. I still need something to terminate the *DSL connection.
even a recent model home router (tp-link, asus, netgear, etc) running openwrt/lede would be better. i'm tempted to get one of these myself now that I no longer need ADSL, so that I can separate my server from my gateway box.
Won't these all have poor CPUs and reliability? Wonder how they compare the Cisco RV134W, which is also a low end VDSL2 modem/router. Apparently it is a Linux based OS, although I am doubtful of openwrt support. It also was wifi, which is not something I want. Last time I went the openwrt route, I had a hard time trying to judge a product that is available,compatible, reliable, up-to-date, and sufficient for my requirements (would like one that can cope with NBN 100/40, although I am sceptical of ever reaching such speeds...). Apparently there are not many *DSL modems that support openwrt. Although I do trust openwrt more then some of the proprietary rubbish firmware I have seen. In the past some of the bugs I have seen in some versions of CISCO IOS amaze me, and make me think no testing was done. Hmm. Just found this post. The sender looks familiar :-). What did you end up using for a modem? https://forum.openwrt.org/t/good-vdsl-modem-for-nbn-in-au-also-lede-fail2ban... -- Brian May <brian@linuxpenguins.xyz> https://linuxpenguins.xyz/brian/