Paxon/AGWPE
 

Anyone here get Paxon working ok with AGWPE? It starts to
work ok, connects fine but then it doesn't send any more
packets. I can see nothing going out in the monitor window.


n2peu

"Brian" wrote in message
om...
Anyone here get Paxon working ok with AGWPE? It starts to
work ok, connects fine but then it doesn't send any more
packets. I can see nothing going out in the monitor window.


Have you tried Flex32 with Paxon? If you can't get AGWPE to cooperate, try
it with Flex32.

Screen-shot tutorials on Flex32 and on Paxon are in the "Tutorials" section
at USPN.

http://www.uspacket.net

Charles, N5PVL

"Brian" wrote in message
om...
Anyone here get Paxon working ok with AGWPE? It starts to
work ok, connects fine but then it doesn't send any more
packets. I can see nothing going out in the monitor window.


Have you tried Flex32 with Paxon? If you can't get AGWPE to cooperate, try
it with Flex32.

Screen-shot tutorials on Flex32 and on Paxon are in the "Tutorials" section
at USPN.

http://www.uspacket.net

Charles, N5PVL

That's not new!
You have to give the complete path to the terminal station, or end call via
first digi call.

f8boe

That's not new!
You have to give the complete path to the terminal station, or end call via
first digi call.

f8boe

"F8BOE" wrote in message ...
That's not new!
You have to give the complete path to the terminal station, or end call via
first digi call.

f8boe

So like this?

c n1abc
Connected to n1abc
Then I send n to see a list of nodes
to connect to a node on the list i send:
c n1def v n1abc

Is that right? If so why doesn't Winpack require that?

Thanks,
n2peu

"F8BOE" wrote in message ...
That's not new!
You have to give the complete path to the terminal station, or end call via
first digi call.

f8boe

So like this?

c n1abc
Connected to n1abc
Then I send n to see a list of nodes
to connect to a node on the list i send:
c n1def v n1abc

Is that right? If so why doesn't Winpack require that?

Thanks,
n2peu

Brian wrote on 02/05/2004 20:41:

"F8BOE" wrote in message ...

That's not new!
You have to give the complete path to the terminal station, or end call via
first digi call.

So like this?

c n1abc
Connected to n1abc
Then I send n to see a list of nodes
to connect to a node on the list i send:
c n1def v n1abc

Is that right? If so why doesn't Winpack require that?

It has nothing to do with WinPack. F8BOE is talking about digipeaters
and you are talking about nodes - they are not the same thing.

If you connect to a node, and you want to connect to another node, say
NODE2, from that node, then you simply use the command C NODE2

--
Roger Barker, G4IDE -
For UI-View go to - http://www.UI-View.com
For WinPack go to - http://www.peaksys.co.uk

Brian wrote on 02/05/2004 20:41:

"F8BOE" wrote in message ...

That's not new!
You have to give the complete path to the terminal station, or end call via
first digi call.

So like this?

c n1abc
Connected to n1abc
Then I send n to see a list of nodes
to connect to a node on the list i send:
c n1def v n1abc

Is that right? If so why doesn't Winpack require that?

It has nothing to do with WinPack. F8BOE is talking about digipeaters
and you are talking about nodes - they are not the same thing.

If you connect to a node, and you want to connect to another node, say
NODE2, from that node, then you simply use the command C NODE2

--
Roger Barker, G4IDE -
For UI-View go to - http://www.UI-View.com
For WinPack go to - http://www.peaksys.co.uk

Yes, so is it: as many digis know each others due to the auto router, you
can just type for example "hb9eas-8 db0frg" in the connection window of
Paxon to access a BBS via your digi. These paths are kept in memory, and
your call-ssid as well so you can choose them for each connection.

An other problem with AGWPE is that it keeps the default SSID for every
connection until you change it manually and with twice the same SSID on one
digi, you'll have problems, so you must enter a different SSID manually each
time you make a connect.

I don't know why these problems occur with Paxon... It should be a bug as
2.00.1114 is the first version running with AGWPE and is a beta-test
version.
Other programs I tested didn't have these problems Winpack, Winstop, WPP...

I think the best way of using Paxon is to run it with Flex32. Just have a
look at uspacket.net.

73 de F8BOE

Yes, so is it: as many digis know each others due to the auto router, you
can just type for example "hb9eas-8 db0frg" in the connection window of
Paxon to access a BBS via your digi. These paths are kept in memory, and
your call-ssid as well so you can choose them for each connection.

An other problem with AGWPE is that it keeps the default SSID for every
connection until you change it manually and with twice the same SSID on one
digi, you'll have problems, so you must enter a different SSID manually each
time you make a connect.

I don't know why these problems occur with Paxon... It should be a bug as
2.00.1114 is the first version running with AGWPE and is a beta-test
version.
Other programs I tested didn't have these problems Winpack, Winstop, WPP...

I think the best way of using Paxon is to run it with Flex32. Just have a
look at uspacket.net.

73 de F8BOE

Roger wrote in message ...
Brian wrote on 02/05/2004 20:41:

"F8BOE" wrote in message ...

That's not new!
You have to give the complete path to the terminal station, or end call via
first digi call.

So like this?

c n1abc
Connected to n1abc
Then I send n to see a list of nodes
to connect to a node on the list i send:
c n1def v n1abc

Is that right? If so why doesn't Winpack require that?

It has nothing to do with WinPack. F8BOE is talking about digipeaters
and you are talking about nodes - they are not the same thing.

If you connect to a node, and you want to connect to another node, say
NODE2, from that node, then you simply use the command C NODE2


These are NET/ROM nodes I'm talking about. I am able to send the
command
C NODE2 and it connects but any other input from me never gets sent.
If I
use a via path to connect (C NODE2 v NODE1) to a node it works fine.
Connects
and input gets sent ok. I like the way Paxon lets you set the colors
of
the headers/input text/output text/etc so you are able to see whats
going
on much easier. I started out using GP/TFPCX and have been looking
for a
windoze "equivalent" ever since :)

Roger wrote in message ...
Brian wrote on 02/05/2004 20:41:

"F8BOE" wrote in message ...

That's not new!
You have to give the complete path to the terminal station, or end call via
first digi call.

So like this?

c n1abc
Connected to n1abc
Then I send n to see a list of nodes
to connect to a node on the list i send:
c n1def v n1abc

Is that right? If so why doesn't Winpack require that?

It has nothing to do with WinPack. F8BOE is talking about digipeaters
and you are talking about nodes - they are not the same thing.

If you connect to a node, and you want to connect to another node, say
NODE2, from that node, then you simply use the command C NODE2


These are NET/ROM nodes I'm talking about. I am able to send the
command
C NODE2 and it connects but any other input from me never gets sent.
If I
use a via path to connect (C NODE2 v NODE1) to a node it works fine.
Connects
and input gets sent ok. I like the way Paxon lets you set the colors
of
the headers/input text/output text/etc so you are able to see whats
going
on much easier. I started out using GP/TFPCX and have been looking
for a
windoze "equivalent" ever since :)