search for: metric10

...ernel 2.6.11-gentoo-r11. Exactly same happened with kernel 2.4.28-gentoo. :( For example, here is a test. I want to ftp to "ftp.rediris.es". I look which would be the route: # ip route get 130.206.1.5 130.206.1.5 via 192.168.17.2 dev eth2 src 192.168.17.1 cache mtu 1500 advmss 1460 metric10 64 I try the ftp: # ftp ftp.rediris.es And in the kernel log appears: Jul 4 16:19:25 thecrow WRONG IFACE: IN= OUT=eth1 SRC=192.168.17.1 DST=130.206.1.5 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=43245 DF PROTO=TCP SPT=49828 DPT=21 WINDOW=5840 RES=0x00 SYN URGP=0 Output to bash "for X in `seq 10` ;...

...use both gateway''s. Possible symptom I''ve noticed is that in the route cache, there tends to be 2 entries, with the used gateway showing up first, such as: 83.53.46.36 from 192.168.0.128 via 10.9.44.15 dev ppp0 src 192.168.0.1 cache <src-direct> mtu 1492 advmss 1452 metric10 64 iif eth0 83.53.46.36 from 192.168.0.128 via 66.189.76.1 dev eth1 src 192.168.0.1 cache <src-direct> mtu 1500 advmss 1460 metric10 64 iif eth0 In this case, ppp0 was listed as the second nexthop. If I reversed the order of the nexthop''s, then the order they show up in the c...

...--dport 53 -j SNAT --to-source 81.77.88.99 Looking inside the cache I find only the route to reach the dns server, but not the one that the dns needs to reach my server: 151.99.0.100 from 192.168.1.2 via 81.77.88.100 dev eth2 src 192.168.1.249 cache <src-direct> mtu 1500 advmss 1460 metric10 64 iif eth0 I experieced in the past that reentering the iptables nat command worked, but it seems a random effect and not always works. Thank''s in advance, Luca Maragnani

...s 1440 (...plus link local and multicast routes) B # ip r l 127.0.0.1 dev lo scope link 192.168.0.0/24 dev eth3 proto kernel scope link src 192.168.0.254 192.168.30.0/24 dev eth1 proto kernel scope link src 192.168.30.254 # ip -6 r l 2020::2 dev eth3 metric 1024 mtu 1500 advmss 1440 metric10 64 (...plus link local and multicast routes) # cat /proc/sys/net/ipv4/ip_forward 1 #cat /proc/sys/net/ipv6/conf/all/forwarding 1 The problem is that i can ping 192.168.30.254 from A, but i can''t ping 3030::254 from A, anyone has a clue why this happens? Is there any feature i need to...

...0 (...plus link local and multicast routes) B *# ip r l* 127.0.0.1 dev lo scope link 192.168.0.0/24 dev eth3 proto kernel scope link src 192.168.0.254 192.168.30.0/24 dev eth1 proto kernel scope link src 192.168.30.254 *# ip -6 r l* 2020::2 dev eth3 metric 1024 mtu 1500 advmss 1440 metric10 64 (...plus link local and multicast routes) *# cat /proc/sys/net/ipv4/ip_forward* 1 *#cat /proc/sys/net/ipv6/conf/all/forwarding* 1 *The problem is that i can ping 192.168.30.254 from A, but i can''t ping 3030::254 from A, anyone has a clue why this happens? Is there any feature i nee...

...s 1440 (...plus link local and multicast routes) B # ip r l 127.0.0.1 dev lo scope link 192.168.0.0/24 dev eth3 proto kernel scope link src 192.168.0.254 192.168.30.0/24 dev eth1 proto kernel scope link src 192.168.30.254 # ip -6 r l 2020::2 dev eth3 metric 1024 mtu 1500 advmss 1440 metric10 64 (...plus link local and multicast routes) # cat /proc/sys/net/ipv4/ip_forward 1 #cat /proc/sys/net/ipv6/conf/all/forwarding 1 The problem is that i can ping 192.168.30.254 from A, but i can''t ping 3030::254 from A, anyone has a clue why this happens? Is there any feature i need to tu...

Hi all, I have a similar question like many asked before I know but Please help as i cant figure out where the problem is and how should I tackle. I have 2 ISP connections. I want to share the bandwidth from both. I have copied the script from many places and created my own after changes. Problem is that only one connection is utilized at a time. Not both working. ratio of consuming