On Fri, 2 Sep 2005, lonely wolf wrote:
> [EMAIL PROTECTED] wrote:
>
>>
>>
>> On Fri, 2 Sep 2005, Tarhon-Onu Victor wrote:
>>
>>> On Fri, 2 Sep 2005, [EMAIL PROTECTED] wrote:
>>>
>>>> uitasem sa dau si asta
>>>
>>>
>>> Nu mai inteleg nici asta:
>>>
>>> [EMAIL PROTECTED] ~]$ ip route li
>>> <snip>
>>> adresa_ip_astral via gw_astral dev eth1 table astral
>>> <endsnip>
>>>
>>> Ma rog, tot ce trebuie sa faci tu este:
>>>
>>> ip rule add from ip_astral table astral
>>> ip route add default via gw_astral table astral
>>>
>>> Atit si nimic mai mult. ++sa verifici sa nu ai trasnai prin firewall,
>>> sau nu cumva sa faci nat la acel ip cu alte ip-uri.
>>
>>
>>
>> deci:
>>
>> [EMAIL PROTECTED] ~]$ ip rule add from 82.208.175.94 table astral
>> [EMAIL PROTECTED] ~]$ ip rule li
>> 0: from all lookup local
>> 32765: from 82.208.175.94 lookup astral
>> 32766: from all lookup main
>> 32767: from all lookup default
>> [EMAIL PROTECTED] ~]$ ip route add default via 82.208.175.65 table astral
>> [EMAIL PROTECTED] ~]$ ip ro li table astral
>> default via 82.208.175.65 dev eth1
>> [EMAIL PROTECTED] ~]$ ip route li |grep 82.208.175.
>> 82.208.175.64/27 dev eth1 proto kernel scope link
>> [EMAIL PROTECTED] ~]$
>> [EMAIL PROTECTED] ~]$ traceroute -i eth1 k.ro
>> traceroute to www.k.ro (194.102.255.23), 30 hops max, 40 byte packets
>>
> foloseste cu incredere ip route get ca sa afli cum sint rutele vazute de
> kernel.
> # ip route get `host www.k.ro|cut -f 4 -d ' '`
> 194.102.255.23 via 82.208.174.129 dev eth3 src xyz.xyz.xyz.xyz
> cache mtu 1500 advmss 1460 metric10 64
>
> daca nu le vede cum crezi tu ca ar trebui sa fie, ai gresit la ip route/rule
> daca da, ai gresit la firewall/NAT
>
[EMAIL PROTECTED] ~]$ ip route get 194.102.255.23 from 82.208.175.94
194.102.255.23 from 82.208.175.94 via 82.208.175.65 dev eth1
cache mtu 1500 advmss 1460 metric10 64
idiotul vede routa. de ce naiba nu merge si cand dau un amarat de trace?
