I think you are not sending the PPPoE request on VLAN 10.

This has worked fine for me for years on older Mikrotik releases and I have
upgraded to 7.4.1 which is the latest stable, but had the long term version
but that has nothing to do with it IMHO.

- Ethernet MTU of 1520 and all other services like DHCP Client disabled
- VLAN 10 interface with a MTU of 1508
- PPPoE attached to VLAN 10 Interface with MTU of 1500 and using PAP (not
CHAP) with a username of "username" and password of "password"

/interface ethernet
set [ find default-name=ether1 ] mtu=1520
/interface vlan
add interface=ether1 mtu=1508 name=ether1-vlan10 vlan-id=10
/interface pppoe-client
add add-default-route=yes dial-on-demand=yes disabled=no
interface=ether1-vlan10 keepalive-timeout=disabled max-mtu=1500 name=pppoe
password=password use-peer-dns=yes user=username
/interface list
add name=WAN
/ppp profile
set *0 use-compression=yes
/interface detect-internet
set detect-interface-list=WAN internet-interface-list=WAN
lan-interface-list=LAN wan-interface-list=WAN
/interface list member
add interface=pppoe list=WAN
/ip firewall nat
add action=masquerade chain=srcnat comment="defconf: masquerade"
ipsec-policy=out,none out-interface-list=WAN

That works for me.

On Wed, Aug 31, 2022 at 11:50 AM Daniel Christie <[email protected]>
wrote:

> RouterOS version on the example we had of this yesterday was 6.48.6
>
> Another customer of ours that had this was probably slightly earlier
> version but they no longer have their Mikrotik plugged in so can’t tell.
>
> We only have the mikrotiks deployed with the long-term stable releases
>
>
>
> Yeah my colleague enabled more logging for PPPoE which also shows…
>
>
>
>
>
> I think what troy Baird has provided me with is the answer we were
> needing. We still have DHCP client enabled on Ether1 in our templated
> config.
>
> So if I understand his response correctly I think we need to disable this.
> Just a little chicken to make change on customers routers right now so will
> keep this noted for next time we have customer outage with it and then test
> it then and if sorts it we will update the others.
>
>
>
> Thanks all for the fast and insightful responses.
>
>
>
> Daniel
>
>
>
> *From:* Pieter De Wit <[email protected]>
> *Sent:* Wednesday, 31 August 2022 11:24 AM
> *To:* Daniel Christie <[email protected]>
> *Cc:* [email protected]
> *Subject:* Re: [nznog] Mikrotik CPE with Spark Fibre issue
>
>
>
> Hey Daniel,
>
>
>
> What version of RouterOS are you running ?
>
>
>
> Have you enabled debugging on PPPOE/PPP and checked the logs ?
>
>
>
> Cheers !
>
>
>
> On 31/08/2022, at 11:22, Daniel Christie <[email protected]> wrote:
>
>
>
> Hi,
>
>
>
> I work for MSP and having issues with customers Mikrotik routers that
> connect specifically with Spark Fibre.
>
> The issue is the routers when initially configured work well and run
> continuously for many day/weeks/months
>
> But eventually something kicks the connection then the PPPoE on the
> Mikrotik will fail to re-establish its WAN fibre connection.
>
>
>
> The solution has been to get customer to get their Spark provided router
> connected which works, then they swap the Mikrotik back in again and it
> works again.
>
> I have done plenty of googling but can’t find anything helpful
> We generally resell voyager fibre to most of our customers with the
> Mikrotik router and they work flawlessly, but some customers insist on
> staying with spark and we prefer to only deploy Mikrotiks
>
>
>
> These logs rotate over and over while its down…
>
> <image001.png>
>
>
>
> Can anyone (hopefully Spark engineer) please help with this?
>
>
> Regards,
>
> Daniel @ Cloudland
>
> _______________________________________________
> NZNOG mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>
>
> _______________________________________________
> NZNOG mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>
_______________________________________________
NZNOG mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to