On 3/30/2024 4:47 PM, Glen Strecker wrote:
Right now, my client can't even talk to its own repeater unless I
tell it to connect to its internal IP address being assigned by the
router. If I go through my normal URL address,
sttammany.ratflector.com, it gets refused every time.
That indicates a passthrough issue at the NAT routers().
When I switched to Fiber service, the ISP provided me with a WAP router that I have limited configuration control over, and then my personal WAP router is connected to it.
In order to have a public IP address, which would be a DHCP address, I have to setup a special rule on the ISP WAP router to direct incoming traffic from specific port to a specific IP address on their NAT range. (port forwarding?)
It is not just a matter of opening up the ports, they have to be directed to specific host. Some NAT routers allow you to specify a IP address to be sent to a local host.
If I do not want to plug the "public" system into the ISP NAT router, and plug it into my NAT router, then it gets more complex to setup.
Also, some ISPs are no longer giving out a unique public IP address from their NAT routers. If you have one of those ISP's you are basically out of luck for home hosting.
If I try to load version 0.4.2 it throws an error trying to load
something called pyaudio. Has everyone moved up to Raspberry Pi
Bookworm to get this stuff going?
I just got bookworm setup on an RPI-4 last weekend and have not had time to test it D-Rats on it. Previously development was done on Anti-X linux using Buster and then Bullseye as their base.
The pyaudio should be handled by installing python-pyaudio. Generally the package names are the same on most Debian based systems.
I was positively content with version 0.3.9 until they started doing
away with the python 2 dependencies and you could not reload it on a
new system anymore.
D-Rats 0.3.9 will drop bytes on a connection to an actual radio, this seems to mainly show up on faster computers. If the input buffer from reading the radio is ever empty, d-rats 0.3.9 incorrectly assumes that the next byte from the radio should be an XON or XOFF character and if not, it just discards it, causing the entire packet received by d-rats to be unreadable. This showed up in file transfer tests over a simulated radio link.
I cannot get a client on another computer to connect to either the
URL updated at Noip.com, or the ,ratflector.com address. I can't even
connect going to my external IP address assigned to my router. I have
the port forwarding set on the router but it seems that something is not
being handled correctly. I can connect to SEWX. I am tending to think
it is something to do with Charter Spectrum because with my previous IP
provider I did not have such problems.
First thing to look at is what address your ISP MODEM is presenting to the WAP router. If it is not the public address your external connection is at, then that is the first thing to resolve.
You need to find out if your ISP Modem is bundled with a WAP router, and then you need to find out what you can configure on the ISP WAP router.
73,
-John
wb8tyw
