Re: Packet Hanging up on BPQ
Duff
?
Sorry I was
wrong about the Channel A or B if this is a Single Port TNC then it would be
Channel A for each
TNC, how
about if temporally comment out the Call in the Ports except for the WL2K Port
and see what happens.
Mike Melnik-N9PMO
BPQ32 Group Moderator
|
Re: Packet Hanging up on BPQ
Here is my monitor screen if that helps. 
|
Re: Packet Hanging up on BPQ
Still the same after all the suggestions.
Duff
|
Re: Packet Hanging up on BPQ
Duff
?
The other
port HF do you have that set with a different Com Port address and Channel B
Not Channel
A? and as Mark Mentioned you should use a Call with a SSID fir WL2K
Mike
Melnik-N9PMO
BPQ32 Group Moderator
|
Re: Packet Hanging up on BPQ
It could be that MyCall in the main configuration of Winlink Express is set to N5RDM, and N5RDM is also set as a NodeCall, PortCall, or an Application Call on your BPQ installation.
Basically, you call using Winlink Express as N5RDM and your BBS answers but your node is intercepting it...
Make sure Winlink Express is using a unique callsign/ssid that is not being used by your BPQ Node.? I have to use mycall-15 when I attempt any connection to my node so there is no interference.
Mark
|
I have my BBS set up and HF is running as it should. I set up a port for BBS 2m packet. When I try to connect on a separate radio the session hangs up after it shows connected and my node name.Do I have something wrong in the configuration file?
 
Im using a TNC-X as a TNC.
Thanks
|
John
Sent you a email about our link and RTT and the problem with IPGATEWAY (Windows 64)
Mike Melnik-N9PMO
BPQ32 Group Moderator
|
Richard Hendricks - KE0GB
Thanks, Mike.? I've been checking my nodes tables from time-to-time, and also changed AUTOSAVE from on to off so each time I run update/upgrade on my RPi and restart, the nodes tables are flushed.? I haven't?seen a case of 255 in the Obsolescence column as of yet.? ?Hopefully, John will find a solution, but I know how busy he is with other BPQ issues. I see that the 255 Obso. count may be coming from KB9SOZ-7 node.? I am getting the same thing on another route from Jim's node (the route back to me) and have asked him to delete his BPQNodes.dat file and reboot, but he has yet to respond. Here's what I get when I connect via W9GM-7's node:
Connected to TelnetServer
c w9gm-7
COSCO:KE0GB-7} Connected to GMNOD:W9GM-7
c kb9soz-7
GMNOD:W9GM-7} Connected to WI105:KB9SOZ-7
no cosco
WI105:KB9SOZ-7} Routes to: COSCO:KE0GB-7 RTT=0.00 FR=3 B 0
> 192 255 6 KE0GB-7? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? <-----255 obso count
144 6 6 W4GON-7
144 6 6 KA9QJT-7
I can just get a connect from his node, then no response after that.
Here's his response to a node route command for Harv - VA3HRA-7:
no va3hra-7
WI105:KB9SOZ-7} Routes to: ON105:VA3HRA-7
> 192 255 6 VA3HRA-7? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?<-----255 obso count
144 1 6 VE3SCN-7
142 5 6 N9PMO-2
?
So, he needs some work done on his nodes tables.? If you're?
monitoring, Jim, again, I ask you to please stop your BPQ
system, delete the BPQNodes.dat file, and reboot.? Let the
system repopulate the nodeslist from scratch and all should
be well.
73 - Rick
?
|
Hi
Rick
?
Yes
VA3HRA-7 showed a Obsolescence of 255 in my Nodes Table, I used the Sysop
command NOD DEL VA3HRA-7
and he is
now deleted, I also checked my BPQNODES.DAT File for similar, how ever one has
to be carful doing
it this way
as many do send a Quality of 255 Obsolescence isn¡¯t shown in the BPQNODES.Dat
file.
?
I will
watch to see if Harv shows up again as Obsolescence of 255, I checked at your
end all is well, as I mentioned
in last
email I do see it from time to time, how it gets changed from a Normal
Obsolescence to 255 I am not
sure, only
thing I can think of is the BPQ32 Node Quality normalizer.
?
May John
will chime in also, I know John and I discussed this before and I think in one
case either G8BPQ showed
up Here as
a Obsolescence 255 or it was in his nodes table once I don¡¯t exactly remember
now.?
?
73
?
Mike
Melnik-N9PMO
BPQ32 Group Moderator
|
Richard Hendricks - KE0GB
Mike: We've been trying to connect to VA3HRA-7 and this morning, I noticed that we are going thru your node, so I checked the routing of Harv's node from you, and got this:
COSCO:KE0GB-7} Connected to WIRAC:N9PMO-2
no on105
WIRAC:N9PMO-2} Routes to: ON105:VA3HRA-7
> 192 255 2 VA3HRA-7? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?<-----There's that dreaded 255 again!
144 6 2 KB9SOZ-7
144 3 2 GM3YEW-4
So, perhaps with this newest release from John, now would be an opportune time to
test it.
73 - Rick
|
Re: IPGATEWAY, 44ENCAP and actual AMPRGW on remote wireguard host
Hi,
I am reworking networking etc here to try to approach this differently.? I think there were some issues with the software and being able to handle IPIP the way I was attempting in this stack and interaction with my network config at the time.?? So I will do some a bit more research and come back after with newer info.? The past info may be completely moot then.
73 Kayne
|
Hello All,
I just discovered some strange behavior with 6.0.23.1 on Windows 10.
If you start the Chat Server first it complains of not finding its config in Appdata\Roaming\BPQ32 but instead works with a config in Appdata\Local\VirtualStore\Program File(x86)\BPQ32. If I start the Mail Server first, then the Chat Server, all is well and the config in Appdata\Roaming\BPQ32 is used as it should be.
Your mileage may vary...
Bob, NS2B
|
Re: IPGATEWAY, 44ENCAP and actual AMPRGW on remote wireguard host
Hi John,
Well yea I wanted to do encap routing back to my main encap termination point in that case.
It may not be as doable on bpq as I thought, i dont know.?
AFAIK, you cant tell bpq in the config to only use a virtual ip assigned to a aliased network nic in linux.
There is no way to specify source ips for tunnel endpoints?? Does it have to use whatever main ip that traffic exits on from the NIC perspective in linux?
Did i overlook something?
|
Re: IPGATEWAY, 44ENCAP and actual AMPRGW on remote wireguard host
What do you want to use IPGATEWAY for? It's main purposes are to run
IP over RF links or to provide an amprnet tunnel endpoint, but you
already have the latter.
73,
John
On 16/07/2022 21:34, Kayne Kruse -
N9SEO wrote:
toggle quoted message
Show quoted text
Hi,
I am struggling to find a way to make linbpq work with
IPGATEWAY.??? OS is Debian 10, kernel 4.19.0-16-686-pae patched
with Marius' YO2LOJ AX25 "else" patch for linux ax25.
My IPIP endpoint is a linux box on the far end of a wireguard
link and uses the main linux gw ip 44.76.0.193 as the routable
wireguard ip and terminates to the linux host at 44.76.0.205
BPQ runs on top that linux box at 44.76.0.205, but I want to use
44.76.0.195 as the IPIP/amprnet ip on BPQ in IPGATEWAY.?
I cannot figure out the correct BPQ config to make it talk to
linux routing table and sort the rest out.? The routes are all
in linux on the device bpq runs on but since TAP wont talk to
interface wg0 because it is not tappable, not sure what my
option is.
Over the wire in a packet dump it should look like
44.76.0.205 -> 44.76.0.193 proto ipip
44.76.0.195 -> ANYTUNNELED_44_IP
vice versa on the return path.? Regardless IPIP packets need to
get to 44.76.0.193 via linux kernel routing to work in
wireguard.
I do this this way because at the linux amprnet gw its easily
controls ingress to only allow amprnet ips to access my amprnet
ips from a centralized firewall at the router gw.
I hope that makes sense, but perhaps I am not clear.?? Let me
know if you need anything further.
IPGATEWAY
ADAPTER enp1s0
44ENCAP 192.168.200.205 ; or I can use 44.76.0.193 as the encap
endpoint or an unused lan IP.? None seemed to do much
usefulness.
IPADDR 44.76.0.195
IPNETMASK 255.255.255.255
NODEFAULTROUTE
IPPORTS 1
ROUTE 0.0.0.0/0 192.168.200.205
;ROUTE 44.0.0.0/9 44.76.0.193 T? # dont use these, they override
linux routes present from wireguard and tie them to LinBPQTAP
interface, not desired - Using kernel routing is desired here, I
use wireguard and freerrp's bgp to manage route tables and they
write to linux routes.
;ROUTE 44.128.0.0/10 44.76.0.193 T
***
I've tried various route's above but removed them as they werent
helpful,
Is there any hope or am I completely out there due to my unique
situation?
Thanks for reading this.
73 Kayne - n9seo
|
Re: IPGATEWAY, 44ENCAP and actual AMPRGW on remote wireguard host
IPGATEWAY
ADAPTER eth0
IPADDR 192.168.1.9
IPNETMASK 255.255.255.0
NODEFAULTROUTE
ENABLESNMP
****
It got cut off, here¡¯s the full paste.
|
Re: IPGATEWAY, 44ENCAP and actual AMPRGW on remote wireguard host
Hi Kayne Here¡¯s my very minimal config:
IPGATEWAY
ADAPTER eth0
IPADDR 192.168.1.9
IPNETMASK 255.255.255.0
NODEFAULTROUTE
ENABLES
Before bullseye, the IP 192.168.1.9 would be ping-able even though it didnt show up on the interface in ifconfig for LinBPQTAP, after bullseye it was completely unresponsive until I added the routes on the host OS. 73 Red
On Mon, Jul 18, 2022 at 05:46 AM, Kayne Kruse - N9SEO wrote:
Hi Red,
I will have to experiment here on that.? It seems valid what you do.? Tho here IM sure if i went your route that you have a minimal ipgateway definition?
I am not certain that here that if i went your path, that the tap interface would actually work at all, even to the local linux box or lan.?? So think I am missing something here on what the issue is.
How does that IPGATEWAY section look on your side?
Kayne
|
Re: IPGATEWAY, 44ENCAP and actual AMPRGW on remote wireguard host
Hi Red,
I will have to experiment here on that.? It seems valid what you do.? Tho here IM sure if i went your route that you have a minimal ipgateway definition?
I am not certain that here that if i went your path, that the tap interface would actually work at all, even to the local linux box or lan.?? So think I am missing something here on what the issue is.
How does that IPGATEWAY section look on your side?
Kayne
|
Re: IPGATEWAY, 44ENCAP and actual AMPRGW on remote wireguard host
HI Kayne Not sure if this is applicable to you but I had serious problems after changing from buster to bullseye where the TAP interface wouldn¡¯t respond to anything either, in the end the OS needed to have a route manually added after it was brought up so I added a background task with a sleep timer after linbpq launched to put the route back each time. I don¡¯t run AMPR so mine is applicable to just getting the TAP device to talk to the OS interfaces so that I can pull SNMP stats from the BPQ node, in my runbpq script that is called from systemd: (sleep 25; /home/bpq/nodes/pe1rrr/LinBPQTAP-route) & The LinBPQTAP-route:
!/bin/bash -x
sudo route del -host 192.168.1.9 dev LinBPQTAP metric 10
sudo route add -host 192.168.1.9 dev LinBPQTAP metric 10
the metric option was crucial in putting the route before any other default in the table.
I hope this sheds some light with some clues where it may be going wrong.
73 all the best
Red
On Sat, Jul 16, 2022 at 01:34 PM, Kayne Kruse - N9SEO wrote:
Hi,
I am struggling to find a way to make linbpq work with IPGATEWAY.??? OS is Debian 10, kernel 4.19.0-16-686-pae patched with Marius' YO2LOJ AX25 "else" patch for linux ax25.
My IPIP endpoint is a linux box on the far end of a wireguard link and uses the main linux gw ip 44.76.0.193 as the routable wireguard ip and terminates to the linux host at 44.76.0.205
BPQ runs on top that linux box at 44.76.0.205, but I want to use 44.76.0.195 as the IPIP/amprnet ip on BPQ in IPGATEWAY.?
I cannot figure out the correct BPQ config to make it talk to linux routing table and sort the rest out.? The routes are all in linux on the device bpq runs on but since TAP wont talk to interface wg0 because it is not tappable, not sure what my option is.
Over the wire in a packet dump it should look like
44.76.0.205 -> 44.76.0.193 proto ipip
44.76.0.195 -> ANYTUNNELED_44_IP
vice versa on the return path.? Regardless IPIP packets need to get to 44.76.0.193 via linux kernel routing to work in wireguard.
I do this this way because at the linux amprnet gw its easily controls ingress to only allow amprnet ips to access my amprnet ips from a centralized firewall at the router gw.
I hope that makes sense, but perhaps I am not clear.?? Let me know if you need anything further.
IPGATEWAY
ADAPTER enp1s0
44ENCAP 192.168.200.205 ; or I can use 44.76.0.193 as the encap endpoint or an unused lan IP.? None seemed to do much usefulness.
IPADDR 44.76.0.195
IPNETMASK 255.255.255.255
NODEFAULTROUTE
IPPORTS 1
ROUTE 0.0.0.0/0 192.168.200.205
;ROUTE 44.0.0.0/9 44.76.0.193 T? # dont use these, they override linux routes present from wireguard and tie them to LinBPQTAP interface, not desired - Using kernel routing is desired here, I use wireguard and freerrp's bgp to manage route tables and they write to linux routes.
;ROUTE 44.128.0.0/10 44.76.0.193 T
***
I've tried various route's above but removed them as they werent helpful,
Is there any hope or am I completely out there due to my unique situation?
Thanks for reading this.
73 Kayne - n9seo
?HI Kayne
|
John
Sent you a couple of emails direct with a couple of problems in Version 6.0.23.4
No worries Guys I think this may be a isolated case related with the AMPR Network.
Mike Melnik-N9PMO
BPQ32 Group Moderator
|
IPGATEWAY, 44ENCAP and actual AMPRGW on remote wireguard host
Hi,
I am struggling to find a way to make linbpq work with IPGATEWAY.??? OS is Debian 10, kernel 4.19.0-16-686-pae patched with Marius' YO2LOJ AX25 "else" patch for linux ax25.
My IPIP endpoint is a linux box on the far end of a wireguard link and uses the main linux gw ip 44.76.0.193 as the routable wireguard ip and terminates to the linux host at 44.76.0.205
BPQ runs on top that linux box at 44.76.0.205, but I want to use 44.76.0.195 as the IPIP/amprnet ip on BPQ in IPGATEWAY.?
I cannot figure out the correct BPQ config to make it talk to linux routing table and sort the rest out.? The routes are all in linux on the device bpq runs on but since TAP wont talk to interface wg0 because it is not tappable, not sure what my option is.
Over the wire in a packet dump it should look like
44.76.0.205 -> 44.76.0.193 proto ipip
44.76.0.195 -> ANYTUNNELED_44_IP
vice versa on the return path.? Regardless IPIP packets need to get to 44.76.0.193 via linux kernel routing to work in wireguard.
I do this this way because at the linux amprnet gw its easily controls ingress to only allow amprnet ips to access my amprnet ips from a centralized firewall at the router gw.
I hope that makes sense, but perhaps I am not clear.?? Let me know if you need anything further.
IPGATEWAY
ADAPTER enp1s0
44ENCAP 192.168.200.205 ; or I can use 44.76.0.193 as the encap endpoint or an unused lan IP.? None seemed to do much usefulness.
IPADDR 44.76.0.195
IPNETMASK 255.255.255.255
NODEFAULTROUTE
IPPORTS 1
ROUTE 0.0.0.0/0 192.168.200.205
;ROUTE 44.0.0.0/9 44.76.0.193 T? # dont use these, they override linux routes present from wireguard and tie them to LinBPQTAP interface, not desired - Using kernel routing is desired here, I use wireguard and freerrp's bgp to manage route tables and they write to linux routes.
;ROUTE 44.128.0.0/10 44.76.0.193 T
***
I've tried various route's above but removed them as they werent helpful,
Is there any hope or am I completely out there due to my unique situation?
Thanks for reading this.
73 Kayne - n9seo
|
Bob NS2B
Red R. R. Tuby (PE1RRR)