Thanks Mike, NBN came back up on new provider today, so will get to play with bridging again tonight. Is there a document somewhere which discusses CPU usage (especially for firewall/NAT rules) on RouterOS? I had thought it was a tunnelling CPU usage issue but I logged in remotely just to get connectivity via NBN for the wife and kids (we've been using Telstra Air with a Groove-52 and a 26dB dish pointed across the valley ;) ), and for now have my CRS simply doing NAT to the TPG VDSL router, and i'm hitting 100% CPU (profiler showing 80% in firewall, 20% in idle) while doing 60mbps on speedtest.net, so it looks like it's more to do with firewalling? I noticed the default firewall config on the groove is using a forward action of 'fasttrack connection' rather than accept on the established forward rule?? On 14 April 2016 at 11:55, Mike Everest <mike@duxtel.com> wrote:
Hi,
Found http://www.nbnco.com.au/content/dam/nbnco2/documents/sfaa-wba2-product- catalogue-nebs-product-tech-spec-fttb-fttn_20150824-to-FTTN-launch.pdf, which suggests each DSL port will accept up to 8 mac addresses, and expire unseen mac's after 300 seconds. May be simply a modem limit then. Time for more playing!
But if you only have one interface attached to that broadcast domain, then pppoe client interface should be the only MAC that is presented to the modem.
BTW, keep meaning to ask.. How far up the expense (and physical footprint) ladder do I need to go, to get a MT device which will do 100mbps of PPTP traffic? (CRS109 tops out at 100% cpu at around the 45mbps mark..) Had been considering doing a RouterOS VM at home and DC with routing preferencing pushing traffic over PPTP/EOIP tunnel between them if they're up, and falling back to the CRS109's at each end if either VM is down, but if there is a MT router which doesn't take much space which will handle it, and doesn't cost the earth, it might just be easier to go that way :)
Don't know about that - pppoe should not consume so much CPU just to run the ppp interface - perhaps there is something else going on there. Try running profiler tool when CPU is pegged to try to find out what subsystem is using up CPU.
Cheers!
Mike.
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
-- Damien Gardner Jnr VK2TDG. Dip EE. GradIEAust rendrag@rendrag.net - http://www.rendrag.net/ -- We rode on the winds of the rising storm, We ran to the sounds of thunder. We danced among the lightning bolts, and tore the world asunder