• Connect...??

    From Bill McGarrity@1:266/404 to All on Wednesday, January 11, 2017 12:41:00
    Hiya Gang...

    Cound someone do me a favor and see if they can connect via binkd to hub.tequilamockingbirdonline.net:24555

    Thanks!!


    --

    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)
  • From Wilfred van Velzen@2:280/464 to Bill McGarrity on Wednesday, January 11, 2017 19:54:26
    Hi,

    On 2017-01-11 12:41:00, Bill McGarrity wrote to All:
    about: "Connect...??":

    Cound someone do me a favor and see if they can connect via binkd to hub.tequilamockingbirdonline.net:24555

    # telnet hub.tequilamockingbirdonline.net 24555
    Trying 2601:8b:8400:5477:a9a2:7e4e:e35d:4239...
    telnet: connect to address 2601:8b:8400:5477:a9a2:7e4e:e35d:4239: Connection refused
    Trying 69.248.146.68...
    telnet: connect to address 69.248.146.68: Connection refused

    Nope...

    Bye, Wilfred.


    --- FMail-W32 1.73.12.63-B20170110
    * Origin: Native IPv6 connectable node (2:280/464)
  • From Michiel van der Vlist@2:280/5555 to Bill McGarrity on Wednesday, January 11, 2017 19:59:24
    Hello Bill,

    On Wednesday January 11 2017 12:41, you wrote to All:

    Cound someone do me a favor and see if they can connect via binkd to hub.tequilamockingbirdonline.net:24555

    19:57 [1996] creating a poll for 1:266/404@fidonet (`d' flavour)
    19:57 [1996] clientmgr started
    + 19:57 [4048] call to 1:266/404@fidonet
    19:57 [4048] trying hub.tequilamockingbirdonline.net
    [2601:8b:8400:5477:a9a2:7e4e:e35d:4239]...
    ? 19:57 [4048] connection to 1:266/404@fidonet failed: {W32 API error
    10061} Connection refused
    19:57 [4048] trying hub.tequilamockingbirdonline.net [69.248.146.68]:24554... ? 19:57 [4048] connection to 1:266/404@fidonet failed: {W32 API error
    10061} Connection refused
    19:57 [1996] the queue is empty, quitting...


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: http://www.vlist.eu (2:280/5555)
  • From Dan Richter@1:317/3 to Bill McGarrity on Wednesday, January 11, 2017 12:02:00
    On 01/11/17, Bill McGarrity said the following...

    Cound someone do me a favor and see if they can connect via binkd to hub.tequilamockingbirdonline.net:24555

    Bill,

    I am unable to connect to it. I get a "Connect failed".


    Dan Richter
    aka Black Panther
    Sysop - Castle Rock BBS

    --- Mystic BBS v1.12 A31 (Windows)
    * Origin: Castle Rock BBS - Rio Rancho, NM (1:317/3)
  • From Bill McGarrity@1:266/404 to Michiel van der Vlist on Wednesday, January 11, 2017 16:19:00
    Michiel van der Vlist wrote to Bill McGarrity <=-

    Hiya Michiel...

    On Wednesday January 11 2017 12:41, you wrote to All:

    Cound someone do me a favor and see if they can connect via binkd to hub.tequilamockingbirdonline.net:24555

    19:57 [1996] creating a poll for 1:266/404@fidonet (`d' flavour)
    19:57 [1996] clientmgr started
    + 19:57 [4048] call to 1:266/404@fidonet
    19:57 [4048] trying hub.tequilamockingbirdonline.net
    [2601:8b:8400:5477:a9a2:7e4e:e35d:4239]...
    ? 19:57 [4048] connection to 1:266/404@fidonet failed: {W32 API error
    10061} Connection refused
    19:57 [4048] trying hub.tequilamockingbirdonline.net [69.248.146.68]:24554... ? 19:57 [4048] connection to 1:266/404@fidonet failed: {W32 API error
    10061} Connection refused
    19:57 [1996] the queue is empty, quitting...


    From the looks of your log you tried on 24554. I made the change on my end from 24555 to 24554. Can you try it again please.

    Thanks


    --

    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)
  • From Bill McGarrity@1:266/404 to Wilfred van Velzen on Wednesday, January 11, 2017 16:20:00
    Wilfred van Velzen wrote to Bill McGarrity <=-


    On 2017-01-11 12:41:00, Bill McGarrity wrote to All:
    about: "Connect...??":

    Cound someone do me a favor and see if they can connect via binkd to hub.tequilamockingbirdonline.net:24555

    # telnet hub.tequilamockingbirdonline.net 24555
    Trying 2601:8b:8400:5477:a9a2:7e4e:e35d:4239...
    telnet: connect to address 2601:8b:8400:5477:a9a2:7e4e:e35d:4239: Connection refused
    Trying 69.248.146.68...
    telnet: connect to address 69.248.146.68: Connection refused

    Nope...

    Thank you....


    --

    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)
  • From Bill McGarrity@1:266/404 to Dan Richter on Wednesday, January 11, 2017 16:20:00
    Dan Richter wrote to Bill McGarrity <=-

    On 01/11/17, Bill McGarrity said the following...

    Cound someone do me a favor and see if they can connect via binkd to hub.tequilamockingbirdonline.net:24555

    Bill,

    I am unable to connect to it. I get a "Connect failed".


    Thanks Dan...


    --

    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)
  • From Wilfred van Velzen@2:280/464 to Bill McGarrity on Wednesday, January 11, 2017 22:30:09
    Hi,

    On 2017-01-11 16:19:00, Bill McGarrity wrote to Michiel van der Vlist:
    about: "Re: Connect...??":

    From the looks of your log you tried on 24554. I made the change on
    my end
    from 24555 to 24554. Can you try it again please.

    Still blocked:

    # telnet hub.tequilamockingbirdonline.net 24554
    Trying 2601:8b:8400:5477:a9a2:7e4e:e35d:4239...
    telnet: connect to address 2601:8b:8400:5477:a9a2:7e4e:e35d:4239: Connection refused
    Trying 69.248.146.68...
    telnet: connect to address 69.248.146.68: Connection refused


    Bye, Wilfred.


    --- FMail-W32 1.73.12.63-B20170110
    * Origin: Native IPv6 connectable node (2:280/464)
  • From Vince Coen@2:250/1 to Bill McGarrity on Wednesday, January 11, 2017 22:00:43
    Hello Bill!

    Wednesday January 11 2017 12:41, you wrote to All:

    Hiya Gang...

    Cound someone do me a favor and see if they can connect via binkd to hub.tequilamockingbirdonline.net:24555

    I have not been able to connect to you for same weeks.

    Have to wait for you to poll me.


    Vince

    --- Mageia Linux v5/Mbse v1.0.6/GoldED+/LNX 1.1.501-b20150715
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Bill McGarrity@1:266/404 to Vince Coen on Thursday, January 12, 2017 11:59:00
    Hiya Vince,,,

    Vince Coen wrote to Bill McGarrity <=-


    Wednesday January 11 2017 12:41, you wrote to Al

    Cound someone do me a favor and see if they can connect via binkd to hub.tequilamockingbirdonline.net:24555

    I have not been able to connect to you for same weeks.

    Have to wait for you to poll me.

    ok.. for some reason I needed to reboot the main server to get those ports open. All ports are now open for IPv4 and IPv6 now.

    The trick I'm trying to do is get the port 24555 open on the new Pi. I created a new sub-domain for it, detup the AAAA DNS but the router is being a pain in the ass... :/

    Everytime I open the port 24555 to the Pi the main server has issues. Clusterfuck. I'm reading the manuals to see if there is a solution.





    --

    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)
  • From Wilfred van Velzen@2:280/464 to Bill McGarrity on Thursday, January 12, 2017 19:05:07
    Hi,

    On 2017-01-12 11:59:00, Bill McGarrity wrote to Vince Coen:
    about: "Re: Connect...??":

    Cound someone do me a favor and see if they can connect via binkd to
    hub.tequilamockingbirdonline.net:24555

    ok.. for some reason I needed to reboot the main server to get those
    ports open. All ports are now open for IPv4 and IPv6 now.

    The trick I'm trying to do is get the port 24555 open on the new Pi. I created a new sub-domain for it, detup the AAAA DNS but the router is
    being
    a pain in the ass... :/

    Everytime I open the port 24555 to the Pi the main server has issues. Clusterfuck. I'm reading the manuals to see if there is a solution.

    I'm now getting a binkp connect on port 24554 on IPv4 but on IPv6 it's blocked.

    And no connects on port 24555...

    Bye, Wilfred.


    --- FMail-W32 1.73.12.63-B20170110
    * Origin: Native IPv6 connectable node (2:280/464)
  • From Nicholas Boel@1:154/10 to Bill McGarrity on Thursday, January 12, 2017 13:49:10
    Hello Bill,

    On Thu Jan 12 2017 11:59:00, Bill McGarrity wrote to Vince Coen:

    Have to wait for you to poll me.

    ok.. for some reason I needed to reboot the main server to get those
    ports open. All ports are now open for IPv4 and IPv6 now.

    The trick I'm trying to do is get the port 24555 open on the new Pi.
    I created a new sub-domain for it, detup the AAAA DNS but the router
    is being a pain in the ass... :/

    Everytime I open the port 24555 to the Pi the main server has issues. Clusterfuck. I'm reading the manuals to see if there is a solution.

    While you're opening port 24555 on your router, are you also running binkd to listen on that same port using the "iport 24555" option in your configuration file? If so, then it's probably your router being that pain in the ass. :)

    Forward port 24555 to the LAN IPv4 address of your Pi. And forward the same port for your IPv6 address of that Pi (if you are able to, of course).

    There really shouldn't be any interference between the two binkd's running, unless you're overlapping somewhere.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20161221
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From mark lewis@1:3634/12.73 to Bill McGarrity on Thursday, January 12, 2017 13:18:18

    On 2017 Jan 12 11:59:00, you wrote to Vince Coen:

    Everytime I open the port 24555 to the Pi the main server has issues. Clusterfuck. I'm reading the manuals to see if there is a solution.

    it should be a simple portforward to the rPi's IP... what router are you using??

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... Once is happenstance. Twice is coincidence. Thrice is enemy action.
    ---
    * Origin: (1:3634/12.73)
  • From Tony Langdon@3:633/410 to Nicholas Boel on Friday, January 13, 2017 08:26:00
    -=> Nicholas Boel wrote to Bill McGarrity <=-

    Forward port 24555 to the LAN IPv4 address of your Pi. And forward the same port for your IPv6 address of that Pi (if you are able to, of course).

    Hmm, one does not forward ports on IPv6, merely opens the packet filter. And yes, make sure binkd is listening on the same port as the outside world sees, since this will be needed for IPv6 (since IPv6 firewalling is just a packet filter).

    There really shouldn't be any interference between the two binkd's running, unless you're overlapping somewhere.

    Agreed.

    I run all my binkp services on the same port, because I have multiple public IPv4 (via VPN) and IPv6 addresses on the LAN.


    ... All's well that ends.
    --- MultiMail/Win32 v0.49
    * Origin: Freeway BBS - freeway.apana.org.au (3:633/410)
  • From Nicholas Boel@1:154/10 to Tony Langdon on Thursday, January 12, 2017 16:06:44
    Hello Tony,

    On Fri Jan 13 2017 08:26:00, Tony Langdon wrote to Nicholas Boel:

    Forward port 24555 to the LAN IPv4 address of your Pi. And
    forward the same port for your IPv6 address of that Pi (if you
    are able to, of course).

    Hmm, one does not forward ports on IPv6, merely opens the packet
    filter. And yes, make sure binkd is listening on the same port as the outside world sees, since this will be needed for IPv6 (since IPv6 firewalling is just a packet filter).

    On my router, the IPv6 packet filter is laid out exactly the same as the IPv4 port forwarding section. So however you want to describe it, I would do the exact same thing (settings-wise) for both IPv4 and IPv6.

    I run all my binkp services on the same port, because I have multiple public IPv4 (via VPN) and IPv6 addresses on the LAN.

    Congrats. Most of us don't have that luxury for IPv4, and it is definitely not helping Bill's issue. :)

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20161221
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Bill McGarrity@1:266/404 to Wilfred van Velzen on Thursday, January 12, 2017 18:26:00
    Wilfred van Velzen wrote to Bill McGarrity <=-

    On 2017-01-12 11:59:00, Bill McGarrity wrote to Vince Coen:
    about: "Re: Connect...??":

    Cound someone do me a favor and see if they can connect via binkd to
    hub.tequilamockingbirdonline.net:24555

    ok.. for some reason I needed to reboot the main server to get those
    ports open. All ports are now open for IPv4 and IPv6 now.

    The trick I'm trying to do is get the port 24555 open on the new Pi. I created a new sub-domain for it, detup the AAAA DNS but the router is
    being
    a pain in the ass... :/

    Everytime I open the port 24555 to the Pi the main server has issues. Clusterfuck. I'm reading the manuals to see if there is a solution.

    I'm now getting a binkp connect on port 24554 on IPv4 but on IPv6 it's blocked.

    And no connects on port 24555...

    I was actually having major issues with the main server (ftn.tequilamockingbirdonline.net) where 24254 on both ipv4 and ipv6 were blocked. Right now I repaired the issues where all port scanners say 24554 is now open on above INA.

    My problem is getting the 24555 open on the Pi. No matter what I do to the router it doesn't work. Still more testing... :)

    Thanks for your help.


    --

    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)
  • From Tony Langdon@3:633/410 to Nicholas Boel on Friday, January 13, 2017 10:42:00
    -=> Nicholas Boel wrote to Tony Langdon <=-

    On my router, the IPv6 packet filter is laid out exactly the same as
    the IPv4 port forwarding section. So however you want to describe it, I would do the exact same thing (settings-wise) for both IPv4 and IPv6.

    Same on mine, manufacturers dumbing things down too much, because there is a key difference between port forwarding and packet filtering. In port forwarding, the internal host can use a different port to what the public sees.
    With packet filtering, that's normally not possible, because the router is doing nothing more than accepting or blocking traffic to a specific port on a LAN host. It is not rewriting packets.

    So, when you're using IPv6, an extra constraint is that the host needs to be listening on the same port that the public sees (My router only has a single field for the port in IPv6).

    I run all my binkp services on the same port, because I have multiple public IPv4 (via VPN) and IPv6 addresses on the LAN.

    Congrats. Most of us don't have that luxury for IPv4, and it is
    definitely not helping Bill's issue. :)

    True, I did have to pay for it. :)


    ... To err is human. To forgive is against company policy.
    --- MultiMail/Win32 v0.49
    * Origin: Freeway BBS - freeway.apana.org.au (3:633/410)
  • From Tony Langdon@3:633/410 to Bill McGarrity on Friday, January 13, 2017 10:56:00
    Bill McGarrity wrote to Wilfred van Velzen <=-

    I was actually having major issues with the main server (ftn.tequilamockingbirdonline.net) where 24254 on both ipv4 and ipv6
    were blocked. Right now I repaired the issues where all port scanners
    say 24554 is now open on above INA.

    My problem is getting the 24555 open on the Pi. No matter what I do to the router it doesn't work. Still more testing... :)

    Thanks for your help.

    You need to break the problem down. Firstly, make sure binkd is listening on 24555 on the Pi, then test this across the LAN using telnet, or if possible, polling from one node to the other. Once that's working, then get the router configured and test from the outside world.


    ... BEWARE - Tagline Thief is in the area...
    --- MultiMail/Win32 v0.49
    * Origin: Freeway BBS - freeway.apana.org.au (3:633/410)
  • From Nicholas Boel@1:154/10 to Tony Langdon on Thursday, January 12, 2017 18:01:04
    Hello Tony,

    On Fri Jan 13 2017 10:42:00, Tony Langdon wrote to Nicholas Boel:

    Same on mine, manufacturers dumbing things down too much, because
    there is a key difference between port forwarding and packet
    filtering. In port forwarding, the internal host can use a different
    port to what the public sees. With packet filtering, that's normally
    not possible, because the router is doing nothing more than accepting
    or blocking traffic to a specific port on a LAN host. It is not
    rewriting packets.

    I have these settings. In my port forwarding section, I can set the service name, port range, local IP, local port, and protocol. In my inbound IPv6 firewall rules, I can set service name, remote IP/CIDR, local IP or fixed interface ID, port range, and protocol.

    So yes, IPv4 you can forward ports to others, whereas IPv6 you can only open ports directly to the address you specify.

    So, when you're using IPv6, an extra constraint is that the host needs
    to be listening on the same port that the public sees (My router only
    has a single field for the port in IPv6).

    Same with mine.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20161221
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Bill McGarrity@1:266/404 to Tony Langdon on Thursday, January 12, 2017 19:02:21
    Re: Re: Connect...??
    By: Tony Langdon to Nicholas Boel on Fri Jan 13 2017 08:26:00

    Hiya Tony...

    Forward port 24555 to the LAN IPv4 address of your Pi. And forward the same port for your IPv6 address of that Pi (if you are able to, of course).

    Hmm, one does not forward ports on IPv6, merely opens the packet
    filter. And yes, make sure binkd is listening on the same port as the outside world sees, since this will be needed for IPv6 (since IPv6 firewalling is just a packet filter).

    My router is a Linksys WRT1900AC and I have done all you've stated. I've enabled IPv6 firewall and then added a port service using the IPv6 address
    for the pi. I also set a single port forwarding for the IPv4 NAT address. Still nothing. The INA I'm using is: hub.tequilamockingbirdonline.net 24555

    I'm back playing in the router now....pain in the ass... lol

    Thanks


    --

    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!!
    --- SBBSecho 3.00-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to mark lewis on Thursday, January 12, 2017 19:17:33
    Re: Connect...??
    By: mark lewis to Bill McGarrity on Thu Jan 12 2017 13:18:18

    Hiya Mark....


    it should be a simple portforward to the rPi's IP... what router are
    you using??

    It's a LInksys WRT1900AC


    --

    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!!
    --- SBBSecho 3.00-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Tony Langdon on Thursday, January 12, 2017 19:24:13
    Re: Re: Connect...??
    By: Tony Langdon to Bill McGarrity on Fri Jan 13 2017 10:56:00

    Hiya Tony....


    You need to break the problem down. Firstly, make sure binkd is
    listening on 24555 on the Pi, then test this across the LAN using
    telnet, or if possible, polling from one node to the other. Once
    that's working, then get the router configured and test from the
    outside world.

    OK... that maybe the issue. Off of the main server (192.168.1.2) I try to telnet to hub.tequilamockingbirdonline.net 24555 (binkd is running on the pi using IPORT of 24555) I get: could not open connection to this host,
    connection failed. :/

    Is there anything I need to do to the pi??


    --

    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!!
    --- SBBSecho 3.00-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Nicholas Boel@1:154/10 to Bill McGarrity on Thursday, January 12, 2017 18:19:46
    Hello Bill,

    On Thu Jan 12 2017 19:02:20, Bill McGarrity wrote to Tony Langdon:

    My router is a Linksys WRT1900AC and I have done all you've stated.
    I've enabled IPv6 firewall and then added a port service using the
    IPv6 address for the pi. I also set a single port forwarding for the
    IPv4 NAT address. Still nothing. The INA I'm using is: hub.tequilamockingbirdonline.net 24555

    I'm back playing in the router now....pain in the ass... lol

    If everything you try seems to fail, you may want to see if there's an update for your router firmware. If you're using the original firmware from when you bought it, there may be a newer version out there. Take a look at the changelog
    and see if there was anything IPv6 related that could be causing whatever issues you're having.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20161221
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Bill McGarrity@1:266/404 to Nicholas Boel on Thursday, January 12, 2017 19:31:08
    Re: Connect...??
    By: Nicholas Boel to Bill McGarrity on Thu Jan 12 2017 18:19:46

    Hiya Nick...

    If everything you try seems to fail, you may want to see if there's
    an update for your router firmware. If you're using the original
    firmware from when you bought it, there may be a newer version out
    there. Take a look at the changelog and see if there was anything
    IPv6 related that could be causing whatever issues you're having.

    I have the router set for Auto updates. I just did it manually and said everything was up to date.

    I am a tad concerned about something though..

    If I try to ping the pi from the server. I get a could not find host. Yet, when I ping it from the laptop that's on the network, it sees it.

    This is really messing with my mind...


    --

    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!!
    --- SBBSecho 3.00-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Tony Langdon@3:633/410 to Nicholas Boel on Friday, January 13, 2017 11:41:00
    -=> Nicholas Boel wrote to Tony Langdon <=-

    I have these settings. In my port forwarding section, I can set the service name, port range, local IP, local port, and protocol. In my inbound IPv6 firewall rules, I can set service name, remote IP/CIDR,
    local IP or fixed interface ID, port range, and protocol.

    So yes, IPv4 you can forward ports to others, whereas IPv6 you can only open ports directly to the address you specify.

    As I expected, and same as my router. :)


    ... Fotoflagellation - The act of waving a Polaroid so it develops faster.
    --- MultiMail/Win32 v0.49
    * Origin: Freeway BBS - freeway.apana.org.au (3:633/410)
  • From Tony Langdon@3:633/410 to Bill McGarrity on Friday, January 13, 2017 11:44:00
    Bill McGarrity wrote to Tony Langdon <=-


    My router is a Linksys WRT1900AC and I have done all you've stated.
    I've enabled IPv6 firewall and then added a port service using the IPv6 address for the pi. I also set a single port forwarding for the IPv4
    NAT address. Still nothing. The INA I'm using is: hub.tequilamockingbirdonline.net 24555

    I'm back playing in the router now....pain in the ass... lol

    Well, from where I sit, it looks like nothing is listening on that port.

    synchronet@md-dstar ~ $ telnet hub.tequilamockingbirdonline.net 24555
    Trying 2601:8b:8400:5477:a9a2:7e4e:e35d:4239...
    Trying 69.248.146.68...
    telnet: Unable to connect to remote host: Connection refused synchronet@md-dstar ~ $ telnet -4 hub.tequilamockingbirdonline.net 24555
    Trying 69.248.146.68...
    telnet: Unable to connect to remote host: Connection refused


    ... BATCH - A group, kinda like a herd.
    --- MultiMail/Win32 v0.49
    * Origin: Freeway BBS - freeway.apana.org.au (3:633/410)
  • From Tony Langdon@3:633/410 to Bill McGarrity on Friday, January 13, 2017 11:49:00
    Bill McGarrity wrote to Tony Langdon <=-

    OK... that maybe the issue. Off of the main server (192.168.1.2) I try
    to telnet to hub.tequilamockingbirdonline.net 24555 (binkd is running
    on the pi using IPORT of 24555) I get: could not open connection to
    this host, connection failed. :/

    Is there anything I need to do to the pi??

    Yes, you need to tell binkd to listen on port 24555. Here's the relevant part of my binkd.conf file.

    # TCP settings. Leave this unchanged if not sure.
    #
    # Suffixes for time intervals are w for weeks, d for days,
    # h for hours, m for minutes, s or no suffix for seconds.
    # You can mix the suffixes, i.e. 1d12h is the same as 36h.
    #
    #iport 25555
    #oport 25555
    #oblksize 4096
    #timeout 5m
    connect-timeout 3m
    #bindaddr 192.168.0.3

    You would want to change iport to 24555 (in mine it's commented out).


    ... These are the voyages of the starchip Enterkey...
    --- MultiMail/Win32 v0.49
    * Origin: Freeway BBS - freeway.apana.org.au (3:633/410)
  • From Wilfred van Velzen@2:280/464.112 to Bill McGarrity on Friday, January 13, 2017 09:37:30
    Hi Bill,

    On 12 Jan 17 18:26, Bill McGarrity wrote to Wilfred van Velzen:
    about: "Re: Connect...??":

    Cound someone do me a favor and see if they can connect via binkd to
    hub.tequilamockingbirdonline.net:24555

    ok.. for some reason I needed to reboot the main server to get those
    ports open. All ports are now open for IPv4 and IPv6 now.

    The trick I'm trying to do is get the port 24555 open on the new Pi.
    I created a new sub-domain for it, detup the AAAA DNS but the router
    is
    being
    a pain in the ass... :/

    Everytime I open the port 24555 to the Pi the main server has issues.
    Clusterfuck. I'm reading the manuals to see if there is a solution.

    I'm now getting a binkp connect on port 24554 on IPv4 but on IPv6
    it's blocked.

    And no connects on port 24555...

    I was actually having major issues with the main server (ftn.tequilamockingbirdonline.net) where 24254 on both ipv4 and ipv6 were blocked. Right now I repaired the issues where all port scanners say 24554 is now open on above INA.

    I asume you mean 24554? And I'm still not getting a connect on the IPv6 address
    and that port. (IPv4 works fine)


    Wilfred.

    --- FMail-W32 1.73.12.63-B20170110
    * Origin: point@work (2:280/464.112)
  • From Nicholas Boel@1:154/10 to Bill McGarrity on Friday, January 13, 2017 07:41:02
    Hello Bill,

    On Thu Jan 12 2017 19:31:08, Bill McGarrity wrote to Nicholas Boel:

    If everything you try seems to fail, you may want to see if
    there's an update for your router firmware. If you're using the
    original firmware from when you bought it, there may be a newer
    version out there. Take a look at the changelog and see if there
    was anything IPv6 related that could be causing whatever issues
    you're having.

    I have the router set for Auto updates. I just did it manually and
    said everything was up to date.

    I am a tad concerned about something though..

    If I try to ping the pi from the server. I get a could not find host.
    Yet, when I ping it from the laptop that's on the network, it sees it.

    This is really messing with my mind...

    I would worry about your original system working before trying to setup a secondary one. Looks like all day yesterday I've failed to connect to you. Not only does your mailer not answer via IPv6, but also either you're hiding your 46:1/159 AKA or you've removed it completely:

    13 Jan 00:04:38 [15535] trying ftn.tequilamockingbirdonline.net [69.248.146.68]:24554...
    13 Jan 00:04:38 [15535] connected
    + 13 Jan 00:04:38 [15535] outgoing session with ftn.tequilamockingbirdonline.net:24554 [69.248.146.68]
    - 13 Jan 00:04:38 [15535] OPT CRAM-MD5-41ecccc4a92b45da8bd1df2e3bfd9aee
    + 13 Jan 00:04:38 [15535] Remote requests MD mode
    - 13 Jan 00:04:38 [15535] SYS TequilaMockingbird Online
    - 13 Jan 00:04:38 [15535] ZYZ Bill McGarrity
    - 13 Jan 00:04:38 [15535] LOC Toms River, New Jersey
    - 13 Jan 00:04:38 [15535] NDL 9600,TCP,BINKP
    - 13 Jan 00:04:38 [15535] TIME Fri, 13 Jan 2017 01:04:04 -0500
    - 13 Jan 00:04:38 [15535] VER binkd/1.1a-68/Win32 binkp/1.1
    + 13 Jan 00:04:38 [15535] addr: 1:266/404@fidonet
    + 13 Jan 00:04:38 [15535] addr: 316:973/2@whispernet (n/a or busy)
    + 13 Jan 00:04:38 [15535] addr: 618:100/24@micronet (n/a or busy)
    ? 13 Jan 00:04:38 [15535] called 46:1/159@agoranet, but remote has no such AKA + 13 Jan 00:04:38 [15535] done (to 46:1/159@agoranet, failed, S/R: 0/0 (0/0 bytes))
    13 Jan 00:04:38 [15535] session closed, quitting...

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20161221
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Bill McGarrity@1:266/404 to Tony Langdon on Friday, January 13, 2017 10:10:50
    Re: Re: Connect...??
    By: Tony Langdon to Bill McGarrity on Fri Jan 13 2017 11:44:00

    Hiya Tony...

    Well, from where I sit, it looks like nothing is listening on that
    port.

    OK... got it all worked out now. It was a command line issue on the way I started binkd. All ports are now open on the Pi and I've connected. Next issue is to try and figure out why the server has an issue resolving hub.tequilamockingbirdonline.net when I try to poll binkd to binkd or
    telnet. Using the NAT address works fine.

    Thanks for your help...

    .


    --

    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!!
    --- SBBSecho 3.00-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Tony Langdon on Friday, January 13, 2017 10:12:54
    Re: Re: Connect...??
    By: Tony Langdon to Bill McGarrity on Fri Jan 13 2017 11:49:00

    Hiya Tony...

    Yes, you need to tell binkd to listen on port 24555. Here's the
    relevant part of my binkd.conf file.

    # TCP settings. Leave this unchanged if not sure. # # Suffixes for

    Oh, I have...

    Mine is...

    IPORT 24555 (uncommented)


    --

    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!!
    --- SBBSecho 3.00-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Wilfred van Velzen on Friday, January 13, 2017 10:14:07
    Re: Re: Connect...??
    By: Wilfred van Velzen to Bill McGarrity on Fri Jan 13 2017 09:37:30

    Hiya Wilfred...

    Got it all straightened out. Was a command line issue starting binkd.

    Thanks for your help...


    --

    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!!
    --- SBBSecho 3.00-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Nicholas Boel on Friday, January 13, 2017 10:15:54
    Re: Connect...??
    By: Nicholas Boel to Bill McGarrity on Fri Jan 13 2017 07:41:02

    Hiya Nick...


    I would worry about your original system working before trying to
    setup a secondary one. Looks like all day yesterday I've failed to
    connect to you. Not only does your mailer not answer via IPv6, but
    also either you're hiding your 46:1/159 AKA or you've removed it completely:

    I took care of both. As I said, I did an unadvised slight change to the command line startup that affected both. All fixed now.

    Thanks


    --

    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!!
    --- SBBSecho 3.00-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Joe Delahaye@1:249/303 to Nicholas Boel on Friday, January 13, 2017 10:48:08
    Re: Connect...??
    By: Nicholas Boel to Bill McGarrity on Thu Jan 12 2017 18:19:46

    My router is a Linksys WRT1900AC and I have done all you've stated.
    I've enabled IPv6 firewall and then added a port service using the
    IPv6 address for the pi. I also set a single port forwarding for
    the IPv4 NAT address. Still nothing. The INA I'm using is:
    hub.tequilamockingbirdonline.net 24555

    I'm back playing in the router now....pain in the ass... lol

    If everything you try seems to fail, you may want to see if there's an update for your router firmware. If you're using the original firmware from when you bought it, there may be a newer version out there. Take a look at the changelog
    and see if there was anything IPv6 related that could be causing whatever issues you're having.


    I originally purchased that same router. Was unable to get incoming IPv6 traffic with it, no matter what I tried. Took it back and got a Dlink version of it instead. That worked. TPlink also would not allow incoming. That was permanently filtered I was told
    --- SBBSecho 3.00-Win32
    * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
  • From Wilfred van Velzen@2:280/464 to Bill McGarrity on Friday, January 13, 2017 16:52:26
    Hi,

    On 2017-01-13 10:14:07, Bill McGarrity wrote to Wilfred van Velzen:
    about: "Re: Connect...??":

    Got it all straightened out.

    Almost:

    IPv4 24555 works
    IPv6 24555 works
    IPv4 24554 works
    IPv6 24554 times out


    Bye, Wilfred.


    --- FMail-W32 1.73.12.64-B20170112
    * Origin: Native IPv6 connectable node (2:280/464)
  • From Nicholas Boel@1:154/10 to Joe Delahaye on Friday, January 13, 2017 09:52:30
    Hello Joe,

    On Fri Jan 13 2017 10:48:08, Joe Delahaye wrote to Nicholas Boel:

    My router is a Linksys WRT1900AC and I have done all you've

    If everything you try seems to fail, you may want to see if
    there's an update for your router firmware. If you're using the
    original firmware from when you bought it, there may be a newer
    version out there. Take a look at the changelog and see if there
    was anything IPv6 related that could be causing whatever issues
    you're having.

    I originally purchased that same router. Was unable to get incoming
    IPv6 traffic with it, no matter what I tried. Took it back and got a Dlink version of it instead. That worked. TPlink also would not
    allow incoming. That was permanently filtered I was told

    The WRT1900AC definitely has IPv6 support, and it also seems to be working now for Bill.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20161221
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Bill McGarrity@1:266/404 to Wilfred van Velzen on Friday, January 13, 2017 11:29:25
    Re: Re: Connect...??
    By: Wilfred van Velzen to Bill McGarrity on Fri Jan 13 2017 16:52:26

    Hiya Wilfred...

    Almost:

    IPv4 24555 works IPv6 24555 works IPv4 24554 works IPv6 24554
    times out

    That's strange.... cause I'm gettingIPv6 connects on both....


    --

    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!!
    --- SBBSecho 3.00-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Tommi Koivula@2:221/1.1 to Wilfred van Velzen on Friday, January 13, 2017 18:39:30

    13 Jan 17 16:52:26, you wrote to Bill McGarrity:

    Got it all straightened out.

    Almost:

    IPv4 24555 works
    IPv6 24555 works
    IPv4 24554 works
    IPv6 24554 times out

    13 Jan 18:38:40 [7688] call to 1:266/404@fidonet
    13 Jan 18:38:40 [7688] trying ftn.tequilamockingbirdonline.net [2601:8b:8400:5477:89a0:1f59:d57d:61da]...
    13 Jan 18:38:40 [7688] connected
    13 Jan 18:38:40 [7688] outgoing session with ftn.tequilamockingbirdonline.net:24554 [2601:8b:8400:5477:89a0:1f59:d57d:61da]

    Works.

    'Tommi

    ---
    * Origin: IPv6 Point at [2001:470:1f15:cb0:2:221:1:1] (2:221/1.1)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Friday, January 13, 2017 18:14:25
    Hi,

    On 2017-01-13 18:39:30, Tommi Koivula wrote to Wilfred van Velzen:
    about: "Connect...??":

    Got it all straightened out.

    Almost:

    IPv4 24555 works
    IPv6 24555 works
    IPv4 24554 works
    IPv6 24554 times out

    13 Jan 18:38:40 [7688] call to 1:266/404@fidonet
    13 Jan 18:38:40 [7688] trying ftn.tequilamockingbirdonline.net [2601:8b:8400:5477:89a0:1f59:d57d:61da]... 13 Jan 18:38:40 [7688]
    connected
    13 Jan 18:38:40 [7688] outgoing session with ftn.tequilamockingbirdonline.net:24554 [2601:8b:8400:5477:89a0:1f59:d57d:61da]

    That explains it. I'm using hub.tequilamockingbirdonline.net, as requested in Bill's original message. And that resolves to a different IPv6 address. When I use the ftn.* address I get a connect on IPv6...

    Bye, Wilfred.


    --- FMail-W32 1.73.12.64-B20170112
    * Origin: Native IPv6 connectable node (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Bill McGarrity on Friday, January 13, 2017 18:16:15
    Hi,

    On 2017-01-13 11:29:25, Bill McGarrity wrote to Wilfred van Velzen:
    about: "Re: Connect...??":

    Almost:

    IPv4 24555 works IPv6 24555 works IPv4 24554 works IPv6 24554
    times out

    That's strange.... cause I'm gettingIPv6 connects on both....

    I'm using hub.tequilamockingbirdonline.net for my testing not ftn.tequilamockingbirdonline.net ... Is that the problem?

    Bye, Wilfred.


    --- FMail-W32 1.73.12.64-B20170112
    * Origin: Native IPv6 connectable node (2:280/464)
  • From Tommi Koivula@2:221/1.1 to Wilfred van Velzen on Friday, January 13, 2017 19:47:50
    Hi Wilfred.

    13 Jan 17 18:14:24, you wrote to me:

    IPv4 24555 works
    IPv6 24555 works
    IPv4 24554 works
    IPv6 24554 times out

    13 Jan 18:38:40 [7688] call to 1:266/404@fidonet
    13 Jan 18:38:40 [7688] trying ftn.tequilamockingbirdonline.net
    [2601:8b:8400:5477:89a0:1f59:d57d:61da]... 13 Jan 18:38:40 [7688]
    connected 13 Jan 18:38:40 [7688] outgoing session with
    ftn.tequilamockingbirdonline.net:24554
    [2601:8b:8400:5477:89a0:1f59:d57d:61da]

    That explains it. I'm using hub.tequilamockingbirdonline.net, as requested in Bill's original message. And that resolves to a different IPv6 address. When I use the ftn.* address I get a connect on IPv6...

    Ok.. I have no special settings, just by the nodelist. ;)

    'Tommi

    ---
    * Origin: IPv6 Point at [2001:470:1f15:cb0:2:221:1:1] (2:221/1.1)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Friday, January 13, 2017 18:59:40
    Hi,

    On 2017-01-13 19:47:50, Tommi Koivula wrote to Wilfred van Velzen:
    about: "Connect...??":

    IPv4 24555 works
    IPv6 24555 works
    IPv4 24554 works
    IPv6 24554 times out

    13 Jan 18:38:40 [7688] call to 1:266/404@fidonet
    13 Jan 18:38:40 [7688] trying ftn.tequilamockingbirdonline.net
    [2601:8b:8400:5477:89a0:1f59:d57d:61da]... 13 Jan 18:38:40 [7688]
    connected 13 Jan 18:38:40 [7688] outgoing session with
    ftn.tequilamockingbirdonline.net:24554
    [2601:8b:8400:5477:89a0:1f59:d57d:61da]

    That explains it. I'm using hub.tequilamockingbirdonline.net, as
    requested in Bill's original message. And that resolves to a different
    IPv6 address. When I use the ftn.* address I get a connect on IPv6...

    Ok.. I have no special settings, just by the nodelist. ;)

    No special settings here either. I was using telnet to test the connection...

    Bye, Wilfred.


    --- FMail-W32 1.73.12.64-B20170112
    * Origin: Native IPv6 connectable node (2:280/464)
  • From Joe Delahaye@1:249/303 to Nicholas Boel on Friday, January 13, 2017 13:25:14
    Re: Connect...??
    By: Nicholas Boel to Joe Delahaye on Fri Jan 13 2017 09:52:30

    I originally purchased that same router. Was unable to get incoming
    IPv6 traffic with it, no matter what I tried. Took it back and got
    a Dlink version of it instead. That worked. TPlink also would not
    allow incoming. That was permanently filtered I was told

    The WRT1900AC definitely has IPv6 support, and it also seems to be working now for Bill.

    Perhaps a different version number. I had IPv6 support, but only going out. It would not accept incoming traffic, unless of course there was something that I misunderstood about how to set it up. No problem with the IPv4 part. The DLink which is also an AC1900 worked almost out of the box.
    --- SBBSecho 3.00-Win32
    * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
  • From Tony Langdon@3:633/410 to Bill McGarrity on Saturday, January 14, 2017 08:32:00
    Bill McGarrity wrote to Tony Langdon <=-

    Well, from where I sit, it looks like nothing is listening on that
    port.

    OK... got it all worked out now. It was a command line issue on the
    way I started binkd. All ports are now open on the Pi and I've
    connected. Next issue is to try and figure out why the server has an issue resolving hub.tequilamockingbirdonline.net when I try to poll
    binkd to binkd or telnet. Using the NAT address works fine.

    Sounds like you're making progress.

    Thanks for your help...

    You're welcome. :)


    ... I find circuses a little too sinister.
    --- MultiMail/Win32 v0.49
    * Origin: Freeway BBS - freeway.apana.org.au (3:633/410)
  • From Tony Langdon@3:633/410 to Bill McGarrity on Saturday, January 14, 2017 08:33:00
    Bill McGarrity wrote to Tony Langdon <=-

    # TCP settings. Leave this unchanged if not sure. # # Suffixes for

    Oh, I have...

    Mine is...

    IPORT 24555 (uncommented)

    Looks good.


    ... Dachshunds are really small crocodiles with fur.
    --- MultiMail/Win32 v0.49
    * Origin: Freeway BBS - freeway.apana.org.au (3:633/410)
  • From Bill McGarrity@1:266/404 to Tommi Koivula on Friday, January 13, 2017 17:50:21
    Re: Connect...??
    By: Tommi Koivula to Wilfred van Velzen on Fri Jan 13 2017 18:39:30

    Hiya Tommi...

    13 Jan 18:38:40 [7688] call to 1:266/404@fidonet 13 Jan 18:38:40
    [7688] trying ftn.tequilamockingbirdonline.net [2601:8b:8400:5477:89a0:1f59:d57d:61da]... 13 Jan 18:38:40 [7688] connected 13 Jan 18:38:40 [7688] outgoing session with ftn.tequilamockingbirdonline.net:24554 [2601:8b:8400:5477:89a0:1f59:d57d:61da]

    Works.

    Thank you!!


    --

    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!!
    --- SBBSecho 3.00-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Wilfred van Velzen on Friday, January 13, 2017 17:53:57
    Re: Re: Connect...??
    By: Wilfred van Velzen to Tommi Koivula on Fri Jan 13 2017 18:14:25

    Hiya Wilfred...


    That explains it. I'm using hub.tequilamockingbirdonline.net, as
    requested in Bill's original message. And that resolves to a
    different IPv6 address. When I use the ftn.* address I get a connect
    on IPv6...

    No, you were doing it correctly. hub.tequilamocokingbirdonline.net on 24555 should be working now. When you tried the 24554 port, it was probably the
    ftn address. When I added the IPv6 forwarding, I had to turn on the IPv6 firewall and then give a pkt exception for it. Once I did that I saw that I also had to give the main server an exception as well. According to ipv6scanner.com all ports on both INA are open and working.

    Thanks for your help..


    --

    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!!
    --- SBBSecho 3.00-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Richard Menedetter@2:310/31 to Bill Mcgarrity on Saturday, January 14, 2017 12:29:12
    Hi Bill!

    12 Jan 2017 19:24, from Bill McGarrity -> Tony Langdon:

    Is there anything I need to do to the pi??

    Do a
    netstat -ltpn

    And tell us what you see.

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: OPERATOR! Trace this call and tell me where I am! (2:310/31)
  • From Wilfred van Velzen@2:280/464 to Bill McGarrity on Saturday, January 14, 2017 12:58:32
    Hi,

    On 2017-01-13 17:53:57, Bill McGarrity wrote to Wilfred van Velzen:
    about: "Re: Connect...??":

    That explains it. I'm using hub.tequilamockingbirdonline.net, as
    requested in Bill's original message. And that resolves to a
    different IPv6 address. When I use the ftn.* address I get a connect
    on IPv6...

    No, you were doing it correctly. hub.tequilamocokingbirdonline.net on 24555 should be working now. When you tried the 24554 port, it was probably the ftn address. When I added the IPv6 forwarding, I had to turn on the IPv6 firewall and then give a pkt exception for it. Once I did
    that
    I saw that I also had to give the main server an exception as well. According to ipv6scanner.com all ports on both INA are open and working.

    So there are 2 ports, 1 IPv4 address, and 2 IPv6 addresses, which makes 6 combinations:

    IPv4 24554 works
    IPv4 24555 works
    ftn IPv6 24554 works
    ftn IPv6 24555 does not work
    hub IPv6 24554 does not work
    hub IPv6 24555 works

    Is this how it should be? ;)


    Bye, Wilfred.


    --- FMail-W32 1.73.12.64-B20170112
    * Origin: Native IPv6 connectable node (2:280/464)
  • From Bill McGarrity@1:266/404 to Richard Menedetter on Saturday, January 14, 2017 09:08:00
    Hiya Ricsi..

    Richard Menedetter wrote to Bill Mcgarrity <=-


    12 Jan 2017 19:24, from Bill McGarrity -> Tony Langdon:

    Is there anything I need to do to the pi??

    Do a
    netstat -ltpn

    And tell us what you see.

    Here ya go....

    root@raspberrypi:~# netstat -ltpn

    Active Internet connections (only servers)

    Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name

    tcp 0 0 0.0.0.0:24555 0.0.0.0:* LISTEN 17978/binkd: server

    tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 885/smbd


    tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 516/sshd


    tcp 0 0 0.0.0.0:631 0.0.0.0:* LISTEN 27479/cupsd

    tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 885/smbd


    tcp6 0 0 :::24555 :::* LISTEN 17978/binkd: server

    tcp6 0 0 :::139 :::* LISTEN 885/smbd


    tcp6 0 0 :::22 :::* LISTEN 516/sshd


    tcp6 0 0 :::631 :::* LISTEN 27479/cupsd

    tcp6 0 0 :::445 :::* LISTEN 885/smbd

    root@raspberrypi:~#

    When I use that command on the Windows Server 2008 box it shows no switch for -l and just gives me the help screen.




    --

    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)
  • From Bill McGarrity@1:266/404 to Wilfred van Velzen on Saturday, January 14, 2017 09:20:00
    Wilfred van Velzen wrote to Bill McGarrity <=-

    Hi,

    On 2017-01-13 17:53:57, Bill McGarrity wrote to Wilfred van Velzen:
    about: "Re: Connect...??":

    That explains it. I'm using hub.tequilamockingbirdonline.net, as
    requested in Bill's original message. And that resolves to a
    different IPv6 address. When I use the ftn.* address I get a connect
    on IPv6...

    No, you were doing it correctly. hub.tequilamocokingbirdonline.net on 24555 should be working now. When you tried the 24554 port, it was probably the ftn address. When I added the IPv6 forwarding, I had to turn on the IPv6 firewall and then give a pkt exception for it. Once I did
    that
    I saw that I also had to give the main server an exception as well. According to ipv6scanner.com all ports on both INA are open and working.

    So there are 2 ports, 1 IPv4 address, and 2 IPv6 addresses, which makes
    6 combinations:

    IPv4 24554 works
    IPv4 24555 works
    ftn IPv6 24554 works
    ftn IPv6 24555 does not work
    hub IPv6 24554 does not work
    hub IPv6 24555 works

    Is this how it should be? ;)


    Should only be 4 combinations...

    ftn sub-domain using port 24554 for both IPv4 and IPv6
    hub sub-domain using port 24555 for both IPv4 and IPv6

    According to ipv6scanner.com... both ports are open on 24554 and both are open on 24555.

    Thanks


    --

    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)
  • From Richard Menedetter@2:310/31 to Bill Mcgarrity on Sunday, January 15, 2017 00:53:04
    Hi Bill!

    14 Jan 2017 09:08, from Bill McGarrity -> Richard Menedetter:

    Do a
    netstat -ltpn
    tcp 0 0 0.0.0.0:24555 0.0.0.0:* LISTEN 17978/binkd: server
    tcp6 0 0 :::24555 :::* LISTEN 17978/binkd: server

    That looks good ... binkd is listening on port 24555 on both IPv4 and IPv6.

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: Plankton lobbyist: "NUKE THE WHALES!" (2:310/31)
  • From Bill McGarrity@1:266/404 to Richard Menedetter on Saturday, January 14, 2017 19:05:29
    Re: Connect...??
    By: Richard Menedetter to Bill Mcgarrity on Sun Jan 15 2017 00:53:04

    Hiya Ricsi...

    That looks good ... binkd is listening on port 24555 on both IPv4 and IPv6.


    --

    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!!
    --- SBBSecho 3.00-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Richard Menedetter on Saturday, January 14, 2017 19:10:11
    Re: Connect...??
    By: Richard Menedetter to Bill Mcgarrity on Sun Jan 15 2017 00:53:04

    Hiya Ricsi....

    Follow-up to the last message... the main server (server 20068) doesn't see
    the hub..

    --

    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!!
    --- SBBSecho 3.00-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Michiel van der Vlist@2:280/5555 to Bill McGarrity on Sunday, January 15, 2017 11:21:45
    Hello Bill,

    On Saturday January 14 2017 19:10, you wrote to Richard Menedetter:

    + 11:21 [2844] call to 1:266/404.1@fidonet
    11:21 [2844] trying hub.tequilamockingbirdonline.net
    [2601:8b:8400:5477:a9a2:7e4e:e35d:4239]:24555...
    11:21 [2844] connected
    + 11:21 [2844] outgoing session with hub.tequilamockingbirdonline.net:24555
    [2601:8b:8400:5477:a9a2:7e4e:e35d:4239]
    - 11:21 [2844] OPT CRAM-MD5-c7e9fa7a9bd42fc3962cc55cedc140ee
    + 11:21 [2844] Remote requests MD mode
    - 11:21 [2844] SYS SportNet Hub
    - 11:21 [2844] ZYZ Bill McGarrity
    - 11:21 [2844] LOC Toms River, NJ
    - 11:21 [2844] NDL 115200,TCP,BINKP
    - 11:21 [2844] TIME Sun, 15 Jan 2017 05:21:13 -0500
    - 11:21 [2844] VER binkd/1.1a-95/Linux binkp/1.1
    + 11:21 [2844] addr: 24:100/5@sportnet (n/a or busy)
    + 11:21 [2844] addr: 1:266/404.1@fidonet
    ? 11:21 [2844] got M_BSY: No AKAs in common domains or all AKAs are busy
    + 11:21 [2844] done (to 1:266/404.1@fidonet, failed, S/R: 0/0 (0/0 bytes))
    11:21 [2844] session closed, quitting...

    I was going to suggest that you change the node number for the hub, but you beat me to it. Having two systems present the same node number is not a good idea.

    Maybe you should do the same for the sportnet AKAs?

    As you can see, 1:266/404.1 responds to a binkp call (also on IPv4), but the session terminates with an M_BSY failure.

    You are not there yet...

    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: http://www.vlist.eu (2:280/5555)
  • From Bill McGarrity@1:266/404 to Michiel van der Vlist on Sunday, January 15, 2017 14:05:00
    Hiya Michiel...

    Michiel van der Vlist wrote to Bill McGarrity <=-


    On Saturday January 14 2017 19:10, you wrote to Richard Menedetter:

    + 11:21 [2844] call to 1:266/404.1@fidonet
    11:21 [2844] trying hub.tequilamockingbirdonline.net
    [2601:8b:8400:5477:a9a2:7e4e:e35d:4239]:24555...
    11:21 [2844] connected
    + 11:21 [2844] outgoing session with hub.tequilamockingbirdonline.net:24555
    [2601:8b:8400:5477:a9a2:7e4e:e35d:4239]
    - 11:21 [2844] OPT CRAM-MD5-c7e9fa7a9bd42fc3962cc55cedc140ee
    + 11:21 [2844] Remote requests MD mode
    - 11:21 [2844] SYS SportNet Hub
    - 11:21 [2844] ZYZ Bill McGarrity
    - 11:21 [2844] LOC Toms River, NJ
    - 11:21 [2844] NDL 115200,TCP,BINKP
    - 11:21 [2844] TIME Sun, 15 Jan 2017 05:21:13 -0500
    - 11:21 [2844] VER binkd/1.1a-95/Linux binkp/1.1
    + 11:21 [2844] addr: 24:100/5@sportnet (n/a or busy)
    + 11:21 [2844] addr: 1:266/404.1@fidonet
    ? 11:21 [2844] got M_BSY: No AKAs in common domains or all AKAs are
    busy + 11:21 [2844] done (to 1:266/404.1@fidonet, failed, S/R: 0/0 (0/0 bytes))
    11:21 [2844] session closed, quitting...

    I was going to suggest that you change the node number for the hub, but you beat me to it. Having two systems present the same node number is
    not a good idea.

    I just added the point address here so it can be tested. I plan on only using it for SportNet to start. My issue now is getting the main server to resolve to hub.tequilamockingbirdonline.net address. I have it's internal DNS server operating just fine... all the settings are correct at no-ip yes nadda. Get a can't recognize that address.

    Maybe you should do the same for the sportnet AKAs?

    I plan on it.

    As you can see, 1:266/404.1 responds to a binkp call (also on IPv4),
    but the session terminates with an M_BSY failure.

    Thank you..

    You are not there yet...

    Certainly alot closer... :)


    --

    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)
  • From mark lewis@1:3634/12.73 to Bill McGarrity on Sunday, January 15, 2017 15:55:28

    On 2017 Jan 15 14:05:00, you wrote to Michiel van der Vlist:

    I just added the point address here so it can be tested. I plan on
    only using it for SportNet to start. My issue now is getting the main server to resolve to hub.tequilamockingbirdonline.net address. I have it's internal DNS server operating just fine... all the settings are correct at no-ip yes nadda. Get a can't recognize that address.

    assuming you're running *nix on the problematic machine, what does

    dig hub.tequilamockingbirdonline.net ANY

    return? over here i see this...

    ===== snip =====
    $ dig hub.tequilamockingbirdonline.net ANY

    ; <<>> DiG 9.9.5-3ubuntu0.11-Ubuntu <<>> hub.tequilamockingbirdonline.net ANY ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24344
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 512
    ;; QUESTION SECTION:
    ;hub.tequilamockingbirdonline.net. IN ANY

    ;; ANSWER SECTION:
    hub.tequilamockingbirdonline.net. 59 IN A 69.248.146.68 hub.tequilamockingbirdonline.net. 59 IN AAAA 2601:8b:8400:5477:a9a2:7e4e:e35d:4239

    ;; Query time: 180 msec
    ;; SERVER: 192.168.xxx.1#53(192.168.xxx.1)
    ;; WHEN: Sun Jan 15 15:59:20 EST 2017
    ;; MSG SIZE rcvd: 105
    ===== snip =====

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... Short Books: Cooking Gourmet Dishes With Tofu.
    ---
    * Origin: (1:3634/12.73)
  • From Jeff Smith@1:282/1031 to Mark Lewis on Sunday, January 15, 2017 19:21:40
    Hello Mark,


    assuming you're running *nix on the problematic machin> ===== snip ===== )\/(ark
    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
    wrong...
    ... Short Books: Cooking Gourmet Dishes With Tofu.e, what does
    dig hub.tequilamockingbirdonline.net ANY

    Here I get the following as a response.

    ; <<>> DiG 9.10.3-P4-Ubuntu <<>> hub.tequilamockingbirdonline.net ANY
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39802
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 4096
    ;; QUESTION SECTION:
    ;hub.tequilamockingbirdonline.net. IN ANY

    ;; ANSWER SECTION:
    hub.tequilamockingbirdonline.net. 60 IN AAAA 2601:8b:8400:5477:a9a2:7e4e:e35 d:4
    239
    hub.tequilamockingbirdonline.net. 60 IN A 69.248.146.68

    ;; Query time: 90 msec
    ;; SERVER: 127.0.1.1#53(127.0.1.1)
    ;; WHEN: Sun Jan 15 19:19:30 CST 2017
    ;; MSG SIZE rcvd: 105


    Jeff



    --- BBBS/Li6 v4.10 Toy-3
    * Origin: The OuijaBoard - Anoka, MN (1:282/1031)
  • From Bill McGarrity@1:266/404 to mark lewis on Monday, January 16, 2017 16:47:00
    Hiya mark..

    mark lewis wrote to Bill McGarrity <=-

    On 2017 Jan 15 14:05:00, you wrote to Michiel van der Vlist:

    I just added the point address here so it can be tested. I plan on
    only using it for SportNet to start. My issue now is getting the main server to resolve to hub.tequilamockingbirdonline.net address. I have it's internal DNS server operating just fine... all the settings are correct at no-ip yes nadda. Get a can't recognize that address.

    assuming you're running *nix on the problematic machine, what does

    Nope, problem is with the Windows Server 2008 box.

    I tried it on the Pi but got command not found.


    I know the Pi sees hub.tequilamockingbirdonline.net


    --

    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)