¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Bpq32
  2. Messages
Single Messages Topics Expanded

Re: New bpq32 install connection refused

 

A few things:
?
You stated you are using Direwolf, but your config is setup for a serial "PITNC".
For direwolf, you should be using the Network KISS options to connect your BPQ node to DireWolf.
?
Your port one for DireWolf for 2M should look more like this if DireWolf is running on the same system:
Replace the PORTNUM as needed, IP if running on another device, Port if KISS Listen on direwolf, and beacon call
PORT
   PORTNUM=1
   ID=144.930 MHz 1200 bps
   TYPE=ASYNC
   SPEED=19200
   PROTOCOL=KISS
   IPADDR=127.0.0.1
   TCPPORT=8001
   RESPTIME=1500
   MHEARD=Y
   BCALL=KN4MKB-7
   MINQUAL=100
   KISSOPTIONS=NOPARAMS
   CHANNEL=A
   FULLDUP=0
   NOKEEPALIVES=1
ENDPORT
?
Your DireWolf Config for 2M should look something like this after your Audio/PTT config:
MODEM 1200
RETRY 5
FRACK 3
MAXFRAME 7
EMAXFRAME 30
PACLEN 128
DWAIT 0
TXDELAY 25
TXTAIL 15
MAXV22 3
?
With that out of the way, you probably need to enter the following command to allow non root users to use all ports (replace 'pi' with your pi username is different):
sudo setcap "CAP_NET_ADMIN=ep CAP_NET_RAW=ep CAP_NET_BIND_SERVICE=ep" pi
?
And gove the executable the right permissions:
sudo chmod +x linbpq
?
I'm not familiar with the Ham stack you are running.
It may have a firewall installed you aren't aware of.
?
Try the following commands to open the ports as the root user:
sudo su
iptables -A INPUT -p tcp --dport PORTNUMBER -j ACCEPT
ufw allow PORTNUMBER
?
If the pi is in the same network as the connecting device, your router and it's forwarded ports have nothing to do with it.
NAT/ Port Forwarding is a routing/firewall function to direct traffic from one network to the port of a device on another.
If your devices are on the same network (255.255.255.0/24), then the NAT is bypassed anyways as it doesn't need to happen.
?
Not to knock the people who build them, but a lot of those autoinstall config builders and install scripts put a lot of "stuff" into the config files they generate.
Things change over time, and everyone setup is different, and it just usually doesn't go well with BPQ for the config portion. If you are ever to change anything in the future, you will need to understand the config anyways.
?
"I tried browser connection to http://127.0.0.1:8010 and Telnet to 127.0.0.1 8010.? Both of these result in 'connection refused' messages."
So if you you doing this from the Pi itself it may be fine.
But if you are connecting from elsewhere, like in your previous post, you need to use the LAN address of your Pi instead of 127.0.0.1.
You can use "ip a" in a terminal to see it.
?
I recommend you just remove the LinBPQ installation, purge any systemd entries, and start from scratch.?
?
I've written a detailed guide to build your own configuration you can find here:
?
Follow along the above link, and also open:
?
That way you can build your config file, follow along and check Johns Documentation to make sure you don't need to tweak something, or add something.
Being a SysOP, I think it pays to build your own. That way you really understand what each of the lines mean and what they do.
?
Join [email protected] to automatically receive all group messages.