Re: ifconfig lo1 down

2011-03-06 Thread Bjoern A. Zeeb
On Sun, 6 Mar 2011, fredrik danerklint wrote: It's new-arp fallout and related to the carp problems with IPv6. ok. where can I read about this problem with carp (since that is what I also gonna to use later on with ip6..) kern/153848 or ther last weeks on this list. Is there any kind of i

Re: ifconfig lo1 down

2011-03-06 Thread fredrik danerklint
> >>> PING6(56=40+8+8 bytes) 2a03:::::xx02 --> > >>> 2a03:::::xx02 16 bytes from 2a03:::::xx02, > >>> icmp_seq=0 hlim=64 time=0.053 ms 16 bytes from > >>> 2a03:::::xx02, icmp_seq=1 hlim=64 time=0.032

Re: ifconfig lo1 down

2011-03-06 Thread Bjoern A. Zeeb
^C Now we run this command: # ifconfig lo1 down and trying to ping again: $ ping xx.xx.xx.2 PING xx.xx.xx.2 (xx.xx.xx.2): 56 data bytes ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ^C --- xx.xx.xx.2 ping statistics --- 3 packets transmitted, 0 pack

Re: ifconfig lo1 down

2011-03-06 Thread Julian Elischer
:::xx02 --> 2a03:::::xx02 16 bytes from 2a03:::::xx02, icmp_seq=0 hlim=64 time=0.053 ms 16 bytes from 2a03:::::xx02, icmp_seq=1 hlim=64 time=0.032 ms ^C Now we run this command: # ifconfig lo1 down and trying to ping again: $ ping xx.xx.xx.2 PING xx.xx.x

Re: ifconfig lo1 down

2011-03-06 Thread fredrik danerklint
x:::xx02 --> > > 2a03:::::xx02 16 bytes from 2a03:::::xx02, > > icmp_seq=0 hlim=64 time=0.053 ms 16 bytes from > > 2a03:::::xx02, icmp_seq=1 hlim=64 time=0.032 ms ^C > > > > Now we run this command: > > > > # ifcon

Re: ifconfig lo1 down

2011-03-05 Thread Sergey Kandaurov
^C > > and > > $ ping6 2a03:::::xx02 > PING6(56=40+8+8 bytes) 2a03:::::xx02 --> 2a03:::::xx02 > 16 bytes from 2a03:::::xx02, icmp_seq=0 hlim=64 time=0.053 ms > 16 bytes from 2a03::::xxxx:xx02, icmp_seq=1 hlim=64 time=0.0

ifconfig lo1 down

2011-03-05 Thread fredrik danerklint
tes from 2a03:::::xx02, icmp_seq=0 hlim=64 time=0.053 ms 16 bytes from 2a03:::::xx02, icmp_seq=1 hlim=64 time=0.032 ms ^C Now we run this command: # ifconfig lo1 down and trying to ping again: $ ping xx.xx.xx.2 PING xx.xx.xx.2 (xx.xx.xx.2):