Hello All,
Rumour has is that Route48 is closing down. I wonder how this will
affect Fidonet. Especially net 134. The majority of nodes in net 134
uses a tunnel from Route48.
Rumour has is that Route48 is closing down. I wonder how this will
affect Fidonet. Especially net 134. The majority of nodes in net 134
uses a tunnel from Route48.
According to their website, it's already closed.
There's always tunnelbroker.com which has been pretty reliable for me
on my home system.
Michiel van der Vlist wrote to All <=-
Rumour has is that Route48 is closing down. I wonder how this
will affect Fidonet. Especially net 134. The majority of nodes in
net 134 uses a tunnel from Route48.
Rumour has is that Route48 is closing down.
Yes. I got email from them yesterday.
In the case of he.net the bussines model was spreading IPv6 so that
they could make money on those needing help getting their bussines
running on IPv6. There are indications that their free tunnels may
not last forever.
Route48? Frankly I know very little about them. But whatever their
bussines model was, it apparently didn't work...
Route48? Frankly I know very little about them. But whatever their
bussines model was, it apparently didn't work...
Don't know about business model, but route48 was nice because they
offered tunnel by wireguard. Wireguard doesn't need public ipv4.
They also had a server in Finland. :)
According to their website, it's already closed.
1:134/101 wirh IPv6 address 2a06:a004:4020:beef:f1d0:1:134:101 is
still online...
According to their website, it's already closed.
1:134/101 wirh IPv6 address 2a06:a004:4020:beef:f1d0:1:134:101 is
still online...
>> Route48? Frankly I know very little about them. But whatever their
>> bussines model was, it apparently didn't work...
TK> Don't know about business model, but route48 was nice because they
TK> offered tunnel by wireguard. Wireguard doesn't need public ipv4.
I am not familiar with Wireguard.
TK> They also had a server in Finland. :)
"had"? Is it down already?
It would be a nice day when these tunnel provider were no longer
needed because we all could get native IPv6 from our regular ISP.
>> Route48? Frankly I know very little about them. But whatever
their
>> bussines model was, it apparently didn't work...
TK> Don't know about business model, but route48 was nice because
they
TK> offered tunnel by wireguard. Wireguard doesn't need public
ipv4.
I am not familiar with Wireguard.
One of the best available VPN software. I have a wireguard server
running at home for remote access.
See https://www.wireguard.com/
I am not familiar with Wireguard.
One of the best available VPN software. I have a wireguard serverIt has a major drawback as compared to GRE or IPIP. You cannot bind
running at home for remote access. See https://www.wireguard.com/
your side of the tunnel to a specific IP address (external address
as related to the tunnel).
I am not familiar with Wireguard.
One of the best available VPN software. I have a wireguard
server running at home for remote access. See
https://www.wireguard.com/
It has a major drawback as compared to GRE or IPIP. You cannot
bind your side of the tunnel to a specific IP address (external
address as related to the tunnel).
Whether you need to set up multiple tunnels with different links (I
guess this is the case), you may use VRF to keep them apart.
Linux does that just fine.
1:134/303 bbs.canerduh.com:24554 2604:3d09:227b:26af:19:a08b:78ab:5e16 Error: Connection timed out 1:134/303 bbs.canerduh.com:24554 24.64.95.197 Ok.
1:134/303 bbs.canerduh.com:24554
2604:3d09:227b:26af:19:a08b:78ab:5e16 Error: Connection timed out
1:134/303 bbs.canerduh.com:24554 24.64.95.197 Ok.
My sincere apologies for not noticing this sooner. Firewall was mis-configured on the binkp port.
For what it's worth, IPv6 should be working on my BBS again.
Travis
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 32:28:51 |
Calls: | 141 |
Files: | 5,058 |
Messages: | 220,694 |