MikroTik

I am looking for NTP server that I can install in hap lite. The package name should be ntp-6.34.6-smips.npk , but there isn't any in extra packages.
Will that functionality be available in the future?

Let's revive the question.
Shame it's 8 months later (ros 6.39.2 current) and still no NTP Server for smips, nor any explain.
Please someone.

appears there is no interest in answering questions?

this is not the proper place to ask questions like this.
I also try it sometimes but it rarely works.
you need to mail to support.

I would not know why the NTP server is not included, but it could be that the device(s) that use smips
at the moment do not have a real time clock good enough to serve time to other systems.

+1
I do like NTP better than SNTP. So hopefully some day it will show up

any updates on NTP on smips?

Since SMIPS devices are designed for home usage and does have limited storage size we do not provide NTP package for such devices. SMIPS stand for small MIPS (MIPS device with limited feature set). Could someone share an example where this would be actually necessary (to run NTP server on SMIPS device)? Most likely if you need NTP server, then you need more powerful device.

Well, I think the assumption is that whether one would need a feature in a typical setup is not so important
as long as the generation of the package is not costing too much. I would assume that adding the
package is a one-time matter of configuration of some compilation server at MikroTik, and it would not
cost memory to anyone except those that install the package. Other features that almost nobody uses
are part of the default package already.

One of the strong points of MikroTik is that even sophisticated services are available across the entire
line of products. This can come in handy e.g. when lab-testing some setup that is planned to roll out
on more sophisticated equipment.

I agree about including NTP to SMIPS for flexibility and, as many places has unstable jitter, or uses Windows which has horrible timing with bad internet, or user just wants to not use 4b/s bandwidth of the internet just to query NTP outside as its many home devices (NAT redirect), no hurts for that extra compile line as the server itself is done.

For a SMIPS router you can always redirect the NTP to your favorite NTP server like -

Just asking ..
Does anybody who need local NTP can afford buying a liitle more expensive device instead of the cheapest one? Is this funcionality worth 20$ more?

Just asking ..
Does anybody who need local NTP can afford buying a liitle more expensive device instead of the cheapest one? Is this funcionality worth 20$ more?

It is more a matter of principle than anything else. And something I consider an advantage of the MikroTik product line compare to others.
Note that SMIPS products already support MPLS, Openflow, Hotspot, routing (BGP/OSPF/RIP) etc. Also not things you would typically
expect in a router of that price/performance. But that is what makes MikroTik so nice.

All that is requested is to add another package, one that in another family is like 256K in size and can probably just be compiled from the source
used in all other routers. Should not be much effort and would make the product line more orthogonal.

Do I need it now? No
Do I want to have the option to test it, in case I ever needed to? Yes
Do I want to have the option to install the package, even I have to uninstall other packages, if I needed this feature? Yes

It's all about the option.

It is more a matter of principle than anything else. And something I consider an advantage of the MikroTik product line compare to others.

I'm huge fan of that myself. Every RouterOS has all features (well, almost), there are only some limits, which are mostly sensible (except the lack of wireless AP mode in L3, I hate that for years, and it's even more strange now when sub-$20 hAP mini has L4 and several times more expensive devices don't).

I vote for having optional ntp package for smips too. Generally all packages should be available the same for all architectures. Let everyone to decide himself what to use and how.

Yes ... it's power of ROS ... many packages ... but ...

hAP mini & hAP lite:

Size of RAM 32 MB
Storage size 16 MB

I would rather vote for more storage and memory.

Are you sure that installing and running all packages for SMIPS let you upgrade it considering above numbers? What about partitions?

When you want something like NTP you can probably remove other things like MPLS or routing to make room.
It is unlikely that a small device would require all functionality at the same time.
Partitions are impossible on 16MB flash devices anyway.

I would rather vote for more storage and memory.

It's different topic, unless you find a way how to do it with software upgrade.

Since SMIPS devices are designed for home usage and does have limited storage size we do not provide NTP package for such devices. SMIPS stand for small MIPS (MIPS device with limited feature set). Could someone share an example where this would be actually necessary (to run NTP server on SMIPS device)? Most likely if you need NTP server, then you need more powerful device.

Are you kidding with this need for justification? All packages should include it, we run scripts for updates and monitoring of these devices and the time needs to be right, we want the NTP client function. I personally don't care if it has the NTP server package but we should be able to pick the packages we want on it.

Speaking of justifying packages, can you break kid controls off into its own package? I really don't want it on my 32core CCR.

Are you kidding with this need for justification? All packages should include it, we run scripts for updates and monitoring of these devices and the time needs to be right, we want the NTP client function. I personally don't care if it has the NTP server package but we should be able to pick the packages we want on it.

You do not need the NTP package to sync the time using NTP!
That function is available in the basic system, configure the System->SNTP Client.
The NTP package is only required when you want the router to be NTP server.
When you install it, the NTP Client function replaces the SNTP Client.

smips devices only have 32mb of ram

its easy to get into memory ram exhaustion

i think in the foreseeable future this devices need to be upgraded to 64mb of ram

smips devices only have 32mb of ram

its easy to get into memory ram exhaustion

i think in the foreseeable future this devices need to be upgraded to 64mb of ram

With that attitude, Apollo 11 would never have gotten to the Moon LOL. (Coders these days sheesh).

With that attitude, Apollo 11 would never have gotten to the Moon LOL. (Coders these days sheesh).

At that time, users were satisfied with UI consisting of a few switches and lights. These days it has to be 4k display with 16M colours, animated changes at 100Hz frame rate and 2 or 4 possible GUI methods. All this costs CPU cycles, storage and memory.

yes im reviving an old thread.. and a use-case where I use NTP server..

we send out a tiny cheap router for teleworker IP sets.. (along with a POE injector) that MT tunnels via L2TP client to the "mother ship".. NTP wont travel across an L2TP tunnel, so we serve it locally.. the HaP Mini is a perfect device for someone to use at home.. since I cant put the NTP package on we have to send those kind of ugly Hex Lite;s.. I like the little black box wit ha stand.. it looks cool for an end user to receive...

the phones themselves dont have access to the internet just to the tunnel to access the phone system.. and of coruse access to the MT which serves DHCP
-Christopher

NTP wont travel across an L2TP tunnel, so we serve it locally..

Well that is hogwash, NTP will travel perfectly well across any path that routes IP.
Maybe you used NTP "broadcast" or "multicast" mode which would not work with L2TP directly, but when you use the L2TP line to route a subnet to/from the central location you can still use directed broadcast if you wish.
But you get better results when using client/server mode anyway. Just configure a couple of central NTP servers in your clients so they can query them.