LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 01-22-2013, 01:02 PM   #1
drewschwartz
LQ Newbie
 
Registered: Jan 2013
Location: new jersey
Posts: 2

Rep: Reputation: Disabled
red hat 6.3 dual NIC issue


I have a red hat 6.3 virtual machine with 2 physical nics installed. I also have a virtual adapter on eth0 as well. I am using this for my vcloud director server

eth1 is 10.3.80.215 - this is the network that has infrastructure servers for vmware (vcenter,etc)

eth0 is 10.231.1.2 which is the http connection for the my vcloud director server.

eth0:0 is 10.231.1.3 which is the console proxy connection.

I can ping any of these ips from anywhere except I can not ping the 10.231 addresses from any machines on the 10.3.80 subnet. It is as if it doesnt know how to route back. I looked and the value of IP_forward is set to 1 (I set it but that didnt help)

Any ideas of how to get this to work? Thanks so much in advance

here is the ifconfig and the route table.

ifconfig
eth0 Link encap:Ethernet HWaddr 00:0C:29:E3:CD:29
inet addr:10.231.1.2 Bcast:10.231.1.255 Mask:255.255.255.0
inet6 addr: fe80::xxx:xxxx:fee3:cd29/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:710145 errors:0 dropped:0 overruns:0 frame:0
TX packets:636043 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:146272731 (139.4 MiB) TX bytes:340604630 (324.8 MiB)

eth0:0 Link encap:Ethernet HWaddr 00:0C:29:E3:CD:29
inet addr:10.231.1.3 Bcast:10.231.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth1 Link encap:Ethernet HWaddr 00:0C:29:E3:CD:33
inet addr:10.3.80.215 Bcast:10.3.80.255 Mask:255.255.255.0
inet6 addr: fe80::xx:xxxx:fee3:cd33/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:26643771 errors:0 dropped:0 overruns:0 frame:0
TX packets:6416677 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4879371482 (4.5 GiB) TX bytes:1349011239 (1.2 GiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:121636 errors:0 dropped:0 overruns:0 frame:0
TX packets:121636 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:12040727 (11.4 MiB) TX bytes:12040727 (11.4 MiB)
route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.231.1.0 * 255.255.255.0 U 0 0 0 eth0
10.3.80.0 * 255.255.255.0 U 0 0 0 eth1
link-local * 255.255.0.0 U 1002 0 0 eth0
link-local * 255.255.0.0 U 1003 0 0 eth1
default 10.231.1.1 0.0.0.0 UG 0 0 0 eth0
 
Old 01-22-2013, 01:06 PM   #2
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417

Rep: Reputation: 1971Reputation: 1971Reputation: 1971Reputation: 1971Reputation: 1971Reputation: 1971Reputation: 1971Reputation: 1971Reputation: 1971Reputation: 1971Reputation: 1971
well for a start you don't actually say you're configuring any client to actually route to that specific machine. Are you? can you show us the output of "iptables -vnL" on the box?
 
Old 01-22-2013, 01:17 PM   #3
drewschwartz
LQ Newbie
 
Registered: Jan 2013
Location: new jersey
Posts: 2

Original Poster
Rep: Reputation: Disabled
This server is the director server for the cloud infra stuff, and the main web portal is 10.231.1.2 The .80 address on the server is for the back end vmware communications. If I connect to the 10.231.1.2 or .3 address from anywhere, it works fine, I can ping it or pull up the web portal no problem. If I am on a machine on the .80 subnet, I am unable to connect to those 2 IP addresses for some reason, I assume its a routing thing, but i dont know for certain.

# iptables -vnL
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

---------- Post added 01-22-13 at 02:18 PM ----------

so i dont need it to be a router, or route for that matter, but it does need to know how to send traffic to that subnet. I believe thats the issue
 
Old 01-22-2013, 02:06 PM   #4
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417

Rep: Reputation: 1971Reputation: 1971Reputation: 1971Reputation: 1971Reputation: 1971Reputation: 1971Reputation: 1971Reputation: 1971Reputation: 1971Reputation: 1971Reputation: 1971
"how to send traffic to that subnet" = "be a router". What's the difference? You need to have clients route traffic to that box to get to the other side of it, and for anything on te other side to know how to get back. That's routing.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Red Hat 9 Wireless NIC wireddecker Linux - Hardware 2 09-16-2003 10:46 PM
Red Hat 9 / WIn XP dual boot issue gwgross Linux - Software 4 05-27-2003 11:30 PM
Red Hat 8 and NIC configuration. chadm1967 Linux - Distributions 6 11-17-2002 12:57 PM
Red Hat 7.0 NIC Installation burtongeek Linux - Newbie 1 03-02-2001 12:33 AM


All times are GMT -5. The time now is 02:37 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration