If an user set a fixed dns server in his configuration, the user can't find the piratebox.
You could opt for the option to redirect all dns traffic to the pbx
Simply add the following rule to /etc/config/firewall
Sometimes a browser caches an ip address, you could redirect all http traffic to the pbx. (sadly not possible for https).
This rule will interfere if you have setup a mesh network.
Simply add the following rule to /etc/config/firewall
You can login to the piratebox via ssh and use vi to edit the file /etc/config/firewall
In bot examples you must relplace the ip 192.168.1.1 with the ip your pbx has.
you can display it with the command: uci get network.lan.ipaddr
You could opt for the option to redirect all dns traffic to the pbx
Simply add the following rule to /etc/config/firewall
config redirect option dest_ip '192.168.1.1' option src_dport '53' option name 'dns_pbx' option target 'DNAT' option proto 'tcp udp' option src 'lan'
Sometimes a browser caches an ip address, you could redirect all http traffic to the pbx. (sadly not possible for https).
This rule will interfere if you have setup a mesh network.
Simply add the following rule to /etc/config/firewall
config redirect option dest_ip '192.168.1.1' option src_dport '80' option name 'http_pbx' option target 'DNAT' option proto 'tcp' option src 'lan'
You can login to the piratebox via ssh and use vi to edit the file /etc/config/firewall
In bot examples you must relplace the ip 192.168.1.1 with the ip your pbx has.
you can display it with the command: uci get network.lan.ipaddr