Hello, I purchased the CubeG-5ac60aypair-US from a reseller and I am having issues with it. I contacted but they will not exchange for this is the first time I have tried to set them up but it has been more than 30 days since purchase
The units do not appear to be pre-configured and ready to use as they are supposed to be. The one labeled master appears to have just a default configuration on it with an IP address of 192.168.88.1 and admin log in with no password, it does not match the information listed on the sticker than came on it. I need to know how to get them configured properly to and paired with each other. Is there any support I can call or instructions step by step to set these up to send signal to each other to feed my other building as intended?
Re: Question for help on wireless cubes [SOLVED]
Cannot say why your deices are like you describe, but setting them up as they should be is relatively easy.
The 192.168.88.1 is the default for a "single" Mikrotik device.
Cube Pro pairs usually have 192.168.88.2 and 192.168.88.3.
Maybe someone tested them and ran Quickset (or whatever), but both of them are the same (with 192.168.88.1) or only one of the two?
Here you can find the default configuration for the pair:
viewtopic.php?t=205042#p1059476
If I were you I would first try to reset configuration, if the procedure doesn't restore the "right " default one, you can still use the posted one(s) applying it/them manualy.
The 192.168.88.1 is the default for a "single" Mikrotik device.
Cube Pro pairs usually have 192.168.88.2 and 192.168.88.3.
Maybe someone tested them and ran Quickset (or whatever), but both of them are the same (with 192.168.88.1) or only one of the two?
Here you can find the default configuration for the pair:
viewtopic.php?t=205042#p1059476
If I were you I would first try to reset configuration, if the procedure doesn't restore the "right " default one, you can still use the posted one(s) applying it/them manualy.
Re: Question for help on wireless cubes
It appears like only the master unit is like I described the other one has the .3 address also is there a way to tell once I do the reset if it shows up correctly inside the software how do I tell if the two are seeing each other and passing data between?
Re: Question for help on wireless cubes
I posted a reply to you but I did not quote you the first time hopefully you see this and can reply to my last postCannot say why your deices are like you describe, but setting them up as they should be is relatively easy.
The 192.168.88.1 is the default for a "single" Mikrotik device.
Cube Pro pairs usually have 192.168.88.2 and 192.168.88.3.
Maybe someone tested them and ran Quickset (or whatever), but both of them are the same (with 192.168.88.1) or only one of the two?
Here you can find the default configuration for the pair:
viewtopic.php?t=205042#p1059476
If I were you I would first try to reset configuration, if the procedure doesn't restore the "right " default one, you can still use the posted one(s) applying it/them manualy.
Re: Question for help on wireless cubes
In theory, there is a default configuration (made in factory) that can (maybe) still recovered doing a reset.
But for all we know it could also be that (for whatever reasons) there has been an error in packaging or an exchange of units in this or that passage from Mikrotik to the importer, from the importer to the wholesaler, from the wholesaler to the reseller.
In any case since you have seemingly the "other half" with the original data/settings so you can try resetting the master unit and if it does not come up with the "right" configuration, you can still recreate the original one following the scheme in the given post and the data (ssid, password, etc.) from the "slave" unit.
But for all we know it could also be that (for whatever reasons) there has been an error in packaging or an exchange of units in this or that passage from Mikrotik to the importer, from the importer to the wholesaler, from the wholesaler to the reseller.
In any case since you have seemingly the "other half" with the original data/settings so you can try resetting the master unit and if it does not come up with the "right" configuration, you can still recreate the original one following the scheme in the given post and the data (ssid, password, etc.) from the "slave" unit.
Re: Question for help on wireless cubes
Are you talking about doing the reset the configuration with the reset button by holding it down for 3 seconds while it is already powered on until the light starts flashing? And also once I do get the configuration reset if it comes up properly where do I look inside the software to tell if the two cubes are seeing each other with a good signal and passing data? Also could you tell me where to look on the slave unit to get the SSID and password and anything else I might need to change in the configuration you posted with the link to the other post to match my units?In theory, there is a default configuration (made in factory) that can (maybe) still recovered doing a reset.
But for all we know it could also be that (for whatever reasons) there has been an error in packaging or an exchange of units in this or that passage from Mikrotik to the importer, from the importer to the wholesaler, from the wholesaler to the reseller.
In any case since you have seemingly the "other half" with the original data/settings so you can try resetting the master unit and if it does not come up with the "right" configuration, you can still recreate the original one following the scheme in the given post and the data (ssid, password, etc.) from the "slave" unit.
Re: Question for help on wireless cubes
Yes, you can do the reset from the button or - if you have access to the unit (like you have) from terminal command line or winbox (easier).
See configuration reset here:
https://help.mikrotik.com/docs/display/ ... Management
https://help.mikrotik.com/docs/display/ ... ationReset
The first "symptom" that the new configuration is the right one is that - again in theory - since you have a sticker, the new login will be "admin" and the password the one on the sticker.
Of course there is a risk involved in this procedure, possibilities are:
1) the device is the "right" one (i.e. it has not been exchanged) and the password on the sticker will work (good)
2) the device, no matter if the "right" or an exchanged one has anyway a factory configuration with blank password.(good)
3) the device is definitely an exchanged one, the password is required and the password on the sticker won't work (bad). In this case it is still possible to do a netinstall to recover the unit, but it is a more complex procedure.
Checking the serial numbers of the two devices you have may give a hint (I presume that Cube pairs have consecutive serial numbers, but I may well be completely wrong).
Also the mac addresses in /interface bridge could be sequential.
In any case, before any attempt, you should follow the instructions here:
viewtopic.php?t=203686#p1051720
and export the current configuration of both devices, saving them on your PC.
The files are plain text and the needed info (minus the router password) are in clear text, not obfuscated/encrypted).
The data that changes between sets of pairs (but that you can also change yourself) should be:
password <- /interface w60g
ssid <- /interface wireless, /interface w60g
wpa2-pre-shared-key <-/interface wireless security-profiles
And likely also mac-address and remote-address (in the /interface w60g station settings) but these should be "local" MAC's that can be generated manually.
Once these are set correctly, you just connect one of the two devices to a PC, point it in the general direction of the other, placed a few meters away, connect this latter one to another PC and you should be able to see how the data passes from one PC to the other, if everything works correctly a pair of Cube Pros should work exactly as a "dumb" two ports network switch, i.e. connect transparently the devices connected to them (hence the name as "wireless wire").
To change the settings, depending if it is just a few settings/values or entire snippets of configuration you could use Winbox GUI or a terminal window (still open from within Winbox) using command lines (but copy/paste is possible, so it is not particularly difficult)
See configuration reset here:
https://help.mikrotik.com/docs/display/ ... Management
https://help.mikrotik.com/docs/display/ ... ationReset
The first "symptom" that the new configuration is the right one is that - again in theory - since you have a sticker, the new login will be "admin" and the password the one on the sticker.
Of course there is a risk involved in this procedure, possibilities are:
1) the device is the "right" one (i.e. it has not been exchanged) and the password on the sticker will work (good)
2) the device, no matter if the "right" or an exchanged one has anyway a factory configuration with blank password.(good)
3) the device is definitely an exchanged one, the password is required and the password on the sticker won't work (bad). In this case it is still possible to do a netinstall to recover the unit, but it is a more complex procedure.
Checking the serial numbers of the two devices you have may give a hint (I presume that Cube pairs have consecutive serial numbers, but I may well be completely wrong).
Also the mac addresses in /interface bridge could be sequential.
In any case, before any attempt, you should follow the instructions here:
viewtopic.php?t=203686#p1051720
and export the current configuration of both devices, saving them on your PC.
The files are plain text and the needed info (minus the router password) are in clear text, not obfuscated/encrypted).
The data that changes between sets of pairs (but that you can also change yourself) should be:
password <- /interface w60g
ssid <- /interface wireless, /interface w60g
wpa2-pre-shared-key <-/interface wireless security-profiles
And likely also mac-address and remote-address (in the /interface w60g station settings) but these should be "local" MAC's that can be generated manually.
Once these are set correctly, you just connect one of the two devices to a PC, point it in the general direction of the other, placed a few meters away, connect this latter one to another PC and you should be able to see how the data passes from one PC to the other, if everything works correctly a pair of Cube Pros should work exactly as a "dumb" two ports network switch, i.e. connect transparently the devices connected to them (hence the name as "wireless wire").
To change the settings, depending if it is just a few settings/values or entire snippets of configuration you could use Winbox GUI or a terminal window (still open from within Winbox) using command lines (but copy/paste is possible, so it is not particularly difficult)
Re: Question for help on wireless cubes
I guess what i am asking you is if I copy and paste the configurations from that other thread you link will I need to edit it to input any info from my specific devices into that configuration or can I just copy and paste the master and the slave configs into them and have them work without doing any further editing.Yes, you can do the reset from the button or - if you have access to the unit (like you have) from terminal command line or winbox (easier).
See configuration reset here:
https://help.mikrotik.com/docs/display/ ... Management
https://help.mikrotik.com/docs/display/ ... ationReset
The first "symptom" that the new configuration is the right one is that - again in theory - since you have a sticker, the new login will be "admin" and the password the one on the sticker.
Of course there is a risk involved in this procedure, possibilities are:
1) the device is the "right" one (i.e. it has not been exchanged) and the password on the sticker will work (good)
2) the device, no matter if the "right" or an exchanged one has anyway a factory configuration with blank password.(good)
3) the device is definitely an exchanged one, the password is required and the password on the sticker won't work (bad). In this case it is still possible to do a netinstall to recover the unit, but it is a more complex procedure.
Checking the serial numbers of the two devices you have may give a hint (I presume that Cube pairs have consecutive serial numbers, but I may well be completely wrong).
Also the mac addresses in /interface bridge could be sequential.
In any case, before any attempt, you should follow the instructions here:
viewtopic.php?t=203686#p1051720
and export the current configuration of both devices, saving them on your PC.
The files are plain text and the needed info (minus the router password) are in clear text, not obfuscated/encrypted).
The data that changes between sets of pairs (but that you can also change yourself) should be:
password <- /interface w60g
ssid <- /interface wireless, /interface w60g
wpa2-pre-shared-key <-/interface wireless security-profiles
And likely also mac-address and remote-address (in the /interface w60g station settings) but these should be "local" MAC's that can be generated manually.
Once these are set correctly, you just connect one of the two devices to a PC, point it in the general direction of the other, placed a few meters away, connect this latter one to another PC and you should be able to see how the data passes from one PC to the other, if everything works correctly a pair of Cube Pros should work exactly as a "dumb" two ports network switch, i.e. connect transparently the devices connected to them (hence the name as "wireless wire").
To change the settings, depending if it is just a few settings/values or entire snippets of configuration you could use Winbox GUI or a terminal window (still open from within Winbox) using command lines (but copy/paste is possible, so it is not particularly difficult)
Re: Question for help on wireless cubes
Yep, I understand now, you like to win easily, don't you? 
You should never copy and paste a whole configuration anyway.
For three reasons:
1) some commands may sort of overwrite existing settings improperly (as an example increasing a reference)
2) some commands may make no sense (to the underlying RoS) because there is a reference in an early line to something that is defined in a later liner (rare but it may happen)
3) if the configuration you paste is "too much" the buffer/cache/whatever will be flooded resulting in incomplete import/wrong import of some lines
Only snippets you can paste (using some common sense), i.e. section by section, it will take some more time but you will have much more control.
The alternative could be to reset with no default configuration and then import a pre-made configuration, but this is a one shot only (if by any chance there is an error in the configuration that locks you out for whatever reasons you need to re-start from scratch with reset or in some cases even netinstall).
BTW the configurations I posted a link to have some settings that have been (correctlly) anonymized/changed so you would need anyway to edit/correct them, before importing.
These default configurations are short, simple ones, it is not difficult to understand what each setting does/is for (the only slightly complex one is the bonding of the two wireless interfaces).
If it helps you another user on another thread (a newcomer like you) had a similar issue and managed to rebuild a working configuration starting from Quickset (no, do NOT use it for the moment):
viewtopic.php?t=209461#p1087285
So it is doable, you only need some patience.
You should never copy and paste a whole configuration anyway.
For three reasons:
1) some commands may sort of overwrite existing settings improperly (as an example increasing a reference)
2) some commands may make no sense (to the underlying RoS) because there is a reference in an early line to something that is defined in a later liner (rare but it may happen)
3) if the configuration you paste is "too much" the buffer/cache/whatever will be flooded resulting in incomplete import/wrong import of some lines
Only snippets you can paste (using some common sense), i.e. section by section, it will take some more time but you will have much more control.
The alternative could be to reset with no default configuration and then import a pre-made configuration, but this is a one shot only (if by any chance there is an error in the configuration that locks you out for whatever reasons you need to re-start from scratch with reset or in some cases even netinstall).
BTW the configurations I posted a link to have some settings that have been (correctlly) anonymized/changed so you would need anyway to edit/correct them, before importing.
These default configurations are short, simple ones, it is not difficult to understand what each setting does/is for (the only slightly complex one is the bonding of the two wireless interfaces).
If it helps you another user on another thread (a newcomer like you) had a similar issue and managed to rebuild a working configuration starting from Quickset (no, do NOT use it for the moment):
viewtopic.php?t=209461#p1087285
So it is doable, you only need some patience.
Re: Question for help on wireless cubes
In terminal ...
entering
/system default-configuration print without-paging
should show what configuration will be applied if the device is reset. The password on the label should be the one in $defconfPassword
If unsure of this password edit this reset script to use your password or add the link to a custom-script where you add your second user with all priviledges or change the admin password.
This is just the output of one of my devices. Passwords and SSID are not the actual ones in current operational setup. Part of the MAC is leaked here , but OK to me.
entering
/system default-configuration print without-paging
should show what configuration will be applied if the device is reset. The password on the label should be the one in $defconfPassword
If unsure of this password edit this reset script to use your password or add the link to a custom-script where you add your second user with all priviledges or change the admin password.
This is just the output of one of my devices. Passwords and SSID are not the actual ones in current operational setup. Part of the MAC is leaked here , but OK to me.
Code: Select all
[admin@Cube] > system default-configuration print without-paging
script: #| Welcome to RouterOS!
#| 1) Set a strong router password in the System > Users menu
#| 2) Upgrade the software in the System > Packages menu
#| 3) Enable firewall on untrusted networks
#| 4) Set your country name to observe wireless regulations
#| -----------------------------------------------------------------------------
#| W60G Bridge:
#| * W60G and LAN interfaces are bridged;
#| wlan60-1 Configuration:
#| ssid: MikroTik-f9323b;
#| mode: station-bridge;
#| password: yes;
#| IP address 192.168.88.3/24 is set on bridge
#| * 5GHz interface is set as W60G backup using bonding
#| wlan1 Configuration:
#| mode: station-bridge;
#| band: 5ghz-a/n/ac;
#| tx-chains: 0;
#| rx-chains: 0;
#| installation: outdoor;
#| wpa2: yes;
#| ht-extension: 20/40/80mhz-XXXX;
#| Login
#| admin user protected by password
:global ssid;
:global defconfMode;
:log info "Starting defconf script";
#-------------------------------------------------------------------------------
# Apply configuration.
# these commands are executed after installation or configuration reset
#-------------------------------------------------------------------------------
:if ($action = "apply") do={
# wait for interfaces
:local count 0;
:while ([/interface ethernet find] = "") do={
:if ($count = 30) do={
:log warning "DefConf: Unable to find ethernet interfaces";
/quit;
}
:delay 1s; :set count ($count +1);
};
:local count 0;
:while ([/interface w60g print count-only] < 1) do={
:set count ($count +1);
:if ($count = 40) do={
:log warning "DefConf: Unable to find w60g interface(s)";
/ip address add address=192.168.88.1/24 interface=ether1 comment="defconf";
/quit
}
:delay 1s;
};
:local count 0;
:while ([/interface wireless print count-only] < 1) do={
:set count ($count +1);
:if ($count = 40) do={
:log warning "DefConf: Unable to find wireless interface(s)";
/ip address add address=192.168.88.1/24 interface=ether1 comment="defconf";
/quit
}
:delay 1s;
};
/interface bridge
add name=bridge disabled=no protocol-mode=rstp comment=defconf auto-mac=no admin-mac=[/interface ethernet get ether1 mac-address];
/interface bridge port
add bridge=bridge interface=ether1 comment=defconf;
/interface w60g
set wlan60-1 disabled=no
set wlan60-1 ssid=MikroTik-f9323b
set wlan60-1 mode=station-bridge
set wlan60-1 password=$defconfPassword
/ip address add address=192.168.88.3/24 interface=bridge comment="defconf";
/interface wireless {
:local ifcId [/interface wireless find where default-name=wlan1]
:local currentName [/interface wireless get $ifcId name]
security-profile set default mode=dynamic-keys group-ciphers=aes-ccm unicast-ciphers=aes-ccm \
authentication-types=wpa2-psk disable-pmkid=yes wpa2-pre-shared-key=$defconfPassword comment=defconf
set $ifcId mode=station-bridge band=5ghz-a/n/ac disabled=no wireless-protocol=any \
distance=dynamic installation=outdoor
set $ifcId channel-width=20/40/80mhz-XXXX;
set $ifcId frequency=auto
set $ifcId ssid=MikroTik-f9323b
}
/interface bonding add name=bond1 mode=active-backup primary=wlan60-1 slaves=wlan60-1,wlan1 comment="defconf"
:delay 1
/interface bridge port
add bridge=bridge interface=bond1 comment=defconf;
:if (!($defconfPassword = "" || $defconfPassword = nil)) do={
/user set admin password=$defconfPassword
}
}
#-------------------------------------------------------------------------------
# Revert configuration.
# these commands are executed if user requests to remove default configuration
#-------------------------------------------------------------------------------
:if ($action = "revert") do={
/user set admin password=""
/system routerboard mode-button set enabled=no
/system routerboard mode-button set on-event=""
/system script remove [find comment~"defconf"]
/ip firewall filter remove [find comment~"defconf"]
/ip firewall nat remove [find comment~"defconf"]
/interface list member remove [find comment~"defconf"]
/interface detect-internet set detect-interface-list=none
/interface detect-internet set lan-interface-list=none
/interface detect-internet set wan-interface-list=none
/interface detect-internet set internet-interface-list=none
/interface list remove [find comment~"defconf"]
/tool mac-server set allowed-interface-list=all
/tool mac-server mac-winbox set allowed-interface-list=all
/ip neighbor discovery-settings set discover-interface-list=!dynamic
:local o [/ip dhcp-server network find comment="defconf"]
:if ([:len $o] != 0) do={ /ip dhcp-server network remove $o }
:local o [/ip dhcp-server find name="defconf" !disabled]
:if ([:len $o] != 0) do={ /ip dhcp-server remove $o }
/ip pool {
:local o [find name="default-dhcp" ranges=192.168.88.10-192.168.88.254]
:if ([:len $o] != 0) do={ remove $o }
}
:local o [/ip dhcp-client find comment="defconf"]
:if ([:len $o] != 0) do={ /ip dhcp-client remove $o }
/ip dns {
set allow-remote-requests=no
:local o [static find comment="defconf"]
:if ([:len $o] != 0) do={ static remove $o }
}
/ip address {
:local o [find comment="defconf"]
:if ([:len $o] != 0) do={ remove $o }
}
:foreach iface in=[/interface ethernet find] do={
/interface ethernet set $iface name=[get $iface default-name]
}
/interface bridge port remove [find comment="defconf"]
/interface bridge remove [find comment="defconf"]
/interface bonding remove [find comment="defconf"]
/interface wireless cap set enabled=no interfaces="" caps-man-addresses=""
/interface wireless reset-configuration wlan1
/interface wireless security-profile set default mode=none\
authentication-types="" disable-pmkid=no wpa2-pre-shared-key="" comment=""
/interface w60g station remove [find comment="defconf"]
/interface w60g reset-configuration wlan60-1
/caps-man manager set enabled=no
/caps-man manager interface remove [find comment="defconf"]
/caps-man manager interface set [ find default=yes ] forbid=no
/caps-man provisioning remove [find comment="defconf"]
/caps-man configuration remove [find comment="defconf"]
}
:log info Defconf_script_finished;
:set defconfMode;
:set ssid;
caps-mode-script: #-------------------------------------------------------------------------------
# Note: script will not execute at all (will throw a syntax error) if
# dhcp or wireless-fp packages are not installed
#-------------------------------------------------------------------------------
#| CAP configuration
#|
#| Wireless interfaces are set to be managed by CAPsMAN.
#| All ethernet interfaces and CAPsMAN managed interfaces are bridged.
#| DHCP client is set on bridge interface.
# bridge port name
:global brName "bridgeLocal";
:global logPref "defconf:";
:global action;
:log info $action
:if ($action = "apply") do={
# wait for ethernet interfaces
:local count 0;
:while ([/interface ethernet find] = "") do={
:if ($count = 30) do={
:log warning "DefConf: Unable to find ethernet interfaces";
/quit;
}
:delay 1s; :set count ($count + 1);
}
:local macSet 0;
:local tmpMac "";
:foreach k in=[/interface ethernet find] do={
# first ethernet is found; add bridge and set mac address of the ethernet port
:if ($macSet = 0) do={
:set tmpMac [/interface ethernet get $k mac-address];
/interface bridge add name=$brName auto-mac=no admin-mac=$tmpMac comment="defconf";
:set macSet 1;
}
# add bridge ports
/interface bridge port add bridge=$brName interface=$k comment="defconf"
}
# try to add dhcp client on bridge interface (may fail if already exist)
:do {
/ip dhcp-client add interface=$brName disabled=no comment="defconf"
} on-error={ :log warning "$logPref unable to add dhcp client";}
# try to configure caps (may fail if for example specified interfaces are missing)
:local interfacesList "";
:local bFirst 1;
# wait for wireless interfaces
:while ([/interface wireless find] = "") do={
:if ($count = 30) do={
:log warning "DefConf: Unable to find wireless interfaces";
/quit;
}
:delay 1s; :set count ($count + 1);
}
# delay just to make sure that all wireless interfaces are loaded
:delay 5s;
:foreach i in=[/interface wireless find] do={
if ($bFirst = 1) do={
:set interfacesList [/interface wireless get $i name];
:set bFirst 0;
} else={
:set interfacesList "$interfacesList,$[/interface wireless get $i name]";
}
}
:do {
/interface wireless cap
set enabled=yes interfaces=$interfacesList discovery-interfaces=$brName bridge=$brName
} on-error={ :log warning "$logPref unable to configure caps";}
}
:if ($action = "revert") do={
:do {
/interface wireless cap
set enabled=no interfaces="" discovery-interfaces="" bridge=none
} on-error={ :log warning "$logPref unable to unset caps";}
:local o [/ip dhcp-client find comment="defconf"]
:if ([:len $o] != 0) do={ /ip dhcp-client remove $o }
/interface bridge port remove [find comment="defconf"]
/interface bridge remove [find comment="defconf"]
}
custom-script: Re: Question for help on wireless cubes
One last question do I need to change the local IP address on the units to match my current Network so they provide the same IP address game on the other end of the point-to-pointYep, I understand now, you like to win easily, don't you?
You should never copy and paste a whole configuration anyway.
For three reasons:
1) some commands may sort of overwrite existing settings improperly (as an example increasing a reference)
2) some commands may make no sense (to the underlying RoS) because there is a reference in an early line to something that is defined in a later liner (rare but it may happen)
3) if the configuration you paste is "too much" the buffer/cache/whatever will be flooded resulting in incomplete import/wrong import of some lines
Only snippets you can paste (using some common sense), i.e. section by section, it will take some more time but you will have much more control.
The alternative could be to reset with no default configuration and then import a pre-made configuration, but this is a one shot only (if by any chance there is an error in the configuration that locks you out for whatever reasons you need to re-start from scratch with reset or in some cases even netinstall).
BTW the configurations I posted a link to have some settings that have been (correctlly) anonymized/changed so you would need anyway to edit/correct them, before importing.
These default configurations are short, simple ones, it is not difficult to understand what each setting does/is for (the only slightly complex one is the bonding of the two wireless interfaces).
If it helps you another user on another thread (a newcomer like you) had a similar issue and managed to rebuild a working configuration starting from Quickset (no, do NOT use it for the moment):
viewtopic.php?t=209461#p1087285
So it is doable, you only need some patience.
Re: Question for help on wireless cubes
Same IP address range is not needed for their operation. They make a bridged (L2) connection between the end-points.
IP addresses are L3 as you know. If you want to get to the Cube devices via IP address, then give them a reachable address.
These IP address do not change the working of the link, they are not part of the link, with the bridged setup.
IP addresses are L3 as you know. If you want to get to the Cube devices via IP address, then give them a reachable address.
These IP address do not change the working of the link, they are not part of the link, with the bridged setup.
Re: Question for help on wireless cubes
To expand on the above, wireless wire kit is philosophically like a two ports managed switch. An IP address for it is needed only for management, it can be *any* address, as long as it is reachable.
This particular two ports switch is however divided in two, so it needs two IP addresses, again, since they are only used for configuration, as long as the two addresses are reachable, they can be *any*.
If you only use Winbox (via MAC) you actually don't even *need* these devices to have an IP address at all.
This particular two ports switch is however divided in two, so it needs two IP addresses, again, since they are only used for configuration, as long as the two addresses are reachable, they can be *any*.
If you only use Winbox (via MAC) you actually don't even *need* these devices to have an IP address at all.