Sponsored Content
Operating Systems Linux Red Hat External NIC cards not pinging with each other in RHEL 5.1 Post 302254812 by MadhukarG on Wednesday 5th of November 2008 08:03:56 AM
Old 11-05-2008
Hi Thanks for the quick reply.. I'm also the part of the same team.

I have tried adding the route to the 192.168.2.0 network from both the machines.. I have tried all the possible solutions, do you think any service is stopping the external card to ping each other?
 

10 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 (3 Replies)
Discussion started by: meyersp
3 Replies

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... (2 Replies)
Discussion started by: texaspanama
2 Replies

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.... (2 Replies)
Discussion started by: melanie_pfefer
2 Replies

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... (2 Replies)
Discussion started by: myork
2 Replies

5. 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... (1 Reply)
Discussion started by: ldaliosmane
1 Replies

6. 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 (2 Replies)
Discussion started by: Gopi Krishna P
2 Replies

7. Red Hat

cannot ssh (use NFS) on RHEL box, but can mount external & ssh out of RHEL box

Ok, Im trying to get NFS working on my RHEL 5 box, apparently i can use the box as a client, but not as a server. If it helps i cant ssh into the box (server), but as a client ssh works fine. Ive configured server: /etc/hosts.allow: all : all all :all@all setup my /etc/exports file... (4 Replies)
Discussion started by: drs.grid
4 Replies

8. Ubuntu

Help asap squid with 2 nic cards setup

I found an old post that talks about 2 nice cards and it is driven by the IP address .... but I didn't understand it because the 2 people skipped information for me the newbie.. Can someone help me... I have the proxy server setup and I believe I have enabled the 2nd nic card, I just need one... (1 Reply)
Discussion started by: trilju2005
1 Replies

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: (9 Replies)
Discussion started by: trilju2005
9 Replies

10. Red Hat

RHEL 5.5 NIC Bonding

I am new to linux. I have a falconstor CDP installation which runs on RHEL 5.5 (Tikanga). There is a vendor option to bond nics in either 802.3ad or round robin, I choose 802.3ad. The server is connected to a Cisco 3750 switch. The problem is dropped packets and eth03 wont come up in the PO... (0 Replies)
Discussion started by: tjcooper
0 Replies
GRE(4)							   BSD Kernel Interfaces Manual 						    GRE(4)

NAME
gre -- encapsulating network device SYNOPSIS
To compile the driver into the kernel, place the following line in the kernel configuration file: device gre Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_gre_load="YES" DESCRIPTION
The gre network interface pseudo device encapsulates datagrams into IP. These encapsulated datagrams are routed to a destination host, where they are decapsulated and further routed to their final destination. The ``tunnel'' appears to the inner datagrams as one hop. gre interfaces are dynamically created and destroyed with the ifconfig(8) create and destroy subcommands. This driver corresponds to RFC 2784. Encapsulated datagrams are prepended an outer datagram and a GRE header. The GRE header specifies the type of the encapsulated datagram and thus allows for tunneling other protocols than IP. GRE mode is also the default tunnel mode on Cisco routers. gre also supports Cisco WCCP protocol, both version 1 and version 2. The gre interfaces support a number of additional parameters to the ifconfig(8): grekey Set the GRE key used for outgoing packets. A value of 0 disables the key option. enable_csum Enables checksum calculation for outgoing packets. enable_seq Enables use of sequence number field in the GRE header for outgoing packets. EXAMPLES
192.168.1.* --- Router A -------tunnel-------- Router B --- 192.168.2.* / / +------ the Internet ------+ Assuming router A has the (external) IP address A and the internal address 192.168.1.1, while router B has external address B and internal address 192.168.2.1, the following commands will configure the tunnel: On router A: ifconfig greN create ifconfig greN inet 192.168.1.1 192.168.2.1 ifconfig greN inet tunnel A B route add -net 192.168.2 -netmask 255.255.255.0 192.168.2.1 On router B: ifconfig greN create ifconfig greN inet 192.168.2.1 192.168.1.1 ifconfig greN inet tunnel B A route add -net 192.168.1 -netmask 255.255.255.0 192.168.1.1 NOTES
The MTU of gre interfaces is set to 1476 by default, to match the value used by Cisco routers. This may not be an optimal value, depending on the link between the two tunnel endpoints. It can be adjusted via ifconfig(8). For correct operation, the gre device needs a route to the decapsulating host that does not run over the tunnel, as this would be a loop. The kernel must be set to forward datagrams by setting the net.inet.ip.forwarding sysctl(8) variable to non-zero. SEE ALSO
gif(4), inet(4), ip(4), me(4), netintro(4), protocols(5), ifconfig(8), sysctl(8) A description of GRE encapsulation can be found in RFC 2784 and RFC 2890. AUTHORS
Andrey V. Elsukov <ae@FreeBSD.org> Heiko W.Rupp <hwr@pilhuhn.de> BUGS
The current implementation uses the key only for outgoing packets. Incoming packets with a different key or without a key will be treated as if they would belong to this interface. The sequence number field also used only for outgoing packets. BSD
November 7, 2014 BSD
All times are GMT -4. The time now is 09:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy