Chromecast Access Control Across VLANs (Linux + mDNS Proxy + REST API)
Budget: $250 – $750 USD
Overview:
We’re looking for a skilled developer or network engineer with experience in Linux, VLANs, mDNS, and API development, to implement a solution that allows discovery and casting to Chromecast devices from clients located in different VLANs, with access controlled via a RESTful HTTP API.
Goal:
Enable specific client devices to discover and cast content (Netflix, HBO, Apple TV+, etc.) to selected Chromecast devices, even if they are on different VLANs. The solution should include a custom mDNS proxy and an ACL system (Access Control List) managed via a REST API.
Network Structure:
- VLAN 10 (192.168.40.0/24) → Chromecast devices
- VLAN 20 (10.30.10.0/24) → Client devices
Devices involved
- Chromecast A, B, C
- Client Devices A, B, C
Project Requirements:
- A Linux server with at least 2 physical or virtual network interfaces (one per VLAN).
- The server will act as an mDNS proxy bridge between the VLANs to allow Chromecast discovery.
- No static routes or router configuration is allowed on the client VLAN (VLAN 20) — this network is out of our control.
- The server must provide DHCP services for VLAN 10 (Chromecast segment).
- Implement ACL logic to define which clients can discover and cast to specific Chromecast devices (e.g., Client A → Chromecast B).
- The ACL must be managed via a RESTful HTTP API, with endpoints to:
- Register Chromecast and client devices
- Create, update, and delete ACL rules
- List allowed client-Chromecast associations
- Support multiple clients discovering and casting to the same Chromecast simultaneously.
- The entire system must be persistent and auto-start on reboot (via systemd or similar).
- The complete and functional source code must be delivered as part of the final deliverables.
Deliverables:
- Linux server setup with 2+ NICs, each in its corresponding VLAN
- Functional DHCP service for VLAN 10
- Working mDNS proxy between VLANs with ACL enforcement
- Fully documented REST API for managing ACLs
- Functional source code of all components
- Setup documentation (how to install, run, and manage the system)
- Testing and validation (clients discovering and casting only to allowed Chromecasts)
- Functional testing showing that:
- Clients can only see permitted Chromecasts
- Unauthorized clients see no Chromecasts
- Multiple authorized clients can share a Chromecast
Constraints:
- No access or configuration changes allowed on the client VLAN router (VLAN 20)
- Everything must be managed and controlled from the Linux bridge server
We’re looking for a skilled developer or network engineer with experience in Linux, VLANs, mDNS, and API development, to implement a solution that allows discovery and casting to Chromecast devices from clients located in different VLANs, with access controlled via a RESTful HTTP API.
Goal:
Enable specific client devices to discover and cast content (Netflix, HBO, Apple TV+, etc.) to selected Chromecast devices, even if they are on different VLANs. The solution should include a custom mDNS proxy and an ACL system (Access Control List) managed via a REST API.
Network Structure:
- VLAN 10 (192.168.40.0/24) → Chromecast devices
- VLAN 20 (10.30.10.0/24) → Client devices
Devices involved
- Chromecast A, B, C
- Client Devices A, B, C
Project Requirements:
- A Linux server with at least 2 physical or virtual network interfaces (one per VLAN).
- The server will act as an mDNS proxy bridge between the VLANs to allow Chromecast discovery.
- No static routes or router configuration is allowed on the client VLAN (VLAN 20) — this network is out of our control.
- The server must provide DHCP services for VLAN 10 (Chromecast segment).
- Implement ACL logic to define which clients can discover and cast to specific Chromecast devices (e.g., Client A → Chromecast B).
- The ACL must be managed via a RESTful HTTP API, with endpoints to:
- Register Chromecast and client devices
- Create, update, and delete ACL rules
- List allowed client-Chromecast associations
- Support multiple clients discovering and casting to the same Chromecast simultaneously.
- The entire system must be persistent and auto-start on reboot (via systemd or similar).
- The complete and functional source code must be delivered as part of the final deliverables.
Deliverables:
- Linux server setup with 2+ NICs, each in its corresponding VLAN
- Functional DHCP service for VLAN 10
- Working mDNS proxy between VLANs with ACL enforcement
- Fully documented REST API for managing ACLs
- Functional source code of all components
- Setup documentation (how to install, run, and manage the system)
- Testing and validation (clients discovering and casting only to allowed Chromecasts)
- Functional testing showing that:
- Clients can only see permitted Chromecasts
- Unauthorized clients see no Chromecasts
- Multiple authorized clients can share a Chromecast
Constraints:
- No access or configuration changes allowed on the client VLAN router (VLAN 20)
- Everything must be managed and controlled from the Linux bridge server