Mark device/interface as "child" of other device/interface

Options
Maverick87
Maverick87 Posts: 60 image  Ally Member
First Comment Friend Collector
edited December 2 in Nebula Ideas

Hello everyone,
I've a USG Flex 200HP firewall, and use:

  • An external switch (not Zyxel) for extend network topology
  • A NWA130BE for Wireless devices

The NWA130BE is not configured for join to NCC and is not managed by the firewall.

Entering to the NCC portal, under the network topology I see this:

image.png image.png

As you can see, all the devices (also an Android phone, the dishwasher, etc etc) are all part of the NETWall (the firewall).
Obviously all these devices, are attached to a single "physical port" as per native device.
For example, the switch are attached to the port 2 (is a 2.5Gbit switch) and the NWA130BE Access Point are attached to an port of the switch.

Example:
FW —> Switch 2.5Gbit (on port 2 of the FW) —> NWA130BE (on port 2 of the switch)
FW —> Switch 2.5Gbit (on port 2 of the FW) —> MBP-di-Valerio (Macbook)
FW —> Switch 2.5Gbit (on port 2 of the FW) —> My work PC
FW —> Raspberry PI (on port 3 of the FW)

In my strict case, I also have some VNET that is "translated" into a VLAN interfaces.

But all of these devices are recognized as "child" of the FW.

My idea is to "mark" a devices or an interface as a child/sub-child and in this case, the network topology follow the child/sub-child assigments, can be also interesting mark the devices as wired or wireless devices can be usefull.

1 votes

Active · Last Updated

Nebula Tips & Tricks