Nice. Modified PPPoE router to 192.168.3.0/24 NAT OPT1 to allow ALL rule OPT1 anything... I did this all remotely but appears to have fixed routing to the 3.x from 2.x trace route shows... start > 192.168.3.152 > 192.168.3.101
Problem... The PPPoE router is an IPCop box using IPSec to connect to another (192.168.1.0/24) Updated the VPN source/destinations fr 192.168.2.0/24 to x.3.0/24 @ both ends Can't get to the other end. Any ideas? On 10/4/07, Tim Nelson <[EMAIL PROTECTED]> wrote: > You've got the same subnet on both your LAN and OPT1 interfaces... You'll > need to change one of them to something besides 192.168.2.x/24 for routing to > work properly. > > Tim Nelson > Systems/Network Engineer > Rockbochs Inc. > (218)727-4332 > > ----- Original Message ----- > From: "MyStiC" <[EMAIL PROTECTED]> > To: support@pfsense.com > Sent: Thursday, October 4, 2007 11:09:23 AM (GMT-0600) America/Chicago > Subject: [pfSense Support] NAT or rule? > > WAN = DHCP (ISP provided) > LAN = 192.168.2.150, DHCP server 192.168.2.0/24 > OPT1 = DHCP IP192.68.2.152/24 GTWY192.168.2.101 > OPT1 connects to separate router (PPPoE WAN) which handles VPN connections > > When I follow the outbound NAT steps for load balancing the WAN & > OPT1, I cannot ping OPT1's gateway or get any other traffic there > either. How can I allow traffic coming from/to OPT1 to LAN? > > --------------------------------------------------------------------- > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
