I just completed the he.net certification programme. I an now a
certified IPv6 Sage.
I just completed the he.net certification programme. I an now a certified IPv6 Sage.
Waiting for the T-shirt. ;-)
On 23.4.2016 17:06, Michiel van der Vlist - All wrote:
I just completed the he.net certification programme. I an now a
certified IPv6 Sage.
Welcome to the club! :)
https://ipv6.he.net/certification/scoresheet.php?pass_name=koivula
Speaking of IPv6, have you tried connecting to me again lately? I
sent you a netmail, about the troubleshooting they did here, but
wonder if y ou ever got it.
As well, can you perhaps explain why the ipv6 address changes every
once in a while (after rebooting router),
but the ethenet address remains the same. (as listed in the
nodelist)
Speaking of IPv6, have you tried connecting to me again lately? I
sent you a netmail, about the troubleshooting they did here, but
wonder if y ou ever got it.
Yes, I got the netmail and I have been trying to connect a couple of times a week. No luck so far.
As well, can you perhaps explain why the ipv6 address changes every
once in a while (after rebooting router),
So maybe that is the problem. I try to connect to 2607:f2c0:f00e:4200:f9e0:b9ff:6166:c8ef
but the ethenet address remains the same. (as listed in the
nodelist)
I am not sure what you mean by the "ethernet address". Do you mean the lower 64
bits of the address? The host part that is based on the MAC address? Yes that would remain the same even if the prefix partm the upper 64 bits are changed by your provider.
Speaking of IPv6, have you tried connecting to me again lately? I
sent you a netmail, about the troubleshooting they did here, but
wonder if y ou ever got it.
Yes, I got the netmail and I have been trying to connect a couple of
times a week. No luck so far.
As well, can you perhaps explain why the ipv6 address changes every
once in a while (after rebooting router),
So maybe that is the problem. I try to connect to
2607:f2c0:f00e:4200:f9e0:b9ff:6166:c8ef
but the ethenet address remains the same. (as listed in the
nodelist)
I am not sure what you mean by the "ethernet address". Do you mean
the lower 64
bits of the address? The host part that is based on the MAC address?
Yes that would remain the same even if the prefix partm the upper 64
bits are changed by your provider.
The address shown by ethernet when you do an IPCONFIG. It is the same as you listed up above.
This is what is showing when I run a test on one of the test sites IPv6-test or test-ipv6
your ipv6 address on the publicinternet appears to be 2607:f2c0:f00e:4200:4559:9feb:be2e:4668
Tunnel adapter Teredo Tunneling Pseudo-Interface:
I just completed the he.net certification programme. I an now a
certified IPv6 Sage.
Welcome to the club! :)
Tnx.
https://ipv6.he.net/certification/scoresheet.php?pass_name=koivula
Ha, my score is higher.
https://ipv6.he.net/certification/scoresheet.php?pass_name=Roetzen
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Teredo? Don't you have native IPv6?
Have you tried disabling that?
I have no way to turn that
off in the router as far as I can see.
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Teredo? Don't you have native IPv6?
Have you tried disabling that?
Not using Teredo. Router is set to Slaac for WAN. I have no way to turn that off in the router as far as I can see. And yes, I have native
Here is a screen dump of my ipv6 test site
Here is a screen dump of my ipv6 test site
Here is a screen dump of my ipv6 test site
What caused the 2 out of 20 that you didn't get?
Anyway, it seems to me as if there's nothing much wrong with your
internet side, so I once again wonder what harm that Teredo tunnel may be causing your system.
BTW, I just noticed that you *DID* get an IPv6 connection to me less than an
hour ago.
^ 23-Apr-2016 22:58:35 CONNECT From 192.168.0.1 #24554
23-Apr-2016 22:58:35 Establishing BinkP transfer protocol
23-Apr-2016 22:58:36 M_NUL : OPT NDA EXTCMD CRYPT GZ
= 23-Apr-2016 22:58:38 Station : The Lion's Den
= 23-Apr-2016 22:58:38 Address : 1:249/303 1:249/300 1:249/0 1:12/0
: 23-Apr-2016 22:58:38 SysOp : Joe Delahaye from Trenton, Ont. Cdn
: 23-Apr-2016 22:58:38 Number : 192.168.0.1
The 192.168.0.1 means that you got relayed via Relay6 to Tedious here.
But it also means that you are not using the latest nodelist, or you'd be using the new contact info for 2:203/0 and therefore should be routed to my binkd server rather than to my Tedious.
Outgoing IPv6 calls to your system still doesn't work however:
+ 23 Apr 23:59:02 [3668] call to 1:249/303@fidonet
23 Apr 23:59:02 [3668] trying 2607:f2c0:f00e:4200:f9e0:b9ff:6166:c8ef [2607:f2c0:f00e:4200:f9e0:b9ff:6166:c8ef]...
? 23 Apr 23:59:23 [3668] connection to 1:249/303@fidonet failed: {W32 API error
10060} Connection timed out
23 Apr 23:59:24 [3668] trying lionsden.darktech.org [69.165.170.121]...
23 Apr 23:59:24 [3668] connected
Did you try the address in the screendump?
But it also means that you are not using the latest nodelist, or
you'd be using the new contact info for 2:203/0 and therefore should
be routed to my binkd server rather than to my Tedious.
I have you as a contact in my binkd contact list, and that has the original info. I do use the additional binkd.txt file that is hatched weekly though. I'll find the new info an change it.
I have you as a contact in my binkd contact list, and that has the original
info. I do use the additional binkd.txt file that is hatched weekly though.
I'll find the new info an change it.
I h ave you listed with the eljaco address, and that is what is showing
in the latest nodelist here
Ha, my score is higher.
https://ipv6.he.net/certification/scoresheet.php?pass_name=Roetzen
Irrelevant. T-shirts are what we count! :)
So you don't have a separate password include file then?
I have all my contacts listed there, and then I have the complete binkd nodelist file on top of that.
Like this:
#
# Include a file
#
include binkd.inc
include pass.inc
E.g. in the pass.inc:
Node 1:249/0@fidonet-xxxxxxxx-
Node 1:249/303@fidonet-xxxxxxxx-
(Notice the two hyphens, very important.)
...and then binkd will override the info in binkd.inc whenever it is updated
(once a week).
No changed IBN flag then, something like from just IBN to IBN:24555?
OK, I guess that means I'll have to wait at least another week before the Z1 calls to my system will begin to end up properly? 8-)
Now that you mention that, yes that is there.
Now that you mention that, yes that is there.
Thanks a million, Joe!
WOW! So what's taking you Z1 guys so long then? 8-)
Nobody uses the nodelist any longer??? Binkd doesnt
Tommy
Now that you mention that, yes that is there.
Thanks a million, Joe!
WOW! So what's taking you Z1 guys so long then? 8-)
Nobody uses the nodelist any longer??? Binkd doesnt, so nobody would ever notice, especially if a contact is hard wired into the setup.
Tommy
My apologies Tommi, a slip on the keyboard a late Saturday evening...
Irrelevant. T-shirts are what we count! :)
Had to browse back...
This is what I wrote "Fri, 30 Jan 2015 14:35:58 +0200"
"Just today I received my T-Shirt from Hurricane Electric."
This is what I wrote "Fri, 30 Jan 2015 14:35:58 +0200"
"Just today I received my T-Shirt from Hurricane Electric."
Almost three month ago...
Well, anyway, you and another guy in a Dutch
forum were inspiration to finally complete te course. I made it to Enthousiast five years ago and then I had to take the hurdle of having an e-mail address on a mail server that can be reached via IPv6.I could not take that hurdle then and I forgot about it. So... yesterday I thought let's have another look at it. And to my surprise, I managed to step through all the levels in one rainy afternoon. ;-)
Every time I get an official nodediff from Ward and then compile a new nodelist for my three different systems, my system now also compiles a new binkd.inc with all the newest nodelist info in it.
As a responsible RC I would probably be expected of nothing less, or I'd be fired on the spot...
Nobody uses the nodelist any longer??? Binkd doesnt, so nobody
would ever notice, especially if a contact is hard wired into the
setup.
Don't you derive your binkd.txt from the weekly nodelist?
"Just today I received my T-Shirt from Hurricane Electric."
Almost three month ago...
Well, 3+12. Time flies. :)
When I got the HE account not so many years ago, I noticed that they blocked port 25. I was told that I must be sage to get it opened. So I did. ;)
Nobody uses the nodelist any longer??? Binkd doesnt, so nobody
would ever notice, especially if a contact is hard wired into the
setup.
Don't you derive your binkd.txt from the weekly nodelist?
No, I receive it here weekly along with the nodelist and nodediff.
MvdV> Rumour has it that they also block IRC if you are not a a sage.When I got the HE account not so many years ago, I noticed that
they blocked port 25. I was told that I must be sage to get it
opened. So I did. ;)
Don't you derive your binkd.txt from the weekly nodelist?
No, I receive it here weekly along with the nodelist and nodediff.
Some tools can extract more binkp nodes from the nodelist than others. Can anyone beat NL2BINKD? It's a bash script with lots of awk :)
I just completed the he.net certification programme. I an now a;)
certified IPv6 Sage.
Waiting for the T-shirt. ;-)
"Just today I received my T-Shirt from Hurricane Electric."
Almost three month ago...
Well, 3+12. Time flies. :)
Oops.., ;-)
When I got the HE account not so many years ago, I noticed that they
blocked port 25. I was told that I must be sage to get it opened. So I
did. ;)
Rumour has it that they also block IRC if you are not a a sage. I wonder what else they block. I can have some sympathy for blocking port 25. If you
do not know what you are doing, you might become an accomplice in spreading
spam. It is a good incentive. But IRC?
Some tools can extract more binkp nodes from the nodelist than others. Can
anyone beat NL2BINKD? It's a bash script with lots of awk :)
Well, I dont have Bash as of yet (it's coming), since I dont do Nix <G>
Re: IPv6 problems
By: Markus Reschke to Joe Delahaye on Sun Apr 24 2016 15:58:46
Don't you derive your binkd.txt from the weekly nodelist?
No, I receive it here weekly along with the nodelist and nodediff.
Some tools can extract more binkp nodes from the nodelist than
others. Can anyone beat NL2BINKD? It's a bash script with lots of
awk :)
Well, I dont have Bash as of yet (it's coming), since I dont do Nix
Well, I dont have Bash as of yet (it's coming), since I dont do Nix
<G>
What? A windoze user without cygwin? <g>
Some tools can extract more binkp nodes from the nodelist than
others. Can anyone beat NL2BINKD? It's a bash script with lots of
awk :)
Well, I dont have Bash as of yet (it's coming), since I dont do Nix
You're getting Bikers Against Statewide Hunger? How is that going to work?
Some tools can extract more binkp nodes from the nodelist than others. Can anyone beat NL2BINKD? It's a bash script with lots of awk :)
What? A windoze user without cygwin? <g>
Nobody uses the nodelist any longer??? Binkd doesnt, so nobody
would ever notice, especially if a contact is hard wired into the
setup.
Don't you derive your binkd.txt from the weekly nodelist?
No, I receive it here weekly along with the nodelist and nodediff.
Re: IPv6 problems
By: Markus Reschke to Joe Delahaye on Sun Apr 24 2016 15:58:46
Don't you derive your binkd.txt from the weekly nodelist?
No, I receive it here weekly along with the nodelist and nodediff.
Some tools can extract more binkp nodes from the nodelist than others. Can
anyone beat NL2BINKD? It's a bash script with lots of awk :)
Well, I dont have Bash as of yet (it's coming), since I dont do Nix <G>
Don't you derive your binkd.txt from the weekly nodelist?
No, I receive it here weekly along with the nodelist and nodediff.
others. CanSome tools can extract more binkp nodes from the nodelist than
anyone beat NL2BINKD? It's a bash script with lots of awk :)
Well, I dont have Bash as of yet (it's coming), since I dont doNix <G>
I wrote one in PERL years ago, when I ran binbkd. I don't run that now
and don't know what I did with the code - but PERL will run on windows.
Isn't that right Benny, Tommy or Torbjörn? The three former
Scandinavian RCs that gave me the responsibility to handle the entire Scandinavia as R20, formerly just Sweden.
certified IPv6 Sage. Waiting for the T-shirt. ;-);)
Congratulation
I am still only professional, as my DNS provider has no AAAA DNS
servers. And I am still too lazy to change the provider :(
IRC is commonly used as a control channel for spam robots.
I can understand the blocking of dns and smtp, but I cannot understand
if isp's don't unblock by request. The way of HE is very ok. :)
What? A windoze user without cygwin? <g>
You just gave Joe his next project. ;) Joe... cygwin does work I used it for a lot of stuff before I found Fedora. I did have bash and awk working but I never tried a script like the one we're talking about.
Don't you derive your binkd.txt from the weekly nodelist?
No, I receive it here weekly along with the nodelist and nodediff.
So someone else derives it. One would think that it reflected the data in that latest nodelist.
CanSome tools can extract more binkp nodes from the nodelist than
others.
anyone beat NL2BINKD? It's a bash script with lots of awk :)
Well, I dont have Bash as of yet (it's coming), since I dont do Nix
<G>
I wrote one in PERL years ago, when I ran binbkd. I don't run that now and don't know what I did with the code - but PERL will run on windows.
Failed to include:
But as you get a fresh one each week you don't need to compile your own.
Don't you derive your binkd.txt from the weekly nodelist?
No, I receive it here weekly along with the nodelist and nodediff.
What? A windoze user without cygwin? <g>
You just gave Joe his next project. ;) Joe... cygwin does work I
used it for a lot of stuff before I found Fedora.
Tommi Koivula wrote to Shawn Highfield <=-
Yep. Nowadays after installing windows it is the very next task to
install cygwin. ;)
Some tools can extract more binkp nodes from the nodelist than
others. Can anyone beat NL2BINKD? It's a bash script with lots of awk
:)
You get extra lines by including Nodes that are Down or on Hold. :(
I get fewer lines, as I exclude lines where Hostnames does not
resolve.
I get fewer lines, as I exclude lines where Hostnames does not
resolve.
Could be another switch :) But I'm not sure, because a node could have
a boken DNS entry today and have it fixed by tomorrow.
Actually we would also have to check if a binkd is listening. Same
story here, binkd might be crashed today and fixed by tomorrow or the
IP address could be wrong. How should we deal with these nodes?
Yep, some like them included, others don't. I could add a switch for filtering them to please all.
I get fewer lines, as I exclude lines where Hostnames does not
resolve.
Could be another switch :) But I'm not sure, because a node could have a boken DNS entry today and have it fixed by tomorrow.
Or the entry could be broken for several months.
We simply don't know. And even if the entry
resolves it doesn't mean that the IP address is correct. Actually we
would
also have to check if a binkd is listening.
Same story here, binkd might
be crashed today and fixed by tomorrow or the IP address could be
wrong.
How should we deal with these nodes?
Don't you derive your binkd.txt from the weekly nodelist?
No, I receive it here weekly along with the nodelist and nodediff.
The BINKD.TXT is generated from the nodelist each week using a a perl script originally written by Jerry Schwartz, my predecessor as RC16.
My ISP (Ziggo) blocks port 25, but only for outgoing
My ISP (Ziggo) blocks port 25, but only for outgoing
I guess you mean incoming. (From Internet to you)
I find it more likely that there will be nodes that cannot accept
incoming IPv4 calls, due to being behind a CGNAT of some type.
It will be quite a while before IPv4 support is dropped entirely.
I noticed the following output in nl2binkp
Node 1:249/303 2607:f2c0:f00e:4200:f9e0:b9ff:6166:c8ef;lionsden.darktech.org -
Node 2:6001/9 node9.fido.bryansk.su:443node9.fido.bryansk.su:8080 -
I used both NL2BINKP and NL2BNKP2 as found on Ulrich's server.
I noticed the following out put in nl2binkp
Node 1:249/303 2607:f2c0:f00e:4200:f9e0:b9ff:6166:c8ef;lionsden.darktech.org -
The IPv6 address should be encased in square brackets.
FRL-1036 mentions this for use in the Nodelist. Apparently the developers of binkd followed this advice for the binkd specific
nodelist as well.
Node 2:6001/9 node9.fido.bryansk.su:443node9.fido.bryansk.su:8080 -
For some odd reason the semicolon is missing after 443
Looks OK here:
Node 1:249/303@fidonet
[2607:f2c0:f00e:4200:f9e0:b9ff:6166:c8ef]; lionsden.darktech.org;lionsden.darktech.org -
lionsden.darktech.org;lionsden.darktech.org -
Not really ;) You need some deduplication function :)
Sysop: | Nelgin |
---|---|
Location: | Plano, TX |
Users: | 509 |
Nodes: | 10 (1 / 9) |
Uptime: | 108:15:35 |
Calls: | 8,193 |
Files: | 15,442 |
Messages: | 913,165 |