Hi all!
I’m currently working with a setup where I have an out going WAN connection managed through a pppoe-client that works and connects to it DSLAM via a modem just fine. The appropriate VLAN has been tagged and I can access the internet just fine.
/ip route> print
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit
# DST-ADDRESS PREF-SRC GATEWAY DISTANCE
0 ADS 0.0.0.0/0 pppoe-wan 1
1 ADC <ip>/32 <ip> pppoe-wan 0
2 ADC 192.168.2.0/24 192.168.2.1 bridge-lan 0
3 ADC 192.168.3.0/24 192.168.3.1 bridge-wifi 0
[admin@mg-r-h01] /ip route>
Off an on I hoewever experience the pppoe-client terminating and re-connecting.
> /interface pppoe-client print value-list
name: pppoe-wan
max-mtu: auto
max-mru: auto
mrru: disabled
interface: isp-vlan
user: user
password: password
profile: default
keepalive-timeout: disabled
service-name:
ac-name:
add-default-route: yes
default-route-distance: 1
dial-on-demand: no
use-peer-dns: no
allow: pap,chap,mschap2
[admin@mg-r-h01] >
Looking at the logs everything seems to be fine. The pppoe-client is configured to set the default route but not DNS.
Monitoring the pppoe-client interface everything seems to be just fine as well:
> interface pppoe-client monitor pppoe-wan
status: connected
uptime: 11m53s
active-links: 1
encoding:
service-name:
ac-name: <ac-name>
ac-mac: <mac>
mtu: 1480
mru: 1480
local-address: <ip>
remote-address: <ip>
The firewall also shouldn’t be in the way of it:
Flags: X - disabled, I - invalid, D - dynamic
0 D ;;; special dummy rule to show fasttrack counters
chain=forward action=passthrough
1 ;;; established,related,new
chain=input action=accept connection-state=established,related,new log=no log-prefix=""
2 ;;; Invalids
chain=input action=drop connection-state=invalid log=no log-prefix=""
3 chain=input action=accept protocol=icmp in-interface=pppoe-wan log=no log-prefix=""
4 chain=input action=accept protocol=tcp in-interface=bridge-lan port=22 log=no log-prefix=""
5 chain=input action=accept protocol=tcp in-interface=bridge-lan port=8291 log=no log-prefix=""
6 chain=input action=drop protocol=tcp in-interface=pppoe-wan port=22 log=no log-prefix=""
7 chain=input action=drop in-interface=pppoe-wan
8 chain=forward action=fasttrack-connection connection-state=established,related log=no log-prefix=""
9 ;;; related, established
chain=forward action=accept connection-state=established,related log=no log-prefix=""
But for some reason, the connection was offline long enough the routing engine seems to just become dormant and ignore the fact the pppoe-client has re-established a connection?
I can’t help but wonder if I’d be able to solve this with more debug information or extended logging, however I lack the imagination to find the useful log topics.
I’ve been scavenging the forum for similar issues before and have attempted several fixes, sadly the up/down scripts lead to my device being too aggressive and boot looping.
Any and all suggestions would be very welcome.