The binkd-version I'm running identifies itself as ...
07 Dec 14:37:39 [5004] BEGIN standalone, binkd/1.1a-94/Win32
BINKD.CFG -cs
So I think that's a goodone. The name of the executable is
binkd-static-perl-zlib-bzlib2
Am I still good?
OK, my dns-provider is dyndns.org, they can manage IPv6. It's
switched-off at the moment.
One individual tells me I need to work with the configuration file of binkd, another source tells me it is already there.
Are you on a window XP machine? XP supports IPv6 but it is disabled by default.
I asked around how to do this but I'm getting conflicting answers or answers to questions not asked.
The binkd-version I'm running identifies itself as ...
07 Dec 14:37:39 [5004] BEGIN standalone, binkd/1.1a-94/Win32 BINKD.CFG -cs
So I think that's a goodone. The name of the executable is
binkd-static-perl-zlib-bzlib2
Am I still good?
As my new router, new since x-number of months, is IPv6 capable and my provider seems to offer it, the intention is to have a go at it.
As my new router, new since x-number of months, is IPv6 capable and Kv>WD> my provider seems to offer it, the intention is to have a go at it.
Just to showoff that I really have Dbridge running on Ipv6
Are you on a window XP machine? XP supports IPv6 but it is disabled Mv>MV> by default.
I forgot: For XP you need SP2. Win 7 and up has IPv6 by default.
Are you on a window XP machine? XP supports IPv6 but it isdisabled by default.
I forgot: For XP you need SP2. Win 7 and up has IPv6 by default.
I'm running Win7.
But if you want help, you have to give us information.
So I ask again.
If you type "binkd -vv" at the command line, what do you see?
If you type "ipconfig /all" at the command line, what do you see?
if you surf to http://ipv6-test.com/ what do you see?
^^^^If you type "binkd -vv" at the command line, what do you see?
********************************************************************** ******* Binkd 1.1a-94 (Apr 4 2016 18:49:54/Win32) Compilation flags: msvc, static, zlib, bzlib2, perl, https, ntlm, amiga_4d_outbound,
bwlim, ipv6.
If you type "ipconfig /all" at the command line, what do you see?
********************************************************************** ******* Windows IP Configuration
Host Name . . . . . . . . . . . . : SERVER
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : lan
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : Intel(R) Ethernet Connection
(2) I219-V
Physical Address. . . . . . . . . : 4C-CC-6A-6C-F1-7A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2a02:a03f:4a2f:c300:4df3:890a:8ec1:7cc (Preferred)
IPv6 Address. . . . . . . . . . . : fd7e:49ab:5d5c:0:4df3:890a:8ec1:7cc0(P eferred)
Temporary IPv6 Address. . . . . . : 2a02:a03f:4a2f:c300:55aa:95e6:46e2:3b6 (Preferred)
Temporary IPv6 Address. . . . . . :
fd7e:49ab:5d5c:0:55aa:95e6:46e2:3b60(P eferred)
Link-local IPv6 Address . . . . . : fe80::4df3:890a:8ec1:7cc0%11(Preferred
if you surf to http://ipv6-test.com/ what do you see?
********************************************************************** ******* IPv4 speed IPv6 speed 91.176.11.57 2a02:a03f:4a2f:c300:55aa:95e6:46e2:3b60 ISP Proximus
Belgacom Roubaix 31.9Mbit/s 65.2Mbit/s Zeeland
76.0 73.2 Paris 78.0
84.7 Portsmouth 51.2 60.1 Canada 20.9
20.9 ********************************************************************** *******
Your IPv6 address is not pingable yet.
What happens iof you try to ping fido.vlist.eu?
Go to the setup of your router and look for a setting to enable ICMP or PING for IPv6.
Hmmm... click om the "general" button on the top..
No incoming IPv6 yet.
So something is still missing.
I think there may be a problem there. The router is ISP-provided and pretty good. However there are 3 lvels to log into "User", "Admin" and "Expert" and they only give-out the password for "User".
What happens iof you try to ping fido.vlist.eu?
********************************************************************** Pinging fido.vlist.eu [2001:1c02:1100:bd00:f1d0:2:280:5555]
with 32 bytes of data:
Reply from 2001:1c02:1100:bd00:f1d0:2:280:5555: time=25ms
Go to the setup of your router and look for a setting to enable
ICMP or PING for IPv6.
I think there may be a problem there. The router is ISP-provided and pretty good. However there are 3 lvels to log into "User", "Admin" and "Expert" and they only give-out the password for "User".
That level is too low to do what you ask.
Let me get to their local shop on Monday and see if they understand
what I'm talking about ...
Hmmm... click om the "general" button on the top..
IPv6 connectivity
Ipv6 Supported
Address 2a02:a03f:4a2f:c300:55aa:95e6:46e2:3b60
Type Native IPv6
SLAAC No
ICMP Filtered
Hostname None
ISP Belgacom
Browser
Default IPv6
Fallback to IPv4 in <1 second
DNS
DNS4+IP6 Reachable
DNS6+IP4 Reachable
DNS6+IP6 Reachable
No incoming IPv6 yet.
ISP-provided routers are usually not-pretty-good, because "they" are
in control, not you.
I've got one Huawei LTE router with ISP branded firmware which doesn't allow incoming IPv6 not matter what. Even with "admin" rights...
What puzzles me is that your binkd does not make outgoing IPv6 calls.
Maybe you still have a friend at Belgacom that can "arrange" something
for you. Maybe there are some tricks to raise your access level. Google
is your friend. An maybe we do not need it for now. Ping is nice, but not essantial.
Let me get to their local shop on Monday and see if they understand Mv>WD> what I'm talking about ...
Don't be surprised if you get a blank stare if you ask about IPv6...
What puzzels me is that you obviously have outgoing IPv6 capability and your OS is configuerd to first try IPv6. A very simple quick test is
here:
www.kame.net
If you see the turtle dance, you have outgoing IPv6.
What puzzles me is that your binkd does not make outgoing IPv6 calls. AFAIK, all versions of binkd that support IPv6 default to the OS
preference when choosing between IPv4 and IPv6. In your case IPv6.
Binkd should make outgoing IPv6 calls. But it does not, you come in with IPv4 in my logs.
Binkd can be forced to use either IPv4 or IPv6 on an outgoing call, but that is not the default.
There may be something in the interface between D'Bridge and Binkd that I am unaware of. Kees should be your man, AFAIK he is the only Fidonet
sysop that got D'Bridge to do IPv6.
By default the IPv6 firewall in the router will drop every unsollicited incomong IPv6 packet. To allow incoming one has to punch a hole in the firewall for the port(s) and destination(s).
- Disble D'Bridge and make sure the binkd server is not running.
- Go to the directory where binkd.exe is located and type:
binkd -pP2:280/5555 binkd.cfg (or whatever is the name of binkd's
config file)
- If it does not make a outgoing IPv6 call to my system:
- Find the part in the config where my node is defined and insert '-6' between
the node number and the password:
node 2:280/5555 -6 password
- Then again: binkd -pP2:280/5555 binkd.cfg
Tell us what happens.
Tell us what happens.
******* node 2:280/5555 fido.vlist.eu -6 XXXXXXXXXX C
Maybe you still have a friend at Belgacom that can "arrange"
something for you. Maybe there are some tricks to raise your
access level. Google is your friend. An maybe we do not need it
for now. Ping is nice, but not essantial.
My Belgacom years are 16 years behind me, the people I knew have
mostly been reorganized away.
Belgacom\Proximus\Skynet do not seem to have a public forum to ask questions and from what I encounter Googling it seems there are a lot
of frustrated people who simply want more.
What they are attempting is discouraging the possibility that you have incoming IPv6, discourage home-servers. Phone-support seems to be of
the "I hope I don't break my nail" kind.
What puzzels me is that you obviously have outgoing IPv6 capability
and your OS is configuerd to first try IPv6. A very simple quick test
is here:
www.kame.net
If you see the turtle dance, you have outgoing IPv6.
Let me put it this way, the turtle isn't dancing, looks more like
swimming but I guess that's what you meant.
There may be something in the interface between D'Bridge and Binkd
that I am unaware of. Kees should be your man, AFAIK he is the
only Fidonet sysop that got D'Bridge to do IPv6.
I think D'bridge is not involved.
Way way back when Chris Irwin dropped away and there litterally was no D'Bridge support until Nick popped and started his Opus Magnum, I
wrote my own work-around to become IP-capable, and to this day these routines still work ... if it ain't broke don't fix it.
It simply is a Binkley-style outbound which I create and Binkd deals
with that.
And D'bridge itself does not have any generic binkp-capable code.
It als creates a Binkly-style outbound ... I think. Let me upgrade to
the latest DB-distributed binkd-code and see what happens.
By default the IPv6 firewall in the router will drop every
unsollicited incomong IPv6 packet. To allow incoming one has to
punch a hole in the firewall for the port(s) and destination(s).
I will play with it some more the next few days.
So I explored further {this is rather fascinating} and installed the binkd-version that came with the latest D'Bridge release (2 days ago).
It reacts different on the binkd '-pP2:280/5555 binkd.cfg'-command:
1) By forcing IPv6:
********************************************************************** ******* 08 Dec 14:02:53 [8964] BEGIN standalone, binkd/1.1a-99/Win32 -pP2:280/5555 binkd.cfg 08 Dec 14:02:53 [8964] creating a poll for 2:280/5555@fidonet (`d' flavour) 08 Dec 14:02:53 [8964] clientmgr
started + 08 Dec 14:02:53 [4556] call to 2:280/5555@fidonet 08 Dec 14:02:53 [4556] trying fido.vlist.eu [2001:1c02:1100:bd00:f1d0:2:280 5555]... ? 08 Dec 14:02:54 [4556] connection to 2:280/5555@fidonet
failed: {W32 API error 10061} Connection refused 08 Dec 14:02:54
[8964] the queue is empty, quitting...
By NOT forcing IPv6 ...
********************************************************************** ******* 08 Dec 14:05:38 [2648] BEGIN standalone, binkd/1.1a-99/Win32 -pP2:280/5555 binkd.cfg 08 Dec 14:05:38 [2648] creating a poll for 2:280/5555@fidonet (`d' flavour) 08 Dec 14:05:38 [2648] clientmgr
started + 08 Dec 14:05:38 [8932] call to 2:280/5555@fidonet 08 Dec 14:05:39 [8932] trying fido.vlist.eu [2001:1c02:1100:bd00:f1d0:2:280 5555]... ? 08 Dec 14:05:40 [8932] connection to 2:280/5555@fidonet
failed: {W32 API error 10061} Connection refused
08 Dec 14:05:40 [8932] trying fido.vlist.eu [83.85.196.65]:24554... ?
08 Dec 14:05:41 [8932] connection to 2:280/5555@fidonet failed: {W32
API error 10061} Connection refused 08 Dec 14:05:41 [2648] the queue
is empty, quitting...
And D'bridge itself does not have any generic binkp-capable code.
Dbrige is just as much involved in the actions as your Fmail. Ward
uses a separate configfile, but the one dbrigde generates is perfectly well, it works here for almost a year. So harping on dbridge is a
waste of time.
Dbrigde is a scanner, tosser, message editor, scheduler and pots
mailer. There is no other connection that BSO file area and semaphore files.
The last few versions were just addition of useless options.
Almost nay available version shoild wordk with ipv6 as long as it is
compiled in.
I was not harping on D'Bridge, I was trying to pinpoint the source of the problem by elimination. The inner workings of D'Bridge have always been treaetd as if they are state secrets. So I had to work on a minimum of knowledge.
The way it looks now, is that the version of binkd that Ward used was the exception. Despite the fact that it showed the IPv6 compile option was used, it would not do IPv6. So replacing it was NOT useless in tracing
the problem.
This is the version I am about to use now ...
************************************************************************* Binkd 1.1a-99 (Jun 25 2018 22:50:08/Win32)
Compilation flags: mingw32, zlib, bzlib2, perldl, https, ntlm, amiga_4d_outbound, bwlim, ipv6, af_force.
Facilities: fts5004 ipv6 *************************************************************************
I just checked and it seems I now have outgoing IPv6-connections with
you, Kees, Wilfred, Tommi...
This is the version I am about to use now ...
********************************************************************** Binkd 1.1a-99 (Jun 25 2018 22:50:08/Win32) Compilation flags:
mingw32, zlib, bzlib2, perldl, https, ntlm, amiga_4d_outbound, bwlim, ipv6, af_force.
Facilities: fts5004 ipv6 **********************************************************************
This is the version I am about to use now ...
***********************************************************************
** Binkd 1.1a-99 (Jun 25 2018 22:50:08/Win32) Compilation flags:
mingw32, zlib, bzlib2, perldl, https, ntlm, amiga_4d_outbound, bwlim,
ipv6, af_force.
Facilities: fts5004 ipv6
***********************************************************************
**
I just checked and it seems I now have outgoing IPv6-connections with you, Kees, Wilfred, Tommi...
I just checked and it seems I now have outgoing IPv6-connections
with you, Kees, Wilfred, Tommi...
Should you try? http://download.binkd.org/
binkd/1.1a-94/Win32
So I think that's a goodone.
binkd/1.1a-94/Win32
So I think that's a goodone.
It is 2 years old.
Did you find out how to punch a hole in the IPv6 firewall of your router yet?
MvdV> Did you find out how to punch a hole in the IPv6 firewall of your MvdV> router yet?
Do you know that your node does not respond for several days on IPv4 to?
MvdV> Did you find out how to punch a hole in the IPv6 firewall of
your
MvdV> router yet?
Do you know that your node does not respond for several days on IPv4 to?
Interesting.
We know that I do not have incoming IPv6 ... yet. And now you're telling me I have no incoming IPv4 either.
Then where does your message come from?
If I look in log I see ...
- 10 Dec 00:00:08 [7604] incoming from 77.243.226.170 (2075)
- 10 Dec 00:00:10 [7604] incoming from 80.211.41.104 (35090)
- 10 Dec 00:00:29 [7604] incoming from 77.243.226.167 (3217)
- 10 Dec 00:01:06 [7604] incoming from 96.49.112.45 (53456)
- 10 Dec 00:02:02 [7604] incoming from 77.243.226.167 (3221)
- 10 Dec 00:03:13 [7604] incoming from 83.130.140.161 (37474)
- 10 Dec 00:04:05 [7604] incoming from 172.104.248.211 (38304)
- 10 Dec 00:09:02 [7604] incoming from 31.200.173.60 (39351)
... Isn't that all IPv4 ?
Yep. Now I have IPv4 connection to you to. On a few days my node can't
get IP from many-glacier.dyndns.org.
Did you find out how to punch a hole in the IPv6 firewall of your
router yet?
No time.
Did you find out how to punch a hole in the IPv6 firewall of your Mv>Mv>> router yet?
No time.
Any progress?
Any progress?
Nope. Low on the agenda for the moment.
Nope. Low on the agenda for the moment.
Is it above or below a totally insignificant chair election, that's
been done with a long time ago, on that agenda?
Did you find out how to punch a hole in the IPv6 firewall of
your router yet?
No time.
Any progress?
Nope. Low on the agenda for the moment.
Nope. Low on the agenda for the moment.
That was a month ago. Any progress?
Nope. Low on the agenda for the moment.
That was a month ago. Any progress?
Nope. Still the same ... low on the agenda.
Nope. Still the same ... low on the agenda.
Another month has passed. Any progress?
Nope. Still the same ... low on the agenda.
So far with IPv4 everything went fine, but what is the next step now?
I think there may be a problem there. The router is ISP-provided and
pretty good. However there are 3 lvels to log into "User", "Admin" and
"Expert" and they only give-out the password for "User".
ISP-provided routers are usually not-pretty-good, because "they" are
in control, not you.
I've got one Huawei LTE router with ISP branded firmware which doesn't allow incoming IPv6 not matter what. Even with "admin" rights...
I just checked and it seems I now have outgoing IPv6-connections with
you, Kees, Wilfred, Tommi...
And Benni ...
MvdV> Another month has passed. Any progress?Nope. Still the same ... low on the agenda.
Another month has passed. Any progress?
Another month has passed. Any progress?Nope. And as I'm leaving for the US in 48hrs and will not return
before Aug.6th at the earliest, yet another month will pass.
Another month has passed. Any progress?
Nope. And as I'm leaving for the US in 48hrs and will not return
before Aug.6th at the earliest, yet another month will pass.
Slowpokes are sooooooo sloooooooow...
Nope. Still the same ... low on the agenda.
Another month has passed. Any progress?
Nope. Still the same ... low on the agenda.
Another month has passed. Any progress?
No. Guess I'm not really trying ... One day I will.
No. Guess I'm not really trying ... One day I will.
Another three months have passed. Is this the day?
No. Guess I'm not really trying ... One day I will.
Another three months have passed. Is this the day?
Another three months have passed. Is this the day?
The ISP is still refusing me the password for the higher-level in the company installed router to deal with this.
Their position is if they release such passwords that the customer may destroy the set-up.
I've also noticed they are able to upload new firmware and reboot the modem/router from a central site. If they give me the password I could change it and deny them the option to auto-update firmware. They want
to avoid that too.
Are you really stuck with Proximus?
The ISP is still refusing me the password for the higher-level in the company installed router to deal with this.
Their position is if they release such passwords that the customer may destroy the set-up.
I've also noticed they are able to upload new firmware and reboot the modem/router from a central site. If they give me the password I could change it and deny them the option to auto-update firmware. They want to avoid that too.
Hi Ward!
Friday December 25 2020 12:36, you wrote to Michiel van der Vlist:
The ISP is still refusing me the password for the higher-level in the
company installed router to deal with this.
Their position is if they release such passwords that the customer may
destroy the set-up.
I've also noticed they are able to upload new firmware and reboot the
modem/router from a central site. If they give me the password I could
change it and deny them the option to auto-update firmware. They want to
avoid that too.
When I ran into a similar problem at my cousin's house, the provider generally closed access to the settings of his router, I just made a reset to the factory configuration and set everything up myself, not forgetting to completely close all incoming connections, except for the ICMP.
Have a nice night.
Stas Mishchenkov.
Great idea.
Also, if possible, ask the ISP to put their equipment in bridge mode
and just put your own router behind their gear.
Hi Andrei!
Sunday December 27 2020 16:09, you wrote to me:
Great idea.
Also, if possible, ask the ISP to put their equipment in bridge mode
and just put your own router behind their gear.
If this is different, then you should think about changing the provider.
Have a nice night.
Stas Mishchenkov.
Sysop: | Weed Hopper |
---|---|
Location: | Clearwater, FL |
Users: | 14 |
Nodes: | 6 (0 / 6) |
Uptime: | 234:16:19 |
Calls: | 55 |
Calls today: | 1 |
Files: | 50,128 |
D/L today: |
43 files (6,535K bytes) |
Messages: | 275,434 |