netguyz08 wrote:
I think this has been mentioned before, but I thought it might be a little different when the VLANs (which have totally separate IP address ranges) were all going through the same switch. They aren't discovered at all.
In fact, it leads me to believe why one server isn't showing up that has 3 NICs. Two of the NICs are on separate VLANs, but the remaining one doesn't show up at all. I even tried to add its MAC and IP address as a device, it accepted it, but then it doesn't show up at all.
Edward,
We haven't yet started development for supporting multiple VLANs or multiple subnets, so it's not surprising that the other 2 NICs aren't being seen by the TBA. We understand the absolute necessity of eventually supporting both of these for small business networks, but it's a complicated problem that we're looking into how to best handle. The main complication is that when the TBA isn't in the same broadcast domain it's difficult to discover things because we can't learn the MAC address to associate the device with. We're currently experimenting with a new kernel with multi-VLAN support, so there is at least progress on this front.
On the 3rd NIC, which presumably is in the same VLAN as the TBA, is it addressed on a different IP subnet than what the TBA is on (via DHCP)? If so, can it ping the TBA? If not, TBA won't currently discover it because of the current limitation of a single IP subnet. TBA currently disregards any IP not on the same subnet, as we didn't want edge devices such as ISP routers or further out on the internet to start leaking into the topology. We'll eventually address this limitation too.
-mike
