Ethernet IoT Devices

IoT
1

I have a Flint 2 router, and I’ve recently begun setting up an IoT network, and migrating my IoT devices over to it. However, I have a Sengled Zigbee hub that connects via Ethernet directly to my router.

If the Sengled Hub is a weak point in my network that could potentially be exploited, I want to isolate it in my IoT network like the rest of the IoT devices, and not let it access my main network. How can I accomplish that for an ethernet based IoT hub? Or am I overthinking this?

I am also considering setting up a Raspberry Pi and playing with Home Assistant, so I may just buy a Zigbee adapter for the Pi, but if I do that I would still likely want the Pi connected via Ethernet for stability without exposing my network.

Kind of a baby at networking beyond setting up a basic WiFi router, but I bought the Flint 2 after researching new routers to upgrade from my Wifi 5 router earlier this year and I’ve been slowly learning.

2

The new Flint4 got a advanced VLAN segmentation feature.

As this is a firmware feature, not limited by the Hardware, I assume it will follow at other routers as well. When it proven working.

I wanted the same, but my approach is a bit more complex: Openwrt New Home Network | LupusE webLife … it is working (with some adjustments) in my home.

The easy way is to wait for GL.iNet to improve and roll out the new firmware features. And I assume the Flint2 as flagship will be in the process.

The hard way is to switch to OpenWrt, which works reliable and stable. But needs aot of love and time.

Edit; preview of the GL.iNet way: Ethernet Port (Firmware v4.10) - GL.iNet Router Docs 4 … very simple and easy to configure

4

Hi,

Flint 2 now has an SDK v4.11 Beta firmware available. If you are willing to try the beta firmware, this configuration can be done directly from the GL.iNet Admin Panel.

After upgrading, go to NETWORK → Ethernet Port , select the LAN port you would like to use for the Sengled Hub, keep it in Standard Mode , and set Access Network to the IoT Network .

image
image1481×652 42 KB

Then the device connected to this port will then become part of the IoT network.

If you prefer to stay on your current firmware, you can also configure this through LuCI:

  1. Go to SYSTEM → Advanced Settings → Go to LuCI .
  2. Go to Network → Interfaces → Devices .
  3. Edit br-lan and remove the LAN port you would like to use for IoT.
  4. Edit br-iot and add the same LAN port to its Bridge ports .
  5. Click Save & Apply .
    image
    image817×191 13.3 KB

    image
    image715×543 27.3 KB

    image
    image
    image723×543 27 KB
5

I want to do this with the Brume 3. When will that and the Flint 4 get v4.11?

6

Hi,

Currently, you can configure the Brume 3 (GL-MT5000) through LuCI to assign a physical LAN port to an isolated IoT network. On the Flint 4, this configuration can already be completed directly through the Web Admin Panel.

The SDK v4.11-based firmware for the Flint 4 is currently being adapted and is expected to become available within a month.

For the Brume 3, we do not have a specific SDK v4.11 release timeline at this time.

7

I seem to get the sense that some models have lower priority. Why? I feel like neither the Brume 3 nor the Mudi 7 gets the attention it deserves.

8

Some features are hardware dependent.

I don't know how the VLAN in particular is included in this, I need to investigate how the internal switch can be addressed per port or similar.

But I know for Mesh it is easily to check if the device supports it: Testing to determine if you are a bot! … I assume this is similar to the VLAN support and if you overlay it it will lead to a very slow device.

That's in a nutshell, why it seems they are getting less attention.