Hello everybody!

with help of https://internet.nl/site/fido.unen.net/3038781/ i found out that none of my nameservers supported ipv6 so i added ipv6 AAAA records for the nameservers and updated the glue records and now it's better.

So does a recursive DNS query fallback into ipv4 if none of the nameservers for a domain have an ipv6 address? Because people could still find my ipv6 AAAA record on my ipv4-only nameservers...

Just curious,
Regards,
Floris


--- GoldED+/LNX 1.1.5--b20170303
* Origin: ----> Fidian on Azure West-Europe (Holland) IPV6. (2:280/2050)

Hello Floris,

On Wednesday November 13 2024 13:20, you wrote to All:

with help of https://internet.nl/site/fido.unen.net/3038781/ i found
out that none of my nameservers supported ipv6 so i added ipv6 AAAA records for the nameservers and updated the glue records and now it's better.

Great!

So what do http://test-ipv6.com and https://ipv6-test.com say?

So does a recursive DNS query fallback into ipv4 if none of the nameservers for a domain have an ipv6 address? Because people could
still find my ipv6 AAAA record on my ipv4-only nameservers...

Don't confuse the accesability with the content of name servers. Most name servers that are accesible by IPv4 only do respond with an AAAA record when that is present for the requested host.

But of course we should all prepare to function in an IPv6 only environment, so the use of name servers that are accesable via IPv6 is much preferred.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

Hello Michiel!

13 Nov 24 13:39, you wrote to Floris van Unen:

Its great to see progress on enabling IPv6 for your nameservers, Floris! Adding AAAA records and updating the glue records is a smart move to enhance IPv6 compatibility.

Regarding your question on IPv6 fallback behavior: If a DNS client (resolver) attempts to resolve a domain over IPv6 and finds that none of the authoritative nameservers for that domain have an IPv6 address, it will indeed fall back to IPv4, provided the client has IPv4 connectivity and the domains nameservers are reachable over IPv4. This fallback ensures accessibility for IPv4-only or mixed IPv4/IPv6 environments but doesnt fully support the vision of an IPv6-only future.

As MV pointed out, preparing for an IPv6-only environment is crucial. While many current nameservers still offer AAAA records over IPv4, native IPv6 access for your nameservers ensures seamless support as networks continue moving towards IPv6-exclusive setups. Additionally, by having both IPv4 and IPv6 connectivity, you improve redundancy and are better positioned to handle requests from diverse client networks.

Using sites like http://test-ipv6.com and https://ipv6-test.com is a fantastic way to confirm full IPv6 functionality. These tools not only check your IPv6 reachability but also evaluate DNS resolution to verify whether queries return IPv6 addresses where available. Its worth checking them out post-configuration to verify everything is set up correctly.

Nice work on pushing IPv6 adoption forward!

Hello Floris,

On Wednesday November 13 2024 13:20, you wrote to All:

with help of https://internet.nl/site/fido.unen.net/3038781/ i
found out that none of my nameservers supported ipv6 so i added
ipv6 AAAA records for the nameservers and updated the glue
records and now it's better.

Great!

So what do http://test-ipv6.com and https://ipv6-test.com say?

So does a recursive DNS query fallback into ipv4 if none of the
nameservers for a domain have an ipv6 address? Because people
could still find my ipv6 AAAA record on my ipv4-only
nameservers...

Don't confuse the accesability with the content of name servers. Most
name servers that are accesible by IPv4 only do respond with an AAAA record when that is present for the requested host.

But of course we should all prepare to function in an IPv6 only environment, so the use of name servers that are accesable via IPv6 is much preferred.

Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

David

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: SkyNet BBS | telnet://bbs.skynetbbs.com:20023 (4:930/1)

Hello David,

On Saturday November 16 2024 22:18, you wrote to All:

Its great to see progress on enabling IPv6 for your nameservers,
Floris! Adding AAAA records and updating the glue records is a smart
move to enhance IPv6 compatibility.

Thanks for you elaborate response.

From your response I presume that you yourself have IPv6 capability. I can not test if your node answers on IPv6, you are not (yet) in the nodelist, so I do not haven your contact data. If you publish your connect info here, I can try to make an IPv6 connection with your system and if hat succeeds, I will enter you in the list of IPv6 nodes as a prospective member of the Fiodonet IPv6 club.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

Hello Michiel!

17 Nov 24 09:56, you wrote to me:

Hello David,

On Saturday November 16 2024 22:18, you wrote to All:

Its great to see progress on enabling IPv6 for your nameservers,
Floris! Adding AAAA records and updating the glue records is a
smart move to enhance IPv6 compatibility.

Thanks for you elaborate response.

From your response I presume that you yourself have IPv6 capability. I
can not test if your node answers on IPv6, you are not (yet) in the nodelist, so I do not haven your contact data. If you publish your
connect info here, I can try to make an IPv6 connection with your
system and if hat succeeds, I will enter you in the list of IPv6 nodes
as a prospective member of the Fiodonet IPv6 club.

Hallo again Michael, yes, I'm coming back to fido after 30 years and indeed my provider assigned me a half-ass /64, which they consider is more than enough for a home user, so I had to decide what I wanetd to have IPv6 connectivity for my home lab or my house, so the LAB won.

With regards to your question, yes I'm on bbs.skynetbbs.com which points to 2800:e2:5480:60::20, I think I created the AAAA on my DNS control panel, so if you poll it should let you in, word of caution my BBS is still very stock but that's because I've found it difficult to modify Mystic default theme and menus.

I'll try to be active on this area because I'm an IPv6 advocate and very pasionate about it, in fact I teach IPv6 classes for "living".

Regards--

Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

David


--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: SkyNet BBS | telnet://bbs.skynetbbs.com:20023 (4:930/1)

Hello David,

On Sunday November 17 2024 14:23, you wrote to me:

With regards to your question, yes I'm on bbs.skynetbbs.com which
points to 2800:e2:5480:60::20, I think I created the AAAA on my DNS control panel, so if you poll it should let you in, word of caution my
BBS is still very stock but that's because I've found it difficult to modify Mystic default theme and menus.

I tried it:

+ 21:25 [1060] call to 4:930/1@fidonet
21:25 [1060] trying bbs.skynetbbs.com [2800:e2:5480:60::2]...
? 21:26 [1060] connection to 4:930/1@fidonet failed: {W32
API error 10060} Connection timed out
21:26 [1060] trying bbs.skynetbbs.com [181.142.97.252]...
21:26 [1060] connected
+ 21:26 [1060] outgoing session with bbs.skynetbbs.com:24554 [181.142.97.252]
- 21:26 [1060] OPT CRAM-MD5-d622da334d8cd27747b0356c9cb4cd70
+ 21:26 [1060] Remote requests MD mode
- 21:26 [1060] SYS SkyNet BBS
- 21:26 [1060] LOC Medellin, Colombia
- 21:26 [1060] ZYZ DavidG
- 21:26 [1060] TIME Sun, 17 Nov 2024 20:26:08 -0500
- 21:26 [1060] VER Mystic/1.12A48 binkp/1.0
- 21:26 [1060] BUILD 2023/01/15 15:29:47 Windows/32
+ 21:26 [1060] addr: 21:3/188@fsxnet (n/a or busy)
+ 21:26 [1060] addr: 3:633/2744.188@fidonet
+ 21:26 [1060] addr: 4:930/1@fidonet
+ 21:26 [1060] addr: 4:930/0@fidonet
+ 21:26 [1060] addr: 4:93/0@fidonet
- 21:26 [1060] QSIZE 0 files 0 bytes
+ 21:26 [1060] done (to 4:930/1@fidonet, OK, S/R: 0/0 (0/0 bytes))
21:26 [1060] session closed, quitting...
21:26 [4008] the queue is empty, quitting...
D:\FIDO6\BINKD>

So no IPv6 connect yet. The first thing to look at would be the firewall. You should create an IPv6 pinhole fo port 24554.

I'll try to be active on this area because I'm an IPv6 advocate and
very pasionate about it, in fact I teach IPv6 classes for "living".

Great!


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

Hi Michiel,

On 2024-11-17 21:27:14, you wrote to David Gonzalez:

With regards to your question, yes I'm on bbs.skynetbbs.com which
points to 2800:e2:5480:60::20,

^^
MvdV> 21:25 [1060] trying bbs.skynetbbs.com [2800:e2:5480:60::2]...
^

I think you forgot a '0' !?

MvdV> ? 21:26 [1060] connection to 4:930/1@fidonet failed: {W32
MvdV> API error 10060} Connection timed out

Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

Hello David,

Sunday November 17 2024 21:27, I wrote to you:

So no IPv6 connect yet. The first thing to look at would be the
firewall. You should create an IPv6 pinhole fo port 24554.

I see you goy it fixed already:

+ 22:06 [4472] call to 4:930/1@fidonet
22:06 [4472] trying bbs.skynetbbs.com [2800:e2:5480:60::2]...
22:06 [4472] connected
+ 22:06 [4472] outgoing session with bbs.skynetbbs.com:24554
[2800:e2:5480:60::2]
- 22:06 [4472] OPT CRAM-MD5-566231661606aa412c74fee39a672079
+ 22:06 [4472] Remote requests MD mode
- 22:06 [4472] SYS SkyNet BBS
- 22:06 [4472] LOC Medellin, Colombia
- 22:06 [4472] ZYZ DavidG
- 22:06 [4472] TIME Sun, 17 Nov 2024 21:06:38 -0500
- 22:06 [4472] VER Mystic/1.12A48 binkp/1.0
- 22:06 [4472] BUILD 2023/01/15 15:29:47 Windows/32
+ 22:06 [4472] addr: 21:3/188@fsxnet (n/a or busy)
+ 22:06 [4472] addr: 3:633/2744.188@fidonet
+ 22:06 [4472] addr: 4:930/1@fidonet
+ 22:06 [4472] addr: 4:930/0@fidonet

So congratulations and welcome to the Fidonet IPv6 club!


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

Hello Wilfred,

On Sunday November 17 2024 21:57, you wrote to me:

On 2024-11-17 21:27:14, you wrote to David Gonzalez:

With regards to your question, yes I'm on bbs.skynetbbs.com
which points to 2800:e2:5480:60::20,

^^

MvdV>> 21:25 [1060] trying bbs.skynetbbs.com [2800:e2:5480:60::2]...

^

I think you forgot a '0' !?

No, the "2" is correct, see next message.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

Hello David,

Sunday November 17 2024 22:07, I wrote to you:

So congratulations and welcome to the Fidonet IPv6 club!

Normally the update for the list as published in Fidonews is hatched at Sunday 22:00 my local time (21:00 UTC). so you just missed that.

But I rehatched it and if all goes well, you will be in the list of tomorrows Fidonews.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

Hello David,

On Sunday November 17 2024 14:23, you wrote to me:

Hallo again Michael, yes, I'm coming back to fido after 30 years and indeed my provider assigned me a half-ass /64, which they consider is
more than enough for a home user, so I had to decide what I wanetd to
have IPv6 connectivity for my home lab or my house, so the LAB won.

Just a /64 is very scroogy. Best Opeating Practice has it that customers should at least get a /56. many give a /48.

Are you sure you can't get more than just a /64? If not, for me that would be a reason to take my bussines elsewhere...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

Hello David,

On Sunday November 17 2024 22:52, you wrote to me:

So congratulations and welcome to the Fidonet IPv6 club!

Yup, but I just changed the IPv6 to match my (local) ipv4, so it's now ::20, give it a go and it should also reply.

Hmmm... That didn't work...

+ 11:12 [4756] call to 4:930/1@fidonet
11:12 [4756] trying bbs.skynetbbs.com [2800:e2:5480:60::2]...
? 11:12 [4756] connection to 4:930/1@fidonet failed: {W32 API error 10060} Conne
ction timed out
11:12 [4756] trying bbs.skynetbbs.com [181.142.97.252]...
? 11:12 [4756] connection to 4:930/1@fidonet failed: {W32 API error 10061} Conne
ction refused
11:12 [4756] trying 2800:e2:5480:60::20 [2800:e2:5480:60::20]...
? 11:12 [4756] connection to 4:930/1@fidonet failed: {W32 API error 10061} Conne
ction refused
11:12 [5792] the queue is empty, quitting...

1) You forgot to update the AAAA record for bbs.skynetbbs.com.

2) It looks like you also forgot to restart Mystic as it is not answereing at all on any IP.

I also had to disable SLAAC from My Mikrotik edge so did not get
EUI-64.

OK.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

Hola Michiel!, saludo cordial

18 Nov 24 11:13, tu escribi(ste) a ti:

Hello David,

On Sunday November 17 2024 22:52, you wrote to me:

So congratulations and welcome to the Fidonet IPv6 club!

Yup, but I just changed the IPv6 to match my (local) ipv4, so
it's now
::20, give it a go and it should also reply.

Hmmm... That didn't work...

+ 11:12 [4756] call to 4:930/1@fidonet
11:12 [4756] trying bbs.skynetbbs.com [2800:e2:5480:60::2]...
? 11:12 [4756] connection to 4:930/1@fidonet failed: {W32 API error
10060} Conne ction timed out 11:12 [4756] trying bbs.skynetbbs.com [181.142.97.252]... ? 11:12 [4756] connection to 4:930/1@fidonet
failed: {W32 API error 10061} Conne ction refused 11:12 [4756] trying 2800:e2:5480:60::20 [2800:e2:5480:60::20]... ? 11:12 [4756] connection
to 4:930/1@fidonet failed: {W32 API error 10061} Conne ction
refused 11:12 [5792] the queue is empty, quitting...

1) You forgot to update the AAAA record for bbs.skynetbbs.com.

I did indeed, that plus I use a shitty provider namecheap, but it's updated now.

2) It looks like you also forgot to restart Mystic as it is not
answereing at all on any IP.

I also had to disable SLAAC from My Mikrotik edge so did not get
EUI-64.

OK.

Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

--
Saludos/Kind Regards
David
- SysOp SkyNet BBS
- telnet://bbs.skynet.com:20023
SEEN-BY: 902/26 930/1 341/66 900/106 902/19 280/464 229/426 0/0 90/0 900/0 SEEN-BY: 902/0

Hola Michiel!, saludo cordial

18 Nov 24 11:13, tu escribi(ste) a ti:

Hello David,

On Sunday November 17 2024 22:52, you wrote to me:

So congratulations and welcome to the Fidonet IPv6 club!

Telia Denmark

Network: AS3308 - Telia Danmark
Router: Copenhagen PowCph
Command: ping 2800:e2:5480:60::20 rapid

ping router 1010000 2800:e2:5480:60::20 rapid
PING 2800:e2:5480:60::20 56 data bytes
!!!!!
---- 2800:e2:5480:60::20 PING Statistics ----
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 158ms, avg = 160ms, max = 163ms, stddev = 1.65ms

Yup, but I just changed the IPv6 to match my (local) ipv4, so
it's now
::20, give it a go and it should also reply.

Hmmm... That didn't work...

+ 11:12 [4756] call to 4:930/1@fidonet
11:12 [4756] trying bbs.skynetbbs.com [2800:e2:5480:60::2]...
? 11:12 [4756] connection to 4:930/1@fidonet failed: {W32 API error
10060} Conne ction timed out 11:12 [4756] trying bbs.skynetbbs.com [181.142.97.252]... ? 11:12 [4756] connection to 4:930/1@fidonet
failed: {W32 API error 10061} Conne ction refused 11:12 [4756] trying 2800:e2:5480:60::20 [2800:e2:5480:60::20]... ? 11:12 [4756] connection
to 4:930/1@fidonet failed: {W32 API error 10061} Conne ction
refused 11:12 [5792] the queue is empty, quitting...

1) You forgot to update the AAAA record for bbs.skynetbbs.com.

2) It looks like you also forgot to restart Mystic as it is not
answereing at all on any IP.

I also had to disable SLAAC from My Mikrotik edge so did not get
EUI-64.

OK.

Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

--
Saludos/Kind Regards
David
- SysOp SkyNet BBS
- telnet://bbs.skynet.com:20023
SEEN-BY: 902/26 930/1 341/66 900/106 902/19 280/464 229/426 0/0 90/0 900/0 SEEN-BY: 902/0

Hello David,

On Monday November 18 2024 16:10, you wrote to me:

1) You forgot to update the AAAA record for bbs.skynetbbs.com.

I did indeed, that plus I use a shitty provider namecheap, but it's updated now.

You got it fixed indeed:

+ 18:09 [4124] call to 4:930/1@fidonet
18:09 [4124] trying bbs.skynetbbs.com [2800:e2:5480:60::20]...
18:09 [4124] connected
+ 18:09 [4124] outgoing session with bbs.skynetbbs.com:24554
[2800:e2:5480:60::20]
- 18:09 [4124] OPT CRAM-MD5-61e9a525e53b71a5e5b137db6d9a7763
+ 18:09 [4124] Remote requests MD mode
- 18:09 [4124] SYS SkyNet BBS
- 18:09 [4124] LOC Medellin, Colombia
- 18:09 [4124] ZYZ DavidG
- 18:09 [4124] TIME Mon, 18 Nov 2024 17:09:06 -0500
- 18:09 [4124] VER Mystic/1.12A48 binkp/1.0
- 18:09 [4124] BUILD 2023/01/15 15:29:47 Windows/32
+ 18:09 [4124] addr: 21:3/188@fsxnet (n/a or busy)
+ 18:09 [4124] addr: 3:633/2744.188@fidonet
+ 18:09 [4124] addr: 4:930/1@fidonet
+ 18:09 [4124] addr: 4:930/0@fidonet
+ 18:09 [4124] addr: 4:93/0@fidonet
- 18:09 [4124] QSIZE 0 files 0 bytes
+ 18:09 [4124] done (to 4:930/1@fidonet, OK, S/R: 0/0 (0/0 bytes))
18:09 [4124] session closed, quitting...
18:09 [4992] the queue is empty, quitting...
D:\FIDO6\BINKD>

And for completeness I also tested your IPv4:

+ 18:08 [1236] call to 4:930/1@fidonet
18:08 [1236] trying bbs.skynetbbs.com [181.142.97.252]...
18:08 [1236] connected
+ 18:08 [1236] outgoing session with bbs.skynetbbs.com:24554 [181.142.97.252]
- 18:08 [1236] OPT CRAM-MD5-39c9548164f002ba1edc734b3a24e065
+ 18:08 [1236] Remote requests MD mode
- 18:08 [1236] SYS SkyNet BBS
- 18:08 [1236] LOC Medellin, Colombia
- 18:08 [1236] ZYZ DavidG
- 18:08 [1236] TIME Mon, 18 Nov 2024 17:08:28 -0500
- 18:08 [1236] VER Mystic/1.12A48 binkp/1.0
- 18:08 [1236] BUILD 2023/01/15 15:29:47 Windows/32
+ 18:08 [1236] addr: 21:3/188@fsxnet (n/a or busy)
+ 18:08 [1236] addr: 3:633/2744.188@fidonet
+ 18:08 [1236] addr: 4:930/1@fidonet
+ 18:08 [1236] addr: 4:930/0@fidonet
+ 18:08 [1236] addr: 4:93/0@fidonet
- 18:08 [1236] QSIZE 0 files 0 bytes
+ 18:08 [1236] done (to 4:930/1@fidonet, OK, S/R: 0/0 (0/0 bytes))
18:08 [1236] session closed, quitting...
18:08 [2920] the queue is empty, quitting...
D:\FIDO6\BINKD>



Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

Hello David,

On Sunday November 17 2024 22:55, you wrote to me:

Are you sure you can't get more than just a /64? If not, for me
that would be a reason to take my bussines elsewhere...

Yup, trust me, been there, done that, but that unfortunately is the
only one that you can get to do bridge mode on the CPE for IPv4,

What type of fysical connection do you have? DSL over 600 Ohm 2 wire? DOCSIS over coax? Opical over glasfiber?

I am in the fortunate position to have a choice between the three. Although DSL is no longer interesting compared to coax or fiberglass.

we're way behind down here in South America (except Brazil) when it
comes to v6, as I said I throw hate everytime I can to those grumpy old-men with their brains stuck on IPv4 and the /30 and v4 VLSM
practices migrated to IPv6.

There are only two IPv6 capable Fidonet nodes in Z4. The first is your ZC elect Fernando Toledo. You are the second.

The otehr issue I do not want to rn n into is using Tunnelbroker, it's slow because of it's 6to4 tunnel nature, but it's an alternative, I do like HE, but being a VPN and its inherent drawbacks drives me away.

He.net has been providing a fantatic service to the IPv6 community. I have had an he.net tunnel for many years. When I finally got native IPv6 in 2016 I did not need them any more. But I am still gratefull for here fantastic service. They even managed to get the "sage T-shirt" delivered exactly on the day of my 70th birthday!


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

Hola Michiel!, saludo cordial

19 Nov 24 11:37, tu escribi(ste) a ti:

Hello David,

What type of fysical connection do you have? DSL over 600 Ohm 2 wire? DOCSIS over coax? Opical over glasfiber?

Providers here are weird, Mine is called Tigo and it's DOCSIS HFC but they do alow IPv4 bridge mode, Claro (big bad monster), DOCSIS too and also offer IOPv6 but meh, etb fiber but no IPv6, so here in my country we're way behind and those big companies give balls about customers and their needs. I'm even afraid of asking becaus eit frusrates and angers me even more.

I am in the fortunate position to have a choice between the three. Although DSL is no longer interesting compared to coax or fiberglass.

I am let's say only coax with two providers becaus eI'm on an apartment complex and tehes a layer of let's say *corruption* where a single (big) provider pays the administration of teh building to keep other providers out.

we're way behind down here in South America (except Brazil) when
it comes to v6, as I said I throw hate everytime I can to those
grumpy old-men with their brains stuck on IPv4 and the /30 and v4
VLSM practices migrated to IPv6.

There are only two IPv6 capable Fidonet nodes in Z4. The first is your
ZC elect Fernando Toledo. You are the second.

Yup, I link to Fernando for my newly (restored) node and I was not foing to be IPv4 only node, so I gave it a go and here we are. Like I said, I love IPv4 and that's one of the topics that I'm pasionate about teaching and researching.

The otehr issue I do not want to rn n into is using Tunnelbroker,
it's slow because of it's 6to4 tunnel nature, but it's an
alternative, I do like HE, but being a VPN and its inherent
drawbacks drives me away.

He.net has been providing a fantatic service to the IPv6 community. I
have had an he.net tunnel for many years. When I finally got native
IPv6 in 2016 I did not need them any more. But I am still gratefull
for here fantastic service. They even managed to get the "sage
T-shirt" delivered exactly on the day of my 70th birthday!

Lovely, I got one of those myself but I lost it, that was my first real approach to v6, I fidled with OpenWRT, dd-wrty all of that until I landed my first Mikrotik and then I just fell inlove with those devices and what tehy could do.

Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

--
Saludos/Kind Regards
David
- SysOp SkyNet BBS
- telnet://bbs.skynet.com:20023
SEEN-BY: 902/26 930/1 341/66 900/106 902/19 280/464 229/426 900/102 4/0 90/0 SEEN-BY: 900/0 902/0