Re: How to force looparound and not loopback?

I don't see how can that be. The TCP/IP stack won't consider
_any_ network adapter. In order to play tricks with NAT you
need to have your data go out a network adapter first.

--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@xxxxxxxx
MVP VC FAQ: http://vcfaq.mvps.org
=====================================

"Ali" <abdulrazaq@xxxxxxxxx> wrote in message
news:1174573253.189196.221770@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Mar 21, 5:08 am, "Alexander Nickolov" <agnicko...@xxxxxxxx> wrote:
That's not possible - routing is not even involved. The
TCP/IP stack detects that the target address is local and
automatically uses the loopback adapter. It never needs
to check the routing table.

--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnicko...@xxxxxxxx
MVP VC FAQ:http://vcfaq.mvps.org
=====================================

<mar...@xxxxxxxxxxx> wrote in message

news:1174350691.771684.226390@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx





Suppose you have two network cards on the same PC (with Vista)
and connect them to a Linksys router. The connections are set up
with "Obtain an IP address automatically" and the router assigns
192.168.1.100 and 192.168.1.101

I want to test a UDP code that sends to one of these IP addresses
through the router.

However, winsock and the table route seem to force a loopback,
i.e. they know that the destination IP address is on the same PC so
the router is never reached.

I want to force a looparound, where datagrams destined for IP2 go out
on IP1 card to the router, and back on card IP2, obviously making sure
they do not go out again on IP1 in a loop but to the receiving code.

Is making changes to the route table the only solution? How?

But what about virtual network? IIRC the NAT can e the possible
solution.

ali



.

Relevant Pages
Loading