search for: advmss

...ving some problem with ipv6, looks like its bridge routing problem but stuck. here are my bridge detail: bridge name bridge id STP enabled interfaces br0 8000.000af75613f2 no eth1 vnet1 br4 8000.000af75613f0 no eth0 ip -6 route shows : unreachable ::/96 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295 unreachable ::ffff:0.0.0.0/96 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295 unreachable 2002:a00::/24 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295 unreachable 2002:7f00::/24 dev lo metric 1024 error -101 mtu 6553...

...ever seen it 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 sh...

...a 192.168.1.1 dev eth1 weight 1 nexthop via 192.168.254.254 dev eth2 weight 1 The problem is that load balancing isnt''t working :-/ root@enrutizador:~# for x in $(seq 1 10); do ip r g 130.206.1.$x; done 130.206.1.1 via 192.168.1.1 dev eth1 src 192.168.1.128 cache mtu 1500 advmss 1460 hoplimit 64 130.206.1.2 via 192.168.1.1 dev eth1 src 192.168.1.128 cache mtu 1500 advmss 1460 hoplimit 64 130.206.1.3 via 192.168.1.1 dev eth1 src 192.168.1.128 cache mtu 1500 advmss 1460 hoplimit 64 130.206.1.4 via 192.168.1.1 dev eth1 src 192.168.1.128 cache mtu 1500 advmss...

....2.11, and kernel 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...

...| +-------+ +-------+ A # ip r l 192.168.30.254 dev eth0 scope link 192.168.0.0/24 dev eth0 scope link 169.254.0.0/16 dev lo scope link 127.0.0.0/8 dev lo scope link # ip -6 r l 2020::254 dev eth0 metric 1024 mtu 1500 advmss 1440 3030::254 dev eth0 metric 1024 mtu 1500 advmss 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...

...28 default equalize nexthop via 192.168.254.254 dev eth2 weight 1 nexthop via 192.168.1.1 dev eth1 weight 1 The problem like sawar... root@enrutizador:~# for x in $(seq 1 10); do ip r g 130.206.1.$x; done 130.206.1.1 via 192.168.1.1 dev eth1 src 192.168.1.128 cache mtu 1500 advmss 1460 hoplimit 64 130.206.1.2 via 192.168.1.1 dev eth1 src 192.168.254.128 cache mtu 1500 advmss 1460 hoplimit 64 130.206.1.3 via 192.168.1.1 dev eth1 src 192.168.254.128 cache mtu 1500 advmss 1460 hoplimit 64 130.206.1.4 via 192.168.1.1 dev eth1 src 192.168.1.128 cache mtu 1500 ad...

...oute add 192.168.1.99 via 192.168.10.1 dev wlan0 table main ip route add 192.168.1.99 dev eth0 table Forw ip -statistics route flush cache ip route get 192.168.1.98 from 172.30.230.230 iif eth1 # 192.168.1.98 from 172.30.230.230 dev eth0 src 172.16.1.1 # cache <src-direct> mtu 1492 advmss 1452 fragtimeout 64 iif eth1 ip route get 192.168.1.99 from 172.30.230.230 iif eth1 # 192.168.1.99 from 172.30.230.230 dev eth0 src 172.16.1.1 # cache <src-direct> mtu 1492 advmss 1452 fragtimeout 64 iif eth1 ip route get 192.168.1.98 # 192.168.1.98 dev eth0 src 192.168.1.10 #...

Hello all, Yesterday I noticed that my system was "leaking" traffic towards the 10/8 network, I have shorewall installed on multiple machines ranging from single interface devices to ones with 10+ interfaces. I tested all the boxes and they are showing the same behavior. All systems are CentOS 3.4, 2.4.21-27.0.2.ELsmp. Shorewall version: 2.2.1 For the host mentioned is a single

...hop via 192.168.3.1 dev eth6 weight 1 root@server1:/backup/ftp# ip ro show cache | egrep ''eth4|eth5|eth6'' -B1 | tail -n20 201.216.128.100 from 192.168.90.5 via 192.168.3.1 dev eth6 src 192.168.90.1 -- 192.168.90.5 from 201.240.149.1 dev eth2 src 192.168.1.2 cache mtu 1500 advmss 1460 hoplimit 64 iif eth5 -- cache <src-direct> mtu 1500 advmss 1460 hoplimit 64 iif eth2 200.114.138.45 from 192.168.90.5 via 192.168.1.1 dev eth4 src 192.168.90.1 -- 192.168.90.5 from 200.74.39.52 dev eth2 src 192.168.1.2 cache mtu 1500 advmss 1460 hoplimit 64 iif eth5 71.80.214...

...ave thesame problem: some packets are sent with wrong src ip via interface via eth0 with 192.168.200.10 via eht1 with 80.48.56.70 but as I know they souldn''t I make simple test: lucy linux # ip ro ge 80.48.56.3 80.48.56.3 via 80.48.56.65 dev eth0 src 192.168.200.10 cache mtu 1500 advmss 1460 metric 10 128 lucy linux # ip ro ge 80.48.56.2 80.48.56.2 via 80.48.56.65 dev eth0 src 80.48.56.70 cache mtu 1500 advmss 1460 metric 10 128 lucy linux # ip ro ge 80.48.56.1 80.48.56.1 via 80.48.56.65 dev eth0 src 192.168.200.10 cache mtu 1500 advmss 1460 metric 10 128 lucy linux...

Dear List. I try to build multipath connection w/ load balance to internet with two different gateway; My system is RH-8.0 with iproute-2.4.7-7.90.1.rpm and Kernel-2.4.26 (patching with Julian A. patch),and follow guide from http://www.linuxvirtualserver.org/~julian/nano.txt, The problem is; when i try to connect to Internet form gateway machine it;s success , but only one interface is

...64 bytes from 2a00:1450:4016:800::1013: icmp_seq=0 ttl=57 time=91.2 ms 64 bytes from 2a00:1450:4016:800::1013: icmp_seq=1 ttl=57 time=95.3 ms These are the routing table entries added by my hand-added configuration: 2000::/3 via 2a02:418:6a04::1 dev eth0 metric 1 expires 21333054sec mtu 1500 advmss 1440 hoplimit 4294967295 default dev eth0 metric 1 expires 21333054sec mtu 1500 advmss 1440 hoplimit 4294967295 So... given the parameters set in my config files, why are the CentOS v5.8 initscripts not configuring my IPv6 routing correctly? One more thing. I get this output on network start...

...B |---- | | | | +-------+ +-------+ A *# ip r l* 192.168.30.254 dev eth0 scope link 192.168.0.0/24 dev eth0 scope link 169.254.0.0/16 dev lo scope link 127.0.0.0/8 dev lo scope link *# ip -6 r l* 2020::254 dev eth0 metric 1024 mtu 1500 advmss 1440 3030::254 dev eth0 metric 1024 mtu 1500 advmss 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...

...| ---- | | | | +-------+ +-------+ A # ip r l 192.168.30.254 dev eth0 scope link 192.168.0.0/24 dev eth0 scope link 169.254.0.0/16 dev lo scope link 127.0.0.0/8 dev lo scope link # ip -6 r l 2020::254 dev eth0 metric 1024 mtu 1500 advmss 1440 3030::254 dev eth0 metric 1024 mtu 1500 advmss 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...

...2 proto static \ nexthop via $GWE1 dev $IFE1 weight 1\ nexthop via $GWE2 dev $IFE2 weight 1 Now after traceroute failure, if i see the routing cache for that ip, it shows following, 205.158.62.141 via 203.88.135.213 dev eth1 src 203.88.135.212 cache mtu 1500 advmss 1460 205.158.62.141 from 192.168.1.51 via 203.88.135.205 dev eth2 src 192.168.1.242 cache <src-direct> mtu 1500 advmss 1460 iif eth0 please see eth1 and eth2 in both entries, now it does not forward this request, what can be the reason behind this and please can anyone suggest me the...

...151.99.0.100 --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

...when I restart network (service network restart) I get: Bringing up interface eth0: WARN : [ipv6_add_route] Unknown error [ OK ] and ip -6 route show dev eth0 generates: 2607:f4b8:3:1::/64 metric 256 expires 21333899sec mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 metric 256 expires 21333899sec mtu 1500 advmss 1440 hoplimit 4294967295 What is missing? I am using http://www.tldp.org/HOWTO/Linux+IPv6-HOWTO/ for some help.

....1 when i look into these packets, there is another icmp redirect with : 0.0.0.0 -> 0.0.0.0 i''ve check many things, the most imports: # ip r g 152.66.235.8 from 157.181.96.1 iif eth0 152.66.235.8 from 157.181.96.1 dev eth0 src 10.0.0.2 cache <src-direct,redirect> mtu 1500 advmss 1460 hoplimit 64 iif eth0 # ip r g 152.66.235.1 152.66.235.1 dev eth0 src 10.0.0.2 cache mtu 1500 advmss 1460 hoplimit 64 i think it should work... our firewall is acting as an arp-proxy on our network, it does some packet filtering and traffic accounting, nothing unusual it runs 2.6.11.8,...

...ip route add default table 222 proto static \ nexthop via $GWE1 dev $IFE1 weight 1\ nexthop via $GWE2 dev $IFE2 weight 1 if i see the routing cache for that ip, shows following, 205.158.62.141 via 203.88.135.213 dev eth1 src 203.88.135.212 cache mtu 1500 advmss 1460 205.158.62.141 from 192.168.1.51 via 203.88.135.205 dev eth2 src 192.168.1.242 cache <src-direct> mtu 1500 advmss 1460 iif eth0 please see eth1 and eth2 in both entries, what can be the reason behind this, thanx in advance, Regards, senthil

...fault via 192.168.2.254 dev eth2 root@ubuntu:~# uname -a Linux ubuntu 2.6.15-23-386 #1 PREEMPT Tue May 23 13:49:40 UTC 2006 i686 GNU/Linux root@ubuntu:~# ip -V ip utility, iproute2-ss041019 root@ubuntu:~# ip route get 1.2.3.1 1.2.3.1 via 192.168.2.254 dev eth2 src 192.168.1.1 cache mtu 1500 advmss 1460 hoplimit 64 root@ubuntu:~# ip route get 1.2.3.2 1.2.3.2 via 192.168.2.254 dev eth2 src 192.168.2.1 cache mtu 1500 advmss 1460 hoplimit 64 As you can see, the "ip route get" always returns ".. via 192.168.2.254 dev eth2 ..." and only switches the source ip but not the...