I’m kind of doubtful you’ll get any useful mtbf numbers for Mikrotik; you could email Mikrotik support and they can look it up for a particular model and probably reply with somewhere in between 5-10 years excluding the switching power supply and just based off of the devices having no moving parts(not even fans). But you can’t really see them for millions of bucks if a device fails sooner any more than you can sue Cisco. That said, they probably have more devices deployed outdoors in the elements than in some cozy cabinet or someone’s home.
At low cost, size, basically powerable by a USB battery, you could get a couple of spares preconfigured in that same cabinet such that a local electrician or security guard can just swap them outside of emergency and that’ll get you going till someone can get on site to fix things up.
On another note, … Seriously? How come people expect something that speaks IP to not require regular servicing or not have reduncies in place? In my mind as long as they speak any kind of network protocol, they need to be patchable and there should be plan B in case something gets hacked. How come this is where things ended up?
Ip isnt its main means of communication, modbus rtu is
Ip is only used for service on the device
But they want service for all 5 devices being done from a central pc
@anon5205053 in one of the posts i said we’re setting up a new network parallel to the old. We’re in the process of selecting the network components.
so i’m to understand you are running a linux machine as your routing base correct?
You do not need to create any vlans etc, and its straight forward (though it’d be easier assigning security as a group)
First enable traffic forwarding in your kernel
echo 1 > /proc/sys/net/ipv4/ip_forward
then you need to set up your interfaces, you can create virtual interfaces on single interface if you as much need or create iptables rules for specific hosts with specific rules.
You can find some quick tips here:
the port forwarding will look as such:
iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to-port 1111
Once it gets request on port 80 on your host router machine, it’ll redirect to port 1111, you can also add from, and to interface into it -i eth0 -o eth0.1
if you are using actual hardware its even easier, and if you plan to use cisco stuff - you may as well get packet tracker and try setting it up. I used to have CCNA(expired) so i may be able to help you with actual config on cisco hardware.
we’re trying not to do ‘hacky’ solutions and ended up on just using 5 tiny NAT devices.
Config of actual devices etc shouldn’t be a problem, got my ccna 2 months ago, still struggling tho…
I think if you read the whole thread you’ll understand what I mean