Community discussions

just joined
Topic Author
Posts: 1
Joined: Sun Jun 26, 2016 4:23 pm

Advice for beginner

Sun Jun 26, 2016 6:10 pm

I've spent all weekend playing with a new RB951G-2HnD and wanted to check if my experience was common. I seemed to have a few problems initially with the setup and I ended up reseting via the switch/website and finally winbox, winbox being different from the others and what eventually got things working. Do people have good sources they would recommend reading to understand this stuff (networking with mikrotik, probably just on networking as well) better? I'd much rather have it working by understanding than good luck of trying random things!!

thanks, Paul
Posts: 484
Joined: Wed Apr 02, 2008 2:12 pm
Location: Minnesota USA

Re: Advice for beginner

Sun Jun 26, 2016 8:32 pm

There's quite a bit of info online in the RouterOS Wiki section.  Along with that, I could easily recommend the following book by Steve Discher: ... entries*=0

Good place to start.

MTCNA - 2011

" The Bitterness of Poor Quality Remains Long After the Sweetness of Low Price is Forgotten "

User avatar
Member Candidate
Member Candidate
Posts: 267
Joined: Thu Nov 06, 2014 1:12 pm
Location: Fuengirola, Spain

Re: Advice for beginner

Wed Jun 29, 2016 7:51 pm

Read the example here in the forum, is a very good option. Read the post. Take a Lite router and practice yourself.

And for european people, here the book.... ... ntersat-21 ... ntersat-21
User avatar
Forum Guru
Forum Guru
Posts: 4051
Joined: Wed May 11, 2011 6:08 pm

Re: Advice for beginner

Wed Jun 29, 2016 11:54 pm

If you want to understand networking theory, the most important concept to understand is the OSI model (7-layer network model).
The OSI model ultimately does not map 1:1 with the Internet - the Internet uses a similar 4-layer model.

As a network engineer, the most important (OSI) layers to me are 1-4

It all seemed like "theoretical stuff that's not useful in the real world" when I was first taught this, but having worked with it, it's a crucial way to understand what's going on. You'll see lots of posts here that mention layer2 and layer3. Learning how to distinguish what layer a problem comes from is key in learning how to break a problem down into testable pieces.

If you don't see the MAC address of another LAN host in the ARP cache, for instance, then you know that the problem is local to your own local network segment - i.e. it's likely either a layer 2 problem (wrong vlan, perhaps?) or a layer 1 problem (cable between switches got unplugged). It could be layer 3 if the other host has the wrong IP settings configured... but it's certainly not going to involve port numbers or access rules in an HTTP server, so don't bother looking there if you don't get ARP replies.
When given a spoon,
you should not cling to your fork.
The soup will get cold.

Who is online

Users browsing this forum: MSN [Bot] and 28 guests