This Is a very noob question, Just to understand how can I test remote located devices.
I have 2 switches
Both have 1 bridge with all interfaces inside.
The 2 switches are interconnected through Eth1.
On the First switch There are some workstations connected.
On the second switch There is no device connected.
I want to test ping from One of the porta in the second switch to One of the devices connected tò the First One, but Is a remote location so I cannot attach nothing to the second switch.
This Is at a very basic level, I mean that I want to understand how can I simulate devices or IPs on a Port. I tried to add an IP to second switch Eth1, but if Eth1 Is inside the bridge It Will not ping, if I remove Eth1 from the bridge I can ping.
You can not simulate pings from specific ports of a switch.
Switches (and bridges) operate on layer 2 - ethernet. In this context ports do matter as switches only forward traffic through single port if they learn destination’s port.
Ping is layer 3 - IP (actually layer 4 - ICMP, but this doesn’t matter much in this discussion). And switch (running ROS) has IP address configured on bridge interface which is a software interface connecting CPU with bridge (switch like entity … or switch chip if you want) over bridge port (which is logically napped on switch-CPU interconnect).
Which means that you can not simulate connectivity through a particular bridge/switch port by runing commands on device’s CPU.
want to test ping from One of the porta in the second switch to One of the devices connected tò the First One, but Is a remote location so I cannot attach nothing to the second switch.
which requires a mac-server and mac-client for you to try pinging remote mac address (just like you do ip ping) - as long as those devices are on the same subnet/vlan since mac address doesn’t go through a router. this tool works in osi layer 2.
by the way - this protocol said to be developed by our beloved MikroTik - so, a huge applause for MT (cmiiw)
… which unfortunately doesn’t help in OP’s scenario.
To actually simulate a device, connected via a particular switch port, any tool would have to inject ethernet frame to that particular switch port Rx buffer so that switch chip learns source MAC address as being behind that port. And then when return frame arrives at that particular port’s Tx buffer, that tool would have to fetch it from this buffer (before switch chip flushes it through related physical port). And we didn’t even touch the issue of how switch chip adapts to ports being down (it might completely disable port’s Rx and Tx buffers FWIW) making wanted simulation next to impossible.
I’m not saying that it’s impossible to manipulate Rx and Tx buffers of individual switch ports via some management connection to switch ship, but I’m not aware of such functionality (neither provided by switch chips nor exposed by ROS). And mac-telnet most certainly doesn’t have ambitions to do it, its only ambition is to provide telnet-like functionality without relying on properly set-up IP layer (the difference between mac-telnet and plain telnet is that the former works directly with L2 and crafts MAC addresses used so that it bypasses usual ARP procedures, these require valid IP addresses set on both connection parties).
(cmiiw)