Ubuntu :: Cannot Detect Network Device When Using Libpcap
May 27, 2011
I use libpcap to write a program to detect network device in Ubuntu but not sucess. The result is no suitable device found. How many reasons are there for that? The code i used is the main user page.
I am currently using fedora 11 kernel 2.6.29 version, i wanted to write device driver for usb to detect my own device. My project is radio with computer. My fm radio get connected to usb port so i need to write h/w interfacing program.
I just added a 2 port network card to a system that is running Fedora 11, but it is INACTIVE. I open the Network Device Control to activate it but there is no network ports in Network Device Control. It is empty.It looks like the system recognize the card and loaded correct driver.
My computer is Dell Inspiron N4020.And after I installed the Ubuntu 10.04 successfully,a problem occured:No wireless device appear nor the wireless signal
So I bought an eMachine e250 from a friend of mine, and installed Backtrack on it. That worked fine, until I realised that I didn't like KDE, and decided to get the gnome-based Gnacktrack (based on Ubuntu 10.10, so I'm fairly sure they work the same). I also have a harddrive from an old laptop that I've scrapped with Ubuntu 10.4 that I run in the laptop, and fpr some bizzare reason, neither operating system is able to detect the wireless card. It worked fine with Backtrack (based on Noppix I believe), and I'm curious as to why the wireless card hates Ubuntu so much. I know that it's unable to detect the wireless card because on start-up it says "Unable to detect WMID device". I even added the wireless card from my scrapped laptop to the laptop, and that NIC was detected just fine. (though I can't use it because the antenna won't reach the slot for the secondary NIC)
im using acer ao532h and just install lucid dual boot with w7. I have problem this mesej coming out when booting after grub then blank screen direct to login screen.
I have a FireWire camera LifeSize connected to my PC in the FireWire interface. My PC has miniPCI slot and with external converter its having a FireWire interface. Now its Ubuntu who is not showing me anything at all when i try:
$ uname -a Linux desktop 2.6.38-11-generic-pae #48-Ubuntu SMP Fri Jul 29 20:51:21 UTC 2011 i686 i686 i386 GNU/Linux
I am attaching a LTO-3 tape drivce into my RHEL5 linux machine. Every time i used to restart my machine to detect the tape drive is there any way to rescan the buses to detect the newly attached scsi devices. In solaris "devfsadm" and "iostat" is there. I need the same kind of thing in linux.
I'm using debian lenny, I bought a new Hp officejet j4500 scanner but the xsane is unable to detect the scanner. It says device not found. If I run xsane as root it detects and works properly it is obvious.I have added the user to scanner,saned and also to root user group.
I have a pair of special radio-devices which support SNMP, but the problem is, that if I snmpwalk those devices, I only see few generic values(sysContact, sysDescr, sysServices etc) and nothing else. Most likely I need MIB files so NMS could know what values can be asked from the radio devices? If yes, is there a possibility to get all the OID's device supports without MIB files as those devices have been out or production for years?
I have installed WICD on Debian . I can now access a new a Network Manager screen, which did not exist before, but it does not display/detect any wireless networks. It is like dead. Before installing WICD I did at least have a wireless WPE encrypted network, which was detected, although it often disconnected for no known reasons. Now even that Network has gone and I can't go on line. Can anybody help here? How can I configure the WICDNetwork Manager to detect an existing network or create a new one? In the latter case, would I have to reconfigure the Router settings to setup/connect to a network in Debian? May be I have to do this, because Tor/Vidalia changes my IP address and so my Network Adapter ( Linksys) can no longer connect to the router. Also, when trying to follow troubleshooting leads in this connection, the Terminal screen on Debian ( CMD) would often return a PERMISSIONS DENIED message.
I am having a situation where I couldn't connect to Internet through wireless and LAN cable. I have done ifconfig, it only shows me "lo" info. May I know how can I bring up the LAN and wireless?
How one could determine (for use in a Bash or Python script) which device (eg /dev/sda1, /dev/hda1... etc) a ramfs was loaded from when booting from a USB drive.
I have a RIPLinux/Tinycore live USB disk that automatically needs to run a script that is stored on the same USB drive but not part of the RIPLinux/Tinycore image. (Please note that I do not want to put this script into the RIPLinux image.) I therefore would like to remix the RIPLinux/Tinycore ISO to automatically run this script once it has started up. After RIP linux has booted I would like to automatically mount the USB drive that RIPLinux/Tinycore was booted from. I need help detecting which device this is.
I am trying to install libpcap and tcpdump, but even if I have already installed Flex, as the terminal tells me to do. What else could I do?
Code: configure: error: Your operating system's lex is insufficient to compile libpcap. Flex is a lex replacement that has many advantages, including being able to compile libpcap. For more information, see [URL].
In my YaST Network Settings (11.3), I see an entry labelled "Unknown Network Device" how to remove the confusion? The Overview tab also correctly lists my three known network devices (listed below), as does the Hardware Information utility. This is the output of lspci, and as far as I can tell, is accurate and complete. So what has YaST seen that it can't identify?
I am running slackware-current and I have tcpdump-4.1.1-i486-1.txz installed. If I remember right libpcap used to be part of tcpdump, but since recently i cannot find it in my system anymore! Tools like nmap give me the error message:
"error while loading shared libraries: libpcap.so.1: cannot open shared object file: No such file or directory"
These days i try make a simple sniffer for a embedded system. and it need the function of dump all the packets into a file, which can be read by wireshark..etc. First i copy a code called simplesniffer.c from the Internet,and and now I want to add the dumpfile funtion to it. i find some problems.Quote:
/* Come from ---- http://blog.chinaunix.net/u/24474/showart_226419.html */ /* simplesniffer.c */ #include <stdio.h>
I've just fully installed Ubuntu on my laptop. I had it running as a secondary operating system and have switched over. Now, however, I'm having all sorts of incredibly frustrating problems, one of which being that it won't detect the wireless networks around me! how I can get the network manager to automatically detect wireless networks in range, this whole process has become very frustrating.
I installed ZTE MF 626 modem in my F10 with kernel 2.6.27.12-170, i run usb_modeswitch and so far things happened normally. Watching through /var/log/messages it says that F10 detects two port device for this modem: ttyUSB1 and ttyUSB2, and in the sequence it disable port ttyUSB1 BUT Network Manager still set this port.I mean, when i connect via wvdial appointing to ttyUSB2 i get connection, but Network Manager fails to do it appointing to ttyUSB1. How to change device port in Network Manager?
I am running Ubuntu Hardy Heron. Trying to configure a ax25 packet software to connect to the internet by way of a port called tun0 that I've created within the software. I can connect within the LAN but not outside. If I execute tcpdump while the tun0 is up, I first receive the message, "WARNING: arptype 65534 not supported by libpcap - falling back to cooked socket."Question: Does this warning relate to my connectivity issue and if so, how can I 'fix' the problem?
I am trying to install libpcap version 1 on my centos 5.5 (which supply libpcap 0.9.4 as built in). I need libpcap>=1.0 to install snort 2.9. I tried to install by downloading source code from tcpdump.org but failed to update libpcap-0.9.4 by libpcap-1.0.0.
My driver is rt2870sta. I know it works because wicd can detect a WEP network, but it can't detect my WPA network despite me being right next to the hub. I consulted the wiki and have wpa_supplicant installed.
My /etc/network/interfaces file reads: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5).
# The loopback network interface auto lo iface lo inet loopback I am added to the group netdev as well.
On an unrelated point, my other usb wifi adapter uses ath9k_htc, but it isn't included with the kernel. I thought it was supposed to be?
I'm running Ubuntu 10.04.1 and am trying to get packet capturing working for my Bluetooth dongle using hcidump.From what I've read, libpcap must be compiled to enable Bluetooth sniffing and given that hcidump isn't finding a single packet, I'm guessing the version Ubuntu has installed for me isn't compiled with bluetooth support.So I downloaded a newer version of libpcap and installed the bluez header files. Configured libpcap and it gave a "Yes" for bluetooth support. It is now installed and sitting in /usr/local/lib/. Now I'm trying to compile hcidump to use this lib rather than the system default but I can't figure out how...I've read that GCC can be passed the -lpcap flag to set the path but I haven't figured out how to do this.
I'm running Squeeze and I'm looking 3 days now for a solution in some weird problem. The NetworkManager Applet shows that there isn't connection although I am connected. The icon has this small "x" and when mouseover it says "No network conncection". Moreover when left clicking it, it says
"Wired Network Device not managed"
While I was looking for the solution a came across this post by an Ubuntu developer who says:network-manager-applet displays the connectivity state of network-manager's managed interfaces not every interface. So the title "network manager says disconnected but is connected and working" is actually misleading. The interface is connected and working but not from network-manager's point of view since it is not managing the interface. Additionally, in Lucid now network-manager applet displays nothing now for non-managed interfaces so is less misleading. You can check to see whether or not an interface is managed by network-manager by using the command line too nm-tool. You'll see "State: unmanaged" for unmanaged interfaces.