Re: Help with network config in RAC Attack 12c

  • From: "Mark J. Bobak" <mark@xxxxxxxxx>
  • To: Chris Taylor <christopherdtaylor1994@xxxxxxxxx>
  • Date: Mon, 14 Jul 2014 13:14:22 -0400

The problem is definitely in routing.

If I (successfully) ping 'google.com' in the host, I can see the IP tha was
resolved.  If I then take that IP and try pinging it in the guest, I get an
error,"connect:  Network is unreachable".

Here's what I see in ifconfig:

[root@racattack1 ~]# ifconfig -a

eth0      Link encap:Ethernet  HWaddr 08:00:27:EC:82:04

          inet addr:192.168.78.51  Bcast:192.168.78.255  Mask:255.255.255.0

          inet6 addr: fe80::a00:27ff:feec:8204/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:87 errors:0 dropped:0 overruns:0 frame:0

          TX packets:73 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:9779 (9.5 KiB)  TX bytes:8813 (8.6 KiB)


eth1      Link encap:Ethernet  HWaddr 08:00:27:23:4D:DD

          inet addr:172.16.100.51  Bcast:172.16.255.255  Mask:255.255.0.0

          inet6 addr: fe80::a00:27ff:fe23:4ddd/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 b)  TX bytes:888 (888.0 b)


eth2      Link encap:Ethernet  HWaddr 08:00:27:64:3D:21

          inet addr:10.0.4.15  Bcast:10.0.4.255  Mask:255.255.255.0

          inet6 addr: fe80::a00:27ff:fe64:3d21/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:1 errors:0 dropped:0 overruns:0 frame:0

          TX packets:11 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:590 (590.0 b)  TX bytes:1110 (1.0 KiB)


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:65536  Metric:1

          RX packets:8 errors:0 dropped:0 overruns:0 frame:0

          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:1091 (1.0 KiB)  TX bytes:1091 (1.0 KiB)



and here's my routing table:

[root@racattack1 ~]# route -n

Kernel IP routing table

Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface

10.0.4.0        0.0.0.0         255.255.255.0   U     0      0        0 eth2

169.254.0.0     0.0.0.0         255.255.0.0     U     1002   0        0 eth0

169.254.0.0     0.0.0.0         255.255.0.0     U     1003   0        0 eth1

169.254.0.0     0.0.0.0         255.255.0.0     U     1004   0        0 eth2

172.16.0.0      0.0.0.0         255.255.0.0     U     0      0        0 eth1

192.168.78.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0


(Those are both from the guest.)


-Mark


On Mon, Jul 14, 2014 at 12:07 PM, Chris Taylor <
christopherdtaylor1994@xxxxxxxxx> wrote:

> Can the guest just not RESOLVE DNS requests or can it not ping outside IP
> addresses at all?
>
> If it's a resolv issue, make sure you look at /etc/resolv.conf - also make
> sure PEERDNS=NO (I believe) in the ifcfg-eth device settings.
>
> If it can't even ping outside IP addresses, then its a routing problem and
> outside traffic is attempting an incorrect interface for outbound traffic.
>
> Chris
>
>
> On Mon, Jul 14, 2014 at 10:45 AM, Mark J. Bobak <mark@xxxxxxxxx> wrote:
>
>> Hi all,
>>
>> I'm working on setting up a two-node RAC, using the RAC Attack 12c guide.
>> (Virtual Box 4.3.12 on Mac OS X 10.9.4 running Oracle Linux 6.5 guests)
>>
>> I'm at the point where I've successfully built the first node, and set up
>> shared storage.
>>
>> I noticed that my guest, racattack1, can't see the Internet.  I thought
>> this should be possible through the NAT interface, on eth2, but it doesn't
>> seem to work.
>>
>> Can anyone offer me some advice?
>>
>> Thanks,
>>
>> -Mark
>>
>
>

Other related posts: