OS X Mavericks

[simoncn]

(28-10-2013 20:09)bbrip Wrote:  nothing has really changed in my setup. Strange....

I thought you said you had recently installed Mavericks. That seems like a change.

[bbrip]

well indeed, but it worked for a day or two and now decided to stop Checked, theres no firewall active on my Mac

[simoncn]

(28-10-2013 22:36)bbrip Wrote:  well indeed, but it worked for a day or two and now decided to stop Checked, theres no firewall active on my Mac

What about other active network adapters (virtual or real)?

[bbrip]

not even sure my Macbook Air has any network adapter other than Wifi... Any Terminal command to locate them? And the NAS is the same that it always was, a ReadyNAS NVX (Btw. MinimWatch runs ok on my old Windows Vista machine....)

[simoncn]

(28-10-2013 23:07)bbrip Wrote:  not even sure my Macbook Air has any network adapter other than Wifi... Any Terminal command to locate them? And the NAS is the same that it always was, a ReadyNAS NVX (Btw. MinimWatch runs ok on my old Windows Vista machine....)

You can type ifconfig in a Terminal window to see all the adapters. If you post the output here, I'll look to see if there's anything that might cause this problem.

[bbrip]

(28-10-2013 23:34)simoncn Wrote:  

(28-10-2013 23:07)bbrip Wrote:  not even sure my Macbook Air has any network adapter other than Wifi... Any Terminal command to locate them? And the NAS is the same that it always was, a ReadyNAS NVX (Btw. MinimWatch runs ok on my old Windows Vista machine....)

You can type ifconfig in a Terminal window to see all the adapters. If you post the output here, I'll look to see if there's anything that might cause this problem.

thanks again for your help. this is what it says

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
    inet 127.0.0.53 netmask 0xffffff00
    inet 127.0.0.54 netmask 0xffffff00
    inet 127.0.0.55 netmask 0xffffff00
    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
    ether 5c:f9:38:99:45:ba
    inet6 fe80::5ef9:38ff:fe99:45ba%en0 prefixlen 64 scopeid 0x4
    inet 192.168.2.141 netmask 0xffffff00 broadcast 192.168.2.255
    nd6 options=1<PERFORMNUD>
    media: autoselect
    status: active
en2: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    options=60<TSO4,TSO6>
    ether 32:00:11:45:40:00
    nd6 options=1<PERFORMNUD>
    media: autoselect <full-duplex>
    status: inactive
p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
    ether 0e:f9:38:99:45:ba
    media: autoselect
    status: inactive
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
    inet6 fe80::c56a:54da:9c0f:72d0%utun0 prefixlen 64 scopeid 0x7
    inet6 fddc:a0bc:786a:6e5:c56a:54da:9c0f:72d0 prefixlen 64
    nd6 options=1<PERFORMNUD>

[simoncn]

(29-10-2013 10:51)bbrip Wrote:  thanks again for your help. this is what it says

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
    inet 127.0.0.53 netmask 0xffffff00
    inet 127.0.0.54 netmask 0xffffff00
    inet 127.0.0.55 netmask 0xffffff00
    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
    ether 5c:f9:38:99:45:ba
    inet6 fe80::5ef9:38ff:fe99:45ba%en0 prefixlen 64 scopeid 0x4
    inet 192.168.2.141 netmask 0xffffff00 broadcast 192.168.2.255
    nd6 options=1<PERFORMNUD>
    media: autoselect
    status: active
en2: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    options=60<TSO4,TSO6>
    ether 32:00:11:45:40:00
    nd6 options=1<PERFORMNUD>
    media: autoselect <full-duplex>
    status: inactive
p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
    ether 0e:f9:38:99:45:ba
    media: autoselect
    status: inactive
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
    inet6 fe80::c56a:54da:9c0f:72d0%utun0 prefixlen 64 scopeid 0x7
    inet6 fddc:a0bc:786a:6e5:c56a:54da:9c0f:72d0 prefixlen 64
    nd6 options=1<PERFORMNUD>

I think the problem is caused by these entries under lo0:

inet 127.0.0.53 netmask 0xffffff00
inet 127.0.0.54 netmask 0xffffff00
inet 127.0.0.55 netmask 0xffffff00

I think these entries will cause ohNet to listen on the loopback adapter (lo0) instead of the correct adapter (en0). This is because ohNet detects and ignores the loopback adapter by looking for the loopback address 127.0.0.1, and the extra addresses are causing ohNet to treat this as a real adapter instead of the loopback adapter.

To solve the problem, you can remove the extra addresses (if you know what has caused them to appear there), or you can add the line

ohnet.subnet = 192.168.2.0

to the minimwatch.config file in the folder

/Users/<your-user-name>/Library/MinimWatch

This folder is hidden in Finder, so you need to use Go > Go to Folder... and type the path there. This setting will cause ohNet to use the en0 adapter instead of the loopback adapter.

In the next release of MinimWatch, it will be possible to set this value using the MinimWatch GUI instead of manually editing the minimwatch.config file.

[bbrip]

(29-10-2013 11:11)simoncn Wrote:  ....., or you can add the line

ohnet.subnet = 192.168.2.0

to the minimwatch.config file in the folder

/Users/<your-user-name>/Library/MinimWatch

This folder is hidden in Finder, so you need to use Go > Go to Folder... and type the path there. This setting will cause ohNet to use the en0 adapter instead of the loopback adapter.

In the next release of MinimWatch, it will be possible to set this value using the MinimWatch GUI instead of manually editing the minimwatch.config file.

Hi Simon, thanks for your help. I located the config file edited and saved it. Stopped and restarted MinimWatch. But it does not correct the problem....

[simoncn]

(29-10-2013 13:42)bbrip Wrote:  Hi Simon, thanks for your help. I located the config file edited and saved it. Stopped and restarted MinimWatch. But it does not correct the problem....

This is turning out to be quite a puzzle. For the next diagnostic step, please add the lines:

.logLevel = trace
ohnet.debug = All-Timer

to the minimwatch.config file, then restart MinimWatch. This will produce detailed trace information in a minimwatch.log file in the same folder as the minimwatch.config file. Close MinimWatch, then zip the log file and post it here. Thanks!

[bbrip]

(29-10-2013 14:23)simoncn Wrote:  

(29-10-2013 13:42)bbrip Wrote:  Hi Simon, thanks for your help. I located the config file edited and saved it. Stopped and restarted MinimWatch. But it does not correct the problem....

This is turning out to be quite a puzzle. For the next diagnostic step, please add the lines:

.logLevel = trace
ohnet.debug = All-Timer

to the minimwatch.config file, then restart MinimWatch. This will produce detailed trace information in a minimwatch.log file in the same folder as the minimwatch.config file. Close MinimWatch, then zip the log file and post it here. Thanks!

Attached the log-file