Community discussions

MikroTik App
 
travisres
just joined
Topic Author
Posts: 17
Joined: Wed May 29, 2013 11:53 pm

Metal only accessible via Telnet on another RouterBoard

Fri Feb 14, 2014 3:18 pm

I'm hoping I'm missing something dumb in my routing table that someone else will spot.
I have a core RB (RB2011-UAS) running 2 networks a x.x.222.0/23 (Main Data) and a x.x220.0/24 (VoIP). Each is in its own bridge on the main RB with ethernet ports assigned appropriately.
On the VoIP network/bridge I have plugged a Metal 2SHPn which is creating a Wifi network for the VoIP gear. From a computer on my main Data network, I can ping / gain access to devices connected to the VoIP network via wireless. Devices on the wireless network can do what they are supposed to do.
The problem is that I can't access the Metal itself from the Data network. Win box, ssh or telnet all time out from any computer on the data network.
I am able to telnet to it FROM the terminal in winbox when connected to the core router.

When telnetted in, I can confirm that the correct services are turned on. There are no firewall filters. Am I missing something dumb?

Partial config below. I can do a full export if needed.

Ether8-VOIPANT on the RB2011 is connected to Ether1-Local

RB2011-UAS
/interface print 
Flags: D - dynamic, X - disabled, R - running, S - slave 
 #     NAME                                TYPE         MTU L2MTU  MAX-L2MTU
 0  R  ether1-WAN                          ether       1500  1522       4074
 1   S ether2                              ether       1500  1522       4074
 2  RS ether3-PERTH                        ether       1500  1522       4074
 3   S ether4-DATA5                        ether       1500  1522       4074
 4  RS ether5-SWITCH                       ether       1500  1522       4074
 5   S ether6                              ether       1500  1598       2028
 6  RS ether7-PRINTER                      ether       1500  1598       2028
 7  RS ether8-AIRPORT                      ether       1500  1598       2028
 8  RS ether9-VOIPANT                      ether       1500  1598       2028
 9  RS ether10-VOIPBOX                     ether       1500  1598       2028
10     sft1                                ether       1500  1522       4074
11  R  BR_DATA                             bridge      1500  1522
12  R  BR_VOIP                             bridge      1500  1598
/ip address print
Flags: X - disabled, I - invalid, D - dynamic 
 #   ADDRESS            NETWORK         INTERFACE                                         
 0   192.168.222.1/23   192.168.222.0   BR_DATA                                                                               
 1   192.168.220.1/24   192.168.220.0   BR_VOIP                                           
 2 D 10.64.41.86/24     10.64.41.0      ether1-WAN
/ip route print
#      DST-ADDRESS        PREF-SRC        GATEWAY            DISTANCE
 0 ADS  0.0.0.0/0                          10.21.49.1                0
 1 ADC  10.21.49.0/24      10.21.49.18     ether1-WAN                0
 2 ADC  192.168.220.0/24   192.168.220.1   BR_VOIP                   0
 3 ADC  192.168.222.0/23   192.168.222.1   BR_DATA                   0
Metal 2SHNPn
/interface print
Flags: D - dynamic, X - disabled, R - running, S - slave 
 #     NAME                                TYPE         MTU L2MTU  MAX-L2MTU MAC-ADDRESS      
 0  RS ether1-local                        ether       1500  1598       2028 D4:CA:6D:7B:0E:7A
 1  RS wlan1-VOIP                          wlan        1500  2290            D4:CA:6D:7B:0E:7B
 2  R  BR_wifi                             bridge      1500  1598            D4:CA:6D:7B:0E:7A
/ip address print
Flags: X - disabled, I - invalid, D - dynamic 
 #   ADDRESS            NETWORK         INTERFACE                                                  
 0   192.168.220.2/24   192.168.220.0   ether1-local
/ip route print
Flags: X - disabled, A - active, D - dynamic, 
C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, 
B - blackhole, U - unreachable, P - prohibit 
 #      DST-ADDRESS        PREF-SRC        GATEWAY            DISTANCE
 0 ADC  192.168.220.0/24   192.168.220.2   BR_wifi                   0
 
User avatar
rickfrey
Trainer
Trainer
Posts: 609
Joined: Sun Feb 14, 2010 11:41 pm
Location: Van, Texas
Contact:

Re: Metal only accessible via Telnet on another RouterBoard

Fri Feb 14, 2014 8:08 pm

The metal is missing the default route. Add:
/ip route
add gateway=192.168.222.1
It should work once you do that.
 
travisres
just joined
Topic Author
Posts: 17
Joined: Wed May 29, 2013 11:53 pm

Re: Metal only accessible via Telnet on another RouterBoard

Fri Feb 14, 2014 10:52 pm

Thanks very much. I had a feeling it would be something stupid. FYI, i actually had to add the default gateway as 192.168.220.1, not 222.1. But you got me to the right place which is what counts.

Thanks again,
 
User avatar
rickfrey
Trainer
Trainer
Posts: 609
Joined: Sun Feb 14, 2010 11:41 pm
Location: Van, Texas
Contact:

Re: Metal only accessible via Telnet on another RouterBoard

Fri Feb 14, 2014 11:10 pm

Glad I could help! :D