[ previous ] [ next ] [ threads ]
 From:  "Josh McAllister" <josh at bluehornet dot com>
 To:  <jesse at wingnet dot net>, <m0n0wall at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall] Re: Public IP's on OPT
 Date:  Wed, 8 Dec 2004 08:16:19 -0800
You say ACT lights up when you ping out, but no replies. This may
indicate m0n0 is using the correct interface, but the wrong source IP.

This may be a silly question, but did you set OPT2 as the applicable
interface on your Outbound NAT entry?

Interface should be OPT2
Source should be LAN net
Destination should be the same host or subnet defined in the static
Target should be IP of OPT2

If you don't have the option to specify OPT interface, be sure you're
running latest version.

Josh McAllister

-----Original Message-----
From: news [mailto:news at sea dot gmane dot org] On Behalf Of Jesse Guardiani
Sent: Wednesday, December 08, 2004 8:30 AM
To: m0n0wall at lists dot m0n0 dot ch
Subject: [m0n0wall] Re: Public IP's on OPT

Kev Latimer wrote:

> Okay, I'm clearly doing something extremely stupid here.
> Traceroutes from both ends die at the router just before they get to
> subnet OPT2 lies on, ie at the m0n0 from my LAN side and at BT's
> just before it gets to ours from the other end.

I've been able to get traceroutes working from the internet to my OPT1
DMZ, but I have yet to be able to get traceroutes working from the LAN
the internet. But remember, traceroute not only uses ICMP, it also uses
UDP ports 33435 - 33524.

If anyone knows how to get traceroutes working from my LAN to the
while using advanced outbound NAT on the LAN, please let me know.

Jesse Guardiani, Systems Administrator
WingNET Internet Services,
P.O. Box 2605 // Cleveland, TN 37320-2605
423-559-LINK (v)  423-559-5145 (f)

To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch