I have a semi working tunnel to he.net have assigned ip's etc. Can
make outgoing FTN/WEB connections. Doing a port scan works to the 2001:470:24:e::10 binkp port says it's open and mbse's log shows
the scan.
pings/traceroutes are also not working.
(prob not a bad thing).
But Scott z3c cant make connections via ipv6 to my system and mine
cant to his.
Does anyone in the echo have experiance with IPV6 and PFsense? (Using
2.2 Beta from Nov 20, as 2.1.5 crashes with my hardware).
I have a semi working tunnel to he.net have assigned ip's etc. Can
make outgoing FTN/WEB connections. Doing a port scan works to the 2001:470:24:e::10 binkp port says it's open and mbse's log shows
the scan.
But Scott z3c cant make connections via ipv6 to my system and mine
cant to his.
I can connect via ipv6 to my other links (Wilfred van Velzen/Nicholas Boel).
pings/traceroutes are also not working. (prob not a bad thing).
Outgoing binkp connections are working now. Still can't ping you
though. Can you try binkp to me again? 2001:4479:cbce:df9b:fc12::3
port 24555.
I can connect to your system:
Can you connect mine?
My IPv6 node connected just fine to sysgod.org:24554. Here's the log:
It appears that your IPv6 issues are solved.
Thanks. That's a 6to4 address which will be replaced as of the next nodelist (or sooner for systems that support DNS SRV records).
Hopefully the new address will be more reliable.
Thanks. That's a 6to4 address which will be replaced as of theDoes that effect 2:203/0 in any way? I've had you added here for
next nodelist (or sooner for systems that support DNS SRV
records). Hopefully the new address will be more reliable.
ages (can't remember why) with an extremely hard to remember session password 2:203/0 <-> 3:712/848.
Outgoing binkp connections are working now. Still can't ping you
though. Can you try binkp to me again? 2001:4479:cbce:df9b:fc12::3
port 24555.
2001:470:24:e::10 binkp port says it's open and mbse's log shows
the scan.
It sounds like you have incoming working properly.
But Scott z3c cant make connections via ipv6 to my system and
mine cant to his.
I can connect via ipv6 to my other links (Wilfred van
Velzen/Nicholas Boel).
Since connections are working for other nodes, I think the problem is probably somewhere in Scott's setup or with his ISP. I was able to
poll your system via IPv6 with no problem.
pings/traceroutes are also not working. (prob not a bad thing).
This could be firewall related. I haven't used PFSense myself, but I might be able to figure out a solution if you netmail me with a copy
of your firewall rules. If I can figure out ip6tables, PFSense should
be a piece of cake.
Thanks. That's a 6to4 address which will be replaced as of the next nodelist (or sooner for systems that support DNS SRV records).
Hopefully the new address will be more reliable.
6to4 is known to have "issues". Im am sure dumping 6to4 and replacing
it with a 6in4 tunnel will be more reliable.
You have to decide about the port numbers though. If you want to
continue to receive incoming om port 24555, the nodelist should also reflect that.
binkp.net also uses SRV records to signal a non standard port. So that won't work for mailers not supporting SRV...
6to4 is known to have "issues". Im am sure dumping 6to4 and
replacing it with a 6in4 tunnel will be more reliable.
Yep. Actually I take that back, it's 6RD not 6in4.
Does binkp.net handle multiple ports in the nodelist? ie.
IBN,IBN:24555 > two separate SRV records with the appropriate
priorities?
Sysop: | Nelgin |
---|---|
Location: | Plano, TX |
Users: | 611 |
Nodes: | 10 (1 / 9) |
Uptime: | 48:22:06 |
Calls: | 9,831 |
Files: | 16,214 |
Messages: | 1,080,104 |