Multiple Interfaces for Multiple Subnet/Vlan Support

Jon_IrishJon_Irish Posts: 19Member, Beta Tester
10 Comments 5 Likes Name Dropper Photogenic
✭✭
edited November 2019 in Fingbox feature requests
Please consider adding multiple interfaces to the fingbox so that it can support multiple subnets/vlans. Even home networks need to be segmented. Everyone in cyber security recommends that IoT devices be hosted on segmented vlan that has no access to the internal home LAN. Thus, a fingbox with at least 2 interfaces (preferably more) is more of a requirement that an option. Please consider this in future revisions of the fingbox.
VioletChepilChiefplumberJon_IrishDGMacLeanmozarellaFingUserWarrenBelgarathRHHGPpanxytras78TheBigBear6t9camaroatomicboyBiggsRichCreedyDawwenMohamed_SultanItoTItan
19
19 votes

Active · Last Updated

Comments

  • VioletChepilVioletChepil London, UKPosts: 2,471Member
    100 Answers 500 Likes 1000 Comments 100 Agrees
    ✭✭✭✭✭✭
    Thanks for submitting! 

    Community Manager at Fing

  • ChiefplumberChiefplumber Posts: 9Member, Beta Tester
    5 Likes Photogenic Founder First Comment
    ✭✭
    I second the feature request.  FingBox is a fantastic device.  I love the monitoring, performance testing capabilities and the device alerts.  I started the multi-LAN thread because many homes are more complex than they appear at first glance.  I have two separate physical LANs in my home, one for the Verizon router and STBs and the primary LAN for "everything" else.  The VZ router/LAN sits behind my router/firewall and gets its "external" address from my primary LAN DHCP server.  ActionTec happens to make LAN extenders that externalize the IP over Coax.  I use these devices to provide RJ45 and WiFi connectivity in hard to reach areas of my house.  Any devices on the ActionTec network extensions receives VZ router addresses, not "primary LAN" addresses.  In addition, I have a third subnet on the firewall for external VPN access and a guest SSID/vLAN on my access points.  In addition,  SONOS creates a SONOSNet mesh for the wireless speaker system.  That's a lot of stuff and I am sure I am not unique.  A higher feature level FingBox with multiple (2 for me) Ethernet interfaces and the ability to understand vLANs would be worth more than the single interface FingBox.  I want to purchase a solution, not rent a capability for $19/month.  I only have one high speed Internet connection so I don't "need" two FingBoxes, two Fing accounts, etc.

    Please help!
  • VioletChepilVioletChepil London, UKPosts: 2,471Member
    100 Answers 500 Likes 1000 Comments 100 Agrees
    ✭✭✭✭✭✭
    Thanks @Chiefplumber - just add your upvote above as well and also @Jon_Irish you can add that in too.
    Just click the upvote above :smile: as I did! 

    Community Manager at Fing

  • vicorlyvicorly Posts: 6Member, Beta Tester
    First Comment Photogenic
    Yeah I wish Fingbox could support multiple subnets, not necessarily VLANs. I have a client where I just installed a nice SonicWALL NSA 2650. Ethernet LAN is 10.0.25.x. Primary WLAN is 10.0.26.x, Guest WLAN is 172.16.7.x - would like the Fingbox to be able to scan all 3.
  • VioletChepilVioletChepil London, UKPosts: 2,471Member
    100 Answers 500 Likes 1000 Comments 100 Agrees
    ✭✭✭✭✭✭
    @vicorly thanks for the feedback and adding to the thread. Don't forget to add your up vote in above as well. 

    Community Manager at Fing

  • DGMacLeanDGMacLean Posts: 2Member, Beta Tester
    Photogenic First Comment
    I too would like to see support for multiple subnets and VLANs. In my home the ISP's devices distribute the cableTV service and my own devices connect to a subordinate WiFi router in an different subnet. Both are distributed using separate 802.1q VLANs on the house's coax cable, and my FingBox sits on a trunk port where it can see the coming and going of various devices by MAC address but can only sort out the IP addresses on its own subnet (the default untagged VLAN on its trunk port). It would be wonderful if its UTP cable port were VLAN-aware and could learn (perhaps via DHCP) about the various subnets on the trunk.
  • VioletChepilVioletChepil London, UKPosts: 2,471Member
    100 Answers 500 Likes 1000 Comments 100 Agrees
    ✭✭✭✭✭✭
    @DGMacLean thanks a lot. Don't forget to add your upvote above! 

    Community Manager at Fing

  • GPpanGPpan Posts: 1Member
    First Comment
    802.1q support would be wonderful.  I have separate VLAN's in my network (Guest, Prod, DMZ) that are controlled by my Cisco switches and Aruba wireless controller.  Right now I would need multiple Fing Boxes to do all my networks.  Having this all on one device would be great to monitor both VLAN's.
  • TheBigBearTheBigBear Posts: 1Member
    First Comment Photogenic
    Yes, I also have a properly segregated home network, DMZ, Guest, Private and Family. Need to be able to set VLAN tag on fingbox interface
  • DawwenDawwen Posts: 1Member
    First Comment Photogenic

    Wow, just wandered in thinking about suggesting this bit thought would there be any other demand. Glad to see I'm not alone. Definite upvote here for the VLAN/.1q trunk support. The ability to treat each net differently would also be awesome eg. Allow everything that joins the guest net, but default deny additions/whitelist access only on other nets kinda of thing. And if all this activity could be dumped out via syslog I'd be super happy.

Sign In or Register to comment.