How to communicate with a device that has an assigned “0.0.0.0” IP address?

Clash Royale CLAN TAG#URR8PPP

up vote
5
down vote

favorite

I have an piece of industrial equipment that runs on a pretty basic OS called VxWorks. I usually communicate with the system for troubleshooting purposes by setting my IPv4 IP to the same range as the local IP and then running diagnostic software.

A few weeks ago I found that for some odd reason the local IP addreess of the system set itself to 0.0.0.0. Now I want to get into diagnostics to change it but my PC will not permit setting an IP beginning in 0.

Is there any other way to communicate with a device that has a local IP of 0.0.0.0 using a windows PC.

There is no way to reset the device to factory default settings without shipping it back to the manufacturer.

networking ip

share|improve this question

edited 3 hours ago

JakeGould

30.2k1092133

asked 4 hours ago

Pablo Gonzalez

261

New contributor

Pablo Gonzalez is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  As others state 0.0.0.0 is not a routable address. Many pieces of software bind to 0.0.0.0 to allow that software to bind to whatever IP address is assigned to the network interface. This makes it easier—for example—to place the device on an DHCP setting and you just connect by getting the devices IP address and that’s that. My big question to you is why you are setting your machine’s IPv4 IP to the same range as the local IP to then running diagnostic software? Makes no sense. You should just get the device’s IP address and connect to that. That said, I have an idea. Posting an answer.
  – JakeGould
  3 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  VX Works might not run DHCP and might therefore need a static IP address, something you would have to do internally on VX Works. In addition to that, any software or interfaces on your PC that talk to that VX Works machine would have to know that IP address. You would have to verify that all machines that need to talk to your VX Works machine know its IP address. It might auto-fill, or you might have to enter it manually. The all-0s address works as a default gateway, however, if your VX Works machine and your host it wants to talk to both have that gateway in common.
  – Shankensteinium
  2 hours ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  How were you able to determine that the device is using an IP address of 0.0.0.0? Did you use a piece of software that was able to communicate with the device over the network, or is there a basic Human-Machine Interface (HMI) on the device to show you the IP address? Also, to get the obvious question out of the way, have you tried turning it off and then on again to see if it picks up a sane address?
  – Sam Skuce
  1 hour ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Literally assigning itself address 0.0.0.0 is not possible if it has a standards compliant IP stack. This leaves a couple of options: 1. It shows 0.0.0.0 as a way to signal that it failed to assign an IP address. 2. It has a broken IP stack which somehow managed to assign itself 0.0.0.0. I don't know enough about VxWorks to say which of the two is most likely. If it really has assigned address 0.0.0.0 you'd need a hacked up IP stack to communicate with it. But that will not do much good if it hasn't assigned an address at all.
  – kasperd
  12 mins ago
  

  
  
  
  

add a comment | 

up vote
5
down vote

favorite

I have an piece of industrial equipment that runs on a pretty basic OS called VxWorks. I usually communicate with the system for troubleshooting purposes by setting my IPv4 IP to the same range as the local IP and then running diagnostic software.

A few weeks ago I found that for some odd reason the local IP addreess of the system set itself to 0.0.0.0. Now I want to get into diagnostics to change it but my PC will not permit setting an IP beginning in 0.

Is there any other way to communicate with a device that has a local IP of 0.0.0.0 using a windows PC.

There is no way to reset the device to factory default settings without shipping it back to the manufacturer.

networking ip

share|improve this question

edited 3 hours ago

JakeGould

30.2k1092133

asked 4 hours ago

Pablo Gonzalez

261

New contributor

Pablo Gonzalez is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  As others state 0.0.0.0 is not a routable address. Many pieces of software bind to 0.0.0.0 to allow that software to bind to whatever IP address is assigned to the network interface. This makes it easier—for example—to place the device on an DHCP setting and you just connect by getting the devices IP address and that’s that. My big question to you is why you are setting your machine’s IPv4 IP to the same range as the local IP to then running diagnostic software? Makes no sense. You should just get the device’s IP address and connect to that. That said, I have an idea. Posting an answer.
  – JakeGould
  3 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  VX Works might not run DHCP and might therefore need a static IP address, something you would have to do internally on VX Works. In addition to that, any software or interfaces on your PC that talk to that VX Works machine would have to know that IP address. You would have to verify that all machines that need to talk to your VX Works machine know its IP address. It might auto-fill, or you might have to enter it manually. The all-0s address works as a default gateway, however, if your VX Works machine and your host it wants to talk to both have that gateway in common.
  – Shankensteinium
  2 hours ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  How were you able to determine that the device is using an IP address of 0.0.0.0? Did you use a piece of software that was able to communicate with the device over the network, or is there a basic Human-Machine Interface (HMI) on the device to show you the IP address? Also, to get the obvious question out of the way, have you tried turning it off and then on again to see if it picks up a sane address?
  – Sam Skuce
  1 hour ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Literally assigning itself address 0.0.0.0 is not possible if it has a standards compliant IP stack. This leaves a couple of options: 1. It shows 0.0.0.0 as a way to signal that it failed to assign an IP address. 2. It has a broken IP stack which somehow managed to assign itself 0.0.0.0. I don't know enough about VxWorks to say which of the two is most likely. If it really has assigned address 0.0.0.0 you'd need a hacked up IP stack to communicate with it. But that will not do much good if it hasn't assigned an address at all.
  – kasperd
  12 mins ago
  

  
  
  
  

add a comment | 

up vote
5
down vote

favorite

up vote
5
down vote

favorite

I have an piece of industrial equipment that runs on a pretty basic OS called VxWorks. I usually communicate with the system for troubleshooting purposes by setting my IPv4 IP to the same range as the local IP and then running diagnostic software.

A few weeks ago I found that for some odd reason the local IP addreess of the system set itself to 0.0.0.0. Now I want to get into diagnostics to change it but my PC will not permit setting an IP beginning in 0.

Is there any other way to communicate with a device that has a local IP of 0.0.0.0 using a windows PC.

There is no way to reset the device to factory default settings without shipping it back to the manufacturer.

networking ip

share|improve this question

edited 3 hours ago

JakeGould

30.2k1092133

asked 4 hours ago

Pablo Gonzalez

261

New contributor

Pablo Gonzalez is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

I have an piece of industrial equipment that runs on a pretty basic OS called VxWorks. I usually communicate with the system for troubleshooting purposes by setting my IPv4 IP to the same range as the local IP and then running diagnostic software.

A few weeks ago I found that for some odd reason the local IP addreess of the system set itself to 0.0.0.0. Now I want to get into diagnostics to change it but my PC will not permit setting an IP beginning in 0.

Is there any other way to communicate with a device that has a local IP of 0.0.0.0 using a windows PC.

There is no way to reset the device to factory default settings without shipping it back to the manufacturer.

networking ip

networking ip

share|improve this question

edited 3 hours ago

JakeGould

30.2k1092133

asked 4 hours ago

Pablo Gonzalez

261

New contributor

Pablo Gonzalez is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

edited 3 hours ago

JakeGould

30.2k1092133

asked 4 hours ago

Pablo Gonzalez

261

New contributor

Pablo Gonzalez is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

share|improve this question

edited 3 hours ago

JakeGould

30.2k1092133

edited 3 hours ago

JakeGould

30.2k1092133

edited 3 hours ago

JakeGould

30.2k1092133

30.2k1092133

asked 4 hours ago

Pablo Gonzalez

261

New contributor

Pablo Gonzalez is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 4 hours ago

Pablo Gonzalez

261

asked 4 hours ago

Pablo Gonzalez

261

261

New contributor

Pablo Gonzalez is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

New contributor

Pablo Gonzalez is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

Pablo Gonzalez is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  As others state 0.0.0.0 is not a routable address. Many pieces of software bind to 0.0.0.0 to allow that software to bind to whatever IP address is assigned to the network interface. This makes it easier—for example—to place the device on an DHCP setting and you just connect by getting the devices IP address and that’s that. My big question to you is why you are setting your machine’s IPv4 IP to the same range as the local IP to then running diagnostic software? Makes no sense. You should just get the device’s IP address and connect to that. That said, I have an idea. Posting an answer.
  – JakeGould
  3 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  VX Works might not run DHCP and might therefore need a static IP address, something you would have to do internally on VX Works. In addition to that, any software or interfaces on your PC that talk to that VX Works machine would have to know that IP address. You would have to verify that all machines that need to talk to your VX Works machine know its IP address. It might auto-fill, or you might have to enter it manually. The all-0s address works as a default gateway, however, if your VX Works machine and your host it wants to talk to both have that gateway in common.
  – Shankensteinium
  2 hours ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  How were you able to determine that the device is using an IP address of 0.0.0.0? Did you use a piece of software that was able to communicate with the device over the network, or is there a basic Human-Machine Interface (HMI) on the device to show you the IP address? Also, to get the obvious question out of the way, have you tried turning it off and then on again to see if it picks up a sane address?
  – Sam Skuce
  1 hour ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Literally assigning itself address 0.0.0.0 is not possible if it has a standards compliant IP stack. This leaves a couple of options: 1. It shows 0.0.0.0 as a way to signal that it failed to assign an IP address. 2. It has a broken IP stack which somehow managed to assign itself 0.0.0.0. I don't know enough about VxWorks to say which of the two is most likely. If it really has assigned address 0.0.0.0 you'd need a hacked up IP stack to communicate with it. But that will not do much good if it hasn't assigned an address at all.
  – kasperd
  12 mins ago
  

  
  
  
  

add a comment | 

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  As others state 0.0.0.0 is not a routable address. Many pieces of software bind to 0.0.0.0 to allow that software to bind to whatever IP address is assigned to the network interface. This makes it easier—for example—to place the device on an DHCP setting and you just connect by getting the devices IP address and that’s that. My big question to you is why you are setting your machine’s IPv4 IP to the same range as the local IP to then running diagnostic software? Makes no sense. You should just get the device’s IP address and connect to that. That said, I have an idea. Posting an answer.
  – JakeGould
  3 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  VX Works might not run DHCP and might therefore need a static IP address, something you would have to do internally on VX Works. In addition to that, any software or interfaces on your PC that talk to that VX Works machine would have to know that IP address. You would have to verify that all machines that need to talk to your VX Works machine know its IP address. It might auto-fill, or you might have to enter it manually. The all-0s address works as a default gateway, however, if your VX Works machine and your host it wants to talk to both have that gateway in common.
  – Shankensteinium
  2 hours ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  How were you able to determine that the device is using an IP address of 0.0.0.0? Did you use a piece of software that was able to communicate with the device over the network, or is there a basic Human-Machine Interface (HMI) on the device to show you the IP address? Also, to get the obvious question out of the way, have you tried turning it off and then on again to see if it picks up a sane address?
  – Sam Skuce
  1 hour ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Literally assigning itself address 0.0.0.0 is not possible if it has a standards compliant IP stack. This leaves a couple of options: 1. It shows 0.0.0.0 as a way to signal that it failed to assign an IP address. 2. It has a broken IP stack which somehow managed to assign itself 0.0.0.0. I don't know enough about VxWorks to say which of the two is most likely. If it really has assigned address 0.0.0.0 you'd need a hacked up IP stack to communicate with it. But that will not do much good if it hasn't assigned an address at all.
  – kasperd
  12 mins ago
  

  
  
  
  

1

1

As others state 0.0.0.0 is not a routable address. Many pieces of software bind to 0.0.0.0 to allow that software to bind to whatever IP address is assigned to the network interface. This makes it easier—for example—to place the device on an DHCP setting and you just connect by getting the devices IP address and that’s that. My big question to you is why you are setting your machine’s IPv4 IP to the same range as the local IP to then running diagnostic software? Makes no sense. You should just get the device’s IP address and connect to that. That said, I have an idea. Posting an answer.
– JakeGould
3 hours ago

As others state 0.0.0.0 is not a routable address. Many pieces of software bind to 0.0.0.0 to allow that software to bind to whatever IP address is assigned to the network interface. This makes it easier—for example—to place the device on an DHCP setting and you just connect by getting the devices IP address and that’s that. My big question to you is why you are setting your machine’s IPv4 IP to the same range as the local IP to then running diagnostic software? Makes no sense. You should just get the device’s IP address and connect to that. That said, I have an idea. Posting an answer.
– JakeGould
3 hours ago

VX Works might not run DHCP and might therefore need a static IP address, something you would have to do internally on VX Works. In addition to that, any software or interfaces on your PC that talk to that VX Works machine would have to know that IP address. You would have to verify that all machines that need to talk to your VX Works machine know its IP address. It might auto-fill, or you might have to enter it manually. The all-0s address works as a default gateway, however, if your VX Works machine and your host it wants to talk to both have that gateway in common.
– Shankensteinium
2 hours ago

VX Works might not run DHCP and might therefore need a static IP address, something you would have to do internally on VX Works. In addition to that, any software or interfaces on your PC that talk to that VX Works machine would have to know that IP address. You would have to verify that all machines that need to talk to your VX Works machine know its IP address. It might auto-fill, or you might have to enter it manually. The all-0s address works as a default gateway, however, if your VX Works machine and your host it wants to talk to both have that gateway in common.
– Shankensteinium
2 hours ago

1

1

How were you able to determine that the device is using an IP address of 0.0.0.0? Did you use a piece of software that was able to communicate with the device over the network, or is there a basic Human-Machine Interface (HMI) on the device to show you the IP address? Also, to get the obvious question out of the way, have you tried turning it off and then on again to see if it picks up a sane address?
– Sam Skuce
1 hour ago

How were you able to determine that the device is using an IP address of 0.0.0.0? Did you use a piece of software that was able to communicate with the device over the network, or is there a basic Human-Machine Interface (HMI) on the device to show you the IP address? Also, to get the obvious question out of the way, have you tried turning it off and then on again to see if it picks up a sane address?
– Sam Skuce
1 hour ago

Literally assigning itself address 0.0.0.0 is not possible if it has a standards compliant IP stack. This leaves a couple of options: 1. It shows 0.0.0.0 as a way to signal that it failed to assign an IP address. 2. It has a broken IP stack which somehow managed to assign itself 0.0.0.0. I don't know enough about VxWorks to say which of the two is most likely. If it really has assigned address 0.0.0.0 you'd need a hacked up IP stack to communicate with it. But that will not do much good if it hasn't assigned an address at all.
– kasperd
12 mins ago

Literally assigning itself address 0.0.0.0 is not possible if it has a standards compliant IP stack. This leaves a couple of options: 1. It shows 0.0.0.0 as a way to signal that it failed to assign an IP address. 2. It has a broken IP stack which somehow managed to assign itself 0.0.0.0. I don't know enough about VxWorks to say which of the two is most likely. If it really has assigned address 0.0.0.0 you'd need a hacked up IP stack to communicate with it. But that will not do much good if it hasn't assigned an address at all.
– kasperd
12 mins ago

add a comment | 

4 Answers
4

active

oldest

votes

up vote
6
down vote

0.0.0.0 is not a valid IP address. RFC1700 (a) states that 0.0.0.0/8 (0.anything.anything.anything) is reserved as a source address only.

Normally you'll see systems and applications bind ports to 0.0.0.0 which means the port is accessible from any interface.

I'm not familiar with VxWrks but I would assume that there is a way to specify a local IP for interfacing with other computer devices.

WindRiver has a variety of manuals on how to configure the IP setup.

share|improve this answer

edited 3 hours ago

JakeGould

30.2k1092133

answered 4 hours ago

Hogstrom

818116

• 
  
  
  

  
  

  
  
  
  
  
  

  
  If 0.0.0.0 is only valid as a source, then how are ports bound to 0.0.0.0 accessible at all? I'm sure I'm missing a detail but this sounds like a contradiction.
  – Captain Man
  13 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  @CaptainMan: You're confusing an aspect of the sockets API with an aspect of the IP protocol. Binding 0.0.0.0 is an API-level thing to accept packets/connections addressed to any locally configured address. It does not involve packets addressed to 0.0.0.0 travelling anywhere at the protocol level.
  – R..
  3 mins ago
  

  
  
  
  

add a comment | 

up vote
4
down vote

The 0.0.0.0 IP address is fine but I would guess that something else has changed on the network that device is on to block zero-configuration networking traffic from allowing your diagnostic software to easily connect to that device.

As others, state in their answer 0.0.0.0 is a non-routable IP address that is often used by software to bind on any IP address on all networking interfaces on a device. This basically means:

“Hey I am a piece of software and will accept any connection made to any assigned IP address on the machine I am running on.”

So if the device uses DHCP and gets an assigned address of 1.2.3.4 then you can connect to that device at 1.2.3.4. And if that address changes to 5.6.7.8 the device will happily allow you to connect to it via 5.6.7.8.

So the 0.0.0.0 seems to be something you discovered but is not the cause of the problem. Rather, I’m my opinion, the issue you have is revealed when you state:

“I usually communicate with the system for troubleshooting purposes by setting my IPv4 IP to the same range as the local IP and then running diagnostic software.”

First, that seems odd. Why would you need to change your machine’s local IP address to connect to the VxWorks device? Shouldn’t you just connect directly to the IP address of the device?

Well, when you state this all I can think of is that the device—and the diagnostic software—might operate using some sort of zero-configuration networking setup. Meaning, the device broadcasts on the network, and the diagnostic software is designed to seek out these device broadcasts to help it connect to device without knowing the exact IP address.

This kind of self-configuring network connection stuff is a convenience until it becomes a headache.

My first guess is that you can connect to the device directly if you can determine what IP address it has assigned to it. And thinking even more, I bet that the reason you could connect to it in the past—but not now—might have to do with some networking change that has blocked the ports that device’s zero-configuration networking setup is broadcasting on. What port that may be? Unsure. But if zero-configuration traffic is not being routed through the network, then that is why you can’t connect to the device and the 0.0.0.0 IP address has nothing to do with it.

share|improve this answer

edited 58 mins ago

answered 2 hours ago

JakeGould

30.2k1092133

add a comment | 

up vote
3
down vote

0.0.0.0 is an unroutable address. There is no way you can route to it because "it doesn't really exist", or actually, "can exist in too many places".

It can have slightly different meanings depending if it's a host or a route.

As a route, which is not applicable in this case, it means "default route" which with no further instruction means either the default gateway, or "any of my routes", or similar to 127.0.0.1

As a host, then most notably in your case, it is either; as explained on Wikipedia:

The address a host claims as its own when it has not yet been assigned an address. Such as when sending the initial DHCPDISCOVER packet when using DHCP.

The address a host assigns to itself when address request via DHCP has failed, provided the host's IP stack supports this.

Assuming it usually uses DHCP, a couple of things to try, rather than a full reset - 'switch it off & on again' or just unplug the network, wait a minute, plug it back in. It might just ask for a new DHCP address.

Also, of course, make sure it can actually see its DHCP server.

share|improve this answer

edited 3 hours ago

JakeGould

30.2k1092133

answered 4 hours ago

Tetsujin

14.9k53159

add a comment | 

up vote
2
down vote

You can trick your PC into thinking that device has a real IP address. But you need the physical address, the thingy with 6 two-hexa-digits fields.
You do that by adding it to your arp resolution table. In Windows, open a cmd terminal and use arp.

arp -s <IP address> <physical address>

Of course, you need an IP address unique and in your network. Otherwise, the stack is going to reroute somewhere else. If you get to this point, you should be able to access the device. The network infrastructure will route according to the physical address.

In Linux is pretty much the same. Open a terminal, use arp.

It may not work!! Some devices answer only to their own IP. But I'm guessing it's not your case.

share|improve this answer

edited 1 hour ago

JakeGould

30.2k1092133

answered 1 hour ago

Gabe Mizuka

211

New contributor

Gabe Mizuka is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "3"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

Pablo Gonzalez is a new contributor. Be nice, and check out our Code of Conduct.

 

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1368916%2fhow-to-communicate-with-a-device-that-has-an-assigned-0-0-0-0-ip-address%23new-answer', 'question_page');

);

Post as a guest

Name Email

4 Answers
4

active

oldest

votes

4 Answers
4

active

oldest

votes

active

oldest

votes

active

oldest

votes

up vote
6
down vote

0.0.0.0 is not a valid IP address. RFC1700 (a) states that 0.0.0.0/8 (0.anything.anything.anything) is reserved as a source address only.

Normally you'll see systems and applications bind ports to 0.0.0.0 which means the port is accessible from any interface.

I'm not familiar with VxWrks but I would assume that there is a way to specify a local IP for interfacing with other computer devices.

WindRiver has a variety of manuals on how to configure the IP setup.

share|improve this answer

edited 3 hours ago

JakeGould

30.2k1092133

answered 4 hours ago

Hogstrom

818116

• 
  
  
  

  
  

  
  
  
  
  
  

  
  If 0.0.0.0 is only valid as a source, then how are ports bound to 0.0.0.0 accessible at all? I'm sure I'm missing a detail but this sounds like a contradiction.
  – Captain Man
  13 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  @CaptainMan: You're confusing an aspect of the sockets API with an aspect of the IP protocol. Binding 0.0.0.0 is an API-level thing to accept packets/connections addressed to any locally configured address. It does not involve packets addressed to 0.0.0.0 travelling anywhere at the protocol level.
  – R..
  3 mins ago
  

  
  
  
  

add a comment | 

up vote
6
down vote

0.0.0.0 is not a valid IP address. RFC1700 (a) states that 0.0.0.0/8 (0.anything.anything.anything) is reserved as a source address only.

Normally you'll see systems and applications bind ports to 0.0.0.0 which means the port is accessible from any interface.

I'm not familiar with VxWrks but I would assume that there is a way to specify a local IP for interfacing with other computer devices.

WindRiver has a variety of manuals on how to configure the IP setup.

share|improve this answer

edited 3 hours ago

JakeGould

30.2k1092133

answered 4 hours ago

Hogstrom

818116

• 
  
  
  

  
  

  
  
  
  
  
  

  
  If 0.0.0.0 is only valid as a source, then how are ports bound to 0.0.0.0 accessible at all? I'm sure I'm missing a detail but this sounds like a contradiction.
  – Captain Man
  13 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  @CaptainMan: You're confusing an aspect of the sockets API with an aspect of the IP protocol. Binding 0.0.0.0 is an API-level thing to accept packets/connections addressed to any locally configured address. It does not involve packets addressed to 0.0.0.0 travelling anywhere at the protocol level.
  – R..
  3 mins ago
  

  
  
  
  

add a comment | 

up vote
6
down vote

up vote
6
down vote

0.0.0.0 is not a valid IP address. RFC1700 (a) states that 0.0.0.0/8 (0.anything.anything.anything) is reserved as a source address only.

Normally you'll see systems and applications bind ports to 0.0.0.0 which means the port is accessible from any interface.

I'm not familiar with VxWrks but I would assume that there is a way to specify a local IP for interfacing with other computer devices.

WindRiver has a variety of manuals on how to configure the IP setup.

share|improve this answer

edited 3 hours ago

JakeGould

30.2k1092133

answered 4 hours ago

Hogstrom

818116

0.0.0.0 is not a valid IP address. RFC1700 (a) states that 0.0.0.0/8 (0.anything.anything.anything) is reserved as a source address only.

Normally you'll see systems and applications bind ports to 0.0.0.0 which means the port is accessible from any interface.

I'm not familiar with VxWrks but I would assume that there is a way to specify a local IP for interfacing with other computer devices.

WindRiver has a variety of manuals on how to configure the IP setup.

share|improve this answer

edited 3 hours ago

JakeGould

30.2k1092133

answered 4 hours ago

Hogstrom

818116

share|improve this answer

share|improve this answer

edited 3 hours ago

JakeGould

30.2k1092133

edited 3 hours ago

JakeGould

30.2k1092133

edited 3 hours ago

JakeGould

30.2k1092133

30.2k1092133

answered 4 hours ago

Hogstrom

818116

answered 4 hours ago

Hogstrom

818116

answered 4 hours ago

Hogstrom

818116

818116

• 
  
  
  

  
  

  
  
  
  
  
  

  
  If 0.0.0.0 is only valid as a source, then how are ports bound to 0.0.0.0 accessible at all? I'm sure I'm missing a detail but this sounds like a contradiction.
  – Captain Man
  13 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  @CaptainMan: You're confusing an aspect of the sockets API with an aspect of the IP protocol. Binding 0.0.0.0 is an API-level thing to accept packets/connections addressed to any locally configured address. It does not involve packets addressed to 0.0.0.0 travelling anywhere at the protocol level.
  – R..
  3 mins ago
  

  
  
  
  

add a comment | 

• 
  
  
  

  
  

  
  
  
  
  
  

  
  If 0.0.0.0 is only valid as a source, then how are ports bound to 0.0.0.0 accessible at all? I'm sure I'm missing a detail but this sounds like a contradiction.
  – Captain Man
  13 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  @CaptainMan: You're confusing an aspect of the sockets API with an aspect of the IP protocol. Binding 0.0.0.0 is an API-level thing to accept packets/connections addressed to any locally configured address. It does not involve packets addressed to 0.0.0.0 travelling anywhere at the protocol level.
  – R..
  3 mins ago
  

  
  
  
  

If 0.0.0.0 is only valid as a source, then how are ports bound to 0.0.0.0 accessible at all? I'm sure I'm missing a detail but this sounds like a contradiction.
– Captain Man
13 mins ago

If 0.0.0.0 is only valid as a source, then how are ports bound to 0.0.0.0 accessible at all? I'm sure I'm missing a detail but this sounds like a contradiction.
– Captain Man
13 mins ago

@CaptainMan: You're confusing an aspect of the sockets API with an aspect of the IP protocol. Binding 0.0.0.0 is an API-level thing to accept packets/connections addressed to any locally configured address. It does not involve packets addressed to 0.0.0.0 travelling anywhere at the protocol level.
– R..
3 mins ago

@CaptainMan: You're confusing an aspect of the sockets API with an aspect of the IP protocol. Binding 0.0.0.0 is an API-level thing to accept packets/connections addressed to any locally configured address. It does not involve packets addressed to 0.0.0.0 travelling anywhere at the protocol level.
– R..
3 mins ago

add a comment | 

up vote
4
down vote

The 0.0.0.0 IP address is fine but I would guess that something else has changed on the network that device is on to block zero-configuration networking traffic from allowing your diagnostic software to easily connect to that device.

As others, state in their answer 0.0.0.0 is a non-routable IP address that is often used by software to bind on any IP address on all networking interfaces on a device. This basically means:

“Hey I am a piece of software and will accept any connection made to any assigned IP address on the machine I am running on.”

So if the device uses DHCP and gets an assigned address of 1.2.3.4 then you can connect to that device at 1.2.3.4. And if that address changes to 5.6.7.8 the device will happily allow you to connect to it via 5.6.7.8.

So the 0.0.0.0 seems to be something you discovered but is not the cause of the problem. Rather, I’m my opinion, the issue you have is revealed when you state:

“I usually communicate with the system for troubleshooting purposes by setting my IPv4 IP to the same range as the local IP and then running diagnostic software.”

First, that seems odd. Why would you need to change your machine’s local IP address to connect to the VxWorks device? Shouldn’t you just connect directly to the IP address of the device?

Well, when you state this all I can think of is that the device—and the diagnostic software—might operate using some sort of zero-configuration networking setup. Meaning, the device broadcasts on the network, and the diagnostic software is designed to seek out these device broadcasts to help it connect to device without knowing the exact IP address.

This kind of self-configuring network connection stuff is a convenience until it becomes a headache.

My first guess is that you can connect to the device directly if you can determine what IP address it has assigned to it. And thinking even more, I bet that the reason you could connect to it in the past—but not now—might have to do with some networking change that has blocked the ports that device’s zero-configuration networking setup is broadcasting on. What port that may be? Unsure. But if zero-configuration traffic is not being routed through the network, then that is why you can’t connect to the device and the 0.0.0.0 IP address has nothing to do with it.

share|improve this answer

edited 58 mins ago

answered 2 hours ago

JakeGould

30.2k1092133

add a comment | 

up vote
4
down vote

The 0.0.0.0 IP address is fine but I would guess that something else has changed on the network that device is on to block zero-configuration networking traffic from allowing your diagnostic software to easily connect to that device.

As others, state in their answer 0.0.0.0 is a non-routable IP address that is often used by software to bind on any IP address on all networking interfaces on a device. This basically means:

“Hey I am a piece of software and will accept any connection made to any assigned IP address on the machine I am running on.”

So if the device uses DHCP and gets an assigned address of 1.2.3.4 then you can connect to that device at 1.2.3.4. And if that address changes to 5.6.7.8 the device will happily allow you to connect to it via 5.6.7.8.

So the 0.0.0.0 seems to be something you discovered but is not the cause of the problem. Rather, I’m my opinion, the issue you have is revealed when you state:

“I usually communicate with the system for troubleshooting purposes by setting my IPv4 IP to the same range as the local IP and then running diagnostic software.”

First, that seems odd. Why would you need to change your machine’s local IP address to connect to the VxWorks device? Shouldn’t you just connect directly to the IP address of the device?

Well, when you state this all I can think of is that the device—and the diagnostic software—might operate using some sort of zero-configuration networking setup. Meaning, the device broadcasts on the network, and the diagnostic software is designed to seek out these device broadcasts to help it connect to device without knowing the exact IP address.

This kind of self-configuring network connection stuff is a convenience until it becomes a headache.

My first guess is that you can connect to the device directly if you can determine what IP address it has assigned to it. And thinking even more, I bet that the reason you could connect to it in the past—but not now—might have to do with some networking change that has blocked the ports that device’s zero-configuration networking setup is broadcasting on. What port that may be? Unsure. But if zero-configuration traffic is not being routed through the network, then that is why you can’t connect to the device and the 0.0.0.0 IP address has nothing to do with it.

share|improve this answer

edited 58 mins ago

answered 2 hours ago

JakeGould

30.2k1092133

add a comment | 

up vote
4
down vote

up vote
4
down vote

The 0.0.0.0 IP address is fine but I would guess that something else has changed on the network that device is on to block zero-configuration networking traffic from allowing your diagnostic software to easily connect to that device.

As others, state in their answer 0.0.0.0 is a non-routable IP address that is often used by software to bind on any IP address on all networking interfaces on a device. This basically means:

“Hey I am a piece of software and will accept any connection made to any assigned IP address on the machine I am running on.”

So if the device uses DHCP and gets an assigned address of 1.2.3.4 then you can connect to that device at 1.2.3.4. And if that address changes to 5.6.7.8 the device will happily allow you to connect to it via 5.6.7.8.

So the 0.0.0.0 seems to be something you discovered but is not the cause of the problem. Rather, I’m my opinion, the issue you have is revealed when you state:

“I usually communicate with the system for troubleshooting purposes by setting my IPv4 IP to the same range as the local IP and then running diagnostic software.”

First, that seems odd. Why would you need to change your machine’s local IP address to connect to the VxWorks device? Shouldn’t you just connect directly to the IP address of the device?

Well, when you state this all I can think of is that the device—and the diagnostic software—might operate using some sort of zero-configuration networking setup. Meaning, the device broadcasts on the network, and the diagnostic software is designed to seek out these device broadcasts to help it connect to device without knowing the exact IP address.

This kind of self-configuring network connection stuff is a convenience until it becomes a headache.

My first guess is that you can connect to the device directly if you can determine what IP address it has assigned to it. And thinking even more, I bet that the reason you could connect to it in the past—but not now—might have to do with some networking change that has blocked the ports that device’s zero-configuration networking setup is broadcasting on. What port that may be? Unsure. But if zero-configuration traffic is not being routed through the network, then that is why you can’t connect to the device and the 0.0.0.0 IP address has nothing to do with it.

share|improve this answer

edited 58 mins ago

answered 2 hours ago

JakeGould

30.2k1092133

The 0.0.0.0 IP address is fine but I would guess that something else has changed on the network that device is on to block zero-configuration networking traffic from allowing your diagnostic software to easily connect to that device.

As others, state in their answer 0.0.0.0 is a non-routable IP address that is often used by software to bind on any IP address on all networking interfaces on a device. This basically means:

“Hey I am a piece of software and will accept any connection made to any assigned IP address on the machine I am running on.”

So if the device uses DHCP and gets an assigned address of 1.2.3.4 then you can connect to that device at 1.2.3.4. And if that address changes to 5.6.7.8 the device will happily allow you to connect to it via 5.6.7.8.

So the 0.0.0.0 seems to be something you discovered but is not the cause of the problem. Rather, I’m my opinion, the issue you have is revealed when you state:

“I usually communicate with the system for troubleshooting purposes by setting my IPv4 IP to the same range as the local IP and then running diagnostic software.”

First, that seems odd. Why would you need to change your machine’s local IP address to connect to the VxWorks device? Shouldn’t you just connect directly to the IP address of the device?

Well, when you state this all I can think of is that the device—and the diagnostic software—might operate using some sort of zero-configuration networking setup. Meaning, the device broadcasts on the network, and the diagnostic software is designed to seek out these device broadcasts to help it connect to device without knowing the exact IP address.

This kind of self-configuring network connection stuff is a convenience until it becomes a headache.

My first guess is that you can connect to the device directly if you can determine what IP address it has assigned to it. And thinking even more, I bet that the reason you could connect to it in the past—but not now—might have to do with some networking change that has blocked the ports that device’s zero-configuration networking setup is broadcasting on. What port that may be? Unsure. But if zero-configuration traffic is not being routed through the network, then that is why you can’t connect to the device and the 0.0.0.0 IP address has nothing to do with it.

share|improve this answer

edited 58 mins ago

answered 2 hours ago

JakeGould

30.2k1092133

share|improve this answer

share|improve this answer

edited 58 mins ago

edited 58 mins ago

edited 58 mins ago

answered 2 hours ago

JakeGould

30.2k1092133

answered 2 hours ago

JakeGould

30.2k1092133

answered 2 hours ago

JakeGould

30.2k1092133

30.2k1092133

add a comment | 

add a comment | 

up vote
3
down vote

0.0.0.0 is an unroutable address. There is no way you can route to it because "it doesn't really exist", or actually, "can exist in too many places".

It can have slightly different meanings depending if it's a host or a route.

As a route, which is not applicable in this case, it means "default route" which with no further instruction means either the default gateway, or "any of my routes", or similar to 127.0.0.1

As a host, then most notably in your case, it is either; as explained on Wikipedia:

The address a host claims as its own when it has not yet been assigned an address. Such as when sending the initial DHCPDISCOVER packet when using DHCP.

The address a host assigns to itself when address request via DHCP has failed, provided the host's IP stack supports this.

Assuming it usually uses DHCP, a couple of things to try, rather than a full reset - 'switch it off & on again' or just unplug the network, wait a minute, plug it back in. It might just ask for a new DHCP address.

Also, of course, make sure it can actually see its DHCP server.

share|improve this answer

edited 3 hours ago

JakeGould

30.2k1092133

answered 4 hours ago

Tetsujin

14.9k53159

add a comment | 

up vote
3
down vote

0.0.0.0 is an unroutable address. There is no way you can route to it because "it doesn't really exist", or actually, "can exist in too many places".

It can have slightly different meanings depending if it's a host or a route.

As a route, which is not applicable in this case, it means "default route" which with no further instruction means either the default gateway, or "any of my routes", or similar to 127.0.0.1

As a host, then most notably in your case, it is either; as explained on Wikipedia:

The address a host claims as its own when it has not yet been assigned an address. Such as when sending the initial DHCPDISCOVER packet when using DHCP.

The address a host assigns to itself when address request via DHCP has failed, provided the host's IP stack supports this.

Assuming it usually uses DHCP, a couple of things to try, rather than a full reset - 'switch it off & on again' or just unplug the network, wait a minute, plug it back in. It might just ask for a new DHCP address.

Also, of course, make sure it can actually see its DHCP server.

share|improve this answer

edited 3 hours ago

JakeGould

30.2k1092133

answered 4 hours ago

Tetsujin

14.9k53159

add a comment | 

up vote
3
down vote

up vote
3
down vote

0.0.0.0 is an unroutable address. There is no way you can route to it because "it doesn't really exist", or actually, "can exist in too many places".

It can have slightly different meanings depending if it's a host or a route.

As a route, which is not applicable in this case, it means "default route" which with no further instruction means either the default gateway, or "any of my routes", or similar to 127.0.0.1

As a host, then most notably in your case, it is either; as explained on Wikipedia:

The address a host claims as its own when it has not yet been assigned an address. Such as when sending the initial DHCPDISCOVER packet when using DHCP.

The address a host assigns to itself when address request via DHCP has failed, provided the host's IP stack supports this.

Assuming it usually uses DHCP, a couple of things to try, rather than a full reset - 'switch it off & on again' or just unplug the network, wait a minute, plug it back in. It might just ask for a new DHCP address.

Also, of course, make sure it can actually see its DHCP server.

share|improve this answer

edited 3 hours ago

JakeGould

30.2k1092133

answered 4 hours ago

Tetsujin

14.9k53159

0.0.0.0 is an unroutable address. There is no way you can route to it because "it doesn't really exist", or actually, "can exist in too many places".

It can have slightly different meanings depending if it's a host or a route.

As a route, which is not applicable in this case, it means "default route" which with no further instruction means either the default gateway, or "any of my routes", or similar to 127.0.0.1

As a host, then most notably in your case, it is either; as explained on Wikipedia:

The address a host claims as its own when it has not yet been assigned an address. Such as when sending the initial DHCPDISCOVER packet when using DHCP.

The address a host assigns to itself when address request via DHCP has failed, provided the host's IP stack supports this.

Assuming it usually uses DHCP, a couple of things to try, rather than a full reset - 'switch it off & on again' or just unplug the network, wait a minute, plug it back in. It might just ask for a new DHCP address.

Also, of course, make sure it can actually see its DHCP server.

share|improve this answer

edited 3 hours ago

JakeGould

30.2k1092133

answered 4 hours ago

Tetsujin

14.9k53159

share|improve this answer

share|improve this answer

edited 3 hours ago

JakeGould

30.2k1092133

edited 3 hours ago

JakeGould

30.2k1092133

edited 3 hours ago

JakeGould

30.2k1092133

30.2k1092133

answered 4 hours ago

Tetsujin

14.9k53159

answered 4 hours ago

Tetsujin

14.9k53159

answered 4 hours ago

Tetsujin

14.9k53159

14.9k53159

add a comment | 

add a comment | 

up vote
2
down vote

You can trick your PC into thinking that device has a real IP address. But you need the physical address, the thingy with 6 two-hexa-digits fields.
You do that by adding it to your arp resolution table. In Windows, open a cmd terminal and use arp.

arp -s <IP address> <physical address>

Of course, you need an IP address unique and in your network. Otherwise, the stack is going to reroute somewhere else. If you get to this point, you should be able to access the device. The network infrastructure will route according to the physical address.

In Linux is pretty much the same. Open a terminal, use arp.

It may not work!! Some devices answer only to their own IP. But I'm guessing it's not your case.

share|improve this answer

edited 1 hour ago

JakeGould

30.2k1092133

answered 1 hour ago

Gabe Mizuka

211

New contributor

Gabe Mizuka is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

up vote
2
down vote

You can trick your PC into thinking that device has a real IP address. But you need the physical address, the thingy with 6 two-hexa-digits fields.
You do that by adding it to your arp resolution table. In Windows, open a cmd terminal and use arp.

arp -s <IP address> <physical address>

Of course, you need an IP address unique and in your network. Otherwise, the stack is going to reroute somewhere else. If you get to this point, you should be able to access the device. The network infrastructure will route according to the physical address.

In Linux is pretty much the same. Open a terminal, use arp.

It may not work!! Some devices answer only to their own IP. But I'm guessing it's not your case.

share|improve this answer

edited 1 hour ago

JakeGould

30.2k1092133

answered 1 hour ago

Gabe Mizuka

211

New contributor

Gabe Mizuka is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

up vote
2
down vote

up vote
2
down vote

You can trick your PC into thinking that device has a real IP address. But you need the physical address, the thingy with 6 two-hexa-digits fields.
You do that by adding it to your arp resolution table. In Windows, open a cmd terminal and use arp.

arp -s <IP address> <physical address>

Of course, you need an IP address unique and in your network. Otherwise, the stack is going to reroute somewhere else. If you get to this point, you should be able to access the device. The network infrastructure will route according to the physical address.

In Linux is pretty much the same. Open a terminal, use arp.

It may not work!! Some devices answer only to their own IP. But I'm guessing it's not your case.

share|improve this answer

edited 1 hour ago

JakeGould

30.2k1092133

answered 1 hour ago

Gabe Mizuka

211

New contributor

Gabe Mizuka is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

You can trick your PC into thinking that device has a real IP address. But you need the physical address, the thingy with 6 two-hexa-digits fields.
You do that by adding it to your arp resolution table. In Windows, open a cmd terminal and use arp.

arp -s <IP address> <physical address>

Of course, you need an IP address unique and in your network. Otherwise, the stack is going to reroute somewhere else. If you get to this point, you should be able to access the device. The network infrastructure will route according to the physical address.

In Linux is pretty much the same. Open a terminal, use arp.

It may not work!! Some devices answer only to their own IP. But I'm guessing it's not your case.

share|improve this answer

edited 1 hour ago

JakeGould

30.2k1092133

answered 1 hour ago

Gabe Mizuka

211

New contributor

Gabe Mizuka is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this answer

share|improve this answer

edited 1 hour ago

JakeGould

30.2k1092133

edited 1 hour ago

JakeGould

30.2k1092133

edited 1 hour ago

JakeGould

30.2k1092133

30.2k1092133

answered 1 hour ago

Gabe Mizuka

211

New contributor

Gabe Mizuka is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

answered 1 hour ago

Gabe Mizuka

211

answered 1 hour ago

Gabe Mizuka

211

211

New contributor

Gabe Mizuka is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

New contributor

Gabe Mizuka is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

Gabe Mizuka is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

add a comment | 

Pablo Gonzalez is a new contributor. Be nice, and check out our Code of Conduct.

 

draft saved

draft discarded

Pablo Gonzalez is a new contributor. Be nice, and check out our Code of Conduct.

Pablo Gonzalez is a new contributor. Be nice, and check out our Code of Conduct.

Pablo Gonzalez is a new contributor. Be nice, and check out our Code of Conduct.

 

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1368916%2fhow-to-communicate-with-a-device-that-has-an-assigned-0-0-0-0-ip-address%23new-answer', 'question_page');

);

Post as a guest

Name Email

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

Name Email

Name

Email

Name Email

Name

Email