:) I'm working for the local public library, a part of the
municipality.
And as I'm living in Germany, I'm happy that I do have a working
computer and not only a typewriter and a fax machine. Our library
building still has some IBM Type-1 cabling (from Token Ring-days) that AN>> we're using for Ethernet via some adapters... I don't think that IPv6
days will come soon here...
And I suppose when push come to shove 1000::/4 coild also be used.
And even 0::/4 with the exeption of 0::/64.
BTW what is already in use within 0000::/1 and 8000::/1 besides
2000::/3?
There are a lot of better options to run a server than a home
connection IMHO.
Most people in Russia cannot even get one *native* IPv6 address for
their home connection, let alone a static one. Well, probably not most
but the majority, I'm for one. I have not noticed ISPs here willing to adopt IPv6.
Mobile operators (mts.ru for sure) give you a dynamic IPv6 address for each mobile device by default (to go together with an RFC1918 IPv4 address).
Many ISPs only offer a /48 to business accounts. For consumer
accounts it is often a /56. A /56 is plenty for most I'd say.
Yeah, I can't see myself using my /56 in my lifetime. What will I do
with 256 networks? :)
There are arguments for more than a /64 for residential use. That
allows for different subnets with different security profiles, such as
for IoT, the car, whatever other network of smart devices you want.
For many, I suspect a /60 would be sufficient.
There are arguments for more than a /64 for residential use. ThatSure ... I agree. My reply was more from the ISP point of view.
allows for different subnets with different security profiles, such
as for IoT, the car, whatever other network of smart devices you
want. For many, I suspect a /60 would be sufficient.
With 1 v6 subnet it is easy, you just announce the subnet.
If you allow more, you need a way to configure them. (eg. VLANs,
different subnet on different LAN port, etc.)
That is added complexity for a low cost product, where most of your residential customers will have no clue what this is all about. So
it makes more sense to offer that on higher tier (and more expensive) services.
Sure ... I agree. My reply was more from the ISP point of view.
With 1 v6 subnet it is easy, you just announce the subnet.
No: when you need to provide the customer with IPv6, you assign one
fixed address for a link, and route a /64 subnet through that address.
Plastic routers (those sold for 20 EUR) deal with this setup just
fine.
If you allow more, you need a way to configure them. (eg. VLANs,
different subnet on different LAN port, etc.)
Or simply route more /64 subnets through that address. Or /56 at once.
That is added complexity for a low cost product, where most of
your residential customers will have no clue what this is all
about. So it makes more sense to offer that on higher tier (and
more expensive) services.
That violates the KISS principle.
With 1 v6 subnet it is easy, you just announce the subnet.No: when you need to provide the customer with IPv6, you assign one
fixed address for a link, and route a /64 subnet through that address. Plastic routers (those sold for 20 EUR) deal with this setup just
fine.
If you allow more, you need a way to configure them. (eg. VLANs,Or simply route more /64 subnets through that address. Or /56 at once.
different subnet on different LAN port, etc.)
That is added complexity for a low cost product, where most ofThat violates the KISS principle.
your residential customers will have no clue what this is all
about. So it makes more sense to offer that on higher tier (and
more expensive) services.
That violates the KISS principle.Indeed. It is easier to just give every customer a /56. And just route
the first /64 to the LAN, so that the user need not configure anything
if he only needs one /64. And the provider does not need to configure anything if the customer needs more.
At least the use of DS-Lite ISP connections makes it a little more apparent to the customers that IPv4 has some disadvantages over IPv6 nowadays.
But I guess the vast majority of 'consumers' who only use simple web browsing, email and media streaming services won't notice it anyway.
So in theory, the transition for those consumers can continue as long
as the services that most people use are reachable via IPv6.
:) I'm working for the local public library, a part of the
municipality.
No, that's my full time job (and I get payed - lucky me *g*).
And although I'm in the IT department of the library, there are other
departments 'above' us who run the city-wide IT.
Well, you're right (and yes, I know that even via 'real' Token Ring,
you can use IPv6 *g*).
My point was more in the direction of the mentality of German
bureaucracy. Changes here take ages. We are still stuck to Microsoft (Windows, Office, AD... all the nice things that malware loves) and
until this year we're still using Lotus Notes (Exchange/Outlook will follow ... *shiver*).
And I'm trying to update things. We've moved out library management
system to Linux servers some years ago (and now it's running much more stable and reliable than before) and are updating hardware as good as
we can. But as said before, we're not on the top of the hierarchy in
the municipality, we are dependant on others who run the network. So
we can't move to IPv6 on our own :)
That's always a good idea!
I could set up a VPN tunnel to one of my vServers, or use some kind of service that you mentioned, to be reachable from outside again. Let's
see how all this will turn out.
That violates the KISS principle.
Indeed. It is easier to just give every customer a /56. And just
route the first /64 to the LAN, so that the user need not
configure anything if he only needs one /64. And the provider
does not need to configure anything if the customer needs more.
It is even simpler to just to hand out a /64 ;)
On 01-16-22 11:35, Richard Menedetter wrote to Tony Langdon <=-
There are arguments for more than a /64 for residential use. That
allows for different subnets with different security profiles, such as
for IoT, the car, whatever other network of smart devices you want.
For many, I suspect a /60 would be sufficient.
Sure ... I agree.
My reply was more from the ISP point of view.
With 1 v6 subnet it is easy, you just announce the subnet.
If you allow more, you need a way to configure them. (eg. VLANs,
different subnet on different LAN port, etc.)
That is added complexity for a low cost product, where most of your residential customers will have no clue what this is all about.
So it makes more sense to offer that on higher tier (and more
expensive) services.
On 01-16-22 18:06, Michiel van der Vlist wrote to Tony Langdon <=-
Neither can I, but I can imagine some wanting/needing more than a /60. The "rule" should be "give them so much they will never come back for more". That wey they avoid having to make administrative exceptions for some customers. There is enough to give every customer a /56.
I know I can add a router behind the primary router. The main manual setup will be to assign a /64 to the LAN side of that router. The existing router will pick up the advertisements, setup routing and optionally open the firewall for that /64 (so that filtering can be controlled by the second router).
I haven't put that to the test yet, but tempted to give it a try
sometime, as a learning exercise. :)
Neither can I, but I can imagine some wanting/needing more than
a /60. The "rule" should be "give them so much they will never
come back for more". That wey they avoid having to make
administrative exceptions for some customers. There is enough to
give every customer a /56.
Yeah, there is that argument. Over time, I can see myself using 3 or
4 /64s. More than 16 is unlikely, unless I start doing a lot of funky
VPN stuff. ;)
It is for you, if your provider only gives you the bare minimum, and
tries to sell you more... :-/
It is for you, if your provider only gives you the bare minimum, and
tries to sell you more... :-/
Except when they think they can make an extra buck... :-/
Except when they think they can make an extra buck... :-/
No, that's my full time job (and I get payed - lucky me *g*).
And although I'm in the IT department of the library, there are other
departments 'above' us who run the city-wide IT.
Well, you're right (and yes, I know that even via 'real' Token Ring,
you can use IPv6 *g*).
That isn't always as simpel as it sounds...
There are probably lots of places where providers still more or less
have a monopoly.
On 01-19-22 12:21, Michiel van der Vlist wrote to Tony Langdon <=-
I did just that a couple of years ago to test prefix delegation. I connected a second router behind my primary router and IIRC it got a
/61 out of the /56 assigned to me. Of that /61, one /64 was routed to
the local LAN of the second router. I presume the process allows for cascading routers until the /56 is exhausted, but I did not explore
that. I was satisfied that I demonstrated prefix delegation worked.
On 01-19-22 12:36, Michiel van der Vlist wrote to Tony Langdon <=-
We also have to get rid of IPv4 think. On top of that list are:
1) NAT is not a security feature.
2) There is no shortage of addresses. Address space is no longer a
scarce commodity.
With the mind still in IPv4 think mode, giving out a /56 to everyone while the vast majority will get no further than using 1 or 2% of that looks like a terrible waste.
Then consider that "waste" is only an issue if there is shortage. With IPv6 there is no shortage of addreses. Thinking "waste" is IPv4 think.
We have to get rid of that.
Same here. The IPv6 connection for my BBS also had problems on friday
because Dynv6 'forgot' the AAAA record that I've configured - but it
seems to be a known problem. Maybe I rewrite the update script (and
recreate the AAAA record on every prefix change) or switch to my own
dyndns solution...
MvdV>> We patiently wait... ;-) Please share your experience with us.Same here. The IPv6 connection for my BBS also had problems on
friday because Dynv6 'forgot' the AAAA record that I've configured
I just noticed that Dynv6 lost my AAAA record again, so I chose to
update my update script. Dynv6 is offering the use of 'nsupdate',
and as I'm already using nsupdate for my own DynDNS solution, I just added a nsupdate call for my Dynv6 zone to the script.
[...]
I hope that this solves the Dynv6 AAAA problem now - I hope that my
IPv6 prefix changes more often than Dynv6 forgets my AAAA record :)
I just noticed that Dynv6 lost my AAAA record again, so I chose to
update my update script. Dynv6 is offering the use of 'nsupdate', and
as I'm already using nsupdate for my own DynDNS solution, I just added
a nsupdate call for my Dynv6 zone to the script. It's basically
working as noted in the API documentation: https://dynv6.com/docs/apis
List of IPv6 nodes
By Michiel van der Vlist, 2:280/5555
Updated 14 May 2022
Node Nr. Sysop Type Provider Remark
6 2:221/1 Tommi Koivula Native Hetzner f
Node Nr. Sysop Type Provider Remark
6 2:221/1 Tommi Koivula Native Hetzner f
^
Elisa
I think I mentioned about that in this echo some time ago?
6 2:221/1 Tommi Koivula Native Hetzner f
^
Elisa
I think I mentioned about that in this echo some time ago?
Please check your entry. Ig it needs updateing, please let me know.
96 2:5020/736 Egor Glukhov Native RUWEB f
97 2:221/10 Tommi Koivula Native Hetzner f INO4
97 1:266/420 Scott Street Native Comcast OO
99 1:218/850 John Nicpon Native LINODE-US
97 2:221/10 Tommi Koivula Native Hetzner f INO4
97 1:266/420 Scott Street Native Comcast
Just a nit pick, 97 appears twice, though the count is correct. :)
107 1:214/22 Ray Quinn t-6in4 he.net
T-6in4 Static 6in4
f Has a ::f1d0:<zone>:<net>:<node> style host address.
(zone, net, node in decimal notation)
f Has a ::f1d0:<zone>:<net>:<node> style host address.
(zone, net, node in decimal notation)
I once had mine set up for this. For the life of me, I cannot find out what I did to make it work. It seems that I failed to backup the network settings when "upgrading" the last time. Can someone point me in the right direction? Using Debian 11 (bullseye)
f Has a ::f1d0:<zone>:<net>:<node> style host address.
(zone, net, node in decimal notation)
I once had mine set up for this. For the life of me, I cannot find out what I did to make it work. It seems that I failed to backup the network settings when "upgrading" the last time. Can someone point me in the right direction? Using Debian 11 (bullseye)
I once had mine set up for this. For the life of me, I cannot find
out what I did to make it work. It seems that I failed to backup the network settings when "upgrading" the last time. Can someone point me
in the right direction? Using Debian 11 (bullseye)
Tuesday November 01 2022 22:55, you wrote to All:
[fido@brorabbit inbound]$ grep ',5858,' ~/nodelist/nodelist.367 ,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-Unpubli shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4
Tuesday November 01 2022 22:55, you wrote to All:
[fido@brorabbit inbound]$ grep ',5858,' ~/nodelist/nodelist.367
,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-Unpubli
shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4
[fido@brorabbit inbound]$ grep ',5858,' ~/nodelist/nodelist.367
,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-U
npubli shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4
This node is on my desktop computer. It is used for debugging and
testing software.
Tuesday November 01 2022 22:55, you wrote to All:
[fido@brorabbit inbound]$ grep ',5858,' ~/nodelist/nodelist.367
,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-Unpubli
shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4
[fido@brorabbit inbound]$ grep ',5858,' ~/nodelist/nodelist.367
,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-Unpubli
shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4
space after 300
shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4
space after 300
space after 300
It's not my. :)
space after 300
It's not my. :)
Of course not. That would have caused an ;E line in the nodelist, if I recall correctly from my MakeNl reverse engineering days. 8-)
36 2:2452/413 Ingo Juergensmann Native RRBONE-COLO f
08 Oct 22 19:40, you wrote to all:
36 2:2452/413 Ingo Juergensmann Native RRBONE-COLO f
I think this should be changed to 2:240/5413 after net 2:2452 shut
down.
Just noticed this one:
Calling 2:240/5413 (2a01:a700:4629:211:f1d0:2:240:5413:24554)
error (Connection timed out)
IPv4 is ok for this node...
Just noticed this one:Netmail send to sysop.
Calling 2:240/5413 (2a01:a700:4629:211:f1d0:2:240:5413:24554)
error (Connection timed out)
IPv4 is ok for this node...
I have checked all the remaining nodes in the list for connectivity
and as a result more nodes have been flagged 6DWN or even DOWN...
Hi Michiel.
I have checked all the remaining nodes in the list for connectivity
and as a result more nodes have been flagged 6DWN or even DOWN...
What happened to 2:221/10 ?
I have checked all the remaining nodes in the list for
connectivity and as a result more nodes have been flagged 6DWN or
even DOWN...
What happened to 2:221/10 ?
; Alexander Kruglikov T-6in4 Tunnel-Brkr-Net1 f
2:5057/19 = 2a03:1ac0:5571:3a38:f1d0:2:5057:19 (Native, ER-Telecom)AKA 2:5057/0
Missing:
2:5057/19 = 2a03:1ac0:5571:3a38:f1d0:2:5057:19 (Native, ER-Telecom) 2:5075/0 and 2:5075/35 = 2a03:80c0:1:f:f1d0:2:5075:35 (Native, RUWEB) 2:5075/37 = 2a03:c980:db:19:: (Native, IHC)
2:5075/128 = 2a03:e2c0:12a2:0:f1d0:2:5075:128 (T-6in4, IP4Market AKA TUNNELBROKER-0)
06.06.2023 21:19, Michiel van der Vlist пие:
93 2:5020/5858
; Alexander Kruglikov T-6in4 Tunnel-Brkr-Net1 f
Also IP4Market, as "TUNNELBROKER-0" in your list
Hello All,
Paul Hayton now has native IPv6
Hi Michiel.
I have checked all the remaining nodes in the list for connectivityWhat happened to 2:221/10 ?
and as a result more nodes have been flagged 6DWN or even DOWN...
I have checked all the remaining nodes in the list for connectivity
and as a result more nodes have been flagged 6DWN or even DOWN...
What happened to 2:221/10 ?why do you ask ?
I have checked all the remaining nodes in the list for connectivity
and as a result more nodes have been flagged 6DWN or even DOWN...
What happened to 2:221/10 ?
why do you ask ?Why do you answer with a question?
Good ${greeting_time}, Benny!
02 Aug 2023 17:28:34, you wrote to Tommi Koivula:
I have checked all the remaining nodes in the list for connectivity
and as a result more nodes have been flagged 6DWN or even DOWN...
What happened to 2:221/10 ?
why do you ask ?Why do you answer with a question?
03 Aug 2023 11:51, Alexey Vissarionov wrote to Benny Pedersen:
Good ${greeting_time}, Benny!
02 Aug 2023 17:28:34, you wrote to Tommi Koivula:
I have checked all the remaining nodes in the list for
connectivity and as a result more nodes have been flagged
6DWN or even DOWN...
What happened to 2:221/10 ?
why do you ask ?Why do you answer with a question?
he, if Tommi can't check logs on his own network, its brokken
I have no logs of the "List of IPv6 nodes". ;-D
08 Feb 2024 09:39, Tommi Koivula wrote to Benny Pedersen:
TK> I have no logs of the "List of IPv6 nodes". ;-D
grep xxxx:: binkd.log
why is it needed to use external lists ?
Btw: Can we still expect updates for this list in the future?
[08:58:54 brorabbit ~]$ grep ,5858, ~/nodelist/nodelist.367 ,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-Unpubli shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4
[08:58:54 brorabbit ~]$ grep ,5858, ~/nodelist/nodelist.367
,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-Unpubli
shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4
[08:58:54 brorabbit ~]$ grep ,5858, ~/nodelist/nodelist.367
,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-U
npubli shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4
Real name is the name from the nodelist. ;)
[08:58:54 brorabbit ~]$ grep ,5858, ~/nodelist/nodelist.367
,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-U
npubli shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4
Real name is the name from the nodelist. ;)
[08:58:54 brorabbit ~]$ grep ,5858, ~/nodelist/nodelist.367
,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-
U npubli shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4
Real name is the name from the nodelist. ;)
Yeah, tell that to Santa Clause, he may believe it. ;-)
Could you please change:
30 2:5001/100 Dmitry Protasoff Native OVH
to
30 2:5001/100 Dmitry Protasoff Native Layer7 Networks
It's a very cheap VPS provider from Germany.
Hmmm...
+ 19:24 [1672] call to 2:5001/100@fidonet
19:24 [1672] trying f100.n5001.z2.binkp.net
[2a00:1911:1:1db:6940:47ee:732a:d826]...
19:24 [1672] connected
+ 19:24 [1672] outgoing session with f100.n5001.z2.binkp.net:24554
[2a00:1911:1:1db:6940:47ee:732a:d826]
- 19:24 [1672] SYS Postmortem
? 19:24 [1672] recv: {W32 API error 10054} An existing
connection was forcibly closed by the remote host
+ 19:24 [1672] done (to 2:5001/100@fidonet, failed, S/R: 0/0 (0/0
bytes)) 19:24 [1672] session closed, quitting...
BinkpAbstractConnector Protocol version 1.1 28-09-24 17:23:08
[00007394] BinkpAsyncConnector Frame received: [ M_ADR
2:280/5555@fidonet ] 28-09-24 17:23:08 [00007394]
BinkpAbstractConnector Invalid address 28-09-24 17:23:08 [00007394] NodelistScanner Using nodelist file nodelist 28-09-24 17:23:08 [00007394] BinkpAbstractConnector Local error: No valid address
specified
@PATH: 280/5555 5020/1042 4441 5001/100
Looks like 2:5020/1042 deserves a punishment..
And you are even not allowed no post here :)
AH, I see. You refuse connections with unlisted systems. There is a
flag for that, the LO flag. You do not carry that flag in the
nodelist. So....
Whatever, it will be fixed in a couple of hours.
@PATH: 280/5555 5020/1042 4441 5001/100
Looks like 2:5020/1042 deserves a punishment..
For what?
And you are even not allowed no post here :)
Says who?
FROM: 2:280/5555
REASON: Sender not active for this area
AREANAME: IPV6
And you are even not allowed no post here :)
Says who?
And you are even not allowed no post here :)
Says who?
You disappear for a long time, then you suddenly start posting to
echoes that you are not connected to. And from an unlisted node.
Shame on you.
AH, I see. You refuse connections with unlisted systems. There is
a flag for that, the LO flag. You do not carry that flag in the
nodelist. So....
I accept connections from unlisted systems, but not from all.
If you are related somehow to 2:5001 - I'll accept connection from
your unlisted node (based on your ip address). But not from some
random Dutch Vodafone ipv6 address with non existing node address. Too suspicious.
We have a very weird guy in R50 who is sending multi-GB pkts and zip
bombs from the TOR network and public proxies to my node.
Whatever, it will be fixed in a couple of hours.
Good! Let's make this world better.
@PATH: 280/5555 5020/1042 4441 5001/100
Looks like 2:5020/1042 deserves a punishment..
For what?
For processing echomail from node that is not in nodelist.
You may not actually be "Michiel van der Vlist", but rather one of his virtual identities. According to the nodelist, the real Michiel van
der Vlist left Fidonet in June
But you accepted a connection from 2:280/464.5555...
Anyway, my fiberglas connection supports IPv6 as you can see. *1)
We have a very weird guy in R50 who is sending multi-GB pkts and
zip bombs from the TOR network and public proxies to my node.
That is annoying and if for that reason you refuse connections from unlisted systems you should fly the LO flag. You do not...
Good! Let's make this world better.
I am listed in today's daily.
For processing echomail from node that is not in nodelist.
Unlisted, but not unknown.
You may not actually be "Michiel van der Vlist", but rather one
of his virtual identities. According to the nodelist, the real
Michiel van der Vlist left Fidonet in June
Those alleged virtual identities would not have the matching
passwpords to have the connection accepted and the echomail processed. That is why passwords were invented.
Anyway, we are getting off-topic.
To get back on topic:
*1) My fiberglass connection supports IPv6 but to my annoyance there
still is a problem with incoming IPv6 connetctions. The modem/router
that they supply (Nokia XS-2426G-B) has no functioning method to
create an IPv6 pinhole in the firewall. :-(
LO flag means I'll have to refuse all connections from unlisted nodes,
but this is not what I want.
I am listed in today's daily.
The problem is that I only update the nodelist weekly. Please wait.
To get back on topic:
*1) My fiberglass connection supports IPv6 but to my annoyance
there still is a problem with incoming IPv6 connetctions. The
modem/router that they supply (Nokia XS-2426G-B) has no
functioning method to create an IPv6 pinhole in the firewall. :-(
Even setting Attack Protection to Disabled + Security level = Off
and configuring port forwarding?
LO flag means I'll have to refuse all connections from unlisted
nodes, but this is not what I want.
No LO does not mean you MUST refuse all connections from unlisted
systems. It just means you refuse unlisted connections. Some of them,
not all of them.
The problem is that I only update the nodelist weekly. Please
wait.
That is not MY problem.
Even setting Attack Protection to Disabled + Security level = Off
Yes, when I disable the IPv6 firewall, incoming IPv6 connection are possible. But of course I am not going to do that. Then ALL
unsollicited IPv6 packets are allowed. No way Jose!
and configuring port forwarding?
Port forwarding is for IPv4, Yes that works.
No LO does not mean you MUST refuse all connections from unlisted
systems. It just means you refuse unlisted connections. Some of
them, not all of them.
From current nodelist:
LO Node accepts calls Only from Listed
There is nothing about "some of them", the description is pretty
strict - "Only from Listed". Could you please cite any Fidonet
document along with your interpretation?
Even setting Attack Protection to Disabled + Security level =
Off
Yes, when I disable the IPv6 firewall, incoming IPv6 connection
are possible. But of course I am not going to do that. Then ALL
unsollicited IPv6 packets are allowed. No way Jose!
Looks like someone decided to skip proper firewall implementation :(
In theory I could fix it by getting my own fiberglass modem/router but
for XSPON they are expensive and there is little choice. Plus that it
is not easy to get it running. I just think that the burden of
providing a decent modem/router is on them.
97 2:5020/715 Alex Barinov T-6in4 he.net
^^^^^^^^^^^^^^^
Non-authoritative answer:
Name: fido.hubahuba.su
Address: 2001:470:1f0b:879:f1d0:2:5020:715
^^^^^^^^^^^^^^^
If you'd like, I can send you the SFP and help to setup it in
compatible router.
Alternatively, you could try configuring your router as a bridge. Is
that possible?
You could then connect it to another intelligent router. I had this
setup in Moscow for a while, but, once again, I can't teleport there
to resolve any issues. However, this might not be a concern in your
case.
Thanks for the offer but I do not have an SFP comatible router at hand
and this is not a good time to start such a major project.I am still
in the process of tuning my Fidonet system after six month of absence
and that takes a lot of time. Not to mention other time concuming
projects in and around the house.
Thanks for the offer but I do not have an SFP comatible router at
hand and this is not a good time to start such a major project.I
am still in the process of tuning my Fidonet system after six
month of absence and that takes a lot of time. Not to mention
other time concuming projects in and around the house.
Another option is a dumb GPON-to-Ethernet bridge as separate device,
but I've never tried them myself. The main issue with these 3rd-party devices is to obtain all required parameters from provider's router,
which is sometimes not possible without the provider's support :(
Sysop: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 993 |
Nodes: | 10 (0 / 10) |
Uptime: | 214:43:35 |
Calls: | 12,972 |
Files: | 186,574 |
Messages: | 3,268,542 |