[ previous ] [ next ] [ threads ]
 From:  Dmitry Sorokin <dimon at intellinet dot ca>
 To:  m0n0wall dash dev at lists dot m0n0 dot ch
 Cc:  Chris Dickens <chris at object dash zone dot net>
 Subject:  Re: [m0n0wall-dev] Wanted Dead - NAT Bouncing Bug : Bounty increased!!
 Date:  Wed, 27 Oct 2004 15:18:35 -0600
Should it only bounce TCP or UDP as well? If UDP, then none of the bounce 
utilities support that for now.

Quoting Chris Dickens <chris at object dash zone dot net>:

> Previously I have written regarding the problems with m0n0 being unable to
> bounce a connection from the LAN back onto the internal network when a
> machine attempts to connect to another server using it's externally situated
> IP address through m0n0wall.  I have confirmed that the majority of other
> products provide this functionality including SonicWall, Astaro, Smoothwall,
> Symantec, and more.  The details of this shortcoming are detailed in the
> following FAQ:
> http://m0n0.ch/wall/docbook/faq-lannat.html
> I previously offered a $100 US bounty for the fix of this problem with
> m0n0wall.  I have decided to up the bounty to $200 US.  If anyone can
> provide the necessary updates to Manuel and have them integrated into the
> next full release of m0n0wall, I will either mail a check drawn on my
> personal account, or send the funds via PayPal to the designated head-hunter
> by way of Manuel's word as to who provided the fix.  An additional $50 US
> will be sent to Manuel as well as a donation to the overall cause of the
> project.  (If Manuel fixes the problem, he gets all $250. :) )
> Just to be 100% clear, the method used in order to facilitate this fix
> cannot involve a form of proxy or DNS server which requires additional
> configuration - it must allow access from any internal server on any port to
> any other server on any port internally at any time with no additional
> configuration other than the standard NAT and firewall rules.
> Thanks!
> --Chris
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash dev dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash dev dash help at lists dot m0n0 dot ch
Spam detection software, running on the system "intellinet.ca", has
identified this incoming email as possible spam.  The original message
has been attached to this so you can view it (if it isn't spam) or block
similar future email.  If you have any questions, see
the administrator of that system for details.

Content preview:  The Votes are in on the Best Web Hosting Service
  URI:../aug/0804.css This is a WebProNews Sponsor Update Please see the
  bottom of this mailing for subscription information. [...] 

Content analysis details:   (7.5 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
 0.3 NO_REAL_NAME           From: does not include a real name
 0.1 EXCUSE_3               BODY: Claims you can be removed from the list
 0.5 EXCUSE_REMOVE          BODY: Talks about how to be removed from mailings
 0.1 HTML_FONTCOLOR_UNKNOWN BODY: HTML font color is unknown to us
 0.1 HTML_LINK_CLICK_HERE   BODY: HTML link text says "click here"
 0.1 HTML_60_70             BODY: Message is 60% to 70% HTML
 0.0 HTML_MESSAGE           BODY: HTML included in message
 0.4 HTML_IMAGE_RATIO_08    BODY: HTML has a low ratio of text to image area
 0.5 HTML_LINK_CLICK_CAPS   BODY: HTML link text says "CLICK"
 0.1 MIME_HTML_ONLY         BODY: Message only has text/html MIME parts
 0.5 HTML_LINK_PUSH_HERE    BODY: HTML link text says "push here" or similar
 0.4 HTML_FONT_INVISIBLE    BODY: HTML font color is same as background
 0.2 NORMAL_HTTP_TO_IP      URI: Uses a dotted-decimal IP address in URL
 1.8 DCC_CHECK              Listed in DCC (http://rhyolite.com/anti-spam/dcc/)
 0.0 CLICK_BELOW            Asks you to click below
 0.8 MSGID_FROM_MTA_HEADER  Message-Id was added by a relay
 1.6 FORGED_MUA_OUTLOOK     Forged mail pretending to be from MS Outlook