That should have been 'doesn't end in .255' not .222
Cheers,
Luis.
Luis wrote:
Hiya,
.255 is usually used as the broadcast IP for any routers/routing in the
network.
The broadcast address is for _network broadcasts_. Change the IP address
you're sending to so that it doesn't end in .222
Hello.
I think that the point was to use broadcasts not to use another
address. I've found the same problem on OS X where when you write
packets to a .255 address they don't get routed across the network,
as if it were a regular address. In looking back on other threads on
this subject, i
Brent Anderson wrote:
Hello.
I think that the point was to use broadcasts not to use another
address. I've found the same problem on OS X where when you write
packets to a .255 address they don't get routed across the network, as
if it were a regular address. In looking back on other threads
Alex-
Thursday, January 11, 2007, 9:56:01 AM, you wrote:
> It is certainly possible to send a broadcast packet from OSX (e.g. you
> can do "ping 192.168.1.255" and it works correctly), but I don't know
> whether or not it is possible to do it from Rev. I'll play with it some
> more later tonight
Hi,
As a workaround witch works for me with any Rev issues i still use
(2.51 to 2.74) under the Windows, Mac OS X, Ubuntu or Solaris
platforms :
Build your stack under the Metacard (2.32 to 2.5 issues tested OK)
first. Reopen and save this stack as "stack.rev" under the Rev
environment
