Hello,

I asked for peering from a large french server (free.fr). All is done
through web form, no people responding.

http://nntpfeed.proxad.net/index.pl

how can I check that the peering works?

The way given in page links works only from the proxad network, so not
from my own server

thanks
jdd

Hi,

jdanield a tapoté le 17/01/2022 12:18:

> I asked for peering from a large french server (free.fr). All is done
> through web form, no people responding.
>
> http://nntpfeed.proxad.net/index.pl
>
> how can I check that the peering works?
>
> The way given in page links works only from the proxad network, so not
> from my own server

Free has is own special tools for that (or tools made by diablo?).
Accessible via telnet or netcat :
<http://nntpfeed.proxad.net/setup_fr.html>

If this works, the feed is correct but may have a delay of some hours
or that make this :

nc nntpfeed.proxad.net nntp
502 nntpfeed.proxad.net: Transfer permission denied to ....

--
Stéphane
Sorry for my poor English!

Le 17/01/2022 à 14:44, yamo' a écrit :
> Hi,
>
> jdanield a tapoté le 17/01/2022 12:18:
>
>> I asked for peering from a large french server (free.fr). All is done
>> through web form, no people responding.
>>
>> http://nntpfeed.proxad.net/index.pl
>>
>> how can I check that the peering works?
>>
>> The way given in page links works only from the proxad network, so not
>> from my own server
>
>
> Free has is own special tools for that (or tools made by diablo?).
> Accessible via telnet or netcat :
> <http://nntpfeed.proxad.net/setup_fr.html>

news@ns507557:/etc/news> telnet nntpfeed.proxad.net nntp
Trying 212.27.60.67...
Connected to nntpfeed.proxad.net.
Escape character is '^]'.
502 nntpfeed.proxad.net: Transfer permission denied to 142.4.209.201 -
newsmaster@proxad.net (DIABLO 5-CUR-20060921-00)
Connection closed by foreign host.

>
> If this works, the feed is correct but may have a delay of some hours
> or that make this :
>
> nc nntpfeed.proxad.net nntp
> 502 nntpfeed.proxad.net: Transfer permission denied to ....
>

same. I will try tomorrow, just in case delay is long. What thrills me
is that the setup page display may workstation IP. However I filled the
right server info.

Do somebody have yet a peer with free.fr?

also, is there a way to check if a peering works (any, not only Free)?
Some grep on the logs?

thanks
jdd

Hi,
jdanield a écrit :

> same. I will try tomorrow, just in case delay is long. What thrills me
> is that the setup page display may workstation IP. However I filled the
> right server info.

Do you have a full stack ipV4?

If not the feed is forbidden (that's my case and I don't want to touch on
something which is working very good...).

> Do somebody have yet a peer with free.fr?

I have and I'm not the only one but you will have more replies for that on
the french fr.usenet.distribution

> also, is there a way to check if a peering works (any, not only Free)?
> Some grep on the logs?

My local grep that I've posted on fr.comp.usenet.serveurs may be helpful...

--
Stéphane

Le 17/01/2022 à 21:55, yamo' a écrit :
> Hi,
> jdanield a écrit :
>
>> same. I will try tomorrow, just in case delay is long. What thrills me
>> is that the setup page display may workstation IP. However I filled the
>> right server info.
>
> Do you have a full stack ipV4?

sure. It's not a home hosted server, but a "kimsufi" (anyway I also have
full stack at home - for free.fr it's enough to ask for one to have it)

>> Do somebody have yet a peer with free.fr?
>
> I have and I'm not the only one but you will have more replies for that on
> the french fr.usenet.distribution

replies? I didn't write there (I just subscribe to see)

>
>> also, is there a way to check if a peering works (any, not only Free)?
>> Some grep on the logs?
>
> My local grep that I've posted on fr.comp.usenet.serveurs may be helpful...
>

what thread? (there are many :-()

thanks
jdd

Le Mardi 18 janvier 2022 à 07:48 UTC, jdanield écrivait sur
news.admin.peering :

> sure. It's not a home hosted server, but a "kimsufi" (anyway I also have
> full stack at home - for free.fr it's enough to ask for one to have it)

« Le service feed nntp n'est accessible que depuis des IPs fixes du
réseau ProXad »

KS is on the OVH network.
Peering with this server is possible with a dedibox or another
dedicated Online/Scaleway server.

@+
--
On ne le dira jamais assez, l'anarchisme, c'est l'ordre sans le
gouvernement ; c'est la paix sans la violence. C'est le contraire
précisément de tout ce qu'on lui reproche, soit par ignorance, soit
par mauvaise foi. -+- Hem Day -+-

Le 20/01/2022 à 19:28, Gérald Niel a écrit :
> Le Mardi 18 janvier 2022 à 07:48 UTC, jdanield écrivait sur
> news.admin.peering :
>
>> sure. It's not a home hosted server, but a "kimsufi" (anyway I also have
>> full stack at home - for free.fr it's enough to ask for one to have it)
>
> « Le service feed nntp n'est accessible que depuis des IPs fixes du
> réseau ProXad »
>
> KS is on the OVH network.
> Peering with this server is possible with a dedibox or another
> dedicated Online/Scaleway server.
>
> @+

yes, I was fearing this :-(

not a real problem, I have other peers :-(

but I don't know where you found this sentence, either I'm blind or it's
not there

http://nntpfeed.proxad.net/
http://nntpfeed.proxad.net/testfeed.pl
http://nntpfeed.proxad.net/setup_fr.html

by the way I could (may be) use a proxy on my own freebox, but I don't
care enough

thanks
jdd

thanjks
jdd

Le Jeudi 20 janvier 2022 à 18:53 UTC, jdanield écrivait sur
news.admin.peering :

> but I don't know where you found this sentence, either I'm blind or it's
> not there

> http://nntpfeed.proxad.net/

You're blind.

Or maybe…

Your personal IP at home is not the IP of your server.
So… check this with lynx or w3m from your server. Not from your home
behind your FreeBox.

--
On ne le dira jamais assez, l'anarchisme, c'est l'ordre sans le
gouvernement ; c'est la paix sans la violence. C'est le contraire
précisément de tout ce qu'on lui reproche, soit par ignorance, soit
par mauvaise foi. -+- Hem Day -+-

Le 20/01/2022 à 22:07, Gérald Niel a écrit :
> Le Jeudi 20 janvier 2022 à 18:53 UTC, jdanield écrivait sur
> news.admin.peering :
>
>> but I don't know where you found this sentence, either I'm blind or it's
>> not there
>
>> http://nntpfeed.proxad.net/
>
> You're blind.
>
> Or maybe…
>
> Your personal IP at home is not the IP of your server.

yes, I noted this on my first post here, but the form didn't ask for IP,
only domain name

> So… check this with lynx or w3m from your server. Not from your home
> behind your FreeBox.
>

done and refused.

I was guessing it was the reason, but there are not so many usenet
servers on the proxad network, so I was in doubt.

May be it's possible (=more simpler than installing INN) to have a "peer
proxy" on my freebox? no idea if this is even possible

jdd

Hi,
jdanield a écrit :
> I was guessing it was the reason, but there are not so many usenet
> servers on the proxad network, so I was in doubt.

There was some servers (mine also), it was working fine* but proxad has some
troubles and may be have the same end as orange/wanadoo...

* sometimes there was binaries on a text only feed.

--
Stéphane
Sorry for my bad English...

Bonjour Stéphane,

> There was some servers (mine also), it was working fine* but proxad has some
> troubles and may be have the same end as orange/wanadoo...
>
> * sometimes there was binaries on a text only feed.

I am unsure what the NNTP architecture of Proxad is. I think I've one
day heard they were using a mix of Diablo feeders and readers, and INN
for a specific purpose I don't remember. Or maybe it was another French
ISP.

The fact there are binaries on a text-only feed reminds me of an old bug
in INN, long time fixed (in 2009 with the 2.4.6 release). We were not
handling and copying strings properly with the Perl C API integration.

Maybe Diablo suffers from a similar issue, or Proxad still uses an old
INN version somewhere.

--
Julien ÉLIE

« Felix qui potuit rerum cognoscere causas. » (Virgile)

Bonjour Julien,
Julien ÉLIE a écrit :
> The fact there are binaries on a text-only feed reminds me of an old bug
> in INN, long time fixed (in 2009 with the 2.4.6 release). We were not
> handling and copying strings properly with the Perl C API integration.

This was maybe a bad configuration of the feed (à '@' which was not
present).

--
Stéphane
Sorry for my bad English...