[ previous ] [ next ] [ threads ]
 
 From:  "Jesse D. Guardiani" <jesse at wingnet dot net>
 To:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: wierd static route problem
 Date:  Mon, 04 Apr 2005 01:00:36 -0400
On Sun, 03 Apr 2005 21:31:59 -0500, Chris Buechler wrote:

> On Apr 3, 2005 12:25 PM, Jesse D. Guardiani <jesse at wingnet dot net> wrote:
>> Hello,
>> 
>> I'm not much of a routing expert, so this could be
>> just a misconfiguration, but I can't figure it out,
>> so I hope someone can help.
>> 
>> I've got a OPT1 interface called WLAN. The subnet is
>> 192.168.89.0/24. On that subnet, I have a machine
>> (192.168.89.52) that needs an IP on a different
>> subnet (192.168.90.3/32) so I can perform a unique
>> outbound NAT mapping on daemons bound to that IP.
>> 
>> So I set up the following static route:
>> 
>>                <route>
>>                        <interface>opt1</interface>
>>                        <network>192.168.90.3/32</network>
>>                        <gateway>192.168.89.52</gateway>
>>                        <descr>matrixica.guardiani.us static
route</descr>
>>                </route>
>> 
> 
> Because 89.52 isn't actually routing to 90.3.

I don't know why you say that. I can ping 90.3 from the firewall,
and, like I said, if I add a static route for 90.3=gw89.52 on another
host then I can access anything at 90.3 perfectly fine.


> Couldn't you just use
> 89.52/32 for your NAT?  Not sure if that'd work or not.

No. I don't want everything on 89.52 hitting that outbound
NAT rule. Just stuff from a particular daemon. Thus the
need for another host IP.

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