|
|
Sponsored Content
Top Forums
UNIX for Advanced & Expert Users
USB-Ethernet/Ethernet-USB
Post 302903617 by Corona688 on Wednesday 28th of May 2014 03:49:57 PM
05-28-2014
Think of it this way -- a serial cable is like a composite television cable. You plug it in and it shows up on the TV, more or less. There's not a whole lot of fiddling.
A network cable is more like an antenna cable. If you plug it in and see nothing, maybe you're on the wrong channel, band, protocol.... It can carry lots of different things at the same time, you have to select what you want.
This is why you can't just 'cat /dev/ethernetdevice' and see the raw data from your data logger. You need to know what IP address and protocol you want to get data from, and have to have your computer configured correctly to read it.
Is there a way it's supposed to be used? Absolutely but we don't know what it is yet since all the information we need to know is missing. You've refused to answer all our questions.
You've been asked repeatedly for information about the device you're trying to log from. What is it? What model is it? Chances are the device will not log information until you make a TCP connection to it. It might use telnet or it might use http or it might use something else. The information may be in its manual.
When you tried to make a network, presumably to talk to this device on, we asked you repeatedly what information you had for the various things on your network. Several working, cooperating pieces all correctly configured are are required for a working network; knowing one computer's settings is less than half the story.
A network cable is more like an antenna cable. If you plug it in and see nothing, maybe you're on the wrong channel, band, protocol.... It can carry lots of different things at the same time, you have to select what you want.
This is why you can't just 'cat /dev/ethernetdevice' and see the raw data from your data logger. You need to know what IP address and protocol you want to get data from, and have to have your computer configured correctly to read it.
Is there a way it's supposed to be used? Absolutely but we don't know what it is yet since all the information we need to know is missing. You've refused to answer all our questions.
You've been asked repeatedly for information about the device you're trying to log from. What is it? What model is it? Chances are the device will not log information until you make a TCP connection to it. It might use telnet or it might use http or it might use something else. The information may be in its manual.
When you tried to make a network, presumably to talk to this device on, we asked you repeatedly what information you had for the various things on your network. Several working, cooperating pieces all correctly configured are are required for a working network; knowing one computer's settings is less than half the story.
| Moderator's Comments: | ||
|
Last edited by Corona688; 05-28-2014 at 04:56 PM..
This User Gave Thanks to Corona688 For This Post:
|
|
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
We are trying to Establish Network using Linux.Now we are facing the problem in configring Ethernet.In out network we are giving eth0 in server and activating it at the boot time,so it is activating as it is but when we define the Ethernet of node on server and allowing it to activate at boot time... (5 Replies)
Discussion started by: at_renai2001
5 Replies
2. Solaris
I have a Quad Ethernet card in a 220R. 2 ports activated. Each has its own hostname file and both hostnames are in the hosts file. I want both ports to have the same IP address so we can use the 2nd port in case we lose communication on the port. On bootup, the box gives me:
SIOCSLIFFLAGS:... (5 Replies)
Discussion started by: hshapiro
5 Replies
3. AIX
Hello everyone
I have a problem with one server, has Aix 5.3 in the errpt has this message
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
F3931284 0105133009 I H ent0 ETHERNET NETWORK RECOVERY MODE
EC0BCCD4 0105133009 T H ent0 ETHERNET DOWN
F3931284 ... (4 Replies)
Discussion started by: lo-lp-kl
4 Replies
4. Solaris
I have a new Sun 440 and I am trying to configure it. Non of the Ethernet ports are enabled; when I issue "ifconfig -a" it returns nothing. Is there a way to know the available port name (e.g. ce, bge, etc.) by running a command or so ? (4 Replies)
Discussion started by: StarSol
4 Replies
5. Solaris
my solris box network is unreachable how to solve this
ipaddress assiagning and entry in vi /etc/host
how to solve network is unreachable (2 Replies)
Discussion started by: tirupathi
2 Replies
6. Solaris
I had installed soalris 10 on my dell vostro 1400.It had installed succefully.
If i type ifconfig -a it is showing only my loop back adpater.
So how to tell me how to mount my usb drive and how to configure
my lan ethernet card,My lan ethernet card is Broadcom.
Tell me step... (1 Reply)
Discussion started by: testerindia25
1 Replies
7. UNIX for Dummies Questions & Answers
Is there an easy way to setup a cross-over cable (USB-USB) between a linux box and a windows PC? My 2 machines are next to each other but I really do not want to keep transfering my files using my USB drive.
Thanks! (4 Replies)
Discussion started by: Xterra
4 Replies
8. AIX
Hi
In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID.
Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Discussion started by: newtoaixos
1 Replies
LEARN ABOUT FREEBSD
kue
KUE(4) BSD Kernel Interfaces Manual KUE(4) NAME
kue -- Kawasaki LSI KL5KUSB101B USB Ethernet driver SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device uhci device ohci device usb device kue Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_kue_load="YES" DESCRIPTION
The kue driver provides support for USB Ethernet adapters based on the Kawasaki LSI KL5KLUSB101B chipset. The KL5KLUSB101B supports a 128-entry multicast filter, single perfect filter entry for the station address and promiscuous mode. Packets are received and transmitted over separate USB bulk transfer endpoints. The Kawasaki chipset supports only 10Mbps half-duplex mode, hence there are no ifmedia(4) modes to select. For more information on configuring this device, see ifconfig(8). HARDWARE
The kue driver supports Kawasaki LSI KL5KLUSB101B based USB Ethernet adapters including: o 3Com 3c19250 o 3Com 3c460 HomeConnect Ethernet USB Adapter o ADS Technologies USB-10BT o AOX USB101 o ATen UC10T o Abocom URE 450 o Corega USB-T o D-Link DSB-650C o Entrega NET-USB-E45, NET-HUB-3U1E o I/O Data USB ETT o Kawasaki DU-H3E o LinkSys USB10T o Netgear EA101 o Peracom USB Ethernet Adapter o Psion Gold Port USB Ethernet adapter o SMC 2102USB, 2104USB DIAGNOSTICS
kue%d: watchdog timeout A packet was queued for transmission and a transmit command was issued, however the device failed to acknowledge the transmission before a timeout expired. kue%d: no memory for rx list The driver failed to allocate an mbuf for the receiver ring. SEE ALSO
arp(4), netintro(4), ng_ether(4), ifconfig(8) HISTORY
The kue device driver first appeared in FreeBSD 4.0. AUTHORS
The kue driver was written by Bill Paul <wpaul@ee.columbia.edu>. BUGS
The kue driver does not accumulate Ethernet collisions statistics because the Kawasaki firmware does not appear to maintain any internal sta- tistics. BSD
October 7, 2006 BSD