|
|
|
amanzi:
@snj:
Mindful that this is in the Quic Forum...
Sorry - meant to say that I'm with Voyager but will be switching to Quic. I'm trying to understand what config I need to adjust to work with Quic, so was hoping someone could share theirs so I can compare.
It depends on how you want the service configured. You have options with quic..
For me personally, I just use Untagged VLAN + PPPoE. A common misconception is that when you use PPPoE you have to reduce the MTU of the connection. With Quic you can set the physical MTU of the ethernet interface to 1508 and set PPPoE as 1500.
The RB5009 has enough grunt to encapsulate PPPoE without any performance detriment. The benefits of PPPoE are it re establishes sessions much quicker than DHCP if you connection ever gets disconnected. I, and other find it more stable, but it all depends on the router you have at your disposal.
Anyway, here's some snippets of my config that I use with Quic. My WAN interface is Ether1. It's been super stable so I hope it works for you :)
If you'd like some IPv6 bits, let me know :)
/interface ethernet set [ find default-name=ether1 ] comment=Chorus mtu=1508 rx-flow-control=auto tx-flow-control=auto
/interface pppoe-client add add-default-route=yes comment=Quic disabled=no interface=ether1 name=pppoe1 password=quic user=quic@quic.nz
/interface list member add interface=pppoe1 list=WAN
/ip firewall nat add action=masquerade chain=srcnat comment="NAT Overload/Masquerade" out-interface-list=WAN
Dunedin, NZ
Quic Broadband | Rocket 1G/1G Hyperfibre (Yes, you read that right!)
Dunedin Live Webcam (4K) | Quic Smokepings
Referral Links:
Quic (use R282731EPGJMG on checkout for free setup, and to help me pay for my fast internet addiction)
Contact Energy (use FRTDD2R for $100 credit)
For IPv6, mine is a bit "manual" the prefix never changes so I'm happy to set it this way..
You'll get assigned a /56 IPv6 prefix which you can do whatever you want with. For me personally I give my WAN interface a linknet within that space, but you dont have to.
Let's say you get a prefix from quic of 2407:8b00:1169:1000::/56 - you can divide this up from 2407:8b00:1169:1000::/64 to 2407:8b00:1169:10ff::/64.
Here's an example:
/ipv6 address add address=2407:8b00:1169:1000::1 comment=LAN interface=bridge1
/ipv6 address add address=2407:8b00:1169:10ff::1 comment=LinkNet interface=pppoe1
/ipv6 dhcp-client add add-default-route=yes interface=pppoe1 pool-name=quic-ipv6-pd request=prefix use-interface-duid=yes use-peer-dns=no
/ipv6 nd set [ find default=yes ] advertise-dns=no
/ipv6 settings set accept-router-advertisements=yes
/ipv6 firewall address-list add address=::/128 comment="unspecified address" list=bad_ipv6
/ipv6 firewall address-list add address=::1/128 comment=lo list=bad_ipv6
/ipv6 firewall address-list add address=fec0::/10 comment=site-local list=bad_ipv6
/ipv6 firewall address-list add address=::ffff:0.0.0.0/96 comment=ipv4-mapped list=bad_ipv6
/ipv6 firewall address-list add address=::/96 comment="ipv4 compat" list=bad_ipv6
/ipv6 firewall address-list add address=100::/64 comment="discard only " list=bad_ipv6
/ipv6 firewall address-list add address=2001:db8::/32 comment=documentation list=bad_ipv6
/ipv6 firewall address-list add address=2001:10::/28 comment=ORCHID list=bad_ipv6
/ipv6 firewall address-list add address=3ffe::/16 comment=6bone list=bad_ipv6
/ipv6 firewall filter add action=accept chain=forward comment="accept established,related,untracked" connection-state=established,related,untracked
/ipv6 firewall filter add action=accept chain=forward comment="accept ICMPv6" protocol=icmpv6
/ipv6 firewall filter add action=drop chain=forward comment="drop invalid" connection-state=invalid
/ipv6 firewall filter add action=drop chain=forward comment="drop packets with bad src ipv6" src-address-list=bad_ipv6
/ipv6 firewall filter add action=drop chain=forward comment="drop packets with bad dst ipv6" dst-address-list=bad_ipv6
/ipv6 firewall filter add action=drop chain=forward comment="rfc4890 drop hop-limit=1" hop-limit=equal:1 protocol=icmpv6
/ipv6 firewall filter add action=accept chain=forward comment="accept HIP" protocol=139
/ipv6 firewall filter add action=accept chain=forward comment="accept ipsec AH" protocol=ipsec-ah
/ipv6 firewall filter add action=accept chain=forward comment="accept ipsec ESP" protocol=ipsec-esp
Dunedin, NZ
Quic Broadband | Rocket 1G/1G Hyperfibre (Yes, you read that right!)
Dunedin Live Webcam (4K) | Quic Smokepings
Referral Links:
Quic (use R282731EPGJMG on checkout for free setup, and to help me pay for my fast internet addiction)
Contact Energy (use FRTDD2R for $100 credit)
3l3m3nt:
It depends on how you want the service configured. You have options with quic..
- Tagged VLAN + PPPoE
- Untagged VLAN + PPPoE
- Tagged VLAN + IPoE
- Untagged VLAN + IPoE
For me personally, I just use Untagged VLAN + PPPoE. A common misconception is that when you use PPPoE you have to reduce the MTU of the connection. With Quic you can set the physical MTU of the ethernet interface to 1508 and set PPPoE as 1500.
The RB5009 has enough grunt to encapsulate PPPoE without any performance detriment. The benefits of PPPoE are it re establishes sessions much quicker than DHCP if you connection ever gets disconnected. I, and other find it more stable, but it all depends on the router you have at your disposal.
Thanks for the info. I'm not really sure which option is better. I thought I heard that performance might be better with DHCP, but it's not like I'm saturating the port or anything like that. Faster reconnection sounds good to me, but why would someone choose to have the connection tagged or untagged?
zebis:
I switched from PPPoE to IPoE/DHCP back in February, setup DHCPv6 via PD and had it working fine, but since rebooting from the outage earlier this week I just can't obtain a prefix, its stuck in 'searching' with what I am sure was the original config. (DHCPv6 also worked over PPP back then too)
Assuming it worked before and all you did was reboot there are two possible explanations:
3l3m3nt:
The benefits of PPPoE are it re establishes sessions much quicker than DHCP if you connection ever gets disconnected. I, and other find it more stable, but it all depends on the router you have at your disposal.
I concur with this advice.
------
In regards to "accept-router-advertisements" under /ipv6/settings all our clients have this set at the default which is "yes-if-forwarding-disabled" however I can't speak for other ISP's.
Here is a working IPv6 config deployed on a lot of routers. No manual IP setting on WAN required because it uses Link Local as it should.
/ipv6 address
add address=::1 from-pool=ipv6-pool1 interface=bridge1
/ipv6 dhcp-client
add add-default-route=yes interface=ether1 pool-name=ipv6-pool1 request=prefix
/ipv6 firewall filter
add action=accept chain=input comment="DHCPv6 port 546 inbound" connection-state=new dst-port=546 protocol=udp src-address=fe80::/16
(and anything else you need)
WFH Linux Systems and Networks Engineer in the Internet industry | Specialising in Mikrotik | APNIC member | Open to job offers | ZL2NET
amanzi:
I also have an RB5009 and am currently with Voyager using PPPoE on VLAN10. Does anyone have a working config they're willing to share? I'll be looking to pay the extra for static IP addresses, and will probably switch from PPPoE to DHCP.
Shouldn't actually need to change anything 😊 but a wee recommendation, stay on PPPoE. The RB5009 has plenty of power and can even route Hyperfibre speeds with PPPoE and that’s exactly what I’m doing with mine.
Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)
Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.
MichaelNZ:
Here is a working IPv6 config deployed on a lot of routers. No manual IP setting on WAN required because it uses Link Local as it should.
Yep, absolutely that'll work. I just like assigning an IP to my WAN interface for some reason 😆
Dunedin, NZ
Quic Broadband | Rocket 1G/1G Hyperfibre (Yes, you read that right!)
Dunedin Live Webcam (4K) | Quic Smokepings
Referral Links:
Quic (use R282731EPGJMG on checkout for free setup, and to help me pay for my fast internet addiction)
Contact Energy (use FRTDD2R for $100 credit)
I just upgraded 7.19.1 > 7.19.4 on alert of this old post from last year :)
I still run the same DHCP config from last year also, just haven't needed to change.
Its likely still slower than PPPoE but for reference:
07:18:43 ether-1 (WAN) link up
07:19:10 dhcp-client on either-1 got IP address x.x.x.x
A little under 30 seconds from the interface establishing its initial layer 1 link speed.
Matt
^ That seems slow. Mine's 9 seconds from first log entry to getting DHCP
2025-08-08 20:02:43 system,info router rebooted by tcp-msg(winbox) [snip]
...
2025-08-08 20:02:52 dhcp,info dhcp-client on vlan1 got IP address [snip]
The actual time to get an IP address via DHCP with a Mikrotik router is sub-1 second.
However some ISP's use Mikrotik for their client connection gateways and due to limitations with DHCP on Mikrotik under some circumstances it can take longer to connect then PPPoE.
This is because due to necessity of how an ISP network scales DHCP is deployed a bit differently to the normal way most people know in their home or business LAN network.
WFH Linux Systems and Networks Engineer in the Internet industry | Specialising in Mikrotik | APNIC member | Open to job offers | ZL2NET
(Off topic but) I know some WISPs are using it, I'd be curious to know if they're used in any of the larger providers.
MadEngineer:
(Off topic but) I know some WISPs are using it, I'd be curious to know if they're used in any of the larger providers.
Its pretty much the only routing and switching gear used in WISP's who tend to be smaller ISP's with their own delivery network.
Larger ISP's don't use Mikrotik in their core network that I know of.
Mikrotik is good gear within its target market which is end users (RB series) and smaller ISP's (CCR and CHR series).
WFH Linux Systems and Networks Engineer in the Internet industry | Specialising in Mikrotik | APNIC member | Open to job offers | ZL2NET
Think we're off topic now but...
MichaelNZ: Larger ISP's don't use Mikrotik in their core network that I know of.
Mikrotik is good gear within its target market which is end users (RB series) and smaller ISP's (CCR series).
Know plenty of larger ISP's that use Mikrotik in their core. You forget there's CHR which provides almost endless opportunities.
Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)
Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.
michaelmurfy:
Know plenty of larger ISP's that use Mikrotik in their core. You forget there's CHR which provides almost endless opportunities.
You are right the CHR did slip from my mind.
Its great they are adopting Mikrotik and its getting into the bigger league because not very long ago they couldn't handle it and we all used Cisco or Juniper.
In our case Cisco was the money sink. By comparison Mikrotik is a bargain.
WFH Linux Systems and Networks Engineer in the Internet industry | Specialising in Mikrotik | APNIC member | Open to job offers | ZL2NET
Just want to say - switched to quic today, and the IPv6 configuration from here https://www.geekzone.co.nz/forums.asp?forumid=194&topicid=306894 (PPPoE not IPoE) worked well for me. There was a moment of "oh noes!" when after setting /ipv6 settings set accept-router-advertisements=yes the connection both to the router and internet was lost for a wee bit, but it came back on and worked afterwards.
|
|
|