Comments on: HOW TO : Microsoft Windows – Routing to /dev/null

By: HOW TO : Route traffic to loopback interface in Linux | Kudithipudi.Org

HOW TO : Route traffic to loopback interface in Linux | Kudithipudi.Org — Tue, 27 Mar 2012 04:02:15 +0000

[...] in 2009 (last decade!! ), I wrote a blog post on how you can trick windows to route traffic destined to a particular IP address to a black-hole. [...]

By: AlexeyAA

AlexeyAA — Wed, 03 Aug 2011 13:07:05 +0000

Upss! With the MS Loopback I bumped into an issue today. On Windows 2000 Server it was revealed that you must not disable “File and Printer Sharing for MS Network” option for this adapter on Active Directory Domain Controller, otherwise you will not be able to configure Group Policy Objects on this server. There is the hint from Microsoft about: http://support.microsoft.com/kb/257435/en-us

By: Vinay

Vinay — Mon, 25 Jul 2011 02:03:31 +0000

Thx for sharing this Alexey.

By: AexeyAA

AexeyAA — Sat, 23 Jul 2011 23:10:52 +0000

better to see once than hear ten times
http://www.youtube.com/watch?v=uIKOQHbMXOo
loopback returns packets back where they came from, so they die in the system

By: AexeyAA

AexeyAA — Sat, 23 Jul 2011 22:16:59 +0000

windows dn’t permit forwarding packets to 127.0.0.1 but you can add/create loopback device in a system, assing stupid ip address to it and create any route to forward packets to it. So, you should open control panel/add hardware/select “add a new hardware”/select “install the hardware manualy”/select “network adapters”/select Microsoft-Microsoft Loopback Adapter. After that you will see a knew network adapter in Network Connections. In its properties you are better to disable all options besides tcp/ip-ip address, which you may assing as 1.0.0.1 255.255.255.252,
for example (and no gateway, of course). Now you may ban google dns like that
route -p add 8.8.8.8 mask 255.255.255.255 1.0.0.1

By: Vinay

Vinay — Thu, 14 Jul 2011 16:09:24 +0000

Juha – Thx for sharing your experience..

- V

By: Juha Jurvanen

Juha Jurvanen — Tue, 12 Jul 2011 11:30:42 +0000

Good article.
What I wanted to achiev was actually to block an incoming IP from an external source and I didn’ät want to do via firewall rules for variuos reasons

I didn’t actually get it to work exactly the way you descripbed it. If I used an unusued IP address the server actually still would route trafic to the target.

So , here’s what I did instead. I used the local machines IP address instead i.e.
if the server had local IP address 192.168.0.2 and the defalut GW was 192.168.0.1 I just used route add {unwanted IP address] 192.168.0.2
instead of having it use 192.168.0.1 as default. Of course the IP address one would point it to can’t have routing enabled..

but still, you did point me in the right direction .
Oh, system was a 2008 server so there might be a difference in windows releases also

Cheers /
Juha Jurvanen
CTO Red Cloud IT

By: Daniel Harrell

Daniel Harrell — Mon, 07 Feb 2011 14:41:36 +0000

Thank you for posting this. Goog content. I bookmarked your blog. Thanks again.

By: Jesse Phaneuf

Jesse Phaneuf — Mon, 23 Aug 2010 06:52:50 +0000

flash

By: David Webster

David Webster — Sat, 07 Nov 2009 20:19:54 +0000

Sometimes “smart” gets trumped by “urgency”. I enjoyed reading your post.