Hi,
I’m using QNX 6.1 patch a on x86 machine.
uname -a is:
: QNX6.1.0 2001/06/25-15:31:48 x86pc x86
I’ve built an IPSec driver.
IPSec packets are seen by any LAN monitor as SIPP-ESP packets.
While using Ethernet adapter everything is working perfectly, i can do ping
which is been encrypted by my driver and then I’m getting echo-reply from
the destination host, which is secure too (SIPP-ESP) and my driver decrypts
it and everything is cool.
Now, while using the same machine but using pppd I’m getting the following:
I’m doing a ping from the QNX machine. (Like i did with Ethernet).
The packet is coming out of the QNX machine encrypted. I can see it with my
LAN monitor.
The encrypted ping packet is been answered with encrypted ping answer.
The answer is to the QNX machine ip address.
The QNX machine is answering: protocol_unrch.
After reading a bit about this answer i learned that this answer is for
protocol that is not supported by the destination host.
After reading a bit on the pppd help, I’ve noticed that it has 3
configuration files, which does not exist in my machine or just empty.
Heeeelllllpppppp.
Any idea?
–
Cheers
Benzy Gabay
Benzy Gabay <bgabay@everbeewireless.com> wrote:
Hi,
I’m using QNX 6.1 patch a on x86 machine.
uname -a is:
: QNX6.1.0 2001/06/25-15:31:48 x86pc x86
I’ve built an IPSec driver.
IPSec packets are seen by any LAN monitor as SIPP-ESP packets.
While using Ethernet adapter everything is working perfectly, i can do ping
which is been encrypted by my driver and then I’m getting echo-reply from
the destination host, which is secure too (SIPP-ESP) and my driver decrypts
it and everything is cool.
Now, while using the same machine but using pppd I’m getting the following:
I’m doing a ping from the QNX machine. (Like i did with Ethernet).
The packet is coming out of the QNX machine encrypted. I can see it with my
LAN monitor.
The encrypted ping packet is been answered with encrypted ping answer.
The answer is to the QNX machine ip address.
The QNX machine is answering: protocol_unrch.
Is your ppp go though ethernet or it go though serial port?
How does your IPSec driver regist to io-net (is it a producer?
Filter? what is the up/below type?)
Is the “protocal_unreach” is an ICMP you seen on wire? Or
is it printed out by something ?
-xtang
After reading a bit about this answer i learned that this answer is for
protocol that is not supported by the destination host.
After reading a bit on the pppd help, I’ve noticed that it has 3
configuration files, which does not exist in my machine or just empty.
Heeeelllllpppppp.
Any idea?
–
Cheers
Benzy Gabay
xtang,
Is your ppp go though Ethernet or it go though serial port?
though serial
How does your IPSec driver regist to io-net (is it a producer?
Filter? what is the up/below type?)
_REG_FILTER_BELOW | _REG_INIT_ONCE | _REG_DREG_ALL,
“devn-my-driver.so”,
“ip”,
“ip”
Is the “protocal_unreach” is an ICMP you seen on wire? Or
is it printed out by something ?
I watch it on the wire with a tired party windows NT program called:
LANWatch32. I’m using it a lot and it is very reliable.
I can also send you the packet in hex that is been read by this program. If
you really need it.
Cheers
“Xiaodan Tang” <xtang@qnx.com> wrote in message
news:9spm5a$6fj$1@nntp.qnx.com…
Benzy Gabay <> bgabay@everbeewireless.com> > wrote:
Hi,
I’m using QNX 6.1 patch a on x86 machine.
uname -a is:
: QNX6.1.0 2001/06/25-15:31:48 x86pc x86
I’ve built an IPSec driver.
IPSec packets are seen by any LAN monitor as SIPP-ESP packets.
While using Ethernet adapter everything is working perfectly, i can do
ping
which is been encrypted by my driver and then I’m getting echo-reply
from
the destination host, which is secure too (SIPP-ESP) and my driver
decrypts
it and everything is cool.
Now, while using the same machine but using pppd I’m getting the
following:
I’m doing a ping from the QNX machine. (Like i did with Ethernet).
The packet is coming out of the QNX machine encrypted. I can see it with
my
LAN monitor.
The encrypted ping packet is been answered with encrypted ping answer.
The answer is to the QNX machine ip address.
The QNX machine is answering: protocol_unrch.
Is your ppp go though ethernet or it go though serial port?
How does your IPSec driver regist to io-net (is it a producer?
Filter? what is the up/below type?)
Is the “protocal_unreach” is an ICMP you seen on wire? Or
is it printed out by something ?
-xtang
After reading a bit about this answer i learned that this answer is for
protocol that is not supported by the destination host.
After reading a bit on the pppd help, I’ve noticed that it has 3
configuration files, which does not exist in my machine or just empty.
Heeeelllllpppppp.
Any idea?
–
Cheers
Benzy Gabay
Forgot to add that the monitoring is not on the serial line but on the
Ethernet line which is located after my ppp server computer. e.g.:
-------- serial --------- Ethernet -------
|QNX|------------------|PPP |--------------------|host |
|PC | |Server| | | |
-------- --------- | --------
|pc with |
“Benzy Gabay” <bgabay@everbeewireless.com> wrote in message
news:9sqqsn$1kn$1@inn.qnx.com…
xtang,
Is your ppp go though Ethernet or it go though serial port?
though serial
How does your IPSec driver regist to io-net (is it a producer?
Filter? what is the up/below type?)
_REG_FILTER_BELOW | _REG_INIT_ONCE | _REG_DREG_ALL,
“devn-my-driver.so”,
“ip”,
“ip”
Is the “protocal_unreach” is an ICMP you seen on wire? Or
is it printed out by something ?
I watch it on the wire with a tired party windows NT program called:
LANWatch32. I’m using it a lot and it is very reliable.
I can also send you the packet in hex that is been read by this program.
If
you really need it.
Cheers
“Xiaodan Tang” <> xtang@qnx.com> > wrote in message
news:9spm5a$6fj$> 1@nntp.qnx.com> …
Benzy Gabay <> bgabay@everbeewireless.com> > wrote:
Hi,
I’m using QNX 6.1 patch a on x86 machine.
uname -a is:
: QNX6.1.0 2001/06/25-15:31:48 x86pc x86
I’ve built an IPSec driver.
IPSec packets are seen by any LAN monitor as SIPP-ESP packets.
While using Ethernet adapter everything is working perfectly, i can do
ping
which is been encrypted by my driver and then I’m getting echo-reply
from
the destination host, which is secure too (SIPP-ESP) and my driver
decrypts
it and everything is cool.
Now, while using the same machine but using pppd I’m getting the
following:
I’m doing a ping from the QNX machine. (Like i did with Ethernet).
The packet is coming out of the QNX machine encrypted. I can see it
with
my
LAN monitor.
The encrypted ping packet is been answered with encrypted ping answer.
The answer is to the QNX machine ip address.
The QNX machine is answering: protocol_unrch.
Is your ppp go though ethernet or it go though serial port?
How does your IPSec driver regist to io-net (is it a producer?
Filter? what is the up/below type?)
Is the “protocal_unreach” is an ICMP you seen on wire? Or
is it printed out by something ?
-xtang
After reading a bit about this answer i learned that this answer is
for
protocol that is not supported by the destination host.
After reading a bit on the pppd help, I’ve noticed that it has 3
configuration files, which does not exist in my machine or just empty.
Heeeelllllpppppp.
Any idea?
–
Cheers
Benzy Gabay
\