Make device discoverable on second subnet

I have successfully set up 2 subnets, 192.168.88.0/24 and 192.168.99./24 on my mikrotik router. The first is accessed by wifi devices on the the main wifi interface; the second by a virtual wifi interface.

So far so good :smiley:

There is a device connected to eth1 with a fixed ip of 192.168.88.2. When by laptop is connected to the second subnet (12.168.99.0/24) discovery software is unable to find the deivce, I presume because it doesn’t have an ip address on this second subnet.

Following this topic: http://forum.mikrotik.com/t/accessing-device-with-different-subnet/105678/1 I can establish a connection to the device through a browser, but the discovery software does not find it.

How can I give one device an ip on both subnets, not just the main one so that the discovery software will find it?

(Quite new to all this so may be using wrong terminology)

Most “discovery” operations require layer 2 adjacency. A different IP subnet creates separation at layer 3.

An example “discovery” mechanism is Bonjour which is bound at layer 2 or link-local. Their is technology solutions that enable you to “stretch” (read: bridge) the Bonjour traffic across layer 3 boundaries. Although this technology is fairly ubiquitous in the enterprise because it’s the easy button it’s often a very bad security practice. It’s definitely something that was thought about with Bonjour and other “discovery” type of services. When it is required that a service be discoverable over layer 3 boundaries it’s often best to look to DNS-SD or DNS based Service Discovery. This uses DNS records to help an application discover services that are not layer 2 adjacent.

I have a similar situation device on another subnet.
i simply created a forward chain firewall rule.
source address (my pc) to destination IP (device) allow
both the discovery software and browser based connections work.