08-29-2009
NIC and eth connection
folks;
This might sounds stupid but i hope someone can give me an answer:
On my Linux SUSE boxes, i have 2 NIC cards NIC1 & NIC2. I always assumed that NIC1 is eth0 when i run "ifconfig" and NIC2 is eth1
but i noticed that's not always the case.
Is there a way or a command i can run to find out which NIC assigned to which eth?
Thanks in advance
9 More Discussions You Might Find Interesting
1. Linux
Hi
I had a DL380 with two two port eth cards. I now replaced one with a four port eth card and my interfaces seemed to have jumped around.
Is there a method of moving eth ports... eg making port eth4 eth2.:confused: (2 Replies)
Discussion started by: theroncj
2 Replies
2. Solaris
Hi everyone,
I am hoping anyone of you could help me in this weird problem we have in 1 of our Solaris 10 servers. Lately, we have been having some ftp problems in this server. Though it can ping any server within the network, it seems that it can only ftp to a select few. For most servers, the... (4 Replies)
Discussion started by: labdakos
4 Replies
3. Solaris
I couldn't install my nic in solaris 10. I compiled and added
the driver but failed to attach the driver and ifconfig output
shows only loopback dev. Please see the following output and tell
me whether my nic has been detected and why the driver failed to
attach?
My nic is detected in linux... (0 Replies)
Discussion started by: vectrum
0 Replies
4. IP Networking
I am new in squid proxy.
My question is how to (and if it's necessary) to set one NIC for inbound traffic (http requests) and one NIC for outbound traffic (http answers)?
Thank you in advance! (4 Replies)
Discussion started by: aixlover
4 Replies
5. Shell Programming and Scripting
I want to run dhcpclient for all the eth* which has no ip
for example
eth0 Link encap:Ethernet HWaddr 00:1E:67:3E:BA:EF
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0... (6 Replies)
Discussion started by: yanglei_fage
6 Replies
6. Red Hat
Dear All
I want tune my NIC's rps, rfs and xps value.
In my system I have two NIC (eth0, eth1) and I have a bond0 ( eth0, eth1).
Here is the question? Which device should I modify ?
eth0 and eth1? or just modify bond0 or modify all device (eth0, eth1, bond0)
Any advice is welcome.... (0 Replies)
Discussion started by: nnnnnnine
0 Replies
7. UNIX for Dummies Questions & Answers
hi guys
I have a server which has 2 nics eth0 and eth1
eth0 is used for our email traffic server. everything working fine
some time later a eth1 was added for backup purposes so this new nic sends data to another vlan for backup purposes
all of a sudden our mail server starts to fail... (3 Replies)
Discussion started by: karlochacon
3 Replies
8. Linux
Hello Admins,
My ask is how can I add two different subnet IPs to same box with two different gateways?
The issue is I can connect to the box when I am on ethernet LAN, but I am not able to connect to the same IP when I am on wifi. The server is RHEL 7 VM on vmware.
How can I get connected... (4 Replies)
Discussion started by: snchaudhari2
4 Replies
9. UNIX for Advanced & Expert Users
Dear all,
I have a remote CentOS7 server that has two network cards. Each card has four ports and port one of card one was defined with the IP address assigned to the server. So far, so good and it's been working for over a year. We have now got cables sorted out so there are four paths... (4 Replies)
Discussion started by: rbatte1
4 Replies
AN(4) BSD Kernel Interfaces Manual AN(4)
NAME
an -- Aironet 4500/4800 and Cisco 340/350 series wireless network driver
SYNOPSIS
an* at pcmcia? function ?
an* at pci? dev ? function ?
an* at isapnp?
DESCRIPTION
The an driver provides support for Aironet Communications 4500/4800 and Cisco Aironet 340/350 series wireless network adapters. This
includes the ISA, PCI and PCMCIA varieties. The 4500 series adapters operate at 1 and 2Mbps while the 4800 series and 340/350 series can
operate at 1, 2, 5.5 and 11Mbps. The ISA, PCI and PCMCIA devices are all based on the same core PCMCIA modules and all have the same pro-
gramming interface, however unlike the Lucent WaveLAN/IEEE cards, the ISA and PCI cards appear to the host as normal ISA and PCI devices and
do not require any PCMCIA support.
The PCMCIA Aironet cards require PCMCIA support. ISA cards can either be configured to use ISA Plug and Play or to use a particular I/O
address and IRQ by properly setting the DIP switches on the board. (The default switch setting is for plug and play.) The an driver has
Plug and Play support and will work in either configuration, however when using a hard-wired I/O address and IRQ, the driver configuration
and the NIC's switch settings must agree. PCI cards require no switch settings of any kind and will be automatically probed and attached.
All host/device interaction with the Aironet cards is via programmed I/O. The Aironet devices support 802.11 and 802.3 frames, power manage-
ment, BSS (infrastructure) and IBSS (ad-hoc) operation modes. The an driver encapsulates all IP and ARP traffic as 802.11 frames, however it
can receive either 802.11 or 802.3 frames. Transmit speed is selectable between 1Mbps, 2Mbps, 5.5Mbps, 11Mbps, or ``auto'' (the NIC automat-
ically chooses the best speed).
By default, the an driver configures the Aironet card to join an access point with an SSID of null string. For ad-hoc mode, in which sta-
tions can communicate among each other without the aid of an access point, the driver must be set using ifconfig(8).
For more information on configuring this device, see ifconfig(8) and ifmedia(4).
HARDWARE
Cards supported by the an driver include:
Aironet 4500 Series
Aironet 4800 Series
Cisco Aironet 340 Series
Cisco Aironet 350 Series
DIAGNOSTICS
an%d: init failed The Aironet card failed to come ready after an initialization command was issued.
an%d: failed to allocate %d bytes on NIC The driver was unable to allocate memory for transmit frames in the NIC's on-board RAM.
an%d: device timeout The Aironet card failed to generate an interrupt to acknowledge a transmit command.
SEE ALSO
arp(4), ifmedia(4), netintro(4), ifconfig(8)
HISTORY
The an device driver first appeared in FreeBSD 4.0, and then in NetBSD 1.6.
AUTHORS
The an driver was written by Bill Paul <wpaul@ee.columbia.edu>.
BSD
December 13, 2000 BSD