Help asap squid with 2 nic cards setup Post: 302761965

9 More Discussions You Might Find Interesting

1. Solaris

NIC cards for sunblade 100

I need to add a PCI NIC to a sunblade 100 running solaris 8. Im new to this and was hoping someone could give me some card names and models which will work for this system and has a driver for this sparc system. thanks

2. IP Networking

Setup 2 NIC cards in one UNIX system

Hi; I have a UNIX box (SCO 5.0.2) with two (2) NIC cards. One card (NIC1) talks to a network 57.14.65.x/27. The other card NIC2) talks to users on 57.14.103.x and 57.14.105.x with subnet mask of 255.255.0.0. If I set NIC2 to this subnet mask (255.255.0.0) it seems like the NIC traffic is now...

3. High Performance Computing

veritas and nic cards

Hello I have 2 machines with 3 NIC cards. When I setup veritas, I receive this message: e1000g1 has an IP address configured on it. It could be a public NIC on ken. Are you sure you want to use e1000g1 for the first private heartbeat link? As if e1000g1 should not have an IP address....

4. HP-UX

routing issues with multiple NIC cards

I am running HP_UX 11.23 with 4 NIC cards (this is our TSM server) I have 4 subnets we are backing across. trying to keep traffic on their subnets. I only have one route statment should I add more. route add net 123.99.8.0 netmask 255.255.255.0 123.99.8.254 route add net 123.99.67.0 netmask...

5. Red Hat

External NIC cards not pinging with each other in RHEL 5.1

We have a setup of two nodes which has two NIC cards in each. One is built in and another is D-Link (external NIC card). We are unable to ping to the external NIC cards in both. Eg: Node A has two IPs 192.168.1.10 (eth0) and 192.168.2.10 (eth1) and Node B has two IPs 192.168.1.20 (eth0) and...

6. HP-UX

HP UX 9000 NIC CARDS

Hello, I am trying to move an HP UX from one locaion to another. The new location don't have any Fiber switches. On the back of my server I see 2 RJ 45 for console management the other for networking , the server also has a fiber NIC card. When I disconnec the fiber and want to user regular...

7. IP Networking

Best reference for understanding low level info on nic cards drivers and functionality

Hi, What is the best reference that gives in detail on nic cards configuration , assigning multiple ip addresses to a single interface, netlink library etc and all basic stuff at this level..? Thanks

8. IP Networking

squid proxy: one NIC for inbound & one NIC for outbound?

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!

9. Ubuntu

How do you setup 2 nic cards for squid Ubuntu server?

I have a made my squid proxy, I now have add another nic card to an old CPU using Ubuntu server 12.04. I have seen another post similar however I am new and did not understand some of it. Something about redirecting IP address and IP table? I don't know how to do this.:confused:

LEARN ABOUT REDHAT

axnet_cs

AXNET_CS(4)						     Kernel Interfaces Manual						       AXNET_CS(4)

NAME

       axnet_cs - Asix AX88190 chipset PCMCIA Ethernet Driver

SYNOPSIS

       insmod axnet_cs.o [pc_debug=n] [irq_list=i,j,...]

DESCRIPTION

       Axnet_cs  is  a driver for PCMCIA ethernet cards based on the Asix AX88190 chipset.  These cards are mostly NE2000 compatible but have sev-
       eral bugs that are sufficiently tricky to work around that a separate driver was deemed necessary.  When this driver is bound to a card, it
       allocates  the  next  available	ethernet  device (eth0..eth#).	This device name will be reported in the kernel log file, and passed on to
       cardmgr(8).

PARAMETERS

       pc_debug=n
	      Selects the PCMCIA debugging level.  This parameter is only available if the module is compiled with debugging enabled.  A  non-zero
	      value enables debugging.

       irq_list=i,j,...
	      Specifies the set of interrupts that may be allocated by this driver.

DIAGNOSTICS

       axnet_cs: this is not an AX88190 card!
	      Indicates that this card is probably a normal NE2000 compatible card, which requires the pcnet_cs driver.

       eth#: interrupt(s) dropped!
	      Indicates that the driver did not receive an interrupt notification for some reason.  The driver will poll the card (with a signifi-
	      cant performance penalty) if the problem persists.  The most likely cause is an interrupt conflict and/or host bridge  configuration
	      problem.

AUTHOR

       David Hinds - dahinds@users.sourceforge.net

SEE ALSO

       cardmgr(8), pcmcia(5).

pcmcia-cs							2001/08/17 12:51:58						       AXNET_CS(4)