Closed GoogleCodeExporter closed 9 years ago
What IP is shown and what it should be instead?
Original comment by lehph...@gmail.com
on 9 Oct 2010 at 2:13
It's showing 192.168.81.1 which is my VMWare IP. VMWare assigns an IP to it's
interface even when it's not running.
Would be ideal if you could pick which interface it would use in preferences
(though I'm not sure how hard that is to do).
Here's my ifconfig:
eth0 Link encap:Ethernet HWaddr 00:26:22:2a:cc:8c
inet addr:99.65.181.60 Bcast:99.65.183.255 Mask:255.255.252.0
inet6 addr: fe80::226:22ff:fe2a:cc8c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:455454 errors:0 dropped:0 overruns:0 frame:0
TX packets:378363 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:122120366 (122.1 MB) TX bytes:88215765 (88.2 MB)
Interrupt:18
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1326 errors:0 dropped:0 overruns:0 frame:0
TX packets:1326 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:97851 (97.8 KB) TX bytes:97851 (97.8 KB)
vmnet1 Link encap:Ethernet HWaddr 00:50:56:c0:00:01
inet addr:192.168.180.1 Bcast:192.168.180.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:309 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
vmnet8 Link encap:Ethernet HWaddr 00:50:56:c0:00:08
inet addr:192.168.81.1 Bcast:192.168.81.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:310 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Original comment by atomics...@gmail.com
on 9 Oct 2010 at 4:31
I'm trying to keep it simple for users, so I look for some network interface
that is not loopback neither is virtual, please copy this jar file to
/usr/share/android-notifier-desktop and let me know if it works for you:
http://dl.dropbox.com/u/1401233/android-notifier-desktop.jar
Original comment by lehph...@gmail.com
on 9 Oct 2010 at 5:19
That folder is protected, says I don't have permissions. How do I copy/replace
it? I'm logged in as an admin user.
Original comment by atomics...@gmail.com
on 11 Oct 2010 at 11:19
Also, are the issues from 222 included in this one?
Original comment by atomics...@gmail.com
on 11 Oct 2010 at 11:31
Try this command: sudo cp android-notifier-desktop.jar
/usr/share/android-notifier-desktop
This is the same jar file posted on issue 222.
Original comment by lehph...@gmail.com
on 12 Oct 2010 at 3:23
Works perfectly and solves issue 222 and 223.
Thank you!
Original comment by atomics...@gmail.com
on 12 Oct 2010 at 3:35
Great. Thank you for testing both issues :)
Original comment by lehph...@gmail.com
on 12 Oct 2010 at 3:56
Also, I've upgraded to Ubuntu 10.10 and still working. FYI.
Original comment by atomics...@gmail.com
on 12 Oct 2010 at 3:57
FYI this bug is not specific to Linux; I just had the same problem on OSX with
0.5.1 (I also have VMWare interfaces). However, even without installing the
update jar in #3 I was still able to send test notifications (so presumably
A.N.D. listens on all interfaces and just picks one address to display in the
preferences window?).
Thanks for your work on Android Notifier -- I just installed it today but it
looks to be of high quality and very promising for the future. I look forward
to SMS send support especially.
Original comment by zakwil...@gmail.com
on 4 Jan 2011 at 7:09
[deleted comment]
I'm getting this vmware issue too in Linux. I still get notifications too.
Sent me down the wrong troubleshooting path. Turns out I forgot to open 10600
in my firewall. Thought it had to do with the incorrect IP.
Original comment by n.underw...@googlemail.com
on 9 Mar 2011 at 7:34
[deleted comment]
Looks like it's only a glitch with the displayed interface, I'm also being
shown vmnet8 but the program is actually listening on the correct eth0
interface (or maybe on all interfaces).
Original comment by qualc...@gmail.com
on 30 Oct 2012 at 3:29
Original issue reported on code.google.com by
atomics...@gmail.com
on 9 Oct 2010 at 12:27