A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Windows 10 » Windows 10 Help Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Eeternal-september



 
 
Thread Tools Rate Thread Display Modes
  #1  
Old September 5th 17, 04:55 PM posted to alt.comp.os.windows-10
Rene Lamontagne
external usenet poster
 
Posts: 2,549
Default Eeternal-september

Lost touch with 213-239-209-88 last night, news groups were all timing
out, this morning I changed back to the name "news.eternal-september.org
a now all back to normal.I was advised this may happen when I switched
to the numbers instead of name.

Rene
Ads
  #2  
Old September 5th 17, 05:24 PM posted to alt.comp.os.windows-10
Rene Lamontagne
external usenet poster
 
Posts: 2,549
Default Eeternal-september

On 9/5/2017 11:07 AM, Franklin wrote:
On Tue, 5 Sep 2017 10:55:54 -0500, Rene Lamontagne
wrote:

Lost touch with 213-239-209-88 last night, news groups were all timing
out, this morning I changed back to the name "news.eternal-september.org
a now all back to normal.I was advised this may happen when I switched
to the numbers instead of name.



https://www.eternal-september.org/

2017-09-05 09:38:05 Server news.eternal-september.org replaced

The old reader server news.eternal-september.org had to be replaced by
new hardware just before the scheduled replacement date. The new
server is up and running, DNS changes are underway. The new server is
called reader.eternal-september.org, but will also be available under
the usual name as soon as the DNS changes have fully propagated.
Currently, connections on port 80 and 443 are not available yet. These
will be available again soon. The new server has an SSL certificate
for both reader.eternal-september.org and news.eternal-september.org.
UUCP connectivity is currently not available, but will be
re-established tomorrow.



Hi, thanks for the info, much appreciated.

Rene

  #3  
Old September 5th 17, 05:44 PM posted to alt.comp.os.windows-10
philo
external usenet poster
 
Posts: 4,807
Default Eeternal-september

On 09/05/2017 11:24 AM, Rene Lamontagne wrote:
On 9/5/2017 11:07 AM, Franklin wrote:
On Tue, 5 Sep 2017 10:55:54 -0500, Rene Lamontagne
wrote:

Lost touch with 213-239-209-88 last night, news groups were all timing
out, this morning I changed back to the name "news.eternal-september.org
a now all back to normal.I was advised this may happen when I switched
to the numbers instead of name.



https://www.eternal-september.org/

2017-09-05 09:38:05 Server news.eternal-september.org replaced

The old reader server news.eternal-september.org had to be replaced by
new hardware just before the scheduled replacement date. The new
server is up and running, DNS changes are underway. The new server is
called reader.eternal-september.org, but will also be available under
the usual name as soon as the DNS changes have fully propagated.
Currently, connections on port 80 and 443 are not available yet. These
will be available again soon. The new server has an SSL certificate
for both reader.eternal-september.org and news.eternal-september.org.
UUCP connectivity is currently not available, but will be
re-established tomorrow.



Hi, thanks for the info, much appreciated.

Rene




Nice for it to be back now. I do have a few backup news servers though
  #4  
Old September 6th 17, 01:35 AM posted to alt.comp.os.windows-10
Micky
external usenet poster
 
Posts: 1,528
Default Eeternal-september

In alt.comp.os.windows-10, on Tue, 05 Sep 2017 09:07:15 -0700, Franklin
wrote:

On Tue, 5 Sep 2017 10:55:54 -0500, Rene Lamontagne
wrote:

Lost touch with 213-239-209-88 last night, news groups were all timing
out, this morning I changed back to the name "news.eternal-september.org
a now all back to normal.I was advised this may happen when I switched
to the numbers instead of name.



https://www.eternal-september.org/

2017-09-05 09:38:05 Server news.eternal-september.org replaced


Very interesting. Agent stopped working for me late last night,
restarting Agent didn't help, and finally today around 2PM ET, I
restarted Windows and everything was fine. Perhaps windows learns the
server IP so it doesn't have to check the DNS each time, and remembers
it even when Agent is closed.

The old reader server news.eternal-september.org had to be replaced by
new hardware just before the scheduled replacement date. The new
server is up and running, DNS changes are underway. The new server is
called reader.eternal-september.org, but will also be available under
the usual name as soon as the DNS changes have fully propagated.
Currently, connections on port 80 and 443 are not available yet. These
will be available again soon. The new server has an SSL certificate
for both reader.eternal-september.org and news.eternal-september.org.
UUCP connectivity is currently not available, but will be
re-established tomorrow.


  #5  
Old September 6th 17, 03:17 AM posted to alt.comp.os.windows-10,alt.free.newsservers
Roy Tremblay[_2_]
external usenet poster
 
Posts: 37
Default Eeternal-september

Franklin actually wrote:

On Tue, 5 Sep 2017 10:55:54 -0500, Rene Lamontagne
wrote:

Lost touch with 213-239-209-88 last night, news groups were all timing
out, this morning I changed back to the name "news.eternal-september.org
a now all back to normal.I was advised this may happen when I switched
to the numbers instead of name.



https://www.eternal-september.org/

2017-09-05 09:38:05 Server news.eternal-september.org replaced

The old reader server news.eternal-september.org had to be replaced by
new hardware just before the scheduled replacement date. The new
server is up and running, DNS changes are underway. The new server is
called reader.eternal-september.org, but will also be available under
the usual name as soon as the DNS changes have fully propagated.
Currently, connections on port 80 and 443 are not available yet. These
will be available again soon. The new server has an SSL certificate
for both reader.eternal-september.org and news.eternal-september.org.
UUCP connectivity is currently not available, but will be
re-established tomorrow.


Also good to cc "alt.free.newsservers" if they're not already informed.
  #6  
Old September 6th 17, 06:12 AM posted to alt.comp.os.windows-10,alt.free.newsservers
max
external usenet poster
 
Posts: 1
Default the new E-S is posting IPs of posters Eeternal-september

Roy Tremblay wrote:
Franklin actually wrote:

On Tue, 5 Sep 2017 10:55:54 -0500, Rene Lamontagne
wrote:

Lost touch with 213-239-209-88 last night, news groups were all timing
out, this morning I changed back to the name "news.eternal-september.org
a now all back to normal.I was advised this may happen when I switched
to the numbers instead of name.



https://www.eternal-september.org/

2017-09-05 09:38:05 Server news.eternal-september.org replaced

The old reader server news.eternal-september.org had to be replaced by
new hardware just before the scheduled replacement date. The new
server is up and running, DNS changes are underway. The new server is
called reader.eternal-september.org, but will also be available under
the usual name as soon as the DNS changes have fully propagated.
Currently, connections on port 80 and 443 are not available yet. These
will be available again soon. The new server has an SSL certificate
for both reader.eternal-september.org and news.eternal-september.org.
UUCP connectivity is currently not available, but will be
re-established tomorrow.


Also good to cc "alt.free.newsservers" if they're not already informed.


Looks like they are leaking...
  #7  
Old September 6th 17, 07:21 AM posted to alt.comp.os.windows-10
Char Jackson
external usenet poster
 
Posts: 10,449
Default Eeternal-september

On Tue, 05 Sep 2017 20:35:38 -0400, micky
wrote:

In alt.comp.os.windows-10, on Tue, 05 Sep 2017 09:07:15 -0700, Franklin
wrote:

On Tue, 5 Sep 2017 10:55:54 -0500, Rene Lamontagne
wrote:

Lost touch with 213-239-209-88 last night, news groups were all timing
out, this morning I changed back to the name "news.eternal-september.org
a now all back to normal.I was advised this may happen when I switched
to the numbers instead of name.



https://www.eternal-september.org/

2017-09-05 09:38:05 Server news.eternal-september.org replaced

The old reader server news.eternal-september.org had to be replaced by
new hardware just before the scheduled replacement date. The new
server is up and running, DNS changes are underway. The new server is
called reader.eternal-september.org, but will also be available under
the usual name as soon as the DNS changes have fully propagated.
Currently, connections on port 80 and 443 are not available yet. These
will be available again soon. The new server has an SSL certificate
for both reader.eternal-september.org and news.eternal-september.org.
UUCP connectivity is currently not available, but will be
re-established tomorrow.


Very interesting. Agent stopped working for me late last night,
restarting Agent didn't help,


Right, because as the announcement above shows, the problem was on their
end and had nothing to do with you. They performed a server hardware
replacement and obviously didn't/don't have a load balancer in place, so
there was an outage while they were offline. I'd normally say that's
pretty sloppy of them, except that AFAIK they run a free service, so
they can do what they like.

and finally today around 2PM ET, I restarted Windows and everything was fine.


Again, see above. The announcement explains that the new server address
will be reader.eternal-september.org, but if you allow time for DNS
propagation then the old name of news.eternal-september.org will also
work once again. You allowed time for DNS propagation, so the old name
once again works for you. People who managed to use the new server name
would have seen their service resume somewhat earlier, since that name
was apparently pre-registered in DNS.

Perhaps windows learns the
server IP so it doesn't have to check the DNS each time, and remembers
it even when Agent is closed.


DNS has a hierarchy or flow chart of operations that it follows in order
to translate a server name into an IP address. Once it learns that
translation, it does store the information for a period of time, but not
for very long. The next time you request the translation, if the old
data has expired, a new DNS request is initiated.


  #8  
Old September 6th 17, 08:05 AM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Eeternal-september

Char Jackson wrote:
On Tue, 05 Sep 2017 20:35:38 -0400, micky
wrote:

In alt.comp.os.windows-10, on Tue, 05 Sep 2017 09:07:15 -0700, Franklin
wrote:

On Tue, 5 Sep 2017 10:55:54 -0500, Rene Lamontagne
wrote:

Lost touch with 213-239-209-88 last night, news groups were all timing
out, this morning I changed back to the name "news.eternal-september.org
a now all back to normal.I was advised this may happen when I switched
to the numbers instead of name.

https://www.eternal-september.org/

2017-09-05 09:38:05 Server news.eternal-september.org replaced

The old reader server news.eternal-september.org had to be replaced by
new hardware just before the scheduled replacement date. The new
server is up and running, DNS changes are underway. The new server is
called reader.eternal-september.org, but will also be available under
the usual name as soon as the DNS changes have fully propagated.
Currently, connections on port 80 and 443 are not available yet. These
will be available again soon. The new server has an SSL certificate
for both reader.eternal-september.org and news.eternal-september.org.
UUCP connectivity is currently not available, but will be
re-established tomorrow.

Very interesting. Agent stopped working for me late last night,
restarting Agent didn't help,


Right, because as the announcement above shows, the problem was on their
end and had nothing to do with you. They performed a server hardware
replacement and obviously didn't/don't have a load balancer in place, so
there was an outage while they were offline. I'd normally say that's
pretty sloppy of them, except that AFAIK they run a free service, so
they can do what they like.


# The affected server is this one. The IP address changed on it.
# DNS cache has refreshed here, so I can see it.
#
# At the current time, the machine is ****ing up headers (it is posting
# the posting-host IP address), and I won't be using it until that is fixed.
# That means a filter on the posting part, isn't enabled yet. It replaces
# that part of the header, with an encrypted string.

news.eternal-september.org

# These are also provided, for users who need them.
# Presumably port 80 is for punching through a corporate firewall or something :-)

reader80.eternal-september.org

reader443.eternal-september.org

The administrator of that server is every bit as skillful as you
and is "in the business". He has done distributed implementations
of his server (back end, front end, authentication) running
on different boxes, and done cut-overs in service. This does
not appear to be a normal response from him. Either he doesn't
have time to do it right, or there is some other detail
we're not aware of.

Did he just change COLOs perhaps ? Dunno. I consider the
change of IP address to be a bit abnormal. But unless he
does a posting describing what hell he just went through,
we'll never know.

*******

The AIOE server I'm using for this post, it was completely
wiped out once. The machine was in a COLO in Italy. The administrator
is Italian. He happened to make a disparaging editorial comment
about the COLO services, and he was kicked to the curb (server
disabled, no backup). He started over again in a German COLO,
from scratch, having to rebuild both the NNTP and HTTP portions.
Now, that's an example of "**** beyond your control". Apparently
Italian law allows that sort of thing. And that's why he is in
Germany now (he is still in Italy, the COLO of the AIOE server
is in Germany).

It's true, there are a few NNTP administrators, who run out
of their moms basement, and they're pretty clueless. Wolfgang
isn't one of them.

And it's not a commercial grade setup. It's not Giganews or something.
It's a hobby project for him.

Paul
  #9  
Old September 6th 17, 08:46 AM posted to alt.comp.os.windows-10,alt.free.newsservers,news.software.readers
Roy Tremblay[_2_]
external usenet poster
 
Posts: 37
Default Eeternal-september

Paul actually wrote:

Char Jackson wrote:
On Tue, 05 Sep 2017 20:35:38 -0400, micky
wrote:

In alt.comp.os.windows-10, on Tue, 05 Sep 2017 09:07:15 -0700, Franklin
wrote:

On Tue, 5 Sep 2017 10:55:54 -0500, Rene Lamontagne
wrote:

Lost touch with 213-239-209-88 last night, news groups were all timing
out, this morning I changed back to the name "news.eternal-september.org
a now all back to normal.I was advised this may happen when I switched
to the numbers instead of name.

https://www.eternal-september.org/

2017-09-05 09:38:05 Server news.eternal-september.org replaced

The old reader server news.eternal-september.org had to be replaced by
new hardware just before the scheduled replacement date. The new
server is up and running, DNS changes are underway. The new server is
called reader.eternal-september.org, but will also be available under
the usual name as soon as the DNS changes have fully propagated.
Currently, connections on port 80 and 443 are not available yet. These
will be available again soon. The new server has an SSL certificate
for both reader.eternal-september.org and news.eternal-september.org.
UUCP connectivity is currently not available, but will be
re-established tomorrow.
Very interesting. Agent stopped working for me late last night,
restarting Agent didn't help,


Right, because as the announcement above shows, the problem was on their
end and had nothing to do with you. They performed a server hardware
replacement and obviously didn't/don't have a load balancer in place, so
there was an outage while they were offline. I'd normally say that's
pretty sloppy of them, except that AFAIK they run a free service, so
they can do what they like.


# The affected server is this one. The IP address changed on it.
# DNS cache has refreshed here, so I can see it.
#
# At the current time, the machine is ****ing up headers (it is posting
# the posting-host IP address), and I won't be using it until that is fixed.
# That means a filter on the posting part, isn't enabled yet. It replaces
# that part of the header, with an encrypted string.

news.eternal-september.org

# These are also provided, for users who need them.
# Presumably port 80 is for punching through a corporate firewall or something :-)

reader80.eternal-september.org

reader443.eternal-september.org

The administrator of that server is every bit as skillful as you
and is "in the business". He has done distributed implementations
of his server (back end, front end, authentication) running
on different boxes, and done cut-overs in service. This does
not appear to be a normal response from him. Either he doesn't
have time to do it right, or there is some other detail
we're not aware of.

Did he just change COLOs perhaps ? Dunno. I consider the
change of IP address to be a bit abnormal. But unless he
does a posting describing what hell he just went through,
we'll never know.

*******

The AIOE server I'm using for this post, it was completely
wiped out once. The machine was in a COLO in Italy. The administrator
is Italian. He happened to make a disparaging editorial comment
about the COLO services, and he was kicked to the curb (server
disabled, no backup). He started over again in a German COLO,
from scratch, having to rebuild both the NNTP and HTTP portions.
Now, that's an example of "**** beyond your control". Apparently
Italian law allows that sort of thing. And that's why he is in
Germany now (he is still in Italy, the COLO of the AIOE server
is in Germany).

It's true, there are a few NNTP administrators, who run out
of their moms basement, and they're pretty clueless. Wolfgang
isn't one of them.

And it's not a commercial grade setup. It's not Giganews or something.
It's a hobby project for him.

Paul


I still think you guys should be cc'ing the alt.free.newssservers group,
especially bearing in mind indications there that "the new E-S is posting
IPs of posters" in the clear (which has happened in the past).
  #10  
Old September 6th 17, 08:48 AM posted to alt.comp.os.windows-10,alt.free.newsservers,news.software.readers
Roy Tremblay[_2_]
external usenet poster
 
Posts: 37
Default Eeternal-september

Roy Tremblay actually wrote:

And it's not a commercial grade setup. It's not Giganews or something.
It's a hobby project for him.


I forget if his real name is Wolfgang, but he goes by Ray Banana and he's a
nice guy from my conversations with him in the past.

Just fyi...
  #11  
Old September 6th 17, 09:41 AM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Eeternal-september

Roy Tremblay wrote:


I still think you guys should be cc'ing the alt.free.newssservers group,
especially bearing in mind indications there that "the new E-S is posting
IPs of posters" in the clear (which has happened in the past).


Now, why do you think I *didn't* do that ? Hmmm ?

Do you think I had my reasons perhaps ?

Plonk.

Paul
  #12  
Old September 6th 17, 03:46 PM posted to alt.comp.os.windows-10
Char Jackson
external usenet poster
 
Posts: 10,449
Default Eeternal-september

On Wed, 06 Sep 2017 03:05:31 -0400, Paul wrote:

Char Jackson wrote:
On Tue, 05 Sep 2017 20:35:38 -0400, micky
wrote:

In alt.comp.os.windows-10, on Tue, 05 Sep 2017 09:07:15 -0700, Franklin
wrote:

On Tue, 5 Sep 2017 10:55:54 -0500, Rene Lamontagne
wrote:

Lost touch with 213-239-209-88 last night, news groups were all timing
out, this morning I changed back to the name "news.eternal-september.org
a now all back to normal.I was advised this may happen when I switched
to the numbers instead of name.

https://www.eternal-september.org/

2017-09-05 09:38:05 Server news.eternal-september.org replaced

The old reader server news.eternal-september.org had to be replaced by
new hardware just before the scheduled replacement date. The new
server is up and running, DNS changes are underway. The new server is
called reader.eternal-september.org, but will also be available under
the usual name as soon as the DNS changes have fully propagated.
Currently, connections on port 80 and 443 are not available yet. These
will be available again soon. The new server has an SSL certificate
for both reader.eternal-september.org and news.eternal-september.org.
UUCP connectivity is currently not available, but will be
re-established tomorrow.
Very interesting. Agent stopped working for me late last night,
restarting Agent didn't help,


Right, because as the announcement above shows, the problem was on their
end and had nothing to do with you. They performed a server hardware
replacement and obviously didn't/don't have a load balancer in place, so
there was an outage while they were offline. I'd normally say that's
pretty sloppy of them, except that AFAIK they run a free service, so
they can do what they like.


# The affected server is this one. The IP address changed on it.
# DNS cache has refreshed here, so I can see it.


When I posted yesterday, the IP address hadn't yet changed. It was still
213.239.209.88, but I see that today it's changed to 176.9.11.100 for
both reader.eternal-september.org and news.eternal-september.org.

# At the current time, the machine is ****ing up headers (it is posting
# the posting-host IP address), and I won't be using it until that is fixed.
# That means a filter on the posting part, isn't enabled yet. It replaces
# that part of the header, with an encrypted string.


Yeah, I saw that. If I was using E-S, I wouldn't be too happy about
that. There be stalkers in these waters who love information like that.

news.eternal-september.org

# These are also provided, for users who need them.
# Presumably port 80 is for punching through a corporate firewall or something :-)

reader80.eternal-september.org

reader443.eternal-september.org


Exactly right, it's for lackeys who get their daily Usenet fix on the
boss's dime. The Highwinds servers have all kinds of ports open to make
it easier for people to get around corporate firewalls and related
policies, for example.

The administrator of that server is every bit as skillful as you
and is "in the business". He has done distributed implementations
of his server (back end, front end, authentication) running
on different boxes, and done cut-overs in service. This does
not appear to be a normal response from him. Either he doesn't
have time to do it right, or there is some other detail
we're not aware of.


Yep, it's not rocket science. Build the new server and test it locally.
If it works as expected, add it to the load balancer pool and gradually
steer *new* connections to it. In other words, be sure to enable
connection persistence. Slow ramp might also be a good idea. After a
configurable period of time, the new server will have all of the
connections and the old server will have bled down to none. At that
point, it can be disconnected and retired. That assumes a load balancer
is in place. If not, about all you can do is a hard cut. People will
notice that, whereas the first approach is entirely seamless.

In the announcement, he says that the old reader server had to be
replaced *before* the scheduled replacement date, (emphasis mine), so
maybe he got caught off guard and had to make up a plan as he went.
Reactive mode versus proactive mode.

snip
And it's not a commercial grade setup. It's not Giganews or something.
It's a hobby project for him.


Agreed, and that's why I initially said he can do what he likes. He can
do hard cuts, DNS changes, even outages, since it's a hobby and it's
free.

  #13  
Old September 6th 17, 03:52 PM posted to alt.comp.os.windows-10
Char Jackson
external usenet poster
 
Posts: 10,449
Default Eeternal-september

On Wed, 06 Sep 2017 03:05:31 -0400, Paul wrote:

# At the current time, the machine is ****ing up headers (it is posting
# the posting-host IP address), and I won't be using it until that is fixed.
# That means a filter on the posting part, isn't enabled yet. It replaces
# that part of the header, with an encrypted string.


In Message-ID: poster Mike Easter
says "In e-s support last nite Ray said 'oops' and restored the
encryption/hash."

So that part might be corrected now.

  #14  
Old September 6th 17, 04:40 PM posted to alt.comp.os.windows-10,alt.free.newsservers
Roy Tremblay[_2_]
external usenet poster
 
Posts: 37
Default Eeternal-september

Char Jackson actually wrote:

In Message-ID: poster Mike Easter
says "In e-s support last nite Ray said 'oops' and restored the
encryption/hash."

So that part might be corrected now.


In the past, as I recall, Ray Banana would (seemingly to us) arbitrarily
expose an NNTP posting ID if he felt that the *newsgroup* list was odd.

So caveat emptor...

Also note that the only free common servers which *change* their hash
frequently are Albasani and Solani.

The rest keep a static hash and some use the *same* encryption forever,
never changing it once for all users.

Essentially, the ES hash keeps only the dumb psychopaths away...
  #15  
Old September 6th 17, 04:52 PM posted to alt.comp.os.windows-10,alt.free.newsservers
Good Guy[_2_]
external usenet poster
 
Posts: 3,354
Default the new E-S is posting IPs of posters Eeternal-september

On 06/09/2017 06:12, max wrote:

Looks like they are leaking...


That's very good news. Roy Tremblay won't be able to hide behind E-S
servers to abuse young boys. The authorities are watching him.



--
With over 500 million devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 01:42 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.