OpenVZ Forum


Home » General » Support » *SOLVED* VEs with different subnets
Re: VEs with different subnets [message #14597 is a reply to message #14592] Tue, 03 July 2007 09:25 Go to previous messageGo to previous message
ugo123 is currently offline  ugo123
Messages: 22
Registered: June 2007
Junior Member
finist wrote on Tue, 03 July 2007 03:20

ugo123 wrote on Tue, 03 July 2007 00:13

Ok, now I remember why source routing wasn't working :

mercury:~# /sbin/ip rule add from 87.98.196.137 table 10
mercury:~# /sbin/ip route add default dev eth0 via 87.98.196.129 table 10
RTNETLINK answers: Network is unreachable
mercury:~#


This is simply means that Hardware Node does not know how to get to 87.98.196.129. Could you please try again with:

# ip route add 87.98.196.128/26 dev eth0
# ip rule add from 87.98.196.137 table 10
# ip route add default dev eth0 via 87.98.196.129 table 10

This should eliminate the "Network is unreachable" error.


Thanks.

Yes, that's what I've figured in my other message.... (and I forgot to mention that I've tried the ip route add 87.98.196.128/26 after some Google-ing).

But still it hasn't worked.... :/

And as I posted... I think that the problem is that the ISP's gateway is null-routing the packets coming from private subnets (martians IPs) as this is a common security rule.

Ugo

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: *RESOLVED* Solaris 10 Template
Next Topic: *BUG REPORTED* Migration problem with 2.6.18-028stab035
Goto Forum:
  


Current Time: Wed Aug 07 00:46:14 GMT 2024

Total time taken to generate the page: 0.03053 seconds