Hi.
I’m using the latest QNX 4.25 and TCP/IP 5.0
I was at a client’s site installing our system and a “funny” thing happen.
I have done UDP broadcast here in our office using the 192.9.200.255
address. When I got to the client’s site, I change the IP address for the
QNX 4 system. I made sure I could ping and be pinged. No problem. Then
tried to broadcast again using the new IP address and it did not work. I
can always go back and use the original IP address but not any other. Why?
What am I missing here?
TIA
Augie
“Operating System Tech Support” <os@qnx.com> wrote in message
news:9rjtsm$b5e$1@nntp.qnx.com…
“Augie Henriques” <> augiehenriques@hotmail.com> > wrote in message
news:9rjoqf$mvd$> 1@inn.qnx.com> …
I have done UDP broadcast here in our office using the 192.9.200.255
address. When I got to the client’s site, I change the IP address for
the
QNX 4 system. I made sure I could ping and be pinged. No problem.
Then
tried to broadcast again using the new IP address and it did not work.
I
can always go back and use the original IP address but not any other.
Why?
What am I missing here?
What was the old IP address you where using? Have yor tried running a
netsniffer to see if the packet actually goes out?
In my office I have setup 192.9.200.19, 192.9.200.53 broadcasting to
192.9.200.255 (port 2000).
In the client’s place we tried 53.141.19.19, 53.141.19.53 broadcasting to
53.141.19.255 (port 2000).
I tried ‘netstat -p’ on the receiving machine and there was no data
received.
I will have to give netsniffer I try.
Augie
-Adam
“Augie Henriques” <augiehenriques@hotmail.com> wrote in message
news:9rjvdk$11d$1@inn.qnx.com…
“Operating System Tech Support” <> os@qnx.com> > wrote in message
news:9rjtsm$b5e$> 1@nntp.qnx.com> …
“Augie Henriques” <> augiehenriques@hotmail.com> > wrote in message
news:9rjoqf$mvd$> 1@inn.qnx.com> …
I have done UDP broadcast here in our office using the 192.9.200.255
address. When I got to the client’s site, I change the IP address for
the
QNX 4 system. I made sure I could ping and be pinged. No problem.
Then
tried to broadcast again using the new IP address and it did not work.
I
can always go back and use the original IP address but not any other.
Why?
What am I missing here?
What was the old IP address you where using? Have yor tried running a
netsniffer to see if the packet actually goes out?
In my office I have setup 192.9.200.19, 192.9.200.53 broadcasting to
192.9.200.255 (port 2000).
In the client’s place we tried 53.141.19.19, 53.141.19.53 broadcasting to
53.141.19.255 (port 2000).
I tried ‘netstat -p’ on the receiving machine and there was no data
received.
I will have to give netsniffer I try.
I don’t have netsniffer for QNX 4 and TCP/IP 5. Were do I get this from?
TIA
Augie
Augie
-Adam
\
192.9.200 is a class C network address so 255 is the broadcast host address.
But 53.141 is a class B network address so the broadcast host should be
255.255 unless you are also specifying as netmask.
If you are specifying a netmask I’m not sure how gracefully they interpret
broadcast requests.
–
Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net
“Augie Henriques” <augiehenriques@hotmail.com> wrote in message
news:9rjvdk$11d$1@inn.qnx.com…
What was the old IP address you where using? Have yor tried running a
netsniffer to see if the packet actually goes out?
In my office I have setup 192.9.200.19, 192.9.200.53 broadcasting to
192.9.200.255 (port 2000).
In the client’s place we tried 53.141.19.19, 53.141.19.53 broadcasting to
53.141.19.255 (port 2000).
Thanks Bill.
That seems to work.
Augie
“Bill Caroselli (Q-TPS)” <qtps@earthlink.net> wrote in message
news:9rk7lh$9iu$1@inn.qnx.com…
192.9.200 is a class C network address so 255 is the broadcast host
address.
But 53.141 is a class B network address so the broadcast host should be
255.255 unless you are also specifying as netmask.
If you are specifying a netmask I’m not sure how gracefully they interpret
broadcast requests.
–
Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net
“Augie Henriques” <> augiehenriques@hotmail.com> > wrote in message
news:9rjvdk$11d$> 1@inn.qnx.com> …
What was the old IP address you where using? Have yor tried running a
netsniffer to see if the packet actually goes out?
In my office I have setup 192.9.200.19, 192.9.200.53 broadcasting to
192.9.200.255 (port 2000).
In the client’s place we tried 53.141.19.19, 53.141.19.53 broadcasting
to
53.141.19.255 (port 2000).
\
“Bill Caroselli (Q-TPS)” <qtps@earthlink.net> wrote in message
news:9rk7lh$9iu$1@inn.qnx.com…
192.9.200 is a class C network address so 255 is the broadcast host
address.
But 53.141 is a class B network address so the broadcast host should be
255.255 unless you are also specifying as netmask.
Just to clarify, I looked it up in the TCP/IP network administration by
O’Reilly & Associates and less that 128 indicates class A address. From 128
to 191 is class B address. From 192 to 223 is class C address and greater
than 223 indicates address is reserved.
So 53. should be class A not class B, correct?
TIA
Augie
If you are specifying a netmask I’m not sure how gracefully they interpret
broadcast requests.
–
Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net
“Augie Henriques” <> augiehenriques@hotmail.com> > wrote in message
news:9rjvdk$11d$> 1@inn.qnx.com> …
What was the old IP address you where using? Have yor tried running a
netsniffer to see if the packet actually goes out?
In my office I have setup 192.9.200.19, 192.9.200.53 broadcasting to
192.9.200.255 (port 2000).
In the client’s place we tried 53.141.19.19, 53.141.19.53 broadcasting
to
53.141.19.255 (port 2000).
\
I don’t have netsniffer for QNX 4 and TCP/IP 5. Were do I get this from?
It’s call netsniff. I think it’s a standard QNX4 utility.
TIA
Augie
Augie
-Adam
\
Actually, that is correct. In which case it should require a subnet mask of
255.255.255
–
Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net
“Augie Henriques” <augiehenriques@hotmail.com> wrote in message
news:9rkaek$ckm$1@inn.qnx.com…
“Bill Caroselli (Q-TPS)” <> qtps@earthlink.net> > wrote in message
news:9rk7lh$9iu$> 1@inn.qnx.com> …
192.9.200 is a class C network address so 255 is the broadcast host
address.
But 53.141 is a class B network address so the broadcast host should be
255.255 unless you are also specifying as netmask.
Just to clarify, I looked it up in the TCP/IP network administration by
O’Reilly & Associates and less that 128 indicates class A address. From
128
to 191 is class B address. From 192 to 223 is class C address and greater
than 223 indicates address is reserved.
So 53. should be class A not class B, correct?
TIA
Augie
In article <9rkeim$gut$1@inn.qnx.com>, “Bill Caroselli (Q-TPS)”
<qtps@earthlink.net> says…
Actually, that is correct. In which case it should require a subnet mask of
255.255.255
Maybe 255 ? > 
–
Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net
“Augie Henriques” <> augiehenriques@hotmail.com> > wrote in message
news:9rkaek$ckm$> 1@inn.qnx.com> …
“Bill Caroselli (Q-TPS)” <> qtps@earthlink.net> > wrote in message
news:9rk7lh$9iu$> 1@inn.qnx.com> …
192.9.200 is a class C network address so 255 is the broadcast host
address.
But 53.141 is a class B network address so the broadcast host should be
255.255 unless you are also specifying as netmask.
Just to clarify, I looked it up in the TCP/IP network administration by
O’Reilly & Associates and less that 128 indicates class A address. From
128
to 191 is class B address. From 192 to 223 is class C address and greater
than 223 indicates address is reserved.
So 53. should be class A not class B, correct?
TIA
Augie
\
–
Stephen Munnings
Software Developer
Corman Technologies Inc.
“Augie Henriques” <augiehenriques@hotmail.com> wrote in message
news:9rjoqf$mvd$1@inn.qnx.com…
I have done UDP broadcast here in our office using the 192.9.200.255
address. When I got to the client’s site, I change the IP address for the
QNX 4 system. I made sure I could ping and be pinged. No problem. Then
tried to broadcast again using the new IP address and it did not work. I
can always go back and use the original IP address but not any other.
Why?
What am I missing here?
What was the old IP address you where using? Have yor tried running a
netsniffer to see if the packet actually goes out?
-Adam