On my fiber router I am getting this now...
IPv6
Status
Available
Global Unicast IPv6 Address
2602:306:83c1:a710::1
Link-local IPv6 Address
fe80::9662:69ff:fee2:7d20
IPv6 Addressing Subnet (including length)
2602:306:83c1:a710::/64
WHich one is my inbound IP address?
Allen Prunty wrote to All <=-
Global Unicast IPv6 Address
2602:306:83c1:a710::1
Link-local IPv6 Address
fe80::9662:69ff:fee2:7d20
IPv6 Addressing Subnet (including length)
2602:306:83c1:a710::/64
WHich one is my inbound IP address?
IPv6 Addressing Subnet (including length)
2602:306:83c1:a710::/64
WHich one is my inbound IP address?
Global Unicast IPv6 AddressThe first one. :)
2602:306:83c1:a710::1
WHich one is my inbound IP address?
Richard Menedetter wrote to Tony Langdon <=-
That is the address of his router.
I do not assume that he will run BinkD on the router.
Allen Prunty wrote to Michiel van der Vlist on 03-05-17 17:22 <=-
Re: IPV6 help
By: Michiel van der Vlist to Allen Prunty on Sun Mar 05 2017 10:23 pm
IPv6 Address. . . . . . . . . . . : 2602:306:83c1:a710:916b:b400:7e4b:ca4
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : attlocal.net
IPv6 Address. . . . . . . . . . . : 2602:306:83c1:a710::40
IPv6 Address. . . . . . . . . . . : 2602:306:83c1:a710:916b:b400:7e4b:ca4
Temporary IPv6 Address. . . . . . : 2602:306:83c1:a710:446b:8c7b:c04d:2594
Link-local IPv6 Address . . . . . : fe80::916b:b400:7e4b:ca4%11
IPv4 Address. . . . . . . . . . . : 192.168.1.233
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::9662:69ff:fee2:7d20%11
192.168.1.254
Link-local IPv6 Address . . . . . : fe80::916b:b400:7e4b:ca4%11
IPv6 Address. . . . . . . . . . . : 2602:306:83c1:a710:916b:b400:7e4b:ca4
IPv6 Address. . . . . . . . . . . : 2602:306:83c1:a710::40
Temporary IPv6 Address. . . . . . : 2602:306:83c1:a710:446b:8c7b:c04d:2594
I am going to have them put this in my ip configuration for my domain.
2602:306:83c1:a710:916b:b400:7e4b:ca4
Will this one get to me? It should pick up if it does because
everything is DMZed to the BBS Machine.
I am going to have them put this in my ip configuration for my domain. 2602:306:83c1:a710:916b:b400:7e4b:ca4
Will this one get to me? It should pick up if it does because
everything is DMZed to the BBS Machine.
Hi Tony!
06 Mar 2017 08:09, from Tony Langdon -> Allen Prunty:
Global Unicast IPv6 Address
2602:306:83c1:a710::1
WHich one is my inbound IP address?
The first one. :)???
That is the address of his router.
I do not assume that he will run BinkD on the router.
Perhaps not.. But I'm running xinetd in my dd-wrt router to forward incoming binkp ipv6 to my OS/2. In that case the router address is
used. :)
Tommi Koivula wrote to Richard Menedetter <=-
Perhaps not.. But I'm running xinetd in my dd-wrt router to forward incoming binkp ipv6 to my OS/2. In that case the router address is
used. :)
Tommi Koivula wrote to Richard Menedetter <=-
Perhaps not.. But I'm running xinetd in my dd-wrt router to
forward incoming binkp ipv6 to my OS/2. In that case the router
address is used. :)
Umm, why forward the traffic? The idea of IPv6 is that there's
sufficient address space for every device to have a public IP.
Michiel van der Vlist wrote to Tony Langdon <=-
Because OS/2 does no support IPv6. So he has to revert to some tricks
to make his OS/2 mailer respond to IPv6 calls...
Because OS/2 does not support IPv6. So he has to revert to some
tricks to make his OS/2 mailer respond to IPv6 calls...
That makes sense.
Perhaps not.. But I'm running xinetd in my dd-wrt router to
forward incoming binkp ipv6 to my OS/2. In that case the router
address is used. :)
Umm, why forward the traffic? The idea of IPv6 is that there's
sufficient address space for every device to have a public IP.
Something is not yet correct!
Michiel van der Vlist wrote to Tony Langdon <=-
That Ipv6 to Ipv4 proxy trick only works for incoming. Outgoing is a another story..
That makes sense.
Depends on your definition of "sense" I'd say. If I want IPv6 and <whatever I use now> does not support it. I'd go look for something to replace <whatvere I use now> by something that does support IPv6.
But this is not the place for an OS war...
Andrew Leary wrote to Tony Langdon <=-
Tommi's using this method to make his OS/2 system available via IPv6. OS/2's TCP/IP stack is IPv4 only.
I am going to just wait until lightspeed fully takes over from Att.
This is getting to be rediculous, it works one week then stops working
the next.
I'm deleteing the aaaa record until I -have- to deal with it, then I
will put it in. I can do an IPV6 outbound no problem at all. Sooner
or later they will have to convert... probably more sooner than later.
I thank you very much for all of the help you have given me this
year... but I'm not going to expend any more energy on this until I
have to.
1) configure the firewall in your router to pass incoming IPv6 port 24554 to the destination. Normally the default setting blocks all unsollicited incoming packets.
2) configure the windows firewall on your fido machine to pass IPv6 port 24554.
Michiel van der Vlist wrote to Allen Prunty <=-
Waiting for them will only result in improvement if the problem lies
with them. But that is problably not the case. More likely you have a firewall problem. To properly respond to incming calls, you have to:
1) configure the firewall in your router to pass incoming IPv6 port
24554 to the destination. Normally the default setting blocks all unsollicited incoming packets.
2) configure the windows firewall on your fido machine to pass IPv6
port 24554.
Exactly. ;)
There will be legacy systems in the future that have to live in an IPv6 network. :)
Sysop: | Nelgin |
---|---|
Location: | Plano, TX |
Users: | 615 |
Nodes: | 10 (1 / 9) |
Uptime: | 54:38:50 |
Calls: | 9,850 |
Calls today: | 5 |
Files: | 96,973 |
Messages: | 1,080,751 |
Posted today: | 1 |