Telnet over second network interface?

Question

linux

Good day to all!
I have on board Debian Jessie and several network adapters for several networks that do not intersect with each other. Accordingly, I have several network interfaces. How to telnet through secondary network interfaces?
There are for pings ping -I "interface", for nmap nmap -e "interface", but for telnet I did not find a parameter (I think the same balalaika with ssh). At first I thought routes. Registered a route through the second interface - nothing. Google suggested something about netcat, but my magic did not work.
Tell me how to solve this with less losses?
Setting output:

[email protected]:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:1a:4d:5d:7b:e2 brd ff:ff:ff:ff:ff:ff
    inet 10.3.196.78/23 brd 10.3.197.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet 192.168.1.50/24 brd 192.168.1.255 scope global eth0:1
       valid_lft forever preferred_lft forever
    inet6 fe80::21a:4dff:fe5d:7be2/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
    link/ether 00:01:02:1e:b4:b2 brd ff:ff:ff:ff:ff:ff
    inet 16.1.0.253/16 brd 16.1.255.255 scope global eth1
       valid_lft forever preferred_lft forever
    inet 192.168.1.253/24 brd 192.168.1.255 scope global eth1:0
       valid_lft forever preferred_lft forever
    inet6 fe80::201:2ff:fe1e:b4b2/64 scope link 
       valid_lft forever preferred_lft forever

[email protected]:~$ ip r
default via 10.3.196.1 dev eth0 
10.3.196.0/23 dev eth0  proto kernel  scope link  src 10.3.196.78 
16.1.0.0/16 dev eth1  proto kernel  scope link  src 16.1.0.253
192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.50 
192.168.1.0/24 dev eth1  proto kernel  scope link  src 192.168.1.253

Answer 1

It seems that there is no way to solve this problem. There is only one way out - disable / enable routes.

Answer 2

Uh dear telnet is what kind of traffic? correct ICMP
hence this is the broadcast range. It is lower level than tcp/ip so your IPs are not needed here at all.
iptables to help you