Home/Platform/Cross-network sharing

Screen sharing across guest Wi-Fi, VLANs, and segmented networks.

Subnets, VLANs, guest Wi-Fi, LTE, the building across town: one workspace, no VPN, no UC call, no cables. This is the capability that sets Polaris apart.

Polaris sessions on a rotating wireframe globe An orthographic wireframe Earth, drawn as a coastline and a fifteen-degree graticule, which can be dragged to rotate. Marked on it are sharing devices, meeting-room displays and Polaris Cloud signaling regions. Sessions play in a loop: both ends of a share open an outbound connection to a signaling region, the region introduces them, and the content itself then travels along a single direct arc between the two endpoints while the signaling links go idle. In the last session of the loop the two ends sit behind a network that will not allow a direct path, the direct arc breaks at a marked obstruction, and the encrypted content instead takes one extra hop through a relay before reaching the display. EU WESTDENVERLONDON
Every session here crosses a network

Guest on LTE in London shares to a Denver boardroom. Both ends dial out; media goes direct.

signaling — outbound TLS 443, both ends dial out media — direct between the two endpoints relayed media — the fallback, one extra hop a NAT no direct path can cross
GUEST DEVICEguest Wi-Fi / LTEPOLARIS CLOUDsignaling brokerPOLARIS PODdisplay · AV VLAN1 · DIAL OUT · TLS 4431 · DIAL OUT · TLS 443both connections start inside the network: no inbound rules, no open ports2 · SCREEN KEY · K7RM2XKEY RESOLVES TO THIS ROOM3 · SDP · ICE EXCHANGED3 · SDP · ICE EXCHANGEDeach side learns a direct path to the other4 · DIRECT MEDIA · ENCRYPTED · DTLS-SRTPEPHEMERAL UDP · PEER-TO-PEER · SOLICITED FLOW PASSES THE STATEFUL FWCLOUD IDLE · OUT OF THE MEDIA PATH5 · UNSOLICITED PACKET✕DROPPED · NO RULE MATCHESSTATEFUL FW · OUTBOUND ONLYSTATEFUL FW · OUTBOUND ONLYCNX-01 · CROSS-NETWORK DATA PATH · TIME RUNS DOWNWARD · CLOUD = SIGNALING ONLYSHEET 1/1 · REV C1 · NO ROUTEGuest Wi-Fi and the display’s VLANhave no route between them.DISPLAY · AV VLANGUEST DEVICE✕2 · THE HANDSHAKEBoth sides dial out to Polaris Cloud:TLS 443, signaling only.POLARIS CLOUDSDP · ICE3 · DIRECT MEDIAThe cloud introduces them, then steps away.Media flows device-to-device, encrypted.CLOUD · OUT OF THE MEDIA PATHENCRYPTED · P2P
1. A guest on LTE tries to reach the display directly. No route exists, and none will be created.2. The share leaves their browser instead: outbound TLS signaling on TCP 443 to webrtc.mersive.com.3. The cloud introduces the two endpoints; they negotiate a direct, encrypted WebRTC connection. Nothing routes through Mersive; nothing bridges.4. Content flows device-to-display over that direct connection. Signaling is outbound-only on both sides: no inbound firewall rules.
thin dashes: signaling to the cloud, outbound TLSbold lines: media, direct between endpointsguest shares from the browser, no apphatched walls: routes that never exist; openings: negotiated flows only
The fallback, in full

When no direct path can be formed, the media takes one relayed hop.

The globe above ends one session in four this way. This is that hop, message by message — what the relay is asked for, what it is allowed to forward, and what it can see.

SHARING DEVICEbehind symmetric NATTURN RELAYpublic address, no NATPOLARIS PODdisplay · AV VLAN1 · SYMMETRIC NAT · A DIFFERENT EXTERNAL PORT FOR EVERY DESTINATIONoutbound, succeeds — mapped to 203.0.113.7:51000the display answers to 203.0.113.7:51000✕that mapping is valid only for traffic to the region that opened it — so the check is dropped, and no candidate pair succeeds2 · ALLOCATE · THE DEVICE ASKS THE RELAY FOR AN ADDRESS OF ITS OWNAllocate401 Unauthorized · realm + nonceAllocate · USERNAME · MESSAGE-INTEGRITYSuccess · XOR-RELAYED-ADDRESS · LIFETIME 600 s198.51.100.20:49200a public address that belongs to the device but lives on the relay. One NAT mapping, one destination — which is the thing symmetric NAT does not break3 · CREATEPERMISSION · THE RELAY IS TOLD WHO MAY REACH ITCreatePermission · XOR-PEER-ADDRESS · 300 sthe relay forwards from that one peer address and drops everything else — it is an allocation, not an open reflector4 · CHANNELBIND · 36 BYTES OF PER-PACKET OVERHEAD BECOME 4ChannelBind · channel number · 600 s5 · RELAYED MEDIA · ENCRYPTED · ONE EXTRA HOPDTLS-SRTP END TO END · THE RELAY FORWARDS CIPHERTEXT IT HOLDS NO KEY FORSYMMETRIC NATSTATEFUL FWCNX-02 · RELAYED FALLBACK · TIME RUNS DOWNWARD · RFC 8656 MECHANICS · RFC 5737 ADDRESSESSHEET 1/1 · REV A1 · NO DIRECT PATHA symmetric NAT uses a differentexternal port for every destination.DEVICEDISPLAY✕2 · ALLOCATEThe device asks a relay for a publicaddress of its own, and authenticates.TURN RELAY198.51.100.20:49200LIFETIME 600 s · ONE PEER PERMITTED3 · RELAYED MEDIAOne extra hop. The relay forwardsciphertext it holds no key for.DTLS-SRTP · END TO END

A symmetric NAT gives every destination a different external port, so the address the display was handed is not the address packets would arrive from.

the device and its NATrelay control messages, then relayed mediaencryption the relay is outside ofhatched walls: the NAT and the firewall, neither of which is opened
Where this saves the day

Three rooms that break a LAN-local system.

The guest presenter

A board member walks in on LTE. No guest Wi-Fi sign-up, no VPN token, no dongle. They join the workspace from a browser and present in under a minute, with zero access to your network.

Try it in your boardroom →

The segmented enterprise

Corp, guest, AV, and OT networks that must never route to each other, by policy. Polaris keeps the isolation intact and still lands every source on the same display.

The enterprise story →

The multi-building campus

Engineering in Building C shares to the war room in Building A, across VLANs and fiber, without spinning up a UC call just to move pixels.

Campus scale →
How cross-network signaling works

Where your content actually goes

Polaris Cloud introduces the two ends of a share. It does not carry them.

When a source and a display sit on different networks, the signaling service at webrtc.mersive.com exchanges connection details between the sharing device and the display, and the two negotiate a direct, encrypted WebRTC connection between themselves. Your content travels from the device to the display. It does not pass through Mersive.

  • What reaches our cloud: session signaling, the connection details the two endpoints need to find each other. Not your screen.
  • What stays on your network: when a source and a display are already on the same network, the connection is negotiated with local addresses only and never leaves the LAN.
  • What never happens: no inbound firewall rules, no bridging of your networks. All cloud traffic is outbound TLS on TCP 443 from both sides. A guest device gets zero access to your network; the workspace is the only shared surface.
The short version

The combination of cross-network capability without a VPN, the workspace, and meeting parity with a composited workspace available in a web browser sets Polaris apart.

✓ No VPN✓ No UC call✓ No inbound holes✓ Guest gets zero network access✓ Every Polaris tier

Check the matrix →   The security read →

See the platform live.

Hardware trials ship for every product, direct from Mersive. When the rooms prove it, we introduce your regional partner for the rollout.

Start a trial Watch on YouTube ↗