Yes, all clients can ping each other.
If you have different subnet on the client side, you must use router for the VPN client and configure the routing on each router so they can connect each of the subnets.
By Default Serial Port on Routerboard configured for console, if you want to make the serial port to become normal serial port for dialing modem you can turn off the console service: " /system console disable serial0 " and then you can configure the ppp dial-out (Client) or dial-in (SERVER).
- make pptp connection on both mt
- make bridge interface on both mt
- make eoip interface on both mt and use pptp ip for eoip remote-address
- put eoip and local-ethernet on the same bridge on each mt
Hi, yes you can use pcq to equalizing your clients bandwith also you can excluding the p2p traffic using mangle and make queue (queue-tree) for your traffic to ensure your clients not taking others bandwith.
Hi, its more simpler if you build one bridge interface and put ether1 and wireless (AP mode) on bridge. If you want to make the routerboard as DHCP-relay you can use DHCP-relay feature.
I just wondering if you already have routerboard as router why you still use windows
I have similar problems and i use NAT to reach the local network NAT-VPN-to-local chain=srcnat out-interface=eth-local src-address=10.xx.xx.82-10.xx.xx.85 action=src-nat to-addresses=10.xx.xx.80 to-ports=0-65535 NAT-VPN-to-Public chain=srcnat out-interface=eth-gateway src-address=10.xx.xx.82-10.xx.x...
Hi, i have similar config for port redirect to my local server and it works perfectly chain=dstnat dst-address=[public ip] protocol=tcp dst-port=80 action=dst-nat to-addresses=172.21.2.2 to-ports=80 chain=dstnat dst-address=[public ip] protocol=tcp dst-port=22 action=dst-nat to-addresses=172.21.2.2 ...