Community discussions

MikroTik App

Search found 5 matches

by jahill70
Mon Dec 04, 2017 6:21 pm
Forum: General
Topic: Route by routing mark in IPv6
Replies: 6
Views: 1621

Re: Route by routing mark in IPv6

Yes, it looks like this feature isn't ever going to arrive, at least not in this decade, and we're likely to need to move away from Mikrotik as a result :-(
by jahill70
Mon Jul 31, 2017 12:20 am
Forum: General
Topic: PPPoE: Peer is not responding
Replies: 23
Views: 19444

Re: PPPoE: Peer is not responding

It looks like the cause of my issue might be a different bug, but as I've already posted in this thread, I thought I'd talk through how I fixed it. I wiped the router, then rebuilt the config from scratch. Line three still played up, but I disconnected two other lines and brought up the third, then ...
by jahill70
Fri Jul 28, 2017 2:19 am
Forum: General
Topic: PPPoE: Peer is not responding
Replies: 23
Views: 19444

Re: PPPoE: Peer is not responding

I've run into the same issue. Adding a third PPPOE client interface means the line connects and immediately disconnects with the log entries 'initializing', 'connecting', 'terminating... - hungup', 'disconnected' all with the same timestamp. This appears to be a major bug. The reply above with 5000 ...
by jahill70
Thu Dec 03, 2015 6:28 pm
Forum: Announcements
Topic: 6.33.2 version is released!
Replies: 41
Views: 11310

Re: 6.33.2 version is released!

jahill70 - Please run this command on your device: "/system logging add topics=pppoe,debug" After that try to connect again. Now generate supout file and send it to support@mikrotik.com http://wiki.mikrotik.com/wiki/Manual:Support_Output_File As mentioned above, I've moved back to the current rc me...
by jahill70
Thu Dec 03, 2015 3:46 am
Forum: Announcements
Topic: 6.33.2 version is released!
Replies: 41
Views: 11310

Re: 6.33.2 version is released!

I found the stable 6.33.2 broke PPPOE with my ISP reporting the wrong username/password combination was being used. The pre-release version 6.34 worked fine before moving to the 'stable' version and, moving back to the release candidate, all works fine again (re-entering the username/passwork combo ...