Recent content by canufrank

One more request @Martineau :) Hoping to tag wlan and guest wlan separately

I've read a few reviews/articles on SNB (like these ones http://www.smallnetbuilder.com/wireless/wireless-features/32238-ac1900-innovation-or-3d-wi-fi & http://www.smallnetbuilder.com/wireless/wireless-features/32320-is-ac1900-worth-it?start=1 &...

Same issue. I couldn't figure out why I couldn't test my setup until finding this.

no-ipset

@octopus, the rows in /tmp/11-curl should be of no interest to you, simply the value assigned to $curl11. Those rows are there to ensure that the curl successfully resolves on any of the URL's possible IP addresses- they relate to your curl target, not the response. (@john9527 's parsing is even...

@john9527 If you're asking me, getting the VPN ID is just one use case for using curl. My primary objective concerns a requirement of my VPN provider's port forwarding service. They need an hourly request to confirm the port they are forwarding. It must come via the tunnel.

@Martineau I was trying to make the above work, but my lack of understanding around dnsmasq is definitely hindering me. I wanted to make ip sets where I can add and delete the rule as needed. e.g. iptables -t mangle -A PREROUTING -i br0 -m set --set Switcheroo dst -j MARK --set-mark 128 ipset...

@octopus The nslookup is already part of curl11 above. It outputs pertinent addresses to /tmp/11-curl local fn=/tmp/11-curl rm -f $fn nslookup "$srv" 2>/dev/null |grep -E "^Address " |while read line; do if [ "${line:11:3}" != 127 ]; then...

The curl11 function I posted above will allow you to query any URL via the tunnel even if normal routing is through the ISP. (I have more robust code to handle nslookup failing if you run into that.) Just ensure that tun_if and tun_p2p are defined or rewrite with your own var names. You can...

ps, Whether or not vpnrouting.sh passes arguments, if openvpn-event and any subsequent scripts are called by the openvpn service (which is always the use case), $script_type is available in the environment and doesn't need to be passed. I'm no longer examining args passed except as a failover

Following all presumes Policy Blocking mode: Objective 1: I would like to find out the VPN's public IP. However, the first 2 both return the WAN's public IP and the 3rd times out curl ipecho.net/plain curl --interface $ifconfig_local ipecho.net/plain curl --interface tun11 ipecho.net/plain...

To summarize my last 2 posts, one cannot query across the tunnel interface unless Redirect != Policy Rules and 'route-nopull' is absent. Else, this will time out: curl -v --interface tun11 checkip.dyndns.com curl: (7) couldn't connect to host The problem is that the router is using table 254...

Confer http://www.snbforums.com/threads/ac87u-client-list-problem-when-using-ap.29675/ Confer http://www.snbforums.com/threads/a-...-that-are-connected-to-the-asus-router.29602/ The problem seems related to networkmap issues.

See http://www.snbforums.com/threads/a-way-to-see-network-clients-that-are-connected-to-aps-that-are-connected-to-the-asus-router.29602/ No solution there yet.

I have the same setup and issue. Can you confirm that the clients are also missing from System Log -> Wireless Log?; and that you CAN see the clients if you select LAN -> DHCP Server -> MAC Address dropdown? If yes to the second, there are obviously different methodologies at work here, not a...