On Saturday, June 09, 2007 at 17:01:30 (+0200), Bernhard Schmidt wrote:
> test1.iks4.birkenwald.de has address 172.16.2.1
> test1.iks4.birkenwald.de has IPv6 address 2001:a60:f00c::1
>
> test2.iks4.birkenwald.de has address 192.168.100.1
> test2.iks4.birkenwald.de has IPv6 address 2001:a60:f00c::1
>
> test3.iks4.birkenwald.de has address 141.1.1.1
> test3.iks4.birkenwald.de has IPv6 address 2001:a60:f00c::1
>
> >>> socket.getaddrinfo('test1.iks4.birkenwald.de', 0, 0,
> socket.SOCK_STREAM)
> [(2, 1, 6, '', ('172.16.2.1', 0)), (10, 1, 6, '', ('2001:a60:f00c::1',
> 0, 0, 0))]
[...]
> 172.16.1.254 dev iks4 proto kernel scope link src 172.16.1.253
> 172.16.2.0/24 via 172.16.1.254 dev iks4
Eine meiner Kisten ist anderer Meinung:
[EMAIL PROTECTED]:~$ sudo ip route add 172.16.2.0/24 via 172.20.63.254 dev eth0
[EMAIL PROTECTED]:~$ sudo ip route
172.16.2.0/24 via 172.20.63.254 dev eth0
172.20.32.0/19 dev eth0 proto kernel scope link src 172.20.32.17
default via 172.20.63.254 dev eth0
[EMAIL PROTECTED]:~$ telnet test1.iks4.birkenwald.de www
Trying 2001:a60:f00c::1...
Trying 172.16.2.1...
[EMAIL PROTECTED]:~$ sudo ip route del 172.16.2.0/24 via 172.20.63.254 dev eth0
[EMAIL PROTECTED]:~$ telnet test2.iks4.birkenwald.de
Trying 2001:a60:f00c::1...
Trying 192.168.100.1...
telnet: Unable to connect to remote host: No route to host
[EMAIL PROTECTED]:~$ sudo ip route add 192.168.100.0/24 via 172.20.63.254 dev
eth0
[EMAIL PROTECTED]:~$ telnet test2.iks4.birkenwald.de
Trying 2001:a60:f00c::1...
Trying 192.168.100.1...
telnet: Unable to connect to remote host: No route to host
[EMAIL PROTECTED]:~$ dpkg -s libc6 | grep -E -e ^Version
Version: 2.3.6.ds1-13
telnet ist netkit-telnet und dürfte auch nur getaddrinfo() benutzen.
Marc
--
_ _ Marc A. Donges +49 721 6904-2130
'v' Klosterweg 28 / E110
/ \ 76131 Karlsruhe
W W http://www.hadiko.de/~marc/
--
ipv6 mailing list
[email protected]
http://listserv.uni-muenster.de/mailman/listinfo/ipv6
