Skip to Content.
Sympa Menu

cacert-sysadm - Re: [Visit BIT][12.12.2013] visit scheduled / no access

cacert-sysadm AT lists.cacert.org

Subject: CAcert System Admins discussion list

List archive

Re: [Visit BIT][12.12.2013] visit scheduled / no access


Chronological Thread 
  • From: "Martin Gummi (CAcert.org)" <martin.gummi AT cacert.org>
  • To: cacert-sysadm AT lists.cacert.org, Wytze van der Raay <wytze AT cacert.org>
  • Subject: Re: [Visit BIT][12.12.2013] visit scheduled / no access
  • Date: Fri, 13 Dec 2013 16:42:22 +0100
  • Organization: CAcert.org

Hello,

- External no web access

cacert.eu 213.154.225.242
monitor.cacert.org 213.154.225.230 no ssh access
svn.cacert.org 213.154.225.238

- Internal

Debian update
ftp.nluug.nl 192.87.102.42 + IPv6 HTTP(80) not works
security.debian.org 195.20.242.89 HTTP(80) not works

Email from wiki.c.o to emailout.intra.c.o I get no mails on my account
from wiki
postfix restart on wiki I can send out to emailout.intra.c.o

Blog I have some errors on admin Dashboard external infos from RSS feeds

--
mit freundlichen Grüßen / best regards
Martin Gummi


On 13.12.2013 16:24, Mario Lipinski wrote:
> I already cared about resolv.conf incl. necessary firewall changes.
>
> Wytze van der Raay
> <wytze AT cacert.org>
> schrieb:
>
> Hi Jan,
>
> On 13.12.2013 12:30, Jan Dittberner wrote:
>
> ...
> thanks for all the work. It seems like at least some services on
> Infra01 are
> not reachable yet. I tried to reach svn and monitor without
> success. Did
> something change that will require changes on the local
> Firewall/network
> configuration on Infra01?
>
>
> There are still some issues with the new firewall setup. The intention
> is
> that no changes should be necessary on infra01. I've found one
> exception to
> that so far: in /etc/resolv.conf, you should update the name server ip.
> The available name servers are now 172.16.2.2 <http://172.16.2.2> and
> 172.16.2.3 <http://172.16.2.3>.
>
> Previously dedicated addresses in the 172.16.2.* subnet where
> routed to
> infra01 and have been NATed to internal 10.* addresses for the
> containers.
> Are the 172.16.2.* addresses still routed to infra01?
>
>
> Yes, that hasn't changed. I am trying to figure out why svn isn't
> working
> at the moment.
>
> Regards,
> -- wytze
>
>
> --
> Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail
> gesendet.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature




Archive powered by MHonArc 2.6.18.

Top of Page