• Ipv6 review...

    From Bill McGarrity@1:266/404 to All on Fri Jan 2 19:44:00 2015
    Hiya Gang...

    First, I appreciate all the help everyone has given me. Thanks...

    Now, here is my plan.

    I am going to leave my 1:266/404 node strictly IPv4. I am going to contact my NC and ask for another node # to operate strickly IPv6. I've already setup ipv6.tequilamockingbirdonline.net as a AAAA dns and it's working. That's the INA I'll be using. I am going to forget D'Bridge for now and just run binkd as a service stricly for that node and still let IRex handle the IPv4..

    OR...

    Will binkd handle both IPv4 and IPv6 and figure out the correct one to use on connect?

    Now, to work on the correct flags for the new node. Being it is IPv6 only, in reading I should tell Mike to also add U,INO4?

    One other thing. Should both nodes share the same netmail, inbound and outbound folders? I say yes but I wanted to make sure.

    As I move along I know there are a few more questions and I'll probably have to bug Rob but this is a good start and I'm getting there.

    Thanks again all!!


    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    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 2.27-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Nicholas Boel@1:154/701 to Bill McGarrity on Sat Jan 3 00:21:40 2015
    Hello Bill,

    On 02 Jan 15 19:44, Bill McGarrity wrote to All:

    I am going to leave my 1:266/404 node strictly IPv4. I am going to contact my NC and ask for another node # to operate strickly IPv6.
    I've already setup ipv6.tequilamockingbirdonline.net as a AAAA dns and it's working. That's the INA I'll be using. I am going to forget D'Bridge for now and just run binkd as a service stricly for that node
    and still let IRex handle the IPv4..

    Odd thing, your v6 address has changed yet again, even though your ipv6.tequilamockingbirdonline.net is responding.

    Will binkd handle both IPv4 and IPv6 and figure out the correct one to
    use on connect?

    Yes. Most definitely. I only use binkd here, and I run dual-stack with IPv4 and IPv6 on the same addresses (I have two nodes with both).

    Now, to work on the correct flags for the new node. Being it is IPv6 only, in reading I should tell Mike to also add U,INO4?

    If you were to do it that way, then yes (if the U flag is required at all).

    One other thing. Should both nodes share the same netmail, inbound
    and outbound folders? I say yes but I wanted to make sure.

    I don't follow on this one. They don't *have* to, but I suppose they could?

    As I move along I know there are a few more questions and I'll
    probably have to bug Rob but this is a good start and I'm getting
    there.

    Rob currently has nothing to do with IPv6. Deuce is the man to talk to about it, as he has made a patch for Synchronet to support it, and is waiting to be able to add it to CVS as soon as Rob is ready for it... or something.

    Regards,
    Nick

    --- GoldED+/LNX 1.1.5-b20130910
    * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/701)
  • From Michiel van der Vlist@2:280/5555 to Bill McGarrity on Sat Jan 3 17:24:12 2015
    Hello Bill,

    On Friday January 02 2015 19:44, you wrote to All:

    First, I appreciate all the help everyone has given me. Thanks...

    You'r welcome.

    Now, here is my plan.

    Ah, a man with a plan...;-)

    I am going to leave my 1:266/404 node strictly IPv4. I am going to contact my NC and ask for another node # to operate strickly IPv6.
    I've already setup ipv6.tequilamockingbirdonline.net as a AAAA dns and it's working. That's the INA I'll be using. I am going to forget D'Bridge for now and just run binkd as a service stricly for that node
    and still let IRex handle the IPv4..

    Forgive my bluntness, but I think that is a lousy plan. By splitting up your IP connectivity between IPv4 and IPv6 and using separate nodes with a different mailer for each, you are making things much more complicated for both yourself and te rest of Fidonet.

    OR...

    Will binkd handle both IPv4 and IPv6 and figure out the correct one to
    use on connect?

    Every IPv6 capable mailer will also do IPv4 and figure out for itself which one to use. And if IPv6 does not work for some reason, it will automativally fall back to IPv4 if possible, And vice versa. Actually, it will be the OS that does all that. The mailer is on the application layer, IPv4/IPv6 is on the internet layer. Two layers lower in the pile.

    Now, to work on the correct flags for the new node. Being it is IPv6 only, in reading I should tell Mike to also add U,INO4?

    An IPv6 only node should carry the INO4 flag. As a regular flag, not a user flag.

    But I strongly advise against that. Things get much more complicated with having to maintain a separate config for IPv6 and IPv4. Besides: automatic fall back will not work with a separate IPv4 and IPv6 mailer.

    One other thing. Should both nodes share the same netmail, inbound
    and outbound folders? I say yes but I wanted to make sure.

    See? There you go already! ;-)

    Forget about Irex. It has not been updated in a decade, it is de facto abandonware. Perhaps you gave up on D'Bridge too quickly.

    Or.. go for binkd. It actually is the only mailer for Windows that has proven to do IPv6 and it presently is the most popular binkd mailer, so there is a lot op experience out there.



    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: 2001:470:1f15:1117::1 (2:280/5555)
  • From Bill McGarrity@1:266/404 to Michiel van der Vlist on Sat Jan 3 18:01:00 2015
    On 01-03-15 17:24, Michiel van der Vlist wrote to Bill McGarrity <=-

    @MSGID: <54A82508.624.2ipv6@tequilamockingbirdonline.net>
    @TZ: 003c
    Hello Bill,

    On Friday January 02 2015 19:44, you wrote to All:

    First, I appreciate all the help everyone has given me. Thanks...

    You'r welcome.

    Now, here is my plan.

    Ah, a man with a plan...;-)

    I didn't say it was a good plan... lol

    I am going to leave my 1:266/404 node strictly IPv4. I am going to contact my NC and ask for another node # to operate strickly IPv6.
    I've already setup ipv6.tequilamockingbirdonline.net as a AAAA dns and it's working. That's the INA I'll be using. I am going to forget D'Bridge for now and just run binkd as a service stricly for that node
    and still let IRex handle the IPv4..

    Forgive my bluntness, but I think that is a lousy plan. By splitting up your IP connectivity between IPv4 and IPv6 and using separate nodes
    with a different mailer for each, you are making things much more complicated for both yourself and te rest of Fidonet.

    Gotcha... scratch that...

    OR...

    Will binkd handle both IPv4 and IPv6 and figure out the correct one to
    use on connect?

    Every IPv6 capable mailer will also do IPv4 and figure out for itself which one to use. And if IPv6 does not work for some reason, it will automativally fall back to IPv4 if possible, And vice versa. Actually,
    it will be the OS that does all that. The mailer is on the application layer, IPv4/IPv6 is on the internet layer. Two layers lower in the
    pile.

    OK... so that answers that... just run binkd for both.. makes like easier...


    Now, to work on the correct flags for the new node. Being it is IPv6 only, in reading I should tell Mike to also add U,INO4?

    An IPv6 only node should carry the INO4 flag. As a regular flag, not a user flag.

    Got it... but that's moot now...

    But I strongly advise against that. Things get much more complicated
    with having to maintain a separate config for IPv6 and IPv4. Besides: automatic fall back will not work with a separate IPv4 and IPv6 mailer.

    One other thing. Should both nodes share the same netmail, inbound
    and outbound folders? I say yes but I wanted to make sure.

    See? There you go already! ;-)


    LOL... hey.. I'm treading water here... but still breathing..

    Forget about Irex. It has not been updated in a decade, it is de facto abandonware. Perhaps you gave up on D'Bridge too quickly.

    Or.. go for binkd. It actually is the only mailer for Windows that has proven to do IPv6 and it presently is the most popular binkd mailer, so there is a lot op experience out there.

    That's what I'll do. I wish it had some sort of interface so I can see what's it's doing. Visual acknowledgement gives me that warm fuzzy feeling.. :)

    thanks for the help. I'll work on things in the next couple of days. Need to work on the cfg including session passwords and stuff. At least the hard part is over.... I think :)


    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    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 2.27-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Nicholas Boel on Sat Jan 3 18:05:00 2015
    On 01-03-15 00:21, Nicholas Boel wrote to Bill McGarrity <=-

    Hiya Nick...

    On 02 Jan 15 19:44, Bill McGarrity wrote to All:

    I am going to leave my 1:266/404 node strictly IPv4. I am going to contact my NC and ask for another node # to operate strickly IPv6.
    I've already setup ipv6.tequilamockingbirdonline.net as a AAAA dns and it's working. That's the INA I'll be using. I am going to forget D'Bridge for now and just run binkd as a service stricly for that node
    and still let IRex handle the IPv4..

    Odd thing, your v6 address has changed yet again, even though your ipv6.tequilamockingbirdonline.net is responding.

    Michiel questioned the same thing... view the previous post to him.

    Will binkd handle both IPv4 and IPv6 and figure out the correct one to
    use on connect?

    Yes. Most definitely. I only use binkd here, and I run dual-stack with IPv4 and IPv6 on the same addresses (I have two nodes with both).

    Now, to work on the correct flags for the new node. Being it is IPv6 only, in reading I should tell Mike to also add U,INO4?

    If you were to do it that way, then yes (if the U flag is required at all).

    Was just confirmed it wasn't but it's going to be moot as I'll be running binkd for both flavors...

    One other thing. Should both nodes share the same netmail, inbound
    and outbound folders? I say yes but I wanted to make sure.

    I don't follow on this one. They don't *have* to, but I suppose they could?

    As I move along I know there are a few more questions and I'll
    probably have to bug Rob but this is a good start and I'm getting
    there.

    Rob currently has nothing to do with IPv6. Deuce is the man to talk to about it, as he has made a patch for Synchronet to support it, and is waiting to be able to add it to CVS as soon as Rob is ready for it...
    or something.

    I'll talk to him then.. see where he's at.

    Thanks!


    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    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 2.27-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)