68 2:5020/736 Egor Glukhov Native THEFIRST
Egor, welcome to th Fidonet IPv6 club!
Bwa-ha-ha... So how many new ${echotag}-capable nodes do we have after just a single message in ...
... R50.SYSOP.DRUNK? :-)
Bwa-ha-ha... So how many new ${echotag}-capable nodes do we have after just a single message in R50.SYSOP.DRUNK? :-)
Bwa-ha-ha... So how many new ${echotag}-capable nodes do we haveAlways present usefull messages to a popular forum. ;)
after just a single message in R50.SYSOP.DRUNK? :-)
Michiel should have a look at what was said. Maybe he can use it
to get some more action, where people are more fluent in English.
Bwa-ha-ha... So how many new ${echotag}-capable nodes do we have
after just a single message in R50.SYSOP.DRUNK? :-)
Always present usefull messages to a popular forum. ;)
Forum? What's that?
Michiel should have a look at what was said. Maybe he can use it
to get some more action, where people are more fluent in English.
I've said "нукатакбля" there, and I seriously doubt that would be usable anywhere besides the echoarea where people are fluent mostly of beer and stronger beverages.
Bwa-ha-ha... So how many new ${echotag}-capable nodes do we have
after just a single message in R50.SYSOP.DRUNK? :-)
Always present usefull messages to a popular forum. ;)
Forum? What's that?
Bwa-ha-ha... So how many new ${echotag}-capable nodes do we have after just a single message in R50.SYSOP.DRUNK? :-)
https://goo.gl/maps/Vh6PRuUgeCC2
A shopping hell in Helsinki! :)
That's fido IPv6 relay for binkp and ifcico I made just for lulz.
There are two IPv6 prefixes:
- "f1d0 style" - 2a04:52c0:101:201:f1d0::/80
- "hex style" - 2a04:52c0:101:201:fed0::/80
Second one is useful for reaching nodes with node-numbers above 9999. Ports are always default no matter which specific node really uses:
- binkp - 24554
- ifcico - 60179
Generation from daily nodelist on daily basis (on 04:00 UTC+03).
Nope, that's not another one.
Try [2a04:52c0:101:201:f1d0:2:280:5555]:24554 for example. ^_^
That's fido IPv6 relay for binkp and ifcico I made just for lulz.
There are two IPv6 prefixes:
- "f1d0 style" - 2a04:52c0:101:201:f1d0::/80
- "hex style" - 2a04:52c0:101:201:fed0::/80
Nope, that's not another one.
Try [2a04:52c0:101:201:f1d0:2:280:5555]:24554 for example. ^_^
That's fido IPv6 relay for binkp and ifcico I made just for lulz.
Try [2a04:52c0:101:201:f1d0:2:280:5555]:24554 for example. ^_^
That's fido IPv6 relay for binkp and ifcico I made just for lulz.
Very stupid and harmful.
That's fido IPv6 relay for binkp and ifcico I made just for lulz.
There are two IPv6 prefixes:
- "f1d0 style" - 2a04:52c0:101:201:f1d0::/80
- "hex style" - 2a04:52c0:101:201:fed0::/80
MvdV> So this is an IPV6 to IPv4 gateway.That's fido IPv6 relay for binkp and ifcico I made just for lulz.
MvdV> I may test that hex option later.There are two IPv6 prefixes:
- "f1d0 style" - 2a04:52c0:101:201:f1d0::/80
- "hex style" - 2a04:52c0:101:201:fed0::/80
That's fido IPv6 relay for binkp and ifcico I made just for lulz.
There are two IPv6 prefixes:
- "f1d0 style" - 2a04:52c0:101:201:f1d0::/80
- "hex style" - 2a04:52c0:101:201:fed0::/80
What kind of interesting prefix is /80? On which OS does this work? =\
That's fido IPv6 relay for binkp and ifcico I made just for
lulz. There are two IPv6 prefixes:
- "f1d0 style" - 2a04:52c0:101:201:f1d0::/80
- "hex style" - 2a04:52c0:101:201:fed0::/80
What kind of interesting prefix is /80? On which OS does thisWelcome to magical world of IPv6. ^_^
work? =\
Very stupid and harmful.
That's pretty much the same thing which I'm using here for my os/2
system: xinetd in linux forwards ipv6 tcp port 24554 to lan 192.168.1.2:24554.
But when the whole nodelist is relayed... It sure can be abused!
MvdV>> So this is an IPV6 to IPv4 gateway.That's fido IPv6 relay for binkp and ifcico I made just for
lulz.
Actually, it isn't strictly IPv6 to IPv4. IPv6 to IPv6 also works.
And if destination IPv4 addresses are unresponsive IPv6 addresses also will be tried.
So it is potentially can be used to reach IPv6-only
nodes if direct routing isn't working for some reason.
Or IPv4 only nodes could use such services to advertise IPv6
reachability when don't want to mess with IPv6 tunnels
or their retro-OS doesn't support IPv6 at all.
Or just want a shiny f1d0-style address but can't have one...
There are could be numerious hypotetical reasons for such services to exist.
As I have already said that experiment was just for fun.
I've tested how recent linux kernels handle thousands of address
aliases on interfaces in memory constrained environment. I hadn't
intended and still don't intent to provide such service for anyone to
use in real life. As it's prone to abuse and centralization.
But as my address was noticed and mistaken as potential new IPv6 fido member I clarified that it's not. ^_^
There are two IPv6 prefixes:
- "f1d0 style" - 2a04:52c0:101:201:f1d0::/80
- "hex style" - 2a04:52c0:101:201:fed0::/80
Bwa-ha-ha... So how many new ${echotag}-capable nodes do we have after just a single message in R50.SYSOP.DRUNK? :-)
Sysop: | Nelgin |
---|---|
Location: | Plano, TX |
Users: | 510 |
Nodes: | 10 (1 / 9) |
Uptime: | 122:06:52 |
Calls: | 8,198 |
Calls today: | 5 |
Files: | 15,442 |
Messages: | 913,554 |
Posted today: | 8 |