Re: route question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Greetings Jerry,

On 5/14/2010 3:45 PM, Jerry Geis wrote:
>> What exactly does not work?  Connecting to what destination IP?  Your
>> default route is pointing out eth2.  So any traffic to a non-directly
>> connected network will go out eth2.  (without some additional static
>> routes)  What are you trying to accomplish?
>>
>>      
> I am attempting to have one box with 3 nic's and use NAT to connect to
> other boxes.
>
> 74.X is eth1 24.X is eth2 and 192.X is eth0
> I have iptable rules for 24.X:25 to goto 192.X:25 and port 80 also.
> This works
> I have iptable ruls for 74.X:25 to goto 192.X:25 and port 80 also. This
> does not work.
>
> the default route is set for 24.X network and it seems like that is why
> that network is working.
> If I change the default route to 74.X then the 74.X network works and
> the 24.X network stops working.
>
> So that is why I thought the "route -n" showing 0.0.0.0 for the gw on
> 74.X was perhaps the issue.
>
> I dont seem to be routing for both networks.
>
> THanks,
>
> Jerry
>    

Since you're routing --- what shows with 'cat 
/proc/sys/net/ipv4/ip_forward'?  If this is 0, I believe you will need 
to 'echo 1 > /proc/sys/net/ipv4/ip_forward' to enable this bit since you 
are requesting traffic to enter one interface and forward through to 
another interface.

Given:
192.x is eth0 / private
24.x is eth2 / public / services smtp and http function
74.x is eth1 / public / services smtp and http does not function

---Does smtp and http function from your 192.x address space?

---If you compare the output of 'netstat -an' is your smtp and http 
server ONLY listening on 24.x:25 and 24.x:80?

---Previously you supplied a route table of:

  route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
24.123.23.168   0.0.0.0         255.255.255.248 U     0      0        0 eth2
74.223.8.176    0.0.0.0         255.255.255.240 U     0      0        0 eth1
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth2
0.0.0.0         24.123.23.169   0.0.0.0         UG    0      0        0 eth2

------

Your route table is pushing 74.223.8.176 THROUGH 0.0.0.0 which is 24.123.23.169.  Unless your two providers advertise both networks, you'll need to add a new route for your 74.x provider.  Try from the command line adding a new default gw -- 'route add default gw 74.x dev eth1'.  When you run 'route -n' again you should find two default routes --
0.0.0.0         24.123.23.169   0.0.0.0         UG    0      0        0 eth2
0.0.0.0         74.x   0.0.0.0         UG    0      0        0 eth1

^^^ The above might help but you will have two equal cost routes which might actually slow your network down for outbound traffic so I would play with metrics also.

Hope this helps!

Bests,
Christopher Davis











_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos

[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux