Re: [Toolserver-l] Ipv6 issues (fwd)

2013-04-07 Thread Platonides
On 07/04/13 09:28, Marlen Caemmerer wrote:
> Sorry, seems I used the wrong sender address...
> 
> -- Forwarded message --
> Date: Sat, 6 Apr 2013 23:59:12
> From: Marlen Caemmerer 
> To: Wikimedia Toolserver 
> Subject: Re: [Toolserver-l] Ipv6 issues
> 
> Hey,
> 
> On Sat, 6 Apr 2013, Merlissimo wrote:
> 
>>
>> I think nosy needs some sleep because she hasn't slept last night.
>>
>> "getent ipnodes willow" does not return the ipv6 address configured at
>> /etc/hostname6.bnx0
> 
> Well...
> rnosy@hemlock:~$ host willow
> willow.toolserver.org has address 185.15.59.202
> willow.toolserver.org has IPv6 address 2a02:ec80:101::2:4
> rnosy@hemlock:~$ host 2a02:ec80:101::2:4
> 4.0.0.0.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.0.1.0.0.8.c.e.2.0.a.2.ip6.arpa
> domain name pointer willow.toolserver.org.
> 
> 
> root@willow:~# ifconfig -a
> lo0: flags=2001000849 mtu
> 8232 index 1
> inet 127.0.0.1 netmask ff00
> bnx0: flags=1000843 mtu 1500 index 2
> inet 185.15.59.202 netmask ffc0 broadcast 185.15.59.255
> ether 0:1d:9:71:74:cb
> lo0: flags=2002000849 mtu
> 8252 index 1
> inet6 ::1/128
> bnx0: flags=2000841 mtu 1500 index 2
> inet6 fe80::21d:9ff:fe71:74cb/10
> ether 0:1d:9:71:74:cb
> bnx0:1: flags=2000841 mtu 1500 index 2
> inet6 2a02:ec80:101::2:4/64

It gives a different output for root? :S

platonides@willow ~ $ ifconfig -a
lo0: flags=2001000849 mtu
8232 index 1
inet 127.0.0.1 netmask ff00
bnx0: flags=1000843 mtu 1500 index 2
inet 185.15.59.202 netmask ffc0 broadcast 185.15.59.255
lo0: flags=2002000849 mtu
8252 index 1
inet6 ::1/128
bnx0: flags=2000841 mtu 1500 index 2
inet6 fe80::21d:9ff:fe71:74cb/10
bnx0:1: flags=2000841 mtu 1500 index 2
inet6 2a02:ec80:101::2:4/64
bnx0:2: flags=20a0841 mtu
1500 index 2
inet6 subnet 2620:0:862:101::/64
bnx0:3: flags=20a0841 mtu
1500 index 2
inet6 subnet 2a02:ec80:101::/64
bnx0:4: flags=2000840 mtu 1500 index 2
inet6 2a02:ec80:101::2:4/64
bnx0:5: flags=2000840 mtu 1500 index 2
inet6 2a02:ec80:101::2:4/64
bnx0:6: flags=2000840 mtu 1500 index 2
inet6 2a02:ec80:101::2:4/64
bnx0:7: flags=2000840 mtu 1500 index 2
inet6 2a02:ec80:101::2:4/64
bnx0:8: flags=2000840 mtu 1500 index 2
inet6 2a02:ec80:101::2:4/64


(bnx0:1,3,4,5,6,7,8 have 2a02:ec80:101::2:4, bnx0:2 2620:0:862:101::)

It looks a problem with the routes:
platonides@willow ~ $ route  get -inet wikimedia.org
   route to: wikimedia-lb.pmtpa.wikimedia.org
destination: default
   mask: default
gateway: vl102-ve6.csw1-esams.wikimedia.org
  interface: bnx0
  flags: 
  recvpipe  sendpipe  ssthreshrtt,ms rttvar,ms  hopcount  mtu
  expire
0 0 0 0 0 0  1500
  0


(correct, it's the same gateway as the linux servers)

platonides@willow ~ $ route  get -inet6 wikimedia.org
   route to: wikimedia-lb.pmtpa.wikimedia.org
destination: default
   mask: default
gateway: fe80::20c:dbff:fefc:b00
  interface: bnx0
  flags: 
 recvpipe  sendpipe  ssthreshrtt,ms rttvar,ms  hopcount  mtu
 expire
0 0 0 0 0 0  1500
  0

fe80::/10 are link local addresses. I expect that the geteway would be
2a02:ec80:101::1 per teh output of the route to be applied on reboot:
platonides@willow ~ $ route  -p show
persistent: route add -inet6 default 2a02:ec80:101::1

2a02:ec80:101::1 and fe80::20c:dbff:fefc:b00 appear to be different
hosts. Although the later does seem to belong to a router, as it runs
RomSShell_4.61 [1]


As a workaround, a bit of googling suggests that writing
DEFAULT_IP=IP_VERSION4 into /etc/default/inet_type should disable ipv6.
Unplumbing the inet6 interfaces should also leave with a working ipv4
system until it is fixed.

Cheers

1- http://www.allegrosoft.com/embedded-ssh-client-server

___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list: 
https://wiki.toolserver.org/view/Mailing_list_etiquette

Re: [Toolserver-l] Ipv6 issues (fwd)

2013-04-07 Thread Marlen Caemmerer

Sorry, seems I used the wrong sender address...


-- Forwarded message --
Date: Sat, 6 Apr 2013 23:59:12
From: Marlen Caemmerer 
To: Wikimedia Toolserver 
Subject: Re: [Toolserver-l] Ipv6 issues

Hey,


On Sat, 6 Apr 2013, Merlissimo wrote:



I think nosy needs some sleep because she hasn't slept last night.

"getent ipnodes willow" does not return the ipv6 address configured at 
/etc/hostname6.bnx0


Well...
rnosy@hemlock:~$ host willow
willow.toolserver.org has address 185.15.59.202
willow.toolserver.org has IPv6 address 2a02:ec80:101::2:4
rnosy@hemlock:~$ host 2a02:ec80:101::2:4
4.0.0.0.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.0.1.0.0.8.c.e.2.0.a.2.ip6.arpa domain 
name pointer willow.toolserver.org.



root@willow:~# ifconfig -a
lo0: flags=2001000849 mtu 8232 
index 1

inet 127.0.0.1 netmask ff00
bnx0: flags=1000843 mtu 1500 index 2
inet 185.15.59.202 netmask ffc0 broadcast 185.15.59.255
ether 0:1d:9:71:74:cb
lo0: flags=2002000849 mtu 8252 
index 1

inet6 ::1/128
bnx0: flags=2000841 mtu 1500 index 2
inet6 fe80::21d:9ff:fe71:74cb/10
ether 0:1d:9:71:74:cb
bnx0:1: flags=2000841 mtu 1500 index 2
inet6 2a02:ec80:101::2:4/64



root@willow:~# host willow
willow.toolserver.org has address 185.15.59.202
willow.toolserver.org has IPv6 address 2a02:ec80:101::2:4
root@willow:~# host 2a02:ec80:101::2:4
4.0.0.0.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.0.1.0.0.8.c.e.2.0.a.2.ip6.arpa domain 
name pointer willow.toolserver.org.



I dont see any problem there.

Do you?


So record is missing at dns. If dns cannot be changed ipv6 address must be 
added to /etc/inet/ipnodes (which is always a good idea if dns is not 100% 
reliable). /usr/lib/inet/in.ndpd is running.




ifconfig -a6 shows that the ip address is configured three times as local 
interface for the same physical interface. Is this expected? And physical 
interface bnx0 is associated with a link local address only. This shows that 
the router is not propagating the site prefix. So you must change the router 
config or add the site prefix locally. Maybe interfaces were not plumbed.




I'd really like to reboot tomorrow. Everytime I do what is the equivalent to 
/etc/init.d/networking restart it adds an interface with the v6 address.


The next try from my side would be to switch back to the old v6 range to see if 
the problems all go away. I currently cant reach even from the same network.


root@willow:~# ping 2a02:ec80:101:301::2:2

^C

Solaris is not my home base system but I only changed the prefixes in the 
config files so it should work as it did before.


Lets see how this goes tomorrow after some sleep.

Cheers
Marlen/nosy


___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list: 
https://wiki.toolserver.org/view/Mailing_list_etiquette

Re: [Toolserver-l] Ipv6 issues

2013-04-06 Thread Merlissimo

Am 06.04.2013 21:27, schrieb DaB.:

Hello,
At Saturday 06 April 2013 21:22:53 DaB. wrote:

Looks like ipv6 is broken at Willow and maybe at more servers. That
probably explains some of the problems we seem to be having right now.


AFAIS willow can not reached by IPv6 and can't reach anything with IPv6
itself. AFAIS it is not a firewall-issue. My experince with ipv6 at Solaris is
very limited so I would prefer that Nosy takes a look first.
Use one of the linux-host for bots as workaround if possible.


I think nosy needs some sleep because she hasn't slept last night.

"getent ipnodes willow" does not return the ipv6 address configured at 
/etc/hostname6.bnx0
So record is missing at dns. If dns cannot be changed ipv6 address must 
be added to /etc/inet/ipnodes (which is always a good idea if dns is not 
100% reliable). /usr/lib/inet/in.ndpd is running.


ifconfig -a6 shows that the ip address is configured three times as 
local interface for the same physical interface. Is this expected? And 
physical interface bnx0 is associated with a link local address only. 
This shows that the router is not propagating the site prefix. So you 
must change the router config or add the site prefix locally. Maybe 
interfaces were not plumbed.


If you cannot found the reason you could create a 6to4 tunnel ;-).

Just some ideas.

Merlissimo

___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list: 
https://wiki.toolserver.org/view/Mailing_list_etiquette

Re: [Toolserver-l] Ipv6 issues

2013-04-06 Thread Marlen Caemmerer

Hello,


On Sat, 6 Apr 2013, Maarten Dammers wrote:


Op 6-4-2013 16:05, John schreef:
I know we had maintenance about 12 hours ago, but I am unable to 
launch any of a half dozen IRC bots, reba and other toolserver IRC 
bots seem to be having similar issues.

multichill@willow:~$ ping chat.freenode.net
no answer from chat.freenode.net

multichill@willow:~$ ping -A inet chat.freenode.net
chat.freenode.net is alive



do you have any idea if this problem occured after the last maintenance or the 
one before?
I'd guess the latter but I have no proof.

Cheers
Marlen/nosy

___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list: 
https://wiki.toolserver.org/view/Mailing_list_etiquette

Re: [Toolserver-l] Ipv6 issues

2013-04-06 Thread DaB.
Hello,
At Saturday 06 April 2013 21:22:53 DaB. wrote:
> Looks like ipv6 is broken at Willow and maybe at more servers. That 
> probably explains some of the problems we seem to be having right now.

AFAIS willow can not reached by IPv6 and can't reach anything with IPv6 
itself. AFAIS it is not a firewall-issue. My experince with ipv6 at Solaris is 
very limited so I would prefer that Nosy takes a look first.
Use one of the linux-host for bots as workaround if possible.

Sincerely,
DaB.

-- 
Userpage: [[:w:de:User:DaB.]] — PGP: 0x2d3ee2d42b255885


signature.asc
Description: This is a digitally signed message part.
___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list: 
https://wiki.toolserver.org/view/Mailing_list_etiquette

[Toolserver-l] Ipv6 issues

2013-04-06 Thread Maarten Dammers

Hi everyone,

Op 6-4-2013 16:05, John schreef:
I know we had maintenance about 12 hours ago, but I am unable to 
launch any of a half dozen IRC bots, reba and other toolserver IRC 
bots seem to be having similar issues.

multichill@willow:~$ ping chat.freenode.net
no answer from chat.freenode.net

multichill@willow:~$ ping -A inet chat.freenode.net
chat.freenode.net is alive

Looks like ipv6 is broken at Willow and maybe at more servers. That 
probably explains some of the problems we seem to be having right now.


Maarten


___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list: 
https://wiki.toolserver.org/view/Mailing_list_etiquette

Re: [Toolserver-l] IPv6

2011-05-30 Thread Maarten Dammers
Op 29-5-2011 16:59, DaB. schreef:
> Hello all,
> At Sunday 29 May 2011 16:59:20 DaB. wrote:
>> deployment of IPv6 at the Toolserver
> great to have them back :-).
Just in time for http://isoc.org/wp/worldipv6day/ ;-)

Maarten


___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list: 
https://wiki.toolserver.org/view/Mailing_list_etiquette


Re: [Toolserver-l] IPv6

2011-05-29 Thread DaB.
Hello all,
At Sunday 29 May 2011 16:59:20 DaB. wrote:
> deployment of IPv6 at the Toolserver

great to have them back :-).

Sincerly,
DaB.

-- 
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885


signature.asc
Description: This is a digitally signed message part.
___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list: 
https://wiki.toolserver.org/view/Mailing_list_etiquette

[Toolserver-l] IPv6

2011-05-28 Thread River Tarnell
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

During the next maintenance window I plan to start the (somewhat 
overdue) deployment of IPv6 at the Toolserver.  In preparation for this, 
I will be adding IPv6 addresses to all hosts today.  

I don't expect this to cause any problems for users, except that the IP 
address for willow (which already has one) will change.  I will leave 
the old IP in place until everything has migrated, but the new IP will 
be used for outgoing connections.

- river.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (SunOS)

iEYEARECAAYFAk3h5w4ACgkQIXd7fCuc5vIc4QCggvuH0CpZ1scPjb82g8xjxcmX
IkoAoK8xKuYW2WO8Zqv4T8qUbamZPAvQ
=c2zi
-END PGP SIGNATURE-

___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list: 
https://wiki.toolserver.org/view/Mailing_list_etiquette


[Toolserver-l] IPv6 issues

2009-04-16 Thread River Tarnell
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

hi,

due to some unknown issue at esams, IPv6 connectivity is non-functional.  i
have removed  records from DNS until the problem is resolved.

- river.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (HP-UX)

iEYEARECAAYFAknm7M4ACgkQIXd7fCuc5vKUGwCfa8UQYzG44U2fvuL71Genc0qB
+e0AniGGdnv7c1USP5idUKzOLViVWGVl
=EoBU
-END PGP SIGNATURE-

___
Toolserver-l mailing list
Toolserver-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/toolserver-l


[Toolserver-l] IPv6 on stable - thank you

2009-01-01 Thread Marcin Cieslak
Hi,

Big thank you for providing IPv6 for the stable toolserver.

I think I was using it unknowingly since around Dec 14th, excellent idea 
- so thanks again.

--Marcin


___
Toolserver-l mailing list
Toolserver-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/toolserver-l