You can congratulate me - `whois 2a01:ba80::/48`
You can congratulate me - `whois 2a01:ba80::/48`Congratulations!
Is there a pinagble host in that range?
I tried 2a01:ba80::1. It does not ping.
Is it a tunnel or is it native?
You can congratulate me - `whois 2a01:ba80::/48`
Congratulations!
Thank you!
Is it a tunnel or is it native?
There really are some advantages in working for LIR... :-)
Yes, it is native (first^W zeroth ALLOCATED-BY-LIR /48 in our ALLOCATED-BY-RIR /32 block).
Also, our NOC department works on setting IPv6 up on links with all
our peers - so the visibility of our IPv6 block is just a matter of
time.
Yes, it is native (first^W zeroth ALLOCATED-BY-LIR /48 in ourFigures. I already wondered, 2a01:ba80:: would normally be associated
ALLOCATED-BY-RIR /32 block).
with a /32. Unless you got the FIRST out of those 65536 /48's ;-)
You can congratulate me - `whois 2a01:ba80::/48`
Congratulations!
Thank you!
Is it a tunnel or is it native?
There really are some advantages in working for LIR... :-)
Yes, it is native (first^W zeroth ALLOCATED-BY-LIR /48 in our ALLOCATED-BY-RIR /32 block).
Also, our NOC department works on setting IPv6 up on links with all
our peers - so the visibility of our IPv6 block is just a matter of
time.
Hello Michiel!
17 Aug 2011 14:02, Michiel van der Vlist wrote to Alexey Vissarionov:
this was the last msg i got from you Michiel
Janis: is there brokken links to some Z2 nodes ?, aslong i can post and get reply back from you i consider it works, but Michiel does not agree :(
I got your message here, Benny :)
Sorry I didn't notice it before..
@MSGID: 2:230/0 4e54e5a0
SEEN-BY: 123/500 124/311 128/2 187 140/1 18 203/0 230/0 150 249/303
261/20 38
SEEN-BY: 263/950 280/464 1141 5003 5555 292/854 340/400 633/260
640/384
SEEN-BY: 712/848 5019/40 5020/545 715 1042 2140 5053/54 5057/70
5068/58
SEEN-BY: 5080/102 5083/444
@PATH: 230/0 261/38 140/1 292/854 280/5555 5020/1042 5080/102
I got your message here, Benny :)
wondering who should make a rescan to sync this to z2, as i understand Michiel
there is 2 versions of IPV6, one in each zone that is not connected :(
if ward have this area could you bridge it for all of us ? :=)
and nicely ask for full rescan
Sorry I didn't notice it before..
no problem, atleast you read it
2nd:
Echoconference IPV6 cross zonegates twice. Such situation is potencial dupedrome.
On Wednesday October 26 2011 12:37, you wrote to Alexey Vissarionov:
Another /545 should also be available via IPv6 atI get an error attempting to ping that: Destination unreachable:
2a01:ba80::f1d0:2:5020:545
Address unreachable
Mine, btw, is 2001:470:1f11:10b9::5.
Ah, Hurricane Electic, just like mine. From the same /40.
But yours does not ping.
root@OpenWrt:~# ping 2001:470:1f11:10b9::5
Mine shoud ping. See origin
root@OpenWrt:~# ping 2001:470:1f11:10b9::5
When you have a chance, please try that again.
It so happens that my main IPv6 router is also based on Linux. OpenWrt on a Linksys WRT54GL.
Ain't working at this moment:
# ping6 2001:470:1f11:10b9::5
PING 2001:470:1f11:10b9::5(2001:470:1f11:10b9::5) 56 data bytes
^C
-+- 2001:470:1f11:10b9::5 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4000ms
# date
Fri Nov 4 10:39:56 CET 2011
# date -u
Fri Nov 4 09:40:15 UTC 2011
Bye, Wilfred.
Odd... Could you try a traceroute when you have a chance?
I can reach others, for instance:
$ ping6 2001:470:1f15:1117::1
PING 2001:470:1f15:1117::1(2001:470:1f15:1117::1) 56 data bytes ^C
-+- 2001:470:1f15:1117::1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 154.914/156.643/158.773/1.529 ms
It so happens that my main IPv6 router is also based on Linux.
OpenWrt on a Linksys WRT54GL.
I recall you mentioning that before but didn't have a chance to
ask you. What version are you using for that?
I've been interested in installing something like that on mine
(though I'm using something else for IPv6 connectivity) and I'd like
to be sure that it has IPv6 capability on it...
Btw: That last system on number 10 doesn't respond to pings either...
$ ping6 2001:470:1f15:1117::1
Hello Jame,
On Friday November 04 2011 16:47, you wrote to me:
It so happens that my main IPv6 router is also based on Linux.I recall you mentioning that before but didn't have a chance to
OpenWrt on a Linksys WRT54GL.
ask you. What version are you using for that?
This is what I see when I start an ssh seesion:
BusyBox v1.17.3 (2011-02-26 16:05:38 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
ATTITUDE ADJUSTMENT (bleeding edge, r25759) ----------
....
And here is where you can download the binary: http://www.vlist.eu/downloads/openwrt-wrt54g-squashfs-r25759.bin
I did not compose that one myself. It was a Dutch guy that I ran across
in a Dutch internet forum that did it for us.
I've been interested in installing something like that on mine
(though I'm using something else for IPv6 connectivity)
and I'd like to be sure that it has IPv6 capability on it...This one sure has. It has been running sinds sring now.
My Linux system should now be available via IPv6. Anyone wanting to
try it should point binkd at ipv6.bnbbbs.net [2001:4830:1100:2bf::2]
... Let me know if you have any problems.
My Linux system should now be available via IPv6. Anyone wanting to
try it should point binkd at ipv6.bnbbbs.net [2001:4830:1100:2bf::2]
... Let me know if you have any problems.
My Linux system should now be available via IPv6. Anyone wanting to
try it should point binkd at ipv6.bnbbbs.net [2001:4830:1100:2bf::2]
... Let me know if you have any problems.
My Linux system should now be available via IPv6. Anyone wanting to try it
should point binkd at ipv6.bnbbbs.net [2001:4830:1100:2bf::2] ... Let me know if you have any problems.
If you want to try outgoing sessions, feel free to connect to my
system at 2:280/5003 or with Wilfred van Velzen at 2:280/464.
DNS provides IPv6 and IPv4 vor bothy systems.
Both have been operational with IPv6 for almost two years and have
crash connects many times a day.
I have the same problem Michiel reported. "Connection refused"
I have the same problem Michiel reported. "Connection refused"
Sounds familiar. I guess none of can still get passed my WinXP firewall?
If only there was a simple way to export all the firewall settings in XP, but the closest I've come to is 'netsh f s i m=e t=a' and it still doesn't "export" all the settings. Especially not the IPv6 ditto, that I rely on to have my three SixXS tunnels working properly.
Alas, I guess I'll have to rebuild my firewall from scratch if I
ever
should get to the point where I change system... :(
should point binkd at ipv6.bnbbbs.net [2001:4830:1100:2bf::2] ...
Last week I got my first Raspberry Pi,
... Let me know if you have any problems.
Maybe we'll soon have reason to create a RASPBERRY echo even in our old, outdated fidonet? 8-)
by the way, by default there is no IPv6 on the Raspberry, but I
guess that is done to save memory.
Both of my systems are on the same IPv4 address, and only one of the supports IPv6.
Using a separate hostname allows me to ensure that all
IPv6 traffic ends up going to the host that supports IPv6.
My Linux system should now be available via IPv6. Anyone wanting to try it
should point binkd at ipv6.bnbbbs.net [2001:4830:1100:2bf::2] ... Let me know if you have any problems.
My Linux system should now be available via IPv6. Anyone wanting
to try it should point binkd at ipv6.bnbbbs.net
[2001:4830:1100:2bf::2]
... Let me know if you have any problems.
to try it should point binkd at ipv6.bnbbbs.net
[2001:4830:1100:2bf::2]
... Let me know if you have any problems.
Problem:
# telnet ipv6.bnbbbs.net binkp
Trying 2001:4830:1100:2bf::2...
telnet: connect to address 2001:4830:1100:2bf::2: Connection refused
My Linux system should now be available via IPv6. Anyone wanting
to try it
should point binkd at ipv6.bnbbbs.net [2001:4830:1100:2bf::2]
... Let me know if you have any problems.
I have the same problem Miechiel reported. "Connection refused"
If you want to try outgoing sessions, feel free to connect to my
system at 2:280/5003 or with Wilfred van Velzen at 2:280/464.
DNS provides IPv6 and IPv4 vor bothy systems.
Both have been operational with IPv6 for almost two years and have
crash connects many times a day.
If you want to try outgoing sessions, feel free to connect to my
system at 2:280/5003 or with Wilfred van Velzen at 2:280/464.
DNS provides IPv6 and IPv4 vor bothy systems.
Both have been operational with IPv6 for almost two years and have
crash connects many times a day.
mbcico was able to connect to both via IPv6 without issues.
# telnet ipv6.bnbbbs.net binkp
Trying 2001:4830:1100:2bf::2...
telnet: connect to address 2001:4830:1100:2bf::2: Connection refused
This should be fixed now; try again.
fido stream tcp nowait ftn /usr/sbin/tcpd
/usr/lib/ifmail/ifcico -r 0
fido stream tcp6 nowait ftn /usr/sbin/tcpd
/usr/lib/ifmail/ifcico -r 0
This should be fixed now; please try again.
Hello Kees!
28 Nov 2013 12:10, Kees van Eeten wrote to Andrew Leary:
fido stream tcp nowait ftn /usr/sbin/tcpd
/usr/lib/ifmail/ifcico -r 0
fido stream tcp6 nowait ftn /usr/sbin/tcpd
/usr/lib/ifmail/ifcico -r 0
----- qico begins -----
# binkp = 24554
# tfido = 60179
# fido = 60177
service tfido
{
# log_type = FILE /home/xpoint/fido/log/xinetd_tfido.ipv4
# log_on_succes = HOST PID
# log_on_failure = HOST PID
# bind = 2.104.223.10
disable = no
protocol = tcp
flags = IPv4
port = 60177
socket_type = stream
wait = no
user = xpoint
server = /usr/sbin/qico
server_args = -a auto
per_source = 1
instances = 1
}
service fido
{
# log_type = FILE /home/xpoint/fido/log/xinetd_fido.ipv4
# log_on_succes = HOST PID
# log_on_failure = HOST PID
# bind = 2.104.223.10
disable = no
protocol = tcp
flags = IPv4
port = 60179
socket_type = stream
wait = no
user = xpoint
server = /usr/sbin/qico
server_args = -a auto
per_source = 1
instances = 1
}
service binkp
{
# log_type = FILE /home/xpoint/fido/log/xinetd_binkp.ipv4
# log_on_succes = HOST PID
# log_on_failure = HOST PID
# bind = 2.104.223.10
disable = no
protocol = tcp
flags = IPv4
port = 24554
socket_type = stream
wait = no
user = xpoint
server = /usr/sbin/qico
server_args = -a binkp
per_source = 1
instances = 1
}
service tfido
{
# log_type = FILE /home/xpoint/fido/log/xinetd_tfido.ipv4
# log_on_succes = HOST PID
# log_on_failure = HOST PID
# bind = 192.168.5.100
disable = yes
protocol = tcp
flags = IPv4
port = 60177
socket_type = stream
wait = no
user = xpoint
server = /usr/sbin/qico
server_args = -a auto
per_source = 1
instances = 1
}
service fido
{
# log_type = FILE /home/xpoint/fido/log/xinetd_fido.ipv4
# log_on_succes = HOST PID
# log_on_failure = HOST PID
# bind = 192.168.5.100
disable = yes
protocol = tcp
flags = IPv4
port = 60179
socket_type = stream
wait = no
user = xpoint
server = /usr/sbin/qico
server_args = -a auto
per_source = 1
instances = 1
}
service binkp
{
# log_type = FILE /home/xpoint/fido/log/xinetd_binkp.ipv4
# log_on_succes = HOST PID
# log_on_failure = HOST PID
# bind = 192.168.5.100
disable = yes
protocol = tcp
flags = IPv4
port = 24554
socket_type = stream
wait = no
user = xpoint
server = /usr/sbin/qico
server_args = -a binkp
per_source = 1
instances = 1
}
service tfido
{
# log_type = FILE /home/xpoint/fido/log/xinetd_tfido.ipv6
# log_on_succes = HOST PID
# log_on_failure = HOST PID
# bind = 2001:470:27:bb3::2
# 2001:16d8:dd00:137::2
disable = yes
protocol = tcp
flags = IPv6
port = 60177
socket_type = stream
wait = no
user = xpoint
server = /usr/sbin/qico
server_args = -a auto
per_source = 1
instances = 1
}
service fido
{
# log_type = FILE /home/xpoint/fido/log/xinetd_fido.ipv6
# log_on_succes = HOST PID
# log_on_failure = HOST PID
# bind = 2001:470:27:bb3::2
# 2001:16d8:dd00:137::2
disable = yes
protocol = tcp
flags = IPv6
port = 60179
socket_type = stream
wait = no
user = xpoint
server = /usr/sbin/qico
server_args = -a auto
per_source = 1
instances = 1
}
service binkp
{
# log_type = FILE /home/xpoint/fido/log/xinetd_binkp.ipv6
# log_on_succes = HOST PID
# log_on_failure = HOST PID
# bind = 2001:470:27:bb3::2
# 2001:16d8:dd00:137::2
disable = yes
protocol = tcp
flags = IPv6
port = 24554
socket_type = stream
wait = no
user = xpoint
server = /usr/sbin/qico
server_args = -a binkp
per_source = 1
instances = 1
}
----- qico ends -----
this is same for qico when i had it serving ipv6 here, qico was not avare of ipv6 for the serving part since xinetd did that for me, i post it here so i have backup of how to make it again :=)
Regards Benny
... there can only be one way of life, and it works :)
--- Msged/LNX 6.2.0 (Linux/3.12.1-gentoo (i686))
* Origin: duggi.junc.org where qico is waiting (1:261/38.20)
Both of my systems are on the same IPv4 address, and only one of
the supports IPv6.
Using a separate hostname allows me to ensure that all
IPv6 traffic ends up going to the host that supports IPv6.
We are still waiting for you. When is your system supporting IPv6 ;)
Now I remember why I do not like xinetd, the config file is to
large. ;)
Both of my systems are on the same IPv4 address, and only one of
the supports IPv6.
Ah, that is an interseting configuration that I did not foresee when I proposed the INO4 flag...
Using a separate hostname allows me to ensure that all
IPv6 traffic ends up going to the host that supports IPv6.
If this situation is permanent, rather than just a experiment, I
suggest that instead of separate host names for IPv4 and IPv6, you use separate host names for the different systems. Example: Use bnbbbs.net
for 320/119 and phoenix.bnbbbs.net for 320/219. Attach just an A
record to bnbbbbs.net and both the A and AAAA records to phoenix.bnbbbs.net
The only snag is that in that case, you'd have to make the ipv6 part listen on port 24555 instead of 24554.
A third solution would be to add an extra node number - say 320/319
for the IPv6 experiment and list it with an INO4 flag to signal no
IPv4.
But the "grand" solution of course is to enable IPv6 for your other
system as well...;-)
Welcome to the gang. I've been (theoretically at lest) IPv6
compatible for more than three years now. But to no (binkp) avail.
felten.yi.org can successfully be pinged, but all telnet/binkp
access will be denied.
But the "grand" solution of course is to enable IPv6 for your
other system as well...;-)
1:320/119 still runs under OS/2, which does not, and probably never
will, support IPv6.
Same here I have two tunnels running. One from SuxSx^
Welcome to the gang. I've been (theoretically at lest) IPv6
compatible for more than three years now. But to no (binkp) avail.
felten.yi.org can successfully be pinged, but all telnet/binkp
access will be denied.
possible get sysresquecd (google it) burn it to a cdrom, boot it, test
it can "ping6 -c3 ipv6.google.com" if that works your networking is
done, but then its windows problem that it does not work on windows, if thats the case you need a router that allow bridge from ipv6 to ipv4 lan
I beg to differ. AFAIK nothing in my nodelist entry says anything
about IPv6 capability.
Being as it may with that, I'm still hoping for one of two things
to happen:
1. Somebody will come up with a simple solution to make the Win XP firewall being able to administer IPv6.
2. The linux world will come up with a firewall administrative tool that's as easy to use as the one in Win XP.
I've been fully IPv6 functional *outwards* for three years now.
It's the incoming connections that I can't get sorted out with the
present Win XP system as router.
I've been fully IPv6 functional *outwards* for three years now.
Welcome to the gang. I've been (theoretically at lest) IPv6
compatible for more than three years now. But to no (binkp) avail.
felten.yi.org can successfully be pinged, but all telnet/binkp
access will be denied.
My servers can be ping6:d and even get port 80 access too (I think
I have all the proper AAAA records registered properly?), but I still
have no idea about how to get those binkp servers of yours to access
mine via IPv6.
Andrew, please, what operating system are you using?
For that matter, anyone still with Windows XP who can get binkp
over IPv6 working, feel free to tell us how you managed to do it.
1. It's the most stable OS that I have ever tried.
2. It has the most simple and flexible administration of the
firewall that I know of.
3. It has all the remains of all my old computers, including all
the fidonet stuff, with loads of MS-DOS programs developed and tweaked
for more than 20 years. Converting it to something else would take far more time and effort than I am willing to spend on our museum piece.
4. My ISP would give me a new IP if ever I change the MAC address
(from my XP router/server), and I don't want to go down that route
again unless necessary.
No, it's a 6in4-static. And I want to keep it that way.
It works for me. But (obviously) IPv6 routing doesn't work as well
as IPv4 does with XP.
Been there, tried that, got a brick to prove it. :)
Nah, just kidding. As I said, it's all about being able to
administer the firewall in a user friendly way. I'm now to old to get
back to the old MS-DOS variant of administering things, I want a GUI.
Don't hold your breath.
I've been nagging JoHo for more than a decade now about releasing the source for FrontDoor, that could easily have been converted to a fully fledged Windows program, but to no avail.
Those old guys obviously don't want anyone to show that their
product could be made even better...?
I've been fully IPv6 functional *outwards* for three years now.
How times fly. It's almost five years now. To be exact, since:
2009-02-11 05:34:22 UTC
2. The linux world will come up with a firewall administrative tool that's as easy to use as the one in Win XP.
You might want to check back from the beginning of this echo (every posted message available on my JamNNTPd server, see origin line).
I've been fully IPv6 functional *outwards* for three years now.
It's the incoming connections that I can't get sorted out with the present Win XP system as router.
http://test-ipv6.com/
1. It's the most stable OS that I have ever tried.
2. It has the most simple and flexible administration of the
firewall that I know of.
3. It has all the remains of all my old computers, including all
the fidonet stuff, with loads of MS-DOS programs developed and tweaked for more than 20 years. Converting it to something else would take far more time and effort than I am willing to spend on our museum piece.
4. My ISP would give me a new IP if ever I change the MAC address (from my XP router/server), and I don't want to go down that route
again unless necessary.
No, it's a 6in4-static. And I want to keep it that way.
It works for me. But (obviously) IPv6 routing doesn't work as well
as IPv4 does with XP.
Been there, tried that, got a brick to prove it. :)
Nah, just kidding. As I said, it's all about being able to
administer the firewall in a user friendly way.
I'm now to old to get
back to the old MS-DOS variant of administering things, I want a GUI.
http://test-ipv6.com/
glibc have default ipv4 first,
http://test-ipv6.com/
I beg to differ. AFAIK nothing in my nodelist entry says anything about IPv6 capability.
MvdV> ^Same here I have two tunnels running. One from SuxSx
glibc have default ipv4 first,
glibc have default ipv4 first,
I don't know if binkd uses glibc for this. But on my linux system,
binkd always uses the IPv6 address first...
I don't know if binkd uses glibc for this. But on my linux system,
binkd always uses the IPv6 address first...
The resolving is done by calling getaddrinfo() which supports IPv4 and IPv6
addresses. The output list can be controlled with /etc/gai-conf. In my case
I prefer IPv4 for outgoing connections because my IPv6 connectivity is based on a tunnel (latency, overhead). The default is to prefer IPv6 if available.
The /etc/gai.conf on my system is the default as provided by the distribution. It only contains 3 non commented out lines regarding private IPv4 address scope... I have native IPv6, so the default is
find for me. ;)
+ 30 Nov 19:35:00 [2310] call to 2:203/0@fidonet
30 Nov 19:35:00 [2310] trying felten.yi.org
[2001:16d8:ff00:306::2]... ? 30 Nov 19:35:00 [2310] connection to 2:203/0@fidonet failed: Connection refused 30 Nov 19:35:00 [2310]
trying felten.yi.org [90.231.158.147]... 30 Nov 19:35:00 [2310]
connected + 30 Nov 19:35:00 [2310] outgoing session with
90.231.158.147
This is a real delay. Binkd really has a hard time here.
This has been setup; the changes should make the next nodelist.
I see little need for an extra node number when with the change above, everything should end up on the proper system.
I doubt that will ever happen, unless I get rid of OS/2.
with is imho /dev/null'ed, another reason to make opensources
speaking of irex, it could be solved with a socks5 proxy, making ipv6
to ipv4 server in irex
This one has been rather useful to me:
http://www.wiberg.nu/ipv6/iptools.php
speaking of irex, it could be solved with a socks5 proxy, making ipv6
to ipv4 server in irex
You got that typo right :-) When I requested a tunnel from them they rejected my request because the forward and reverse mapping of my MXs aren't exactly the same.
In one of their FAQs they say that they want to make sure that you got
a valid email address. My email address works great for 15 years now!
WTF! And SixXS is offering an email address for problems with the
tunnel request but wasn't to be bothered to respond to my emails.
SuxXS is absolutely the correct name!
Yes they make you jump through hoops and the process cam be annoying.
Once you get past that, they offer a stable and reliable service.
he.net is much more lenient. No hoops to jump through, but they only
offer 6in4 static. You need a (semi) static globally unique IPv4 for that...
You cannot compare with Irex, it does not support IPV6.
Yes if it did forward, a port would answer, so waht is ypur point?.
Indeed.
DNS is not Fidonet.
It is probably available for your WRT linux in your router.
It is probably available for your WRT linux in your router.
or soekris running with shorewall/shorewall6, the linksys is more for teknican people not suited for swedish nodes :=)
You cannot compare with Irex, it does not support IPV6.
with proxy it does :)
even with inetd if it can redirect connections, i think it could even be iptable line :=)
+1, he have working ipv6 wan, but still no ipv6 lan
irelevant, since i see more example on loose of incorrect dns, then its not fidonet :=)
or soekris running with shorewall/shorewall6, the linksys is more for
teknican people not suited for swedish nodes :=)
I will leave that judgement to you, I was addressing a Dutch node ;)
Addresssing random outgoing traffic could be a challenge.
I do not know how his network infratructure is organised, and I
think it would be unwise to publish it.
Last year, when I made a survey of IPv6 nodes, there were a number
of nodes, that presented an IPv6 address, but did not respond to a binkd connection request.
It is probably available for your WRT linux in your router.
I probably was fortunate then, I've never had any problems
with any of my three tunnels.
Yes, Jeroen can be an arrogant SOB -- I've had several clashes with
him in the support forum --
but then again, he's giving the world a free service, that's
outstanding.
Absolutely. The end servers for Sweden are operated by Bahnhof --
the best ISP we have.
E.g. they never give out consumer data to the media industry.
Even when ordered to do so by our courts they fight the decision all
the way through our system to the highest level.
They will never give NSA, GCHQ or any other snooping agency access
to their fibres.
In short, I'm extremely happy with the service that Jeroen is providing, and impressed that he choose Bahnhof for the end of the
Swedish tunnels. That shows that he really knows what he's doing IMHO.
he.net is much more lenient. No hoops to jump through, but they
only offer 6in4 static. You need a (semi) static globally unique
IPv4 for that...
Right. 6in4 static also doesn't traverse NAT routers very well,
unless they specifically support it. My old ZyWALL 35 doesn't,
so I ended up using a sixxs.net AYIYA tunnel.
Once I upgrade to a new router that supports IPv6, I will probably
switch to a 6in4 static tunnel until such time as my ISP deploys
native IPv6.
----- dante begins -----
* net-proxy/dante
Available versions: 1.1.19-r4 ~1.3.2 ~1.3.2-r1 ~1.4.0_pre1 ~1.4.0_pre1-r1 {debug kerberos pam selinux static-libs tcpd}
Homepage: http://www.inet.no/dante/
Description: A free socks4,5 and msproxy implementation
----- dante ends -----
already done
and btw xinetd can forward ipv6 to ipv4 lan, if hostnames is used in
irex config then outgoing is working aswell to ipv6 servers, even
binkd can call ipv6 servers via squid proxy, if ipv6 was not ready natively in it
They got an interface to update the endpoint IPv4 address,
similar to dynDNS. OpenWRT has built-in support for that ;-)
DNS is not Fidonet.
Last year, when I made a survey of IPv6 nodes, there were a number of nodes, that presented an IPv6 address, but did not respond to a binkd connection request.
They got an interface to update the endpoint IPv4 address,
similar to dynDNS. OpenWRT has built-in support for that ;-)
They got an interface to update the endpoint IPv4 address,
Without timeout, just for updating.
It isn't linux specific, it's just a simple script run after
reconnecting the internet access. It takes the new WAN IPv4 address
and updates the tunnel endpoint at he.net. That could be done by most script languages. And the script may also be run on your PC.
so I ended up using a sixxs.net AYIYA tunnel.
Once I upgrade to a new router that supports IPv6, I will
probably switch to a 6in4 static tunnel until such time as my ISP
deploys native IPv6.
so I ended up using a sixxs.net AYIYA tunnel.
The information I got from sixxs.net says that I have a routed /64
subnet;
I haven't tried setting up anything on that yet.
When I do upgrade, I'm going to switch to something with gigabit
ethernet support.
I have done a little looking into what routers have IPv6 support or
can have it added by flashing to alternative firmware.
Once I upgrade to a new router that supports IPv6, I will
probably switch to a 6in4 static tunnel until such time as my
ISP deploys native IPv6.
Most ISPs aren't (yet.)
I haven't tried setting up anything on that yet.
My AYIYA tunnel ends on a Linux box, so I should be able to make it work. I just need to configure the addresses for each machine manually, unless I decide to play with setting up a DHCPv6 server.
Nice! I get a new IPv4 address every 24h. AFAIK that would change to 6 months if I switch to an All-IP service.
All that update stuff can be done by php, python, perl or whatever you prefer and run in the background without any GUI.
My AYIYA tunnel ends on a Linux box, so I should be able to make it
work.
I just need to configure the addresses for each machine manually,
unless I decide to play with setting up a DHCPv6 server.
My IPv6 tunnel also end on a Linux. In principle radvd does some advertising on the network, but I do not think it works very well. The vserver on the same box and a workstation on the lan have
static adresses. The other boxes do not make IPv6 connections and it
is safer if they are not adressable from outside.
Nono, there is no need for that. IPv6 has SLAAC (Stateless Address
Auto Configuration) The router broadcasts router advertisements that
tells the hosts on the LAN what the prefix is. The hosts make up the
lower 64 bits from their MAC address. No need to configure anything on
the other machines on your LAN.
Address Auto Configuration) The router broadcasts router
advertisements that tells the hosts on the LAN what the prefix
is. The hosts make up the lower 64 bits from their MAC address.
No need to configure anything on the other machines on your LAN.
I had to set the IPv6 address of my Linux system's Ethernet connection
manually;
once I did that radvd takes care of the router advertisements, and a Windows 7 Ultimate laptop was able to SLAAC a working IPv6 address.
In fact, it passes test-ipv6.com's test suite with a score of 10/10.
I still need to cleanup my startup/shutdown scripts a bit, but it's working fine.
TWIMC: my node (2:5020/545) is finally reachable via native
${areatag}.
I haven't played that much with relay6 but I think you need to
set up one relay6 session for each node you plan to poll. ;-)
Even so, I haven't managed to get the slightest life sign from any outgoing session no matter how I try.
I generated a poll using IPv6 so you can see what IP address it comes from. Perhaps you can find something there that will show me the way.
BjФrn Felten wrote to Ray Quinn <=-
Excellent. Now you "only" have the inbound to take care of. 8-)
+ 20 Aug 10:52:49 [1860] call to 1:214/22@fidonet
20 Aug 10:52:49 [1860] trying bbs.quinnnet.org [2602:306:bd31:aa50:e23f:49ff:fead:fa9]...
[2602:306:bd31:aa50:e23f:49ff:fead:fa9]...
I am running Debian Linux (Jessie). When I type ifconfig, I get fe80::e23f:49ff:fead:fa9/64 as the IPv6 address.
I am not in the same town as that computer and cannot further test the
IP address until I can get back home.
Ray Quinn wrote to BjФrn Felten <=-
I am running Debian Linux (Jessie). When I type ifconfig, I get fe80::e23f:49ff:fead:fa9/64 as the IPv6 address. I am not in the same
town as that computer and cannot further test the IP address until I
can get back home.
Michiel van der Vlist wrote to Ray Quinn <=-
Anyway, 2602:306:bd31:aa50:e23f:49ff:fead:fa9 is the ip address of
your binkp system.
But it does not yet answer on that address
+ 01:03 [3764] call to 1:214/22@fidonet
01:03 [3764] trying 2602:306:bd31:aa50:e23f:49ff:fead:fa9 [2602:306:bd31:aa50:e23f:49ff:fead:fa9]...
? 01:04 [3764] connection to 1:214/22@fidonet failed: {W32 API
error 10060} Connection timed out
Most likely you have a firewall issue. You have to configure your firewall(s) to pass port 24554 IPv6. Both in your router as in the
system running your binkp system.
Michiel van der Vlist wrote to Ray Quinn <=-
Also note the ff:fe in the middle. This tells me it is a so called
SLAAC addres. The lower 64 bit or the host part of the address is
derived form yoy MAC address. Remove the FF:fe and invert leat but
one significant buye of the most significant nibble en you get e0:3f:49:ad:0f:a9 as your MAC address.
I am not in the same town as that computer and cannot further test the
IP address until I can get back home.
From the information I got so far I am 90% confident that 2602:306:bd31:aa50:e23f:49ff:fead:fa9 is the correct address.
When you get back home look at the firewall first.
Tony Langdon wrote to Ray Quinn <=-
Ray Quinn wrote to BjФrn Felten <=-
I am running Debian Linux (Jessie). When I type ifconfig, I get fe80::e23f:49ff:fead:fa9/64 as the IPv6 address. I am not in the same
town as that computer and cannot further test the IP address until I
can get back home.
That's a link local address, not valid outside your LAN. Are there
any other IPv6 addresses?
I concur. I logged in remotely today and did a
telnet -6 localhost 24554
and binkd responded back so I know it responds to IPv6 connections.
eth1 Link encap:Ethernet HWaddr e0:3f:49:ad:0f:a9
inet6 addr: 2602:306:bd31:aa50:e23f:49ff:fead:fa9/64 Scope:Global
inet6 addr: fe80::e23f:49ff:fead:fa9/64 Scope:Link
Also note the ff:fe in the middle. This tells me it is a so
called SLAAC addres. The lower 64 bit or the host part of the
address is derived form yoy MAC address. Remove the FF:fe and
invert leat but one significant buye of the most significant
nibble en you get
e0:3f:49:ad:0f:a9 as your MAC address.
aa50:e23 - invert the 0 and the e to get e0, skip the 2, then the 3f,
the 49, skip the ff:ea to get to the ad, add 0 in front of f to get
0f, then the a9. I see the pattern, but have no idea as to why.
From the information I got so far I am 90% confident that
2602:306:bd31:aa50:e23f:49ff:fead:fa9 is the correct address.
I believe that may be the case...
When you get back home look at the firewall first.
Headed out to the fireline tomorrow... This may be the last contact
for a bit.
Ray Quinn wrote to Tony Langdon <=-
Perhaps you can tell me what I am seeing here. Here is the entire
output of ifconfig:
root@bbs:~# ifconfig
eth1 Link encap:Ethernet HWaddr e0:3f:49:ad:0f:a9
inet addr:104.49.12.129 Bcast:104.49.12.135 Mask:255.255.255.248
inet6 addr: 2602:306:bd31:aa50:e23f:49ff:fead:fa9/64 Scope:Global
inet6 addr: fe80::e23f:49ff:fead:fa9/64 Scope:Link
root@bbs:~# ifconfig
Markus Reschke wrote to Ray Quinn <=-
Hello Ray!
Aug 21 21:46 2016, Ray Quinn wrote to Tony Langdon:
root@bbs:~# ifconfig
Please use "ip addr show" instead,
I am beginning to suspect that the IPv6 address shown above is not
routed to me or there is a firewall issue. The ports I have checked
are open on the IPv4 interface, but not using IPv6. I don't see it
above, but another resource shows that the gateway for eth1 is fe80::62fe:20ff:fe4f:b8b5.
Ray Quinn wrote to Markus Reschke <=-
Hello Andrew,
- 14:02 [1632] incoming from 213.178.37.175 (55786)
+ 14:02 [368] incoming session with 213.178.37.175
- 14:02 [368] SYS Warlock_BBS
- 14:02 [368] ZYZ Andrew_Komardin
- 14:02 [368] LOC Togliatti--Russia
- 14:02 [368] NDL 4M,TCP,BINKP,ICM,INA:fido.globaldynamics.su
- 14:02 [368] TIME Sun, 16 Oct 2016 16:02:45 +0400
- 14:02 [368] VER binkd/1.1a-94/Linux binkp/1.1
+ 14:02 [368] addr: 2:5075/37@fidonet
- 14:02 [368] OPT NDA EXTCMD CRYPT
Alas, no incoming IPv6 yet...
Would someone try to connect to binkd on the standard port using
IPv6?
Would someone try to connect to binkd on the standard port using
IPv6? Any one of these addresses should work:
bbs.quinnnet.org binkd6.quinnnet.org binkd6.us99.us
Would someone try to connect to binkd on the standard port using
IPv6? Any one of these addresses should work:
bbs.quinnnet.org binkd6.quinnnet.org binkd6.us99.us
Connection successful, got an answer from some broken binkp implementation.
Would someone try to connect to binkd on the standard port using IPv6?
Any one of these addresses should work:
bbs.quinnnet.org
binkd6.quinnnet.org
binkd6.us99.us
*** Quoting Ray Quinn from a message to All ***
Would someone try to connect to binkd on the standard port using
IPv6?
Seems to work from here:
22:10 [269083] BEGIN, binkd/1.1a-115/Linux -vpP 1:214/22 binkd.cfg
22:10 [269083] creating a poll for 1:214/22@fidonet (`d' flavour)
22:10 [269083] clientmgr started
$ -d 1:214/22@fidonet
+ 22:10 [269084] call to 1:214/22@fidonet
22:10 [269084] trying binkd6.quinnnet.org [2001:470:1f04:8c6::2]...
22:10 [269084] connected
+ 22:10 [269084] outgoing session with binkd6.quinnnet.org:24554 [2001:470:1f04:8c6::2]
- 22:10 [269084] OPT CRAM-MD5-465f8910a99dc30994a52b33783a4618 CRYPT
+ 22:10 [269084] Remote requests MD mode
+ 22:10 [269084] Remote requests CRYPT mode
- 22:10 [269084] SYS US 99 BBS
- 22:10 [269084] ZYZ Ray Quinn
- 22:10 [269084] LOC Visalia, CA
- 22:10 [269084] NDL 115200,TCP,BINKP
- 22:10 [269084] TIME Fri Jul 29 2022 19:10:22 GMT-0700 (PDT)
- 22:10 [269084] VER BinkIT/2.41,JSBinkP/4,sbbs3.19c/Linux binkp/1.1
+ 22:10 [269084] addr: 1:214/22@fidonet
+ 22:10 [269084] done (to 1:214/22@fidonet, OK, S/R: 0/0 (0/0 bytes))
22:10 [269084] session closed, quitting...
22:10 [269083] rc(269084)=0
22:10 [269083] the queue is empty, quitting...
Hi Alexey,
On 2022-07-30 13:41:42, you wrote to Ray Quinn:
Would someone try to connect to binkd on the standard port using
IPv6? Any one of these addresses should work:
bbs.quinnnet.org binkd6.quinnnet.org binkd6.us99.us
Connection successful, got an answer from some broken binkp
implementation.
What is broken about it? I get binkit (synchronet) on the line. My
binkd usually has no problem exchanging mail with those...
Connection successful, got an answer from some broken binkp implementation.
Thank you. I know it used to work a long time ago as I was once number
32 or so on "The List."
Thank you. I know it used to work a long time ago as I was once
number 32 or so on "The List."
That's Jay Harris. Ray is #107 ... ???
Hello Wilfred,
On Sunday July 31 2022 12:18, you wrote to me:
That's Jay Harris. Ray is #107 ... ???
Ah, these North Americans. They all look alike to me. ;-)
Travis, welcome to the Fidonet IPv6 club!
Sysop: | Nelgin |
---|---|
Location: | Plano, TX |
Users: | 510 |
Nodes: | 10 (1 / 9) |
Uptime: | 125:06:30 |
Calls: | 8,198 |
Files: | 15,443 |
Messages: | 913,613 |