|
Roberto Nibali wrote:
>>> Using tcpdump:
>>>
>>> 1. I see the request arriving on the real server over the tunnel
>>> link. 2. On the real server I see the response being sent.
>
> Do you by any chance see the response passing by the director?
No, on the director I only see the request.
>> I'm not sure exactly what this is indicative of, but:
>>
>> On the real server -
>>
>> "traceroute -S <VIP> <client>" - nothing comes through. Does this
>> mean there's a router config problem, i.e. a router is not letting
>> those packets through due to the source address?
>
> What's your routing entries? ip rule show, ip route show? What does an
> ip route get <client> from <VIP> show you?
On the director: (presumably not interesting)
# ip route get 217.8.220.94 from 88.198.198.122
217.8.220.94 from 88.198.198.122 via 88.198.41.97 dev eth1
cache mtu 1500 advmss 1460 fragtimeout 64
On the real server:
# ip route get 217.8.220.94 from 88.198.198.122
217.8.220.94 from 88.198.198.122 via 88.198.7.129 dev eth1
cache mtu 1500 advmss 1460 fragtimeout 64
# ip rule show
0: from all lookup local
32766: from all lookup main
32767: from all lookup default
# ip route show
88.198.7.128/27 dev eth1 proto kernel scope link src 88.198.7.133
169.254.0.0/16 dev eth1 scope link
127.0.0.0/8 dev lo scope link
default via 88.198.7.129 dev eth1
> Where about in Zürich are you?
We're in Herrliberg, about 25mins south on the Goldcoast.
> Cheers,
> Roberto Nibali, ratz (in Altstetten right now)
Ah, I suspect I know who you are working for :-)
/Per Jessen, Zürich
|
