search for: 3c01

...p6tables -L -v -n") on my Fremont server and still can't traceroute6 or ping6 it. Nor can I do so from my home system on Comcast. What else could be blocking ping6, traceroute6, and telnet to port 25 on IPv6? >From AT&T host to Linode host: [root at saruman ~]# traceroute6 2600:3c01::f03c:91ff:febc:e22d traceroute to 2600:3c01::f03c:91ff:febc:e22d (2600:3c01::f03c:91ff:febc:e22d), 30 hops max, 80 byte packets 1 2001:1890:1837:5b00::1 (2001:1890:1837:5b00::1) 3.230 ms 3.181 ms 3.137 ms 2 2001:1890:c05:2f3a::ee6e:61cd (2001:1890:c05:2f3a::ee6e:61cd) 6.906 ms 6.901 ms...

On 4/28/2020 3:17 PM, Chris Adams wrote: > - gateway sends a router solicitation and gets a router advertisement > with "stateful config" set, which tells gateway to do DHCPv6 (but > default route comes from RA) I'm not seeing any outbound IPv6 traffic from my CentOS 7 box on the WAN interface. I do see RA's emitting from the LAN interface, from radvd. Is there

I have been gradually moving more tinc servers over to ipv6 addresses on the tinc 1.1 branch. Tinc is inserting a default route for ipv6 for some reason... default via 2600:3c01:e030:f2::1 dev tinc6 proto static metric 950 pref medium In my case the default route supplied by ra is still the correct thing, but I don't see where in the code tinc is inserting this route from.... which, as I'm also connecting tinc over ipv6 makes things rather circular in some insta...

...complains when it starts up, and won't let me confirm the security exception. On the server the following error occurs in the log: Sep 25 20:17:49 librelamp dovecot: imap-login: Disconnected (no auth attempts in 1 secs): user=<>, rip=2600:1010:b064:f260:e83e:562d:2316:18df, lip=2600:3c01::f03c:91ff:fee4:310c, TLS handshaking: SSL_accept() failed: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca: SSL alert number 48, session=<u7agQAlasK8mABAQsGTyYOg+Vi0jFhjf> I believe this is a client issue, as it worked just fine in CentOS 7.3 client, but I am hoping th...

...milar problem, that's a solution. -=- This is what I see in the mail server log when current CentOS thunderbird tries to connect: Sep 25 20:17:49 librelamp dovecot: imap-login: Disconnected (no auth attempts in 1 secs): user=<>, rip=2600:1010:b064:f260:e83e:562d:2316:18df, lip=2600:3c01::f03c:91ff:fee4:310c, TLS handshaking: SSL_accept() failed: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca: SSL alert number 48, session=<u7agQAlasK8mABAQsGTyYOg+Vi0jFhjf> --- Since it works with current evolution and with older thunderbird, I assume it is a bug in cu...

...the security exception. >> >> On the server the following error occurs in the log: >> >> Sep 25 20:17:49 librelamp dovecot: imap-login: Disconnected (no auth >> attempts in 1 secs): user=<>, >> rip=2600:1010:b064:f260:e83e:562d:2316:18df, >> lip=2600:3c01::f03c:91ff:fee4:310c, TLS handshaking: SSL_accept() >> failed: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert >> unknown ca: SSL alert number 48, >> session=<u7agQAlasK8mABAQsGTyYOg+Vi0jFhjf> >> >> I believe this is a client issue, as it worked just fine...

...t; On the server the following error occurs in the log: >>>> >>>> Sep 25 20:17:49 librelamp dovecot: imap-login: Disconnected (no auth >>>> attempts in 1 secs): user=<>, >>>> rip=2600:1010:b064:f260:e83e:562d:2316:18df, >>>> lip=2600:3c01::f03c:91ff:fee4:310c, TLS handshaking: SSL_accept() >>>> failed: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert >>>> unknown ca: SSL alert number 48, >>>> session=<u7agQAlasK8mABAQsGTyYOg+Vi0jFhjf> >>>> >>>> I believe this i...

...is what I see in the mail server log when current CentOS >> thunderbird tries to connect: >> >> Sep 25 20:17:49 librelamp dovecot: imap-login: Disconnected (no auth >> attempts in 1 secs): user=<>, >> rip=2600:1010:b064:f260:e83e:562d:2316:18df, >> lip=2600:3c01::f03c:91ff:fee4:310c, TLS handshaking: SSL_accept() >> failed: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert >> unknown ca: SSL alert number 48, >> session=<u7agQAlasK8mABAQsGTyYOg+Vi0jFhjf> >> >> --- >> >> Since it works with current evolut...

...=- > > This is what I see in the mail server log when current CentOS > thunderbird tries to connect: > > Sep 25 20:17:49 librelamp dovecot: imap-login: Disconnected (no auth > attempts in 1 secs): user=<>, > rip=2600:1010:b064:f260:e83e:562d:2316:18df, > lip=2600:3c01::f03c:91ff:fee4:310c, TLS handshaking: SSL_accept() > failed: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown > ca: SSL alert number 48, session=<u7agQAlasK8mABAQsGTyYOg+Vi0jFhjf> > > --- > > Since it works with current evolution and with older thunderbir...

...on't let me confirm > the security exception. > > On the server the following error occurs in the log: > > Sep 25 20:17:49 librelamp dovecot: imap-login: Disconnected (no auth > attempts in 1 secs): user=<>, > rip=2600:1010:b064:f260:e83e:562d:2316:18df, > lip=2600:3c01::f03c:91ff:fee4:310c, TLS handshaking: SSL_accept() > failed: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert > unknown ca: SSL alert number 48, > session=<u7agQAlasK8mABAQsGTyYOg+Vi0jFhjf> > > I believe this is a client issue, as it worked just fine in CentOS 7.3 >...

...;>> >>> On the server the following error occurs in the log: >>> >>> Sep 25 20:17:49 librelamp dovecot: imap-login: Disconnected (no auth >>> attempts in 1 secs): user=<>, >>> rip=2600:1010:b064:f260:e83e:562d:2316:18df, >>> lip=2600:3c01::f03c:91ff:fee4:310c, TLS handshaking: SSL_accept() >>> failed: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert >>> unknown ca: SSL alert number 48, >>> session=<u7agQAlasK8mABAQsGTyYOg+Vi0jFhjf> >>> >>> I believe this is a client issue, as...

...following error occurs in the log: >>>>> >>>>> Sep 25 20:17:49 librelamp dovecot: imap-login: Disconnected (no auth >>>>> attempts in 1 secs): user=<>, >>>>> rip=2600:1010:b064:f260:e83e:562d:2316:18df, >>>>> lip=2600:3c01::f03c:91ff:fee4:310c, TLS handshaking: SSL_accept() >>>>> failed: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert >>>>> unknown ca: SSL alert number 48, >>>>> session=<u7agQAlasK8mABAQsGTyYOg+Vi0jFhjf> >>>>> >>>>&...

On Fri, Mar 04, 2016 at 12:16:37PM -0800, Dave Taht wrote: > I have been gradually moving more tinc servers over to ipv6 addresses > on the tinc 1.1 branch. > > Tinc is inserting a default route for ipv6 for some reason... > > default via 2600:3c01:e030:f2::1 dev tinc6 proto static metric 950 > pref medium > > In my case the default route supplied by ra is still the correct > thing, but I don't see where in the code tinc is inserting this route > from.... which, as I'm also connecting tinc over ipv6 makes things >...

Hi list, I've recently managed to install CentOS 4.4 on an Apple Mac Pro. Functionality-wise everything works great, but when trying to benchmark the system, I don't get stable runtimes, they differ by more than 30%. For example a benchmark run with our PDE solving code takes between 500 and 800 s on the completely unloaded machine. Suspicious kernel output (complete output attached):

...0E280 ctl 0xFFFFC2000000E2B8 bmdma 0x0 irq 17 ata3: PATA max UDMA/133 cmd 0xFFFFC2000000E300 ctl 0xFFFFC2000000E338 bmdma 0x0 irq 17 ata1: SATA link down (SStatus 0) scsi0 : sata_promise ata2: SATA link down (SStatus 0) scsi1 : sata_promise ata3: dev 1 cfg 49:2f00 82:346b 83:7f01 84:4003 85:3468 86:3c01 87:4003 88:003f ata3: dev 1 ATA-6, max UDMA/100, 234441648 sectors: LBA48 ata3: dev 1 configured for UDMA/100 scsi2 : sata_promise Vendor: ATA Model: WDC WD1200JB-00D Rev: 75.1 Type: Direct-Access ANSI SCSI revision: 05 SCSI device sda: 234441648 512-byte hdwr sect...