Hi,
I have built a filter below IP which is receiving all files and suppose to
do IPSec encryption/decryption.
This driver works perfectly on QNX on x86 machine including the ability to
receive incoming ftp and telnet (meaning that ftpd and telnetd are running
perfectly on / with it)
Now, while moving this driver to RPX-Lite with ppc i am have a problem to
access the RPX-Lite machine with ftp (i only can with serial line with
qtalk).
My inetd.conf contains both the ftp and telnet command lines, which I’ve
copied from the x86 machine. Also my hosts, passwd exists too.
Scenario:
Loading the RPX-Lite with my image, using ksh.
Before i load my driver: i can connect to the RPX-Lite with telnet / ftp
from a different machine and from the RPX-Lite to a different machine.
After i load my driver: i CAN’T connect to the RPX-Lite with telnet / ftp
from a different machine and i CAN from the RPX-Lite to a different machine.
p.s.: 1) i can do ping from both sides before & after i load my driver.
2) I’ve also tried the same scenario with all of the x86 qnx /etc
directory in it (except hosts and passwd).
Does anyone has any idea or directing to lead me to the solution?
\
Cheers
Benzy Gabay
R&D, QNX team
Everbee Wireless http://www.everbeewireless.com
What error message(s) are you getting?
“Benzy Gabay” <bgabay@everbeewireless.com> wrote in message
news:9t3at8$bom$1@nntp.qnx.com…
Hi,
I have built a filter below IP which is receiving all files and suppose to
do IPSec encryption/decryption.
This driver works perfectly on QNX on x86 machine including the ability to
receive incoming ftp and telnet (meaning that ftpd and telnetd are running
perfectly on / with it)
Now, while moving this driver to RPX-Lite with ppc i am have a problem to
access the RPX-Lite machine with ftp (i only can with serial line with
qtalk).
My inetd.conf contains both the ftp and telnet command lines, which I’ve
copied from the x86 machine. Also my hosts, passwd exists too.
Scenario:
Loading the RPX-Lite with my image, using ksh.
Before i load my driver: i can connect to the RPX-Lite with telnet / ftp
from a different machine and from the RPX-Lite to a different machine.
After i load my driver: i CAN’T connect to the RPX-Lite with telnet / ftp
from a different machine and i CAN from the RPX-Lite to a different
machine.
p.s.: 1) i can do ping from both sides before & after i load my driver.
2) I’ve also tried the same scenario with all of the x86 qnx /etc
directory in it (except hosts and passwd).
Does anyone has any idea or directing to lead me to the solution?
\
Cheers
Benzy Gabay
R&D, QNX team
Everbee Wireless > http://www.everbeewireless.com
no error messages appear.
I’m doing telnet from the remote qnx machine and i don’t even get to see the
login, it gets stacked. although i can see that the tcp session traffic is
going on (i see it in a network monitor i have).
“Issam Haddad” <ihaddad@asurent.com> wrote in message
news:9tat86$h0a$1@inn.qnx.com…
What error message(s) are you getting?
“Benzy Gabay” <> bgabay@everbeewireless.com> > wrote in message
news:9t3at8$bom$> 1@nntp.qnx.com> …
Hi,
I have built a filter below IP which is receiving all files and suppose
to
do IPSec encryption/decryption.
This driver works perfectly on QNX on x86 machine including the ability
to
receive incoming ftp and telnet (meaning that ftpd and telnetd are
running
perfectly on / with it)
Now, while moving this driver to RPX-Lite with ppc i am have a problem
to
access the RPX-Lite machine with ftp (i only can with serial line with
qtalk).
My inetd.conf contains both the ftp and telnet command lines, which I’ve
copied from the x86 machine. Also my hosts, passwd exists too.
Scenario:
Loading the RPX-Lite with my image, using ksh.
Before i load my driver: i can connect to the RPX-Lite with telnet /
ftp
from a different machine and from the RPX-Lite to a different machine.
After i load my driver: i CAN’T connect to the RPX-Lite with telnet /
ftp
from a different machine and i CAN from the RPX-Lite to a different
machine.
p.s.: 1) i can do ping from both sides before & after i load my driver.
2) I’ve also tried the same scenario with all of the x86 qnx
/etc
directory in it (except hosts and passwd).
Does anyone has any idea or directing to lead me to the solution?
\
Cheers
Benzy Gabay
R&D, QNX team
Everbee Wireless > http://www.everbeewireless.com
\
One thing that has bitten me before is that the default inetd.conf looks for
executables in the /bin directory, whereas the files in my ppc build script
end up (typically) in /proc/boot. Just a thought…
“Benzy Gabay” <bgabay@everbeewireless.com> wrote in message
news:9tatil$2k9$1@nntp.qnx.com…
no error messages appear.
I’m doing telnet from the remote qnx machine and i don’t even get to see
the
login, it gets stacked. although i can see that the tcp session traffic is
going on (i see it in a network monitor i have).
“Issam Haddad” <> ihaddad@asurent.com> > wrote in message
news:9tat86$h0a$> 1@inn.qnx.com> …
What error message(s) are you getting?
“Benzy Gabay” <> bgabay@everbeewireless.com> > wrote in message
news:9t3at8$bom$> 1@nntp.qnx.com> …
Hi,
I have built a filter below IP which is receiving all files and
suppose
to
do IPSec encryption/decryption.
This driver works perfectly on QNX on x86 machine including the
ability
to
receive incoming ftp and telnet (meaning that ftpd and telnetd are
running
perfectly on / with it)
Now, while moving this driver to RPX-Lite with ppc i am have a problem
to
access the RPX-Lite machine with ftp (i only can with serial line with
qtalk).
My inetd.conf contains both the ftp and telnet command lines, which
I’ve
copied from the x86 machine. Also my hosts, passwd exists too.
Scenario:
Loading the RPX-Lite with my image, using ksh.
Before i load my driver: i can connect to the RPX-Lite with telnet /
ftp
from a different machine and from the RPX-Lite to a different machine.
After i load my driver: i CAN’T connect to the RPX-Lite with telnet /
ftp
from a different machine and i CAN from the RPX-Lite to a different
machine.
p.s.: 1) i can do ping from both sides before & after i load my
driver.
2) I’ve also tried the same scenario with all of the x86 qnx
/etc
directory in it (except hosts and passwd).
Does anyone has any idea or directing to lead me to the solution?
\
Cheers
Benzy Gabay
R&D, QNX team
Everbee Wireless > http://www.everbeewireless.com
\
mine are under /bin.
“Issam Haddad” <ihaddad@asurent.com> wrote in message
news:9tb3ja$o67$1@inn.qnx.com…
One thing that has bitten me before is that the default inetd.conf looks
for
executables in the /bin directory, whereas the files in my ppc build
script
end up (typically) in /proc/boot. Just a thought…
“Benzy Gabay” <> bgabay@everbeewireless.com> > wrote in message
news:9tatil$2k9$> 1@nntp.qnx.com> …
no error messages appear.
I’m doing telnet from the remote qnx machine and i don’t even get to see
the
login, it gets stacked. although i can see that the tcp session traffic
is
going on (i see it in a network monitor i have).
“Issam Haddad” <> ihaddad@asurent.com> > wrote in message
news:9tat86$h0a$> 1@inn.qnx.com> …
What error message(s) are you getting?
“Benzy Gabay” <> bgabay@everbeewireless.com> > wrote in message
news:9t3at8$bom$> 1@nntp.qnx.com> …
Hi,
I have built a filter below IP which is receiving all files and
suppose
to
do IPSec encryption/decryption.
This driver works perfectly on QNX on x86 machine including the
ability
to
receive incoming ftp and telnet (meaning that ftpd and telnetd are
running
perfectly on / with it)
Now, while moving this driver to RPX-Lite with ppc i am have a
problem
to
access the RPX-Lite machine with ftp (i only can with serial line
with
qtalk).
My inetd.conf contains both the ftp and telnet command lines, which
I’ve
copied from the x86 machine. Also my hosts, passwd exists too.
Scenario:
Loading the RPX-Lite with my image, using ksh.
Before i load my driver: i can connect to the RPX-Lite with telnet
/
ftp
from a different machine and from the RPX-Lite to a different
machine.
After i load my driver: i CAN’T connect to the RPX-Lite with telnet
/
ftp
from a different machine and i CAN from the RPX-Lite to a different
machine.
p.s.: 1) i can do ping from both sides before & after i load my
driver.
2) I’ve also tried the same scenario with all of the x86 qnx
/etc
directory in it (except hosts and passwd).
Does anyone has any idea or directing to lead me to the solution?
\
Cheers
Benzy Gabay
R&D, QNX team
Everbee Wireless > http://www.everbeewireless.com
\