I have a whole subnet, routing is what I need.
The computers also MUST have public IP addresses assigned to their
interfaces.
That will also screw me over when one of the subnets needs to talk to the
other subnet using public IPs....
http://faq.pfsense.com/index.php?action=artikel&cat=8&id=29&artlang=en
I also would have to get my ISP to change the routing to my network as the
routing currently is
xxx.xxx.xx1.001 modem
xxx.xxx.xx1.002 WAN
xxx.xxx.xx2.001 LAN
xxx.xxx.xx2.002 Computer
xxx.xxx.xx2.003 Computer
xxx.xxx.xx2.004 Computer
xxx.xxx.xx2.005 Computer
and the static route is xxx.xxx.xx2.xxx/26 xxx.xxx.xx1.002
so there are no "extra" IPs on the outside with which to do 1:1 to begin
with.
I just want simple, simple, simple, basic, routing!!!!!
Packet goes in one interface, firewall rules executed, packet goes out other
interface with destination unaltered...
=o(
From: Gary Buckmaster <[EMAIL PROTECTED]>
Reply-To: support@pfsense.com
To: support@pfsense.com
Subject: Re: [pfSense Support] Can't get basic routing to work.
Date: Fri, 04 Aug 2006 15:14:53 -0500
That's the whole point. Please read the documentation, and research 1:1
NAT to see why it will work for this purpose.
A. Jones wrote:
I can't set up a 1:1 as the wan interface is on a different subnet than my
lan interface....
From: "Tim Dickson" <[EMAIL PROTECTED]>
Reply-To: support@pfsense.com
To: <support@pfsense.com>
Subject: RE: [pfSense Support] Can't get basic routing to work.
Date: Fri, 4 Aug 2006 12:13:53 -0700
If bridging is not an option I would recommend setting 1:1 mappings for
each public address. It will work beautifully and will also allow you
to set up two separate networks.
-Tim
-----Original Message-----
From: A. Jones [mailto:[EMAIL PROTECTED]
Sent: Friday, August 04, 2006 7:29 AM
To: support@pfsense.com
Subject: [pfSense Support] Can't get basic routing to work.
I can't get the most basic of basic routing to work.
Here's my network setup....
Intel computer with 512 ram and new xeon.
Two Intel PWLA8492MT Dual port Gig-E Cards plus 2 onboard intel Gig-E
ports.
DSL Modem (Subnet A)
|
pfSense WAN (Subnet A)
|
PfSense LAN (Subnet B)
|
Computers with static public IPs (Subnet B)
Bridging is not an option as in the near future I want to cut subnet B
into two subnets and put each half subnet onto different interfaces.
I've tried going to advanced NAT and deleting all the rules while having
subnet B on LAN.
Deleting all the NAT rules while having subnet B on OPT1.
DISABLING THE FIREWALL!!! while having subnet B on LAN/OPT1.
I just can't get packets to get through.....
The joke is that it all works fine when I use the default rule created
for NAT.
But I don't want or need NAT for this setup.
I MUST have public, static IPs on the computers.... =o/
Please help!!!!
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's
FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_________________________________________________________________
Dont just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
