We’re running QNX 4.24 and we would like to build redundancy into our IP
connection. I
thought I could do this with the “-d forward” option of Socket. Can I do
this on a single
LAN or do they have to be separate? As a test, I have the following
netstart:
Socket -d forward 192.168.140.1 &
ifconfig en1 192.168.140.1 up
ifconfig en2 192.168.140.2 up
If I pull the connection to en1, I loose access to 192.168.140.1. Is there
any way
to accomplish this?
Thanks,
Barry
I’m not at all clear as to what you are trying to accomplish.
The -d forward parameter is making the node a router that will
pass on packets. Do you have two Lan cards, dual networks?
Is this QNX → QNX or QNX → !QNX?
Previously, Barry Hines wrote in comp.os.qnx:
We’re running QNX 4.24 and we would like to build redundancy into our IP
connection. I
thought I could do this with the “-d forward” option of Socket. Can I do
this on a single
LAN or do they have to be separate? As a test, I have the following
netstart:Socket -d forward 192.168.140.1 &
ifconfig en1 192.168.140.1 up
ifconfig en2 192.168.140.2 upIf I pull the connection to en1, I loose access to 192.168.140.1. Is there
any way
to accomplish this?Thanks,
Barry
\
–
Mitchell Schoenbrun --------- maschoen@pobox.com
This is QNX → !QNX with two LAN cards, two connections, but not dual
networks. The concern is card failure.
Thanks
Barry Hines
Barry,
AFAIK, one NIC = one IP address. If you want to have the backup card backup
the IP address, you would need to do the required ipconfig commands to give
the second card the IP address of the first card after you have detected
that it has failed.
Stan Driggs
“Barry Hines” <Barry.Hines@tripointglobal.com> wrote in message
news:99fvkc$98v$1@inn.qnx.com…
This is QNX → !QNX with two LAN cards, two connections, but not dual
networks. The concern is card failure.Thanks
Barry Hines
“Stan Driggs” <stan@no.spam.please.ensco.com> wrote in message
news:9asjfi$qaa$1@inn.qnx.com…
Barry,
AFAIK, one NIC = one IP address. If you want to have the backup card
backup
the IP address, you would need to do the required ipconfig commands to
give
the second card the IP address of the first card after you have detected
that it has failed.
usually one ip address → one nic but not vise versa 
one nic can have a
set of ip addresses so called aliases. for example for server external
address to access internet and internal address to access lan.
Stan Driggs
“Barry Hines” <> Barry.Hines@tripointglobal.com> > wrote in message
news:99fvkc$98v$> 1@inn.qnx.com> …
This is QNX → !QNX with two LAN cards, two connections, but not dual
networks. The concern is card failure.Thanks
Barry Hines
// wbr
The one NIC = one IP address is not the problem. The problem is the QNX
limitation that forces the two NIC’s to be on separate subnets.
ian zagorskih wrote in message <9au5j9$o6s$1@inn.qnx.com>…
“Stan Driggs” <> stan@no.spam.please.ensco.com> > wrote in message
news:9asjfi$qaa$> 1@inn.qnx.com> …
Barry,AFAIK, one NIC = one IP address. If you want to have the backup card
backup
the IP address, you would need to do the required ipconfig commands to
give
the second card the IP address of the first card after you have detected
that it has failed.usually one ip address → one nic but not vise versa >
set of ip addresses so called aliases. for example for server external
address to access internet and internal address to access lan.Stan Driggs
“Barry Hines” <> Barry.Hines@tripointglobal.com> > wrote in message
news:99fvkc$98v$> 1@inn.qnx.com> …
This is QNX → !QNX with two LAN cards, two connections, but not dual
networks. The concern is card failure.Thanks
Barry Hines// wbr
I’m also looking into this.
FYI, I’ve tried the following and it seamed to work using QNX4.25D and
TCP/IP 4.25C:
Does anyone have comments on this test? Potential problems?
One problem is that I have no easy way to detect that the main link is up
again.
I’m planning to write a PING alike application to detect NIC or network
failure and have it to automaticly reconfigure the interface to use the
alternate NIC on failure.
Cesar.
“Barry Hines” <Barry.Hines@tripointglobal.com> wrote in message
news:9bf3ej$p1c$1@inn.qnx.com…
The one NIC = one IP address is not the problem. The problem is the QNX
limitation that forces the two NIC’s to be on separate subnets.
ian zagorskih wrote in message <9au5j9$o6s$> 1@inn.qnx.com> >…“Stan Driggs” <> stan@no.spam.please.ensco.com> > wrote in message
news:9asjfi$qaa$> 1@inn.qnx.com> …
Barry,AFAIK, one NIC = one IP address. If you want to have the backup card
backup
the IP address, you would need to do the required ipconfig commands to
give
the second card the IP address of the first card after you have
detected
that it has failed.usually one ip address → one nic but not vise versa >
a
set of ip addresses so called aliases. for example for server external
address to access internet and internal address to access lan.Stan Driggs
“Barry Hines” <> Barry.Hines@tripointglobal.com> > wrote in message
news:99fvkc$98v$> 1@inn.qnx.com> …
This is QNX → !QNX with two LAN cards, two connections, but not
dual
networks. The concern is card failure.Thanks
Barry Hines// wbr
\
Cesar Hernandez <chernandez@vds.ca> wrote:
I’m also looking into this.
FYI, I’ve tried the following and it seamed to work using QNX4.25D and
TCP/IP 4.25C:
- Configure NIC1 (ne1)
ifconfig en1 192.168.150.1 up netmask 255.255.255.0
route add -net 0 192.168.150.2- Start 2 telnet sessions to another computer, one to each direction.
- Unplug the cable from NIC1 and plug it on NIC2
4 Unconfigure routing of NIC1:
ifconfig en1 down
ifconfig en1 delete 192.168.150.1
route delete 0 192.168.150.2
5 Configure NIC2 (en2) with the same IP address
ifconfig en2 192.168.150.1 up netmask 255.255.255.0
route add -net 0 192.168.150.2
6 Check the status of telnet sessions: OK (it also worked with 2 FTP
sessions transmitting data)Does anyone have comments on this test? Potential problems?
One problem is that I have no easy way to detect that the main link is up
again.I’m planning to write a PING alike application to detect NIC or network
failure and have it to automaticly reconfigure the interface to use the
alternate NIC on failure.
You can re-config the failed interface to another IP (192.168.150.100),
and have your “PING alike” application do slow pull on it to detect if
the link is up again
-xtang
Cesar.
“Barry Hines” <> Barry.Hines@tripointglobal.com> > wrote in message
news:9bf3ej$p1c$> 1@inn.qnx.com> …
The one NIC = one IP address is not the problem. The problem is the QNX
limitation that forces the two NIC’s to be on separate subnets.
ian zagorskih wrote in message <9au5j9$o6s$> 1@inn.qnx.com> >…“Stan Driggs” <> stan@no.spam.please.ensco.com> > wrote in message
news:9asjfi$qaa$> 1@inn.qnx.com> …
Barry,AFAIK, one NIC = one IP address. If you want to have the backup card
backup
the IP address, you would need to do the required ipconfig commands to
give
the second card the IP address of the first card after you have
detected
that it has failed.usually one ip address → one nic but not vise versa >
a
set of ip addresses so called aliases. for example for server external
address to access internet and internal address to access lan.Stan Driggs
“Barry Hines” <> Barry.Hines@tripointglobal.com> > wrote in message
news:99fvkc$98v$> 1@inn.qnx.com> …
This is QNX → !QNX with two LAN cards, two connections, but not
dual
networks. The concern is card failure.Thanks
Barry Hines// wbr
\
I’m planning to write a PING alike application to detect NIC or network
failure and have it to automaticly reconfigure the interface to use the
alternate NIC on failure.You can re-config the failed interface to another IP (192.168.150.100),
and have your “PING alike” application do slow pull on it to detect if
the link is up again >-xtang
Again the limitation of each IP address to be on separate sub-net networks
makes life complicated.
Your suggestion will only work if we re-configure the failed interface (en1)
to another IP address on another sub-net (Ex: 192.168.160.1), which means
that the remote monitored gateway will required to be configured on that
sub-net too. Otherwise, the routing table will redirect packets to the good
interface (en2) now assigned to reach the 192.168.150 sub-net.
Cesar.