Interfaces showing ether1 and ether1-gateway

RouterOS General
1

Hi,

Please assist, I have recently bought a new RouterBoard HexS since my old one could not do Gigabit.
I am really impressed thus far with the Mikrotik, but I need some help please.

Please see my questions marked Q1 to Q4 below.

I did a backup of the old router [RB-951UI2] , then transferred the backup file to my new HexS [RB760iGS] and did a restore. After that I noticed a new Interface ether1, I never had that before.
Now I have ether1 and ether1-gateway. Q1: Is this normal?

I am also busy diagnosing why I cannot get full bandwidth as what the ISP is delivering (I am getting 200Mbps), this might be at their end,
but they are yet to come back to me, should be getting 900Mbps. Q2: If you can think of reason please comment.
- I have disabled the Queues and the CPU load is very low:
- Very nice nice router Hex S: [RB760iGS]

I am seeing Interface listed witch I do not totally understand, and therefor I might be doing several stuff all wrong.
I have a queue tree for UP and DOWN, and the interfaces I am using is
UP: ether1
DOWN: bridge-local <<-- Q3: is this the correct interface to use?

Also my firewall rules, well some of them is using ether1, as the interface e.g. drop all packets from public internet that are not dst-natted.

My Interface list is as such: I find to odd that I have an ether1-gateway and it is not running, Q4: why am I seeing ether1-gateway

Flags: D - dynamic, X - disabled, R - running, S - slave 
 #     NAME                                TYPE       ACTUAL-MTU L2MTU  MAX-L2MTU MAC-ADDRESS      
 0  R  ether1                              ether            1500  1596       2026 --:--:--:--:--:8E
 1     ether1-gateway                      ether            1500  1598       2026 --:--:--:--:--:80
 2  RS ether2-master-local                 ether            1500  1598       2026 --:--:--:--:--5:81
 3  RS ether3-slave-local                  ether            1500  1598       2026 --:--:--:--:--:82
 4  RS ether4-slave-local                  ether            1500  1598       2026 --:--:--:--:--:83
 5  RS ether5-slave-local                  ether            1500  1598       2026 --:--:--:--:--:84
 6  R  bridge-local                        bridge           1500  1598            --:--:--:--:--:81
16  R  ;;; eth1 not part of the bridge
       vlan-spark                          vlan             1500  1592            --:--:--:--:--:8E
2

A backup in one device is not usable as restore for another device. Use “export” in a terminal session.
See https://wiki.mikrotik.com/wiki/Manual:Configuration_Management , how to use the exported file.

As there are master-slave interfaces, this probably comes from an old RouterOS version.(before 6.41). The way RouterOS handles interfaces on the switch has changed.

3

Can you tell more about that change, or give a link where this is described?

4

It changed in 6.41, so where should one look ???

5

All right, thanks!
Of course in the Changelog at https://mikrotik.com/download/changelogs :slight_smile:

Release 6.41 2017-12-22
What’s new in 6.41 (2017-Dec-22 11:55):

Important note!!! Backup before upgrade!
RouterOS (v6.40rc36-rc40 and) v6.41rc1+ contains new bridge implementation that supports hardware offloading (hw-offload).
This update will convert all interface “master-port” configuration into new bridge configuration, and eliminate “master-port” option as such.
Bridge will handle all Layer2 forwarding and the use of switch-chip (hw-offload) will be automatically turned on based on appropriate conditions.
The rest of RouterOS Switch specific configuration remains untouched in usual menus for now.
Please, note that downgrading to previous RouterOS versions will not restore “master-port” configuration, so use backups to restore configuration on downgrade.

!) bridge - implemented software based vlan-aware bridges;
https://wiki.mikrotik.com/wiki/Manual:Interface/Bridge#Bridge_VLAN_Filtering >
!) switch - “master-port” conversion into a bridge with hardware offload “hw” option;
https://wiki.mikrotik.com/wiki/Manual:Switch_Chip_Features#Bridge_Hardware_Offloading >
…