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


... I got some powdered water, but I don't know what to add.
--- SBBSecho 3.00-Win32
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Hello Allen,

On Sunday March 05 2017 14:38, you wrote to All:

On my fiber router I am getting this now...

IPv6

Status
Available

Global Unicast IPv6 Address
2602:306:83c1:a710::1

That is the global address of your router.

Ping is not enabled on your router.

D:\FIDO>ping 2602:306:83c1:a710::1

Ping wird ausgef�hrt f�r 2602:306:83c1:a710::1 mit 32 Bytes Daten:

Zeit�berschreitung der Anforderung.
Zeit�berschreitung der Anforderung.
Zeit�berschreitung der Anforderung.
Zeit�berschreitung der Anforderung.

Ping-Statistik f�r 2602:306:83c1:a710::1:
Pakete: Gesendet = 4, Empfangen = 0, Verloren = 4 (100% Verlust),

Link-local IPv6 Address
fe80::9662:69ff:fee2:7d20

The so called link local address of your router. Only vaild on the LAN.

IPv6 Addressing Subnet (including length)
2602:306:83c1:a710::/64

That is the subnet assigned to your LAN. Any device on your LAN that supports IPv6 will get one or more IPv6 addresses in this range.

WHich one is my inbound IP address?

You do not have just ONE inbound IPv6 address. Every device on your LAN has one or more of them.

Type ipconfig in the console of one of your Windows machines and tell us what happens.



Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20161221
* Origin: he.net certified sage (2:280/5555)

Allen Prunty wrote to All <=-

Global Unicast IPv6 Address
2602:306:83c1:a710::1

This is your public IP.

Link-local IPv6 Address
fe80::9662:69ff:fee2:7d20

This one is only valid on your LAN and not reachable from outside.

IPv6 Addressing Subnet (including length)
2602:306:83c1:a710::/64

This specifies the address block routed to you.

WHich one is my inbound IP address?

The first one. :)


... Years of development: We finally got one to work.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)

Re: IPV6 help
By: Michiel van der Vlist to Allen Prunty on Sun Mar 05 2017 10:23 pm


Windows IP Configuration


Ethernet adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

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

Tunnel adapter isatap.attlocal.net:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : attlocal.net

Tunnel adapter isatap.{25EFC15E-69C3-46E6-BFE7-A4A967D5FA4F}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :


... Almost everything in life is easier to get into than out of.
--- SBBSecho 3.00-Win32
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Hi Allen!

05 Mar 2017 14:38, from Allen Prunty -> All:

IPv6 Addressing Subnet (including length)
2602:306:83c1:a710::/64
WHich one is my inbound IP address?

You have 2^64 inbound IPs, if the firewall is not blocking inbound traffic.

The router will advertise the /64 prefix, and your IPv6 LAN devices will autoconfigure public IPv6 addresses.
You just need to assure that the firewal will let through the traffic.

CU, Ricsi

--- GoldED+/LNX
* Origin: Those who live by the sword KILL those who don't (2:310/31)

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.

CU, Ricsi

--- GoldED+/LNX
* Origin: Oxymorons... military intelligence and tech support! (2:310/31)

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.

Good point, I'm used to looking at IPv6 addresses on the actual device I'm using.


... As easy as 3.1415926535897932384626433832795028841
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)

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

Try this on Allen...

Remember, if this box is not DMZ'd in your router, you'll have to set the firewall and allow this address in the router to access the ports you want.


--

Bill

Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net:81
FTP: ftp.tequilamockingbirdonline.net:2121
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
Radio: radio.tequilamockingbirdonline.net:8010/live


... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!
=== MultiMail/Win32 v0.50
--- SBBSecho 3.00-Win32
* Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)

Hello Allen,

On Sunday March 05 2017 17:22, you wrote to me:

Wireless LAN adapter Wireless Network Connection:

So that is your active interface.

Note: While in IPv4 an interface can have more than one IP address, it normally has only one. In IPv6 it is common that an interface has more than one IP address.

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

Let me fuck up the order...

Link-local IPv6 Address . . . . . : fe80::916b:b400:7e4b:ca4%11

Every IPv6 interface as at least one address: the link local address. It is assigned automatically, even if there is no router and no internet connection. A link local address alaways starts with fe80:: The so called prefix. The last 64 bits (916b:b400:7e4b:ca4) is the suffix. It is derived from the MAC address.

IPv6 Address. . . . . . . . . . . : 2602:306:83c1:a710:916b:b400:7e4b:ca4

This is the so called SLAAC address. Note that the suffix is the same as that of the link local address. The 2602:306:83c1:a710 is the prefix. The prefix is broadcast by your router's "router advertisements" The SLAAC address of the interface is derived from the prefix advertised by the router and the suffix derived from the MAC address. This is the address that you could use as the address to link to a host name that can be used by others to access servers on that interface.

IPv6 Address. . . . . . . . . . . : 2602:306:83c1:a710::40

This is probably an address assigned by DHCP6. I can't be sure without further information.

Temporary IPv6 Address. . . . . . : 2602:306:83c1:a710:446b:8c7b:c04d:2594

This is a so called Privacy Extension Address. Used for outgoing calls when PrivacyExtensiosn are enabled in Windows. Not to be used for incoming as a new one is generated every 24 hours.


Hope this helps


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20161221
* Origin: he.net certified sage (2:280/5555)

Re: IPV6 help
By: Michiel van der Vlist to Allen Prunty on Mon Mar 06 2017 12:38 am

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.

Allen


... What do you say we make some apple juice and fax it to each other?
--- SBBSecho 3.00-Win32
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Hello Allen,

On Sunday March 05 2017 21:00, you wrote to me:

I am going to have them put this in my ip configuration for my domain.

2602:306:83c1:a710:916b:b400:7e4b:ca4

That is no good if your mailer does not answer to that address:

+ 09:23 [2636] call to 1:2320/100@fidonet
09:23 [2636] trying 2602:306:83c1:a710:916b:b400:7e4b:ca4
[2602:306:83c1:a710:916b:b4007e4b:ca4]...
? 09:24 [2636] connection to 1:2320/100@fidonet failed: {W32 API
error 10060} Connection timed out
09:24 [2636] trying f100.n2320.z1.binkp.net [104.60.26.113]...
09:24 [2636] connected
+ 09:24 [2636] outgoing session with f100.n2320.z1.binkp.net:24554 [104.60.26.113]

Will this one get to me? It should pick up if it does because
everything is DMZed to the BBS Machine.

As you can see, it doesn't. You have to fix that first before you add an AAAA record to your host name. Advertising an IPv6 address that does not connect decreases your connectivity because the other side will try IPv6 first and time out.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20161221
* Origin: he.net certified sage (2:280/5555)

Hi Allen!

05 Mar 2017 21:00, from Allen Prunty -> Michiel van der Vlist:

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.

It does not answer to pings.
Are you sure the firewall lets it through

Something is not yet correct!

CU, Ricsi

--- GoldED+/LNX
* Origin: Superior ability breeds superior ambition (2:310/31)

Hello, Richard Menedetter : Tony Langdon.
On 06/03/2017 00:27 you wrote:

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

--- HotdogEd/2.13.4 (Android; Google Android; rv:1) Hotdoged/1480338873000 Hotd
* Origin: *** nntp://rbb.bbs.fi *** Lake Ylo *** Finland *** (2:221/360)

Hi Tommi!

06 Mar 2017 20:38, from Tommi Koivula -> 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. :)

Sure possible ... but the probability that this is Allens configuration is extremely small.

CU, Ricsi

--- GoldED+/LNX
* Origin: I shave with Occam's razor. (2:310/31)

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.


... Error reading REALITY.SYS - Solar System halted.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)

Hello Tony,

On Tuesday March 07 2017 08:16, you wrote to Tommi Koivula:

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.

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...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20161221
* Origin: he.net certified sage (2:280/5555)

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...

That makes sense.


... Hey, look! A completely new undocumented fea&%$#*@ NO CARRIER
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)

Hello Tony,

On Tuesday March 07 2017 11:13, you wrote to me:

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 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...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20161221
* Origin: he.net certified sage (2:280/5555)

Hello Tony!

07 Mar 17 08:16, you wrote to Tommi Koivula:

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.

Tommi's using this method to make his OS/2 system available via IPv6. OS/2's TCP/IP stack is IPv4 only.

Andrew

--- GoldED+/LNX 1.1.5-b20161221
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

Re: IPV6 help
By: Richard Menedetter to Allen Prunty on Mon Mar 06 2017 09:54 am

Something is not yet correct!

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.

Allen

... Seeing is deceiving. It's eating that's believing.
--- SBBSecho 3.00-Win32
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Michiel van der Vlist wrote to Tony Langdon <=-

That Ipv6 to Ipv4 proxy trick only works for incoming. Outgoing is a another story..

Yep, I can see that.

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...

Agree on both counts, but sometimes you might want a legacy system to interact with the IPv6 Internet.


... Command not found. Damn, it was here a minute ago... hold on...
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)

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.

Yes, once OS/2 was mentioned, everything fell into place.


... Pentium Myth #1: The computer only does what you tell it.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)

Hello Allen,

On Tuesday March 07 2017 03:25, you wrote to Richard Menedetter:

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.

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.

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.

Don't give up so easely.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20161221
* Origin: he.net certified sage (2:280/5555)

Re: IPV6 help
By: Michiel van der Vlist to Allen Prunty on Tue Mar 07 2017 01:38 pm

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.

I have done all of that in the past and they reverted back to an older firmware as they had problems with some on the newer firmware (My guess is they had idiots who could not separate the ipv4 fromt he ipv6) You can no longer specify IPV6 ports.

Plus to complicate things I have a business class router and it is fiber. I have to practically call them when they change my firmware and beg for them to reset what they have changed.

If it wasn't the cheapest fiber in town I would have switched a long time ago, but I retired from the industry and this is at a price I can afford if I give it up I will never be able to afford this class of service again.

Allen

... A continuing flow of paper is sufficient to continue the flow of paper.
--- SBBSecho 3.00-Win32
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

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.

Yes to both counts. I know I have to open access to incoming traffic on my router, before the outside world can see IPv6 hosts on my LAN, as it defaults to blocking all incoming IPv6 traffic (which is how it should be). And Windows Firewall can catch you off guard when you least expect it. It usually tries to help you, but it's also possible to miss the dialog that pops up, and occasionally, it doesn't pop up at all.


... We are the very model of cartoon individuals.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)

Exactly. ;)

There will be legacy systems in the future that have to live in an IPv6 network. :)

Yes. IPv4 will not disappear for a long time. Or ever. ;)

'Tommi

--- Sylpheed 3.5.1 (GTK+ 2.24.23; i686-pc-mingw32)
* Origin: *** nntp://rbb.bbs.fi *** Lake Ylo *** Finland *** (2:221/360)