WhatPulse Forums » Support » Client software v » No interfaces listed in Ubuntu 12.10 Welcome back, Guest.


Post Reply 
 
Thread Rating:
  • 1 Votes - 1 Average
  • 1
  • 2
  • 3
  • 4
  • 5
No interfaces listed in Ubuntu 12.10
01-08-2013, 12:27 AM
Post: #11
RE: No interfaces listed in Ubuntu 12.10
Wp is working on my version of Ubuntu 12.10, here's what I have for their comparison:

eth0 - only the device file exists, no vendor, this is my wired adapter (not in use at the moment).
eth1 - both files exist, this is my wireless adapter for some reason, I don't have a wlan0.
Find all posts by this user
Quote this message in a reply
01-08-2013, 11:48 AM
Post: #12
RE: No interfaces listed in Ubuntu 12.10
Please also post whether that interface is recognized, and if you don't have a problem, there's no need to check them at all. ;-)
Visit this user's website Find all posts by this user
Quote this message in a reply
01-08-2013, 07:21 PM
Post: #13
RE: No interfaces listed in Ubuntu 12.10
I doubt it is a problem with sysfs stuff. I don't have either of those files on my colo'd gentoo server for its two main interfaces (bond0, and eth1.100); however it still works fine they just get listed as 'uknown device:


[Image: whatpulse_unknown.png]

You guys actually just try running the thing as root to see if it works that way (not saying run it permanently like that).
Find all posts by this user
Quote this message in a reply
01-08-2013, 07:29 PM
Post: #14
RE: No interfaces listed in Ubuntu 12.10
(01-08-2013 07:21 PM)houkouonchi Wrote:  I doubt it is a problem with sysfs stuff.

You don't have to doubt; it will skip a interface if those files doesn't exist, under certain conditions. That skipping has been removed for the next version, so I want to confirm if that was the case for these users.
Visit this user's website Find all posts by this user
Quote this message in a reply
01-08-2013, 07:32 PM (This post was last modified: 01-08-2013 07:37 PM by houkouonchi.)
Post: #15
RE: No interfaces listed in Ubuntu 12.10
(01-08-2013 07:29 PM)smitmartijn Wrote:  
(01-08-2013 07:21 PM)houkouonchi Wrote:  I doubt it is a problem with sysfs stuff.

You don't have to doubt; it will skip a interface if those files doesn't exist, under certain conditions. That skipping has been removed for the next version, so I want to confirm if that was the case for these users.

So then how is it working for me?

root@方向音痴: 11:31 AM :/sys/class/net/bond0# find -name "*vend*"
root@方向音痴: 11:31 AM :/sys/class/net/bond0# find -name "*dev*"
./dev_id
root@方向音痴: 11:31 AM :/sys/class/net/bond0# cd ../eth1.100
root@方向音痴: 11:31 AM :/sys/class/net/eth1.100# find -name "*dev*"
./dev_id
root@方向音痴: 11:32 AM :/sys/class/net/eth1.100# find -name "*vend*"
root@方向音痴: 11:32 AM :/sys/class/net/eth1.100#

As you can see I do not have those files and as you can see in the screenshot it list them as 'unknown' yet reporting is working fine for me on 2.0.1.

Had to add this to a second post as I was over the character limit...

Although it does seem to skip all the tun interfaces and stuff on my server and the interfaces that don't have an IP address on them as well:

Code:
root@方向音痴: 11:33 AM :/sys/class/net/eth1.100# ip addr
1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth5: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:25:90:00:13:c0 brd ff:ff:ff:ff:ff:ff
3: eth4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:25:90:00:13:c1 brd ff:ff:ff:ff:ff:ff
4: eth3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:25:90:00:13:c2 brd ff:ff:ff:ff:ff:ff
5: eth2: <BROADCAST,MULTICAST,SLAVE,UP,10000> mtu 1500 qdisc pfifo_fast master bond0 qlen 1000
    link/ether 00:25:90:00:13:c3 brd ff:ff:ff:ff:ff:ff
6: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc mq qlen 1000
    link/ether 00:30:48:de:ee:4a brd ff:ff:ff:ff:ff:ff
    inet 10.176.18.21/20 brd 10.176.31.255 scope global eth0
    inet6 fe80::230:48ff:fede:ee4a/64 scope link
       valid_lft forever preferred_lft forever
7: eth1: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc mq qlen 1000
    link/ether 00:30:48:de:ee:4b brd ff:ff:ff:ff:ff:ff
    inet6 fe80::230:48ff:fede:ee4b/64 scope link
       valid_lft forever preferred_lft forever
8: teql0: <NOARP> mtu 1500 qdisc noop qlen 100
    link/void
9: sit0: <NOARP> mtu 1480 qdisc noop
    link/sit 0.0.0.0 brd 0.0.0.0
10: ip6tnl0: <NOARP> mtu 1460 qdisc noop
    link/tunnel6 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
11: bond0: <BROADCAST,MULTICAST,MASTER,UP,10000> mtu 1500 qdisc noqueue
    link/ether 00:25:90:00:13:c3 brd ff:ff:ff:ff:ff:ff
    inet 208.97.140.21/24 brd 208.97.140.255 scope global bond0
    inet 208.97.138.21/24 brd 208.97.138.255 scope global bond0:0
    inet 208.97.143.21/24 brd 208.97.143.255 scope global bond0:1
    inet 208.97.141.254/24 brd 208.97.141.255 scope global bond0:2
    inet 208.97.140.22/24 brd 208.97.140.255 scope global secondary bond0:3
    inet6 fe80::225:90ff:fe00:13c3/64 scope link
       valid_lft forever preferred_lft forever
12: eth1.100@eth1: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
    link/ether 00:30:48:de:ee:4b brd ff:ff:ff:ff:ff:ff
    inet 208.97.141.21/24 brd 208.97.141.255 scope global eth1.100
    inet 66.33.216.221/24 brd 66.33.216.255 scope global eth1.100:0
    inet 69.163.188.21/25 brd 69.163.188.127 scope global eth1.100:1
    inet 208.97.141.22/24 brd 208.97.141.255 scope global secondary eth1.100:2
    inet 208.97.141.23/24 brd 208.97.141.255 scope global secondary eth1.100:3
    inet 208.97.141.24/24 brd 208.97.141.255 scope global secondary eth1.100:4
    inet6 2607:f298:1:100:feed:face:beef:d00d/64 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::230:48ff:fede:ee4b/64 scope link
       valid_lft forever preferred_lft forever
13: eth1.105@eth1: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
    link/ether 00:30:48:de:ee:4b brd ff:ff:ff:ff:ff:ff
    inet 75.119.199.211/25 brd 75.119.199.255 scope global eth1.105
    inet6 fe80::230:48ff:fede:ee4b/64 scope link
       valid_lft forever preferred_lft forever
50: tun5: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.5.1 peer 172.16.5.2/32 scope global tun5
51: tun20: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.20.1 peer 172.16.20.2/32 scope global tun20
52: tun6: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.6.1 peer 172.16.6.2/32 scope global tun6
53: tun18: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.18.1 peer 172.16.18.2/32 scope global tun18
54: tun273: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.20.1.2 peer 172.20.1.1/32 scope global tun273
55: tun8: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.8.1 peer 172.16.8.2/32 scope global tun8
56: tun22: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.22.1 peer 172.16.22.2/32 scope global tun22
57: tun17: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.17.1 peer 172.16.17.2/32 scope global tun17
60: tun24: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.24.1 peer 172.16.24.2/32 scope global tun24
61: tun2: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.2.1 peer 172.16.2.2/32 scope global tun2
62: tun270: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.31.2.2 peer 172.31.2.1/32 scope global tun270
63: tun256: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 192.168.0.1 peer 192.168.0.2/32 scope global tun256
64: tun4: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.4.1 peer 172.16.4.2/32 scope global tun4
65: tun16: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.16.1 peer 172.16.16.2/32 scope global tun16
67: tun27: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.27.1 peer 172.16.27.2/32 scope global tun27
68: tun26: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.26.1 peer 172.16.26.2/32 scope global tun26
69: tun12: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.12.1 peer 172.16.12.2/32 scope global tun12
70: tun7: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.7.1 peer 172.16.7.2/32 scope global tun7
71: tun11: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.11.1 peer 172.16.11.2/32 scope global tun11
72: tun23: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.23.1 peer 172.16.23.2/32 scope global tun23
73: tun257: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 192.168.169.9 peer 192.168.169.10/32 scope global tun257
74: tun258: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 192.168.200.1 peer 192.168.200.2/32 scope global tun258
76: tun1: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.1.1 peer 172.16.1.2/32 scope global tun1
77: tun3: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.3.1 peer 172.16.3.2/32 scope global tun3
78: tun21: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.21.1 peer 172.16.21.2/32 scope global tun21
80: tun19: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.19.1 peer 172.16.19.2/32 scope global tun19
81: tun15: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.15.1 peer 172.16.15.2/32 scope global tun15
82: tun260: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 192.168.199.1 peer 192.168.199.2/32 scope global tun260
83: tun9: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.9.1 peer 172.16.9.2/32 scope global tun9
84: tun25: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.25.1 peer 172.16.25.2/32 scope global tun25
85: tun28: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.28.1 peer 172.16.28.2/32 scope global tun28
86: vboxnet0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
87: tun29: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.29.1 peer 172.16.29.2/32 scope global tun29
88: tun10: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.10.1 peer 172.16.10.2/32 scope global tun10
90: tun30: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 172.16.30.1 peer 172.16.30.2/32 scope global tun30
94: tun333: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/[65534]
    inet 10.99.118.178 peer 10.99.118.177/32 scope global tun333

Only eth0, bond0, and eth1.100/105 stuff appears to be listed for me.
Find all posts by this user
Quote this message in a reply
01-08-2013, 07:47 PM
Post: #16
RE: No interfaces listed in Ubuntu 12.10
(01-08-2013 07:29 PM)smitmartijn Wrote:  doesn't exist, under certain conditions.

I did not say "if they don't exist, it won't get recognized" - please don't post a lot of info when uncalled for...it will confuse people.
Visit this user's website Find all posts by this user
Quote this message in a reply
01-08-2013, 09:22 PM
Post: #17
RE: No interfaces listed in Ubuntu 12.10
(01-08-2013 11:48 AM)smitmartijn Wrote:  Please also post whether that interface is recognized, and if you don't have a problem, there's no need to check them at all. ;-)

Hi, please see my post on the page before this... I think I could reproduce it: one of the files not there -> problem, files there -> fine...
Find all posts by this user
Quote this message in a reply
01-25-2013, 08:52 AM
Post: #18
RE: No interfaces listed in Ubuntu 12.10
I'm currently running v2.02 and i still got the issues:
- both files for both NIC's are there, but WP does not recognize them
- running WP with "sudo" still does not show the interfaces
- pcap seems to be set up right:

user @ host ~/bin/WhatPulse $ getcap ./whatpulse
./whatpulse = cap_net_admin,cap_net_raw+eip
Find all posts by this user
Quote this message in a reply
02-01-2013, 06:54 PM
Post: #19
RE: No interfaces listed in Ubuntu 12.10
@roemer2011: I have exactly the same issue under ubuntu 12.10 with WP 2.0.1 and 2.0.3.
Files are there, running WP with sudo for test but no network interfaces there, pcap is installed and set up.
Anyone know how to fix this?

bx02@ubuntu:~$ sudo ./whatpulse
"sni-qt/9763" WARN 19:52:06.171 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE
Opening database file: "/home/bx02/.local/share/data/WhatPulse/whatpulse.db"
Opened database in: 12 ms
"/home/bx02/.local/share/data/WhatPulse/whatpulse.wpw"
Creating device listener for "/dev/input/event0"
Creating device listener for "/dev/input/event1"
Creating device listener for "/dev/input/event2"
Creating device listener for "/dev/input/event3"
Creating device listener for "/dev/input/event4"
Starting NetworkMonitor..
WhatPulse has started
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
QPropertyAnimation: you're trying to animate a non-existing property opacity of your QObject
Find all posts by this user
Quote this message in a reply
02-01-2013, 08:24 PM
Post: #20
RE: No interfaces listed in Ubuntu 12.10
I have no idea where to start searching for this issue ... Do you know of some commandline-switches for WP, e.g. to make it a bit more verbose?
Find all posts by this user
Quote this message in a reply
Post Reply 


Possibly Related Threads...
Thread: Author Replies: Views: Last Post
  Cannot start WhatPulse using Ubuntu 19.10 Adrriii 1 90 11-01-2019 02:37 PM
Last Post: Adrriii
  Whatpulse isn't running after upgrading Ubuntu 1geeky 0 229 08-06-2019 05:46 AM
Last Post: 1geeky
  Ubuntu 16.04 and Libqt5 VanackSabbadium 0 437 06-09-2019 02:24 PM
Last Post: VanackSabbadium
  [CLOSED] Network traffic not recorded on Ubuntu 16.04 LTS GnaXi 4 1,674 09-15-2016 03:33 AM
Last Post: smitmartijn
  Ubuntu on Mac SeeEmAge 0 719 04-29-2016 09:10 PM
Last Post: SeeEmAge
  Memory leak WhatPulse 2.6.3 on Ubuntu 15.04 Wouter0100 2 1,952 01-07-2016 11:52 AM
Last Post: Wouter0100
Sad [Ubuntu 14.04.3] Mouse clicks not logged Carlgo11 0 947 12-16-2015 09:45 AM
Last Post: Carlgo11
  [CLOSED] WhatPulse not starting - Ubuntu 12.04 on Chromebook Code-E 6 2,675 05-19-2015 05:58 PM
Last Post: Divisi
  [SOLVED] Uninstall from Ubuntu vell 1 1,588 02-24-2015 09:05 PM
Last Post: smitmartijn
  Inactive interfaces, PPPOE connection Cyph 3 2,033 01-01-2015 09:11 PM
Last Post: smitmartijn

Forum Jump:


User(s) browsing this thread: 1 Guest(s)