How-to guide
Choose exactly which MeshCore traffic is allowed to cross the MeshCore IP Bridge's internet link — without changing anything on your local mesh.
Overview
Without a filter, the IP Bridge forwards every packet it hears on one mesh to the other. The packet filter adds a checkpoint on each board that decides, packet by packet, whether it may cross the internet link.
The bridge is also a normal MeshCore repeater. A packet blocked from crossing the link is still repeated on the local mesh as usual. Filtering never makes the local mesh quieter or less reliable.
The filter only decides what goes out over the tunnel and what comes in from it. A blocked outbound packet is never sent; a blocked inbound packet is never transmitted into the local mesh.
Use cases
Reference
Every rule is a block rule: anything that matches a rule is stopped, and everything else crosses. Keywords aren't case‑sensitive.
| Rule | Blocks |
|---|---|
| advert | Flood adverts — the node announcements that spread across the whole mesh. |
| advert0 | Zero‑hop adverts — announcements meant only for nodes in direct radio range. |
| txt | Direct (private, one‑to‑one) text messages. |
| grp_txt | All channel text messages, on every channel. To block just one channel, use a channel rule below. |
| grp_data | All channel data packets. |
| ack | Delivery acknowledgements. |
| req response | Requests to a node (e.g. login, status, telemetry) and their responses. |
| anon_req | Anonymous requests, such as logging in to a room server or repeater. |
| path | Returned‑path packets, which let two nodes learn a direct route to each other. |
| trace | Trace packets used to test a route. |
| multipart control raw | Multipart, control and raw/custom packets. |
| Rule | Blocks |
|---|---|
| public | The default MeshCore Public channel. |
| #name | A hashtag channel, e.g. #foxton. Type the name exactly as the channel uses it, including the # — capitals matter. No spaces or , | " \. |
| psk:<base64> | A private channel, identified by its secret key in base64 (the key you'd share in a channel link or QR code). 16‑ or 32‑byte keys are accepted. |
Under the hood
MeshCore channel messages are encrypted, so the bridge can't read them — and doesn't need to. Each channel message carries a 1‑byte channel hash, worked out from the channel's key, followed by a short message authentication code (MAC) made with that key.
#name, or the key you pasted in.ch d9, and each channel rule chip on the dashboard shows the hash it matches. If a #name rule never gets any hits, compare the two — a different hash usually means the name's capitalisation differs from the channel's.Reference
Each board has its own rules and its own direction setting. Rules aren't copied across the link.
| Direction | On this board, rules apply to… |
|---|---|
| both ways | Packets heard on the local mesh going out to the tunnel, and packets arriving from the tunnel going into the local mesh. This is the default. |
| mesh → IP only | Only what this board sends out. Traffic arriving from the other end is never filtered here. |
| IP → mesh only | Only what this board lets into its local mesh. Everything it hears locally is still sent out. |
If you control both boards, block traffic where it leaves (mesh → IP). It then never uses internet bandwidth, and the other end doesn't have to discard it.
If you only control your end, use IP → mesh rules to decide what the other side is allowed to put on your mesh's airtime.
How to
http://192.168.1.50, and find the Packet filter panel. With no rules it reads “No rules — everything crosses (default)”.Changes take effect immediately and are saved on the board straight away, so they survive a reboot or power cut. There's no need to click Save & reboot.
⏸ Bypass filter temporarily lets everything through while keeping your rules. The panel shows BYPASSED while it's on. Click ▶ Re‑enable filter to switch back. Bypass isn't saved, so a reboot always turns the filter back on.
How to
The dashboard's live packet log and counters show exactly what the filter is doing.
| You see | Meaning |
|---|---|
→ air, ✕ ip | Heard on the local mesh and repeated there, but blocked from going out over the link. The reason shows the rule, e.g. filter: advert. |
✕ ip blocked | Arrived from the other end but blocked from entering this mesh. |
| Filtered → IP | Counter of packets blocked on the way out. |
| Filtered ← IP | Counter of packets blocked on the way in. |
| “N blocked” on a chip | How many packets that rule has stopped. |
| hash look‑alikes passed | Channel messages that shared a rule's hash byte but belonged to a different channel, so were allowed through. |
Examples
On both boards: + Adverts, direction mesh → IP only.
On both boards: + Public channel, direction both ways. Hashtag channels, private channels and direct messages still cross.
On your board: add #foxton (your channel name, exactly as typed in the app), direction both ways.
Block txt, req, response, anon_req and trace. Channel messages keep flowing; direct messages and remote admin stay on each side.
Advanced
The same rules can be managed from the USB serial console, or remotely from a MeshCore app's repeater admin command line.
ipfilter # show rules, direction and hit counts ipfilter add advert # add a rule ipfilter add #foxton ipfilter del public # remove a rule ipfilter dir out # both | out (mesh → IP) | in (IP → mesh) ipfilter bypass 1 # 1 = bypass, 0 = filter on ipfilter clear # remove all rules
For scripting from the local network:
GET /api/filter
POST /api/filter {"op":"add","value":"#foxton"}
# op: add | del | clear | dir | bypass
Support
The name must match the channel exactly, including capitals — #Foxton and #foxton are different channels. Compare the ch xx hash on the rule chip with the hash shown on that channel's messages in the feed. If they differ, remove the rule and re‑add it with the right spelling.
Click Bypass filter. If the traffic flows again, it's a rule: check which chip's blocked count goes up, and remember that grp_txt blocks every channel. Also check the other board — it has its own rules.
An ack rule is probably blocking the delivery receipts on one of the boards. Remove it.
Rules are stored with the board's other settings, so choosing Erase device when flashing clears them. Updating over WiFi, or flashing without erasing, keeps them. Note down your rules (the ipfilter command prints them all) before a full erase.
The board is still on v1.0.0. Update it to v1.1.1 — see step 1. The FIRMWARE [4/4] screen on the board shows the installed build.
The packet filter idea comes from Mr Stone's meshcore-esp-now-filtered-bridge (MIT licence). It has been re‑implemented for the IP Bridge, with the added channel MAC check described above.