Cound someone do me a favor and see if they can connect via binkd to hub.tequilamockingbirdonline.net:24555
Cound someone do me a favor and see if they can connect via binkd to hub.tequilamockingbirdonline.net:24555
Cound someone do me a favor and see if they can connect via binkd to hub.tequilamockingbirdonline.net:24555
Michiel van der Vlist wrote to Bill McGarrity <=-
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...
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...
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".
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.
Hiya Gang...
Cound someone do me a favor and see if they can connect via binkd to hub.tequilamockingbirdonline.net:24555
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.
beingCound 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
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.
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.
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.
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.
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).
I run all my binkp services on the same port, because I have multiple public IPv4 (via VPN) and IPv6 addresses on the LAN.
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...
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. :)
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.
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).
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).
it should be a simple portforward to the rPi's IP... what router are
you using??
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.
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 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.
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
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??
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.
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...
Well, from where I sit, it looks like nothing is listening on that
port.
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
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:
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.
Got it all straightened out.
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
Almost:
IPv4 24555 works IPv6 24555 works IPv4 24554 works IPv6 24554
times out
Got it all straightened out.
Almost:
IPv4 24555 works
IPv6 24555 works
IPv4 24554 works
IPv6 24554 times out
connectedGot 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]
13 Jan 18:38:40 [7688] outgoing session with ftn.tequilamockingbirdonline.net:24554 [2601:8b:8400:5477:89a0:1f59:d57d:61da]
Almost:
IPv4 24555 works IPv6 24555 works IPv4 24554 works IPv6 24554
times out
That's strange.... cause I'm gettingIPv6 connects on both....
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...
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. ;)
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.
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.
Thanks for your help...
Bill McGarrity wrote to Tony Langdon <=-
# TCP settings. Leave this unchanged if not sure. # # Suffixes for
Oh, I have...
Mine is...
IPORT 24555 (uncommented)
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.
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...
Is there anything I need to do to the pi??
thatThat 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
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.
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.
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? ;)
Do atcp 0 0 0.0.0.0:24555 0.0.0.0:* LISTEN 17978/binkd: server
netstat -ltpn
tcp6 0 0 :::24555 :::* LISTEN 17978/binkd: server
That looks good ... binkd is listening on port 24555 on both IPv4 and IPv6.
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.
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...
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 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
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
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,027 |
| Nodes: | 17 (0 / 17) |
| Uptime: | 62:27:21 |
| Calls: | 502,334 |
| Calls today: | 2 |
| Files: | 100,779 |
| D/L today: |
10,901 files (1,026M bytes) |
| Messages: | 300,077 |