My Brume 2 is at 10.0.0.1. My main computer/server is a Mac, located at 10.0.0.2. On my LAN, I can connect to this Mac at 10.0.0.2 AND at “mac.local”.
I have a working WireGuard VPN at 10.0.8.1. When connected, I can reach the Brume 2 at 10.0.0.1, and my Mac at 10.0.0.2. But, I cannot connect to “mac.local”.
How can I tell the Brume 2 / WireGuard how to get to “mac.local”?
^It’s not the way I’d do it but I don’t see why it wouldn’t work. I’d set some static DHCP leases beforehand, just to be sure: GL GUI → Clients → Online Clients → $clientName → Action → Modify
Another or option is to use LuCI → Network → DHCP and DNS → Static Leases which will give you the equivalent of → Hostnames (result: iphone.lan). You can install LuCI via GL GUI → System → Advanced Settings. Be warned there’s been a lot of changes since 2005/2006.
In the Files app on my iPhone, I connect to this computer by smb://mac.local
This works on my LAN, of course. I wish for this same connection to work over my WireGuard VPN. (I know that I could use smb://10.0.0.2 just fine on/off my LAN, but this is the scenario I’d like to resolve).
OpenWrt DHCP defaults to .lan instead. .local creates conflicts w/ other DNS-based software used by Windows/Linux because Apple decided some years ago to ‘hijack’ that particular pseudo-TLD.
LuCI → Network → DHCP and DNS → General Settings → Local server & Local domain
John, before you continue configuring various options for your Burme 2 (eg: editing your hosts file as @SpitzAX3000 suggested), I’d highly suggest you back up your current state.
Hypothetically, yes… but keep in mind that caveat I mentioned re: pseudo-TLD. You could have some troubles in the future if you start mixing other client operating system on your LAN.
I would really preform a backup first. It’s all in that HOW-TO. Keep that resulting tarball in a safe place.
Instead of changing these settings just edit your Mac server name from mac.local to mac. Then disconnect it from the router and reconnect again to have it as mac.lan