07-30-2012
Lan card not reaching Gateway
Hi,
I have this problem on RHEL box. I am using two NIC's of same model and make (Intel 82557) in the adjacent PCI slots . I am using each one for different subnet and have assigned them ipaddresses and gateways of respective subnets . While one is O.K. connecting to its gateway other don't. I have checked this card in Winows and its working fine. Card is not faulty. Problem only starts in RHEL.
ip1 192.168.14.2 -----> gateway 192.168.14.1
ip2 172.16.18.3 --X--> gateway 172.16.18.1
Any help is aprreciated.
Thanks,
Dexter
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
The Lan card in one of our UIII WS's seem doesn't work,so with ping command i can not see any of the machines in LAN and with some other tests i'm sure it's not OK.
I tried to use the second card on PCI port ,but the replaced card was one of the ordinary card for PC's ...by the way after... (1 Reply)
Discussion started by: nikk
1 Replies
2. Cybersecurity
what is lan card autonegotiation ?
how to enable and disable this feature? (2 Replies)
Discussion started by: nabil_boussetta
2 Replies
3. SCO
Dear all
Im facing one problem in SCO 5.0.5 , its that in the server there are three LAN cards INTEL PRO 100 series but when we configure all the three cards then LAN stops working . self ping is possible but no one can ping the server. If we remove driver of any one card LAN starts working.
Is... (1 Reply)
Discussion started by: ccvyas
1 Replies
4. Solaris
Hi,
i have a RealTek Lan Card on my machine. Does Solaris 9 supports this lan card .
Thank You,
Shafi (3 Replies)
Discussion started by: sol8admin
3 Replies
5. SCO
hi all
i have installed SCO 5.0.5 on a "Netfinity 5000" IBM server. But the OS is not detecting the lan card. how can i detect it.... help and thanks in advance .
bidhayak (3 Replies)
Discussion started by: bidhayakm
3 Replies
6. Programming
Please tell me API in Solaris / Linux / UNIX to get status information of LAN card. (1 Reply)
Discussion started by: mansoorulhaq
1 Replies
7. Linux
Hi.
I have a lan card installed on my server. I want to check the duplex speed of it. How can I check it?
Help is appreciated.
Thank you. (3 Replies)
Discussion started by: Amol21
3 Replies
8. Solaris
Hi,
I've recently moved my pci LAN card from Slot2 Slot5 on my sun x4270_m2 server (solaris 10).
I've done the touch / reconfigure and devfsadm, however my issue is that im able to configure the e1000g7 port with an ip address (192.168.0.1) but if i plug my laptop (set with static ip... (7 Replies)
Discussion started by: kerrygold
7 Replies
9. Red Hat
we have red hat 6 linux box
There are two lan card
one lan card eth0 have ip 10.82.190.31/24 GW 10.82.190.254
2th lan card eth1 have ip 10.82.188.33/24 GW 10.82.188.254
I have below route ... I use two route table
root@xxx# netstat -rn
Kernel IP routing table
Destination Gateway ... (5 Replies)
Discussion started by: chuikingman
5 Replies
10. UNIX for Beginners Questions & Answers
Dear friends
I use RedHat 6.5, which sets the gateway in the configuration file / etc / sysconfig / network as GATEWAY = 192.168.1.26, and the gateway in the configuration file / etc / sysconfig / network-scripts / ifcfg-eth11 as GATEWAY = 192.168.1.256. The two gateways are different.... (6 Replies)
Discussion started by: tanpeng
6 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