Adding loopback address

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a scenario where I need to loop back the 2.0.0.0 subnet. I figured
doing something like:

route add 2.0.0.0 mask 255.0.0.0 127.0.0.1 metric 1 if 1

would do the trick, but it keeps coming back to me with:
The route addition failed: The parameter is incorrect

Anyone know why this is happening and how to get around it?

Thanks,


Eric Sambell
 
Explain why you believe you need to do this in the first place,...that is
probably the real "root" of the issue.
 
What I'm trying to do is emulate a piece of hardware that can only have an IP
address on the 2.0.0.0 subnet. The concept being have the control program
that's provided by the manufacturer running on the same PC as an emulator for
the piece of hardware. As the emulator is something I'm working on, the
loopback can come back to any address, it just has to appear to the control
program that it is on the 2.0.0.0 subnet.

Thanks,

Eric Sambell

Phillip Windell said:
Explain why you believe you need to do this in the first place,...that is
probably the real "root" of the issue.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


Eric Sambell said:
I have a scenario where I need to loop back the 2.0.0.0 subnet. I figured
doing something like:

route add 2.0.0.0 mask 255.0.0.0 127.0.0.1 metric 1 if 1

would do the trick, but it keeps coming back to me with:
The route addition failed: The parameter is incorrect

Anyone know why this is happening and how to get around it?

Thanks,


Eric Sambell
Click to expand...
Click to expand...
 
Add the Microsoft Loopback Adapter. It is just a "software" adapter but you
install it the same as you would install a pysical adapter's drives.

Once it is added assign the IP# and mask to it from the 2.* network.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


Eric Sambell said:
What I'm trying to do is emulate a piece of hardware that can only have an IP
address on the 2.0.0.0 subnet. The concept being have the control program
that's provided by the manufacturer running on the same PC as an emulator for
the piece of hardware. As the emulator is something I'm working on, the
loopback can come back to any address, it just has to appear to the control
program that it is on the 2.0.0.0 subnet.

Thanks,

Eric Sambell

Phillip Windell said:
Explain why you believe you need to do this in the first place,...that is
probably the real "root" of the issue.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


Eric Sambell said:
I have a scenario where I need to loop back the 2.0.0.0 subnet. I figured
doing something like:

route add 2.0.0.0 mask 255.0.0.0 127.0.0.1 metric 1 if 1

would do the trick, but it keeps coming back to me with:
The route addition failed: The parameter is incorrect

Anyone know why this is happening and how to get around it?

Thanks,


Eric Sambell
Click to expand...
Click to expand...
Click to expand...
 
Sweet, thanks very much, I think this will work out.

Phillip Windell said:
Add the Microsoft Loopback Adapter. It is just a "software" adapter but you
install it the same as you would install a pysical adapter's drives.

Once it is added assign the IP# and mask to it from the 2.* network.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


Eric Sambell said:
What I'm trying to do is emulate a piece of hardware that can only have an IP
address on the 2.0.0.0 subnet. The concept being have the control program
that's provided by the manufacturer running on the same PC as an emulator for
the piece of hardware. As the emulator is something I'm working on, the
loopback can come back to any address, it just has to appear to the control
program that it is on the 2.0.0.0 subnet.

Thanks,

Eric Sambell

Phillip Windell said:
Explain why you believe you need to do this in the first place,...that is
probably the real "root" of the issue.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


I have a scenario where I need to loop back the 2.0.0.0 subnet. I figured
doing something like:

route add 2.0.0.0 mask 255.0.0.0 127.0.0.1 metric 1 if 1

would do the trick, but it keeps coming back to me with:
The route addition failed: The parameter is incorrect

Anyone know why this is happening and how to get around it?

Thanks,


Eric Sambell
Click to expand...
Click to expand...
Click to expand...
 
Back
Top