The official Mikrotik router thread

You mentioned Telkom and Cool ideas so not sure what service you have, however telkom on openserve works with the default pppoe settings.
Thanks for this - was using a Cool Ideas test account to see if the issue was with Telkom Internet or with my line/hardware.
 
Thanks for this - was using a Cool Ideas test account to see if the issue was with Telkom Internet or with my line/hardware.
If you never came right this should be all you need to test

Code:
/interface ethernet
set [ find default-name=ether2 ] name=GPON
set [ find default-name=ether1 ] name=Local
/interface pppoe-client
add add-default-route=yes disabled=no interface=GPON use-peer-dns=yes keepalive-timeout=60 name=TelkomPPPoE [email protected]
/ip pool
add name=dhcp_pool1 ranges=172.16.8.200-172.16.8.254
/ip dhcp-server
add address-pool=dhcp_pool1 authoritative=after-2sec-delay interface=Local lease-time=12h name=dhcp1
/ip address
add address=172.16.8.1/24 interface=Local network=172.16.8.0
/ip firewall nat
add action=masquerade chain=srcnat out-interface=TelkomPPPoE
 
If you never came right this should be all you need to test

Code:
/interface ethernet
set [ find default-name=ether2 ] name=GPON
set [ find default-name=ether1 ] name=Local
/interface pppoe-client
add add-default-route=yes disabled=no interface=GPON use-peer-dns=yes keepalive-timeout=60 name=TelkomPPPoE [email protected]
/ip pool
add name=dhcp_pool1 ranges=172.16.8.200-172.16.8.254
/ip dhcp-server
add address-pool=dhcp_pool1 authoritative=after-2sec-delay interface=Local lease-time=12h name=dhcp1
/ip address
add address=172.16.8.1/24 interface=Local network=172.16.8.0
/ip firewall nat
add action=masquerade chain=srcnat out-interface=TelkomPPPoE
Thanks so much...

What is your max MTU value set at?
 
Its not set, and defaults to an actual of 1492. You can add this in the pppoe client but its not necessary max-mtu=1492
Thanks.. despite everything mentioned and tried, still had no luck.
Landed up returning the router to Scoop and getting a Unifi unit.

Spent the whole weekend trying to get it to work - PEBKAC clearly.
 
RouterOS 7.13.5 [Stable]
Feb 19th 2024

What's new in 7.13.5 (2024-Feb-16 19:35):

*) bridge - fixed MLAG connection after peer-link flap (introduced in v7.13);
*) bridge - fixed packet forwarding after changing HW offloaded bridge interface settings in certain cases (introduced in v7.13);
*) dns - do not close connection with DoH server after query execution (introduced in v7.13.3);
*) leds - fixed modem signal strength for RBSXTR&R11e-LTE (introduced in v7.13);
*) sms - increased SMS read timeout;
*) wifi-qcom - improved memory allocating process;
*) wifi-qcom - improved regulatory compliance for L11, L22 devices;
*) wifi-qcom - improved system stability for L11, L22 devices;
 
Evening all,

Quick question: we have a connection with Vox with the provided a Mikrotik hAP ac2 but I need to extend the wifi signal to cover a back bedrooms.

The hAP installed does not have a POE out, confirmed with a picture of the front of the unit.

But can anyone here recommend an AP for a quick install…I was thinking of a cAP lite since it’s cheap and in stock at Scoop. Can this be powered with a gizzu, or what’s my best option here?

Thanks
 
Last edited:
Evening all,

Quick question: we have a connection with Vox with the provided a Mikrotik hAP ac2 but I need to extend the wifi signal to cover a back bedrooms.

The hAP installed does not have a POE out, confirmed with a picture of the front of the unit.

But can anyone here recommend an AP for a quick install…I was thinking of a cAP lite since it’s cheap and in stock at Scoop. Can this be powered with a gizzu, or what’s my best option here?

Thanks
cAP lite can take 10-60v on PoE which I assume is how you want to power it from the gizzu so don't see any problems there.

If you have full access to your hap you can use Capsman to manage wireless on both devices. A bit of a initial setup but once configured you just put your AP in CAP mode and plug it in

 
cAP lite can take 10-60v on PoE which I assume is how you want to power it from the gizzu so don't see any problems there.

If you have full access to your hap you can use Capsman to manage wireless on both devices. A bit of a initial setup but once configured you just put your AP in CAP mode and plug it in


Is using Capsman a requirement for just a single AP addition or would connecting the cAP lite to a lan port on the hAP and powering it not just work as a connected AP and expand the wireless coverage?

I'm not very familiar with the Mikrotik line of kit
 
Is using Capsman a requirement for just a single AP addition or would connecting the cAP lite to a lan port on the hAP and powering it not just work as a connected AP and expand the wireless coverage?

I'm not very familiar with the Mikrotik line of kit
The benefit of using Capsman is that you get a single SSID which is better for your client devices. Any changes you make on your controller will be made to all access points on your network. You could setup the cAP on its own but everything will be separate.
 
Big one lots I could fit in here

RouterOS 7.14 [Stable]
Feb 29th 2024, 14:46


7.14 changelog:​

!) rose-storage - moved SMB service to the RouterOS bundle;
!) smb - removed legacy SMB service (replaced with newer and faster ROSE SMB service, compatible with SMB 2.1, SMB 3.0 and SMB 3.1.1);
*) 6to4 - make "ipsec-secret" sensitive parameter;
*) api - improved REST API stability when processing invalid requests;
*) api - properly return SNMP OIDs when requested;
*) arm - improved system stability when using microSD on RB1100Dx4;
*) arp - added ARP status;
*) bgp - allow to leak routes between local VRFs;
*) bridge - added MLAG support for MSTP bridges;
*) bridge - avoid per-VLAN host flushing on HW offloaded bridge;
*) bridge - fixed auto "path-cost" for bonding interfaces (introduced in v7.13);
*) bridge - fixed MLAG connection after peer-link flap (introduced in v7.13);
*) bridge - fixed packet forwarding after changing HW offloaded bridge interface settings in certain cases (introduced in v7.13);
*) bridge - improved bridge VLAN configuration validation;
*) bridge - improved configuration speed on large VLAN setups;
*) bridge - improved protocol-mode MSTP functionality;
*) bridge - improved protocol-mode STP and RSTP functionality;
*) bridge - make "point-to-point=yes" default value for non-wireless bridge ports;
*) bridge - removed "mst-config-digest" from MSTI menu;
*) bridge - try to set wireless bridge ports as edge ports automatically;
*) bth - added simple "Back To Home Users" manager under IP/Cloud menu;
*) calea - improved system stability when adding bridge rule without "calea" package installed;
*) certificate - improved certificate validation performance;
*) console - added ":tolf" and ":tocrlf" commands for converting line break to/from LF or CRLF;
*) console - added "show-at-cli-login" option to display a note before telnet login;
*) console - added missing "where" clause for "/ipv6/firewall/filter" table print command;
*) console - do not accept negative or too large values for ":delay" command;
*) console - do not allow to use out-of-range values for time type fields;
*) console - fix configuration export when user does not have a "sniff" policy;
*) console - fixed delayed output from ":grep" command in certain cases;
*) console - fixed incorrect behavior of ":eek:nerror" command in certain cases;
*) console - hint on reset command help that ".rsc file" is required for "run-after-reset" parameter;
*) console - improved editor functionality in full screen mode;
*) console - improved stability when using autocomplete with "export";
*) console - increased maximum file content length that can be managed through command line to 60 KB;
*) console - updated copyright notice;
*) container - improved VETH interface management responsiveness and reliability;
*) container - restrict "/container/shell" menu for users without "write" permissions;
*) defconf - added log about configuration reset due to pressed reset button;
*) defconf - fixed Audience scanning-for-wps-ap timeout;
*) defconf - fixed configuration script on KNOT devices if "ppp-out" interface is removed;
*) defconf - fixed firewall rule for IPv6 UDP traceroute;
*) defconf - fixed wifi configuration if interface MAC address is changed;
*) defconf - improved wifi interface detection after upgrade;
*) defconf - increased LTE interface wait time;
*) defconf - updated health settings on configuration revert;
*) defconf - use "fq_codel" queue as default interface queue for wired ports on LTE devices;
*) dhcpv6-client - install dynamic IPv6 blackhole routes in corresponding routing-table;
*) dhcpv6-client - updated error logging when multiple prefixes received on renew;
*) disk - added exFAT and NTFS mount/read/write support;
*) disk - added global disk "settings" menu;
*) disk - fixed changing settings on some GPT formatted disks;
*) disk - properly unmount disk when it is disconnected;
*) dns - do not add new entries to cache if "cache-size" is reached;
*) dns - fixed domain name lookup resolving for internal services;
*) ethernet - fixed issue with default interface names for CRS310-8G+2S+ in rare cases;
*) ethernet - improved cable-test reliability for hAP ax3 PoE out port;
*) ethernet - resolved minor memory leak while processing packets;
*) fetch - added "head" option for "http-method";
*) fetch - added "patch" option for "http-method";
*) fetch - allow specifying link-local address in FTP mode;
*) fetch - allow to use certificate and check-certificate parameters only in HTTPS mode;
*) fetch - do not require "content-length" for HTTP (introduced in v7.13);
*) fetch - fixed DNS resolving when domain has only AAAA entries (introduced in v7.13);
*) fetch - fixed fetch execution when unexpected data is received in HTTP payload;
*) fetch - fixed fetch when using "src-path" with HTTP/HTTPS modes (introduced in v7.13);
*) fetch - fixed fetch when using "src-path" with SFTP mode (introduced in v7.13);
*) fetch - fixed incorrect "src-path" error message when "upload=yes";
*) fetch - fixed IPv4 address logging (introduced in v7.13);
*) fetch - improved fetch stability in SFTP mode;
*) fetch - improved file download stability with HTTP/HTTPS modes;
*) fetch - less verbose logging;
*) fetch - print all "Set-Cookies" headers in response;
*) fetch - treat any 2xx HTTP return code as success (introduced in v7.13);
 
RouterOS 7.14.1 [Stable]
Mar 11th 2024, 08:37


7.14.1 changelog:​

*) bgp-vpn - use VRF interface as gateway for leaked connected routes;
*) chr - fixed Xen and Vultr missing ethernet (introduced in v7.14);
*) chr - fixed bogus messages printed out while booting up the system (introduced in v7.14);
*) console - fixed do/while implementation not working with variables (introduced in v7.14);
*) ethernet - fixed default names for CRS310-8G+2S+ device (introduced in v7.14);
*) lte - fixed R11e-LTE-US modem dial-up;
*) sfp - improved system stability for CR2004-1G-2XS-PCIe (introduced in v7.14);
*) vrf - fixed VRF interfaces being moved to main table after reboot (introduced in v7.14);
*) wireguard - do not attempt to connect to peer without specified endpoint-address;
 
Good morning everyone.
I have a "monitoring" question: When Eskom starts loadshedding, my inverter kicks in for essential loads, but my poolpump connected to a sonoff switch is not on essential, so it will be off, with no ping response.
I am trying to determine when we are running off the inverter, and the easiest seem to be to do a ping test to the SONOFF, if no response, I know we are in loadshedding.
Is this kind of notification via email or something available on the Mikrotik?
 
Good morning everyone.
I have a "monitoring" question: When Eskom starts loadshedding, my inverter kicks in for essential loads, but my poolpump connected to a sonoff switch is not on essential, so it will be off, with no ping response.
I am trying to determine when we are running off the inverter, and the easiest seem to be to do a ping test to the SONOFF, if no response, I know we are in loadshedding.
Is this kind of notification via email or something available on the Mikrotik?
Use the netwatch function. You can them either mail yourself or tell the RB to do something
 
Good morning everyone.
I have a "monitoring" question: When Eskom starts loadshedding, my inverter kicks in for essential loads, but my poolpump connected to a sonoff switch is not on essential, so it will be off, with no ping response.
I am trying to determine when we are running off the inverter, and the easiest seem to be to do a ping test to the SONOFF, if no response, I know we are in loadshedding.
Is this kind of notification via email or something available on the Mikrotik?
I think the most awesome solution you will find, is if you have a router that can run docker containers.

Then you install Uptime Kuma on there, and the monitoring alert types will be far more.


 
I think the most awesome solution you will find, is if you have a router that can run docker containers.

Then you install Uptime Kuma on there, and the monitoring alert types will be far more.


Thanks for this ... doesn't seem clear for "State change" notifications. ie. I don't want constant notifications that the pump is down, only need notification when its status changes
 
Thanks for this ... doesn't seem clear for "State change" notifications. ie. I don't want constant notifications that the pump is down, only need notification when its status changes
It only notifies when going down and when up again. At least that's how it works for me. I get it as slack notifications on my phone.
 
Good morning everyone.
I have a "monitoring" question: When Eskom starts loadshedding, my inverter kicks in for essential loads, but my poolpump connected to a sonoff switch is not on essential, so it will be off, with no ping response.
I am trying to determine when we are running off the inverter, and the easiest seem to be to do a ping test to the SONOFF, if no response, I know we are in loadshedding.
Is this kind of notification via email or something available on the Mikrotik?
You can do that with the new v4 version of Mikrocloud. And if you follow their LinkedIn page you stand a chance to win a hap.
 
I think the most awesome solution you will find, is if you have a router that can run docker containers.

Then you install Uptime Kuma on there, and the monitoring alert types will be far more.


I swear by Uptime Kuma! Its the bee's knees.
 
Top
Sign up to the MyBroadband newsletter
X