cred ca ar ajuta si # ip route flush cache traceroute ala nu ar trebui sa plece prin rds? ca doar aia e ruta default...
Monday, September 5, 2005, 10:44:07 AM, you wrote: > On 9/2/05, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> wrote: >> datele problemei: >> >> 2 provideri, unul este rds unul astral, nu ca ar avea treaba denumirea. >> 2 interfete de retea in server. >> 1 bucata squid. >> >> ce am facut: >> >> [EMAIL PROTECTED] ~]$ cat /etc/iproute2/rt_tables >> # >> # reserved values >> # >> 255 local >> 254 main >> 253 default >> 0 unspec >> # >> # local >> # >> #1 inr.ruhep >> 100 astral >> >> [EMAIL PROTECTED] ~]$ ip route li >> <snip> >> adresa_ip_astral via gw_astral dev eth1 table astral >> <endsnip> >> >> [EMAIL PROTECTED] ~]$ ip route li table astral >> default via gw_astral dev eth1 >> >> >> ruta default e pe rds si as vrea sa ramana asa. >> pe adresa ip alocata de astral am bindat un server de proxy >> >> >> cand dau >> [EMAIL PROTECTED] ~]$ traceroute -s adresa_ip_astral k.ro >> traceroute to www.k.ro (194.102.255.23) from adresa_ip_astral, 30 hops >> max, >> 40 byte packets >> >> >> nu se duce nici mort, rezultatul fiind >> >> 1 * * * >> 2 * pitesti-bb1-ge0-1.rdsnet.ro (62.231.100.161) 10.919 ms 9.249 ms >> 3 bucuresti-bb3-ge0-1-v93.rdsnet.ro (193.231.253.130) 9.799 ms 10.477 >> ms 9.493 ms >> 4 buh1-xr1-vl2.rdsnet.ro (193.231.191.36) 10.448 ms 10.131 ms * >> 5 * xcr1-vl64.b.astralnet.ro (83.103.173.6) 10.405 ms * >> 6 www.k.ro (194.102.255.23) 9.855 ms >> >> adica tot via rds. >> >> unde gresesc? >> >> multumesc >> > Daca te tot joci cu rules si routes, e posibil sa-ti apara delay-uri > semnificative (cateva minute) pana la "activarea" modificarilor. Solutia e echo "1" >> /proc/sys/net/ipv4/route/flush. -- Best regards, Ionut mailto:[EMAIL PROTECTED]
