MinimServer Forum

Full Version: Minimwatch subnet not found with VPN
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hello,

sometimes I connect with my Mac via VPN to my NAS at home.

However I can't get Minimwatch to work on my Mac.
Even though I set the ohnet.subnet property to 192.168.1.0, Minimwatch reports that the subnet could not be found.
My local IP for the VPN adapter is 192.168.1.202 and I can also connect with the web browser to the Minimserver address http://192.168.1.100:9790.

I already disabled my Macs firewall but still no success.
Is there a way to further analyze this problem ?
(18-03-2015 14:27)Fotospecht Wrote: [ -> ]Hello,

sometimes I connect with my Mac via VPN to my NAS at home.

However I can't get Minimwatch to work on my Mac.
Even though I set the ohnet.subnet property to 192.168.1.0, Minimwatch reports that the subnet could not be found.
My local IP for the VPN adapter is 192.168.1.202 and I can also connect with the web browser to the Minimserver address http://192.168.1.100:9790.

I already disabled my Macs firewall but still no success.
Is there a way to further analyze this problem ?

Please open a Terminal window on the Mac, enter this command:

ifconfig

and post the full output here.
Here is the output of ifconfig:

Code:
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
    options=3<RXCSUM,TXCSUM>
    inet6 ::1 prefixlen 128
    inet 127.0.0.1 netmask 0xff000000
    inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
    nd6 options=1<PERFORMNUD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV>
    ether 3c:07:54:4c:c6:38
    inet6 fe80::3e07:54ff:fe4c:c638%en0 prefixlen 64 scopeid 0x4
    inet 10.97.199.81 netmask 0xfffffe00 broadcast 10.97.199.255
    nd6 options=1<PERFORMNUD>
    media: autoselect (100baseTX <full-duplex>)
    status: active
en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
    ether 60:c5:47:22:50:ab
    inet6 fe80::62c5:47ff:fe22:50ab%en1 prefixlen 64 scopeid 0x5
    inet 169.254.231.134 netmask 0xffff0000 broadcast 169.254.255.255
    nd6 options=1<PERFORMNUD>
    media: autoselect
    status: active
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
    lladdr a4:b1:97:ff:fe:af:04:06
    nd6 options=1<PERFORMNUD>
    media: autoselect <full-duplex>
    status: inactive
en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
    options=60<TSO4,TSO6>
    ether b2:00:1a:f0:40:61
    media: autoselect <full-duplex>
    status: inactive
p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
    ether 02:c5:47:22:50:ab
    media: autoselect
    status: inactive
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    options=63<RXCSUM,TXCSUM,TSO4,TSO6>
    ether 3e:07:54:c4:54:00
    Configuration:
        id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
        maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
        root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
        ipfilter disabled flags 0x2
    member: en2 flags=3<LEARNING,DISCOVER>
            ifmaxaddr 0 port 7 priority 0 path cost 0
    nd6 options=1<PERFORMNUD>
    media: <unknown type>
    status: inactive
bridge100: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    options=3<RXCSUM,TXCSUM>
    ether 3e:07:54:c4:54:64
    inet 192.168.2.1 netmask 0xffffff00 broadcast 192.168.2.255
    inet6 fe80::3c07:54ff:fec4:5464%bridge100 prefixlen 64 scopeid 0xa
    Configuration:
        id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
        maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
        root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
        ipfilter disabled flags 0x2
    member: en1 flags=3<LEARNING,DISCOVER>
            ifmaxaddr 0 port 5 priority 0 path cost 0
    nd6 options=1<PERFORMNUD>
    media: autoselect
    status: active
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
    inet 192.168.1.202 --> 192.168.1.202 netmask 0xffffffff
(18-03-2015 14:56)Fotospecht Wrote: [ -> ]Here is the output of ifconfig:

Thanks for the quick reply.

This tunnel:

utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
inet 192.168.1.202 --> 192.168.1.202 netmask 0xffffffff

seems to be pointing to itself. How did you set up the VPN at both ends?

What is the 192.168.2.1 address?
The 192.168.2.1 is used by the Internet sharing service, where my Mac is configured as a local Wifi access point.

The VPN is a Cisco IPSec VPN. I've verified that the host is routing correctly over the VPN interface (which Mac OS/X calls "utun0"):

Code:
~$ scutil --nc list | grep Connected
* (Connected)      D7EB7C34-F481-436A-B259-7DB89602628B IPSec              "VPN (Cisco IPSec)"              [IPSec]


~$ route -v get 192.168.1.100
u: inet 192.168.1.100; u: link ; RTM_GET: Report Metrics: len 128, pid: 0, seq 1, errno 0, flags:<UP,GATEWAY,HOST,STATIC>
locks:  inits:
sockaddrs: <DST,IFP>
nas.fritz.box
   route to: nas.fritz.box
destination: default
       mask: default
  interface: utun0
      flags: <UP,DONE,CLONING,STATIC>
recvpipe  sendpipe  ssthresh  rtt,msec    rttvar  hopcount      mtu     expire
       0         0         0         0         0         0      1280         0

locks:  inits:
sockaddrs: <DST,GATEWAY,NETMASK,IFP,IFA>
default  default utun0 192.168.1.202
Please try using 192.168.1.202 for the ohnet.subnet property. Is this accepted as valid?
It is accepted but the icon is still grey.
(18-03-2015 16:09)Fotospecht Wrote: [ -> ]It is accepted but the icon is still grey.

OK, this is progress.

The SSDP M-SEARCH request is probably arriving at the remote VPN server and being forwarded to MinimServer. If so, MinimServer will attempt to send a response to the sender's 192.168.1.202 address using a UDP packet. Are the routers at both the server end and client end set up to be able to handle this UDP packet and route it to your Mac? The UDP destination port number is allocated dynamically by MinimWatch when the M-SEARCH request is sent.
Reference URL's