Re: AXIP Links
- I think the the only time it might make sense is when interfacing with nodes running other software. If you define two (or more) AXIP listeners the first port becomes the source port for all traffic from your node.
Example (portion from axip cfg):
A node listening on UDP ports 10092 and 10093.
All the axudp traffic from that node will have a source port of 10092 even if you're sending traffic to 10093. Some software/firewall configurations seem to expect the traffic to have matching source and destination ports. Odd connectivity issues may develop as a result.
This a flaw in BPQ32? Not IMHO. Firewall configurations can be written/modified to allow for this. Beyond that, I question the programming of the other software that needs source/destination ports to match.
Since 10093 seems to be the most common axudp port, I always make sure it's the first listener defined in the axip cfg.
This deals with most problems. I can see where if you're talking to more than one "picky" remote system on odd port numbers then the multiple axip port approach may be the only way to get things talking both ways. IF the new port approach fixes the source port issue for that particular link?
Easy fix? Standardize upon 10093 and make you life (and those you link to) easier ;-)
--- In BPQ32@yahoogroups.com, "John Wiseman" <john.wiseman@...> wrote:
> You no longer need the BPQAXIP.cfg file. You don't have to define
> separate ports for each neighbour, but you can if you want to. You can
> still have all your axip links on one axip port. Just include your
> current bpqaxip.cfg between the CONFIG and ENDPORT.
> I can't really see any advantage to having a separate BPQ PORT for each
> axip neighbour. It may be more familiar to those used to xrouter, but
> there is an overhead. If you only have a few axip neighbours then it
> won't do much harm, but remember there is a limit of 32 ports,and using
> ports above 16 is pretty much untested, and may upset some application
> programs that were written when there was a limit of 16.
> -----Original Message-----
> From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of
> Sent: 15 October 2010 04:46
> To: BPQ32@yahoogroups.com
> Subject: [BPQ32] AXIP Links
> Hi John & ALL, I have become a little confused after reading "Recent
> Changes to BPQ32 Node" "7th October 2010 Version 18.104.22.168" .... "You
> can still have separate config files, but I recommend converting to the
> new format." - ie
> You can now included all driver configuration information in bpq32.cfg.
> Just before the ENDPORT add CONFIG, then the config statements from your
> driver.cfg file,
> Does this mean - We do not need the BPQAXIP.CFG file -
> Thus if we have two AXUDP links, we can use the following entry within
> BPQ32.CFG file eg -
> ID=AXUDP Link to VK2AAL
> BROADCAST NODES
> MHEARD ON
> UDP 10093 ;Listens for UDP packets on this port number
> MAP VK2AAL 192.168.1.10 UDP 10093 B
> MAP DUMMY bpqchatmon.ham-radio-op.net UDP 10090 B
> ID=AXUDP Link to VK2VVV
> BROADCAST NODES
> MHEARD ON
> UDP 93 ;Listens for UDP packets on this port number
> MAP VK2VVV 192.168.1.11 UDP 93 B
> So if we do a "P"orts command, it will display
> 10 AXUDP Link to VK2AAL
> 11 AXUDP Link to VK2VVV
> Regards Rod....///