This is not something you normally do. If you want the application to be listening on 192.168.0.10:2000, then bind your program to that IP+port tupple. Unconditionally forwarding like you propose buys you nothing and will slow down the flow of data as it has to go through another userland application (ie: your software proxy.)

Most OSes provide a NAT function (such as with PF under BSD or Netfilter under Linux), but here again, why waste kernel resources translating IPs instead of just putting your application on the IP you intend to listen for connections on? RFC1918 and IPv6 space is abundant, so it's a matter of needing a 2nd address, just assign one and bind to that.

If you still think you need to do what you propose, maybe you can elaborate on what you're attempting to do? This feels like a case of trying to fit a square-peg in a round-hole.

Now that I've (hopefully) talked you out of writing, or even using, a software proxy to talk to your own host, I'll give you some hints that socket code can get tricky. You need to worry about what I/O blocking mode you use, how to deal with partial reads and writes, what to do when one side performs a half-close (send EOF on a socket stream,) and similar complexities.

Writing good socket-code generally requires a decent understanding of how the protocols work, plus programmatic concepts like buffers, polling, plus some design decisions when dealing with a bi-directional socket on each end. That last part could mean you juggle 4 I/O flows (in+out from the sender, and in+out to the receiver,) or that you go to a forked or threaded model where each process handles the flow in a single direction across the proxy's pipe.

If you want to get more serious about socket code, I can recommend the UNPv1 book as an excellent place to start. The examples it has are in C, although the concepts are very usable in Perl (though reading the book's code examples really requires at least a basic understanding of C.)

In reply to Re^2: Networking with IO::Socket by Apero
in thread Networking with IO::Socket by TheVend

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.