Exchange / Two internet lines
Selling from a network with two internet lines
Some homes and offices have two lines, for example cable plus Starlink, with a router that can use both. You choose which one to share. The seller app doesn't choose for you: you send the device that runs it out the line you want.
Status: these steps come from each vendor's documented features and our own lab plan. We haven't tested every router or version, so run the checks at the end before you start sharing. Menu names change between versions.
The idea
- Run the seller app on one small device (a spare mini PC, a Raspberry Pi-class box, or a virtual machine). Give it a fixed address on your network, for example
192.0.2.10. - Send that device, and only that device, out the line you want to share. Your router calls this policy routing, a traffic route or a gateway rule. Everything else in your home keeps using its normal line.
- Make sure it can't fall back to the other line. If the shared line goes down, the device should have no internet at all, not quietly switch to the line you didn't choose.
- Keep it away from the rest of your network. Put it on its own network (VLAN) if your router can, and block it from reaching your other devices and your router's login page. The app already refuses private addresses, and this adds a second wall.
Only share a real home or office line that you pay for. The Seller Agreement doesn't allow sharing through a datacenter, a VPN, or a rented server.
Example: UniFi
- Settings, Internet: note the name of each line. Pick the one you want to share.
- Create a network for the device (Settings, Networks, New): a normal network, its own VLAN ID, its own subnet, and no access to other networks if the form has that option.
- Create a firewall rule that blocks that network from your other networks and from the router itself, and allows it to reach the internet.
- Create a traffic route (Settings, Routing, or Policy-Based Routes): source is the device's single address
192.0.2.10, not the whole network; interface is the line you chose; destination is any. Turn the kill switch on (the option that drops the traffic if that line is down). If your version has no kill switch option, stop here and don't share.
Example: pfSense
- Give the device a static DHCP mapping (Services, DHCP Server) so it keeps
192.0.2.10. - On the interface the device sits on, add a rule at the top: source
192.0.2.10, destination any, and under Advanced Options set Gateway to the line you chose. - Directly below it add a block rule for the same source and any destination. In pfSense, if the chosen gateway is down the first rule can be skipped, and without the block rule the traffic would go out your other line.
- Above both, add block rules from the device to your other internal networks and to the firewall's own address.
Example: OPNsense
- Give the device a static DHCP lease (Services, DHCPv4) so it keeps
192.0.2.10. - On its interface, add a pass rule at the top: source
192.0.2.10, destination any, and set Gateway to the line you chose. - Directly below it add a block rule for the same source, so a down line means no internet and not a fallback to the other line.
- Above both, add block rules from the device to your other internal networks and to the firewall's own address.
Check it before you share
- From the device, run
curl -s https://ifconfig.me. It should show the public address of the line you chose, not the other one. - Unplug the line you chose. The device should lose its internet completely. Plug it back in and it should return by itself. If it ever shows the other line's address, fix the rule before you start sharing.
- From the device, try to open your router's login page and another computer on your network. Both should fail.
Then sign up as a seller. We'll invite you to install the app when it's ready.