On Tue, Mar 30, 2010 at 5:38 PM, Evgeny Yurchenko <[email protected]>wrote:
> Danny wrote: > > > > On Tue, Mar 30, 2010 at 4:56 PM, Evgeny Yurchenko <[email protected]>wrote: > >> Danny wrote: >> >>> I cannot do that, because the main infrastructured is already built-in. >>> >>> I mean 192.168.212.0/24 <http://192.168.212.0/24> and 172.24.24.0/24 < >>> http://172.24.24.0/24>, both got ROUTER GW as default router "today". >>> >>> >>> I have installed 2xPfsense, plugged in this way >>> OPT1 in 192.168.212.0/24 <http://192.168.212.0/24> >>> OPT2 in 172.24.24.0/24 <http://172.24.24.0/24> >>> >>> We have leased a WAN Link, (pfSense WAN interface) >>> >>> "Tomorrow" we have to change the default gateway for both networks, to >>> point to pfsense, LoadBalacing with failover, to continue using former link, >>> and in case the ROUTER GW is down, use the WAN of pfSense as an alternative >>> >>> ROUTER GW, and inet (172.16.0.2), is managed by third parties, that愀 the >>> reason I cannot plug directly to pfsense >>> >>> Thank you >>> Regards >>> >>> >>> >>> On Tue, Mar 30, 2010 at 4:14 PM, Evgeny Yurchenko >>> <[email protected]<mailto: >>> [email protected]>> wrote: >>> >>> Evgeny Yurchenko wrote: >>> >>> Danny wrote: >>> >>> Hi, >>> >>> I'm trying to setup this: >>> >>> >>> ____ >>> ___ >>> ( ) >>> ( ) >>> ( inet ) >>> ( inet ) >>> (____) >>> (____) >>> |22.22.22.4 >>> |172.16.0.2 >>> | | >>> | | >>> |22.22.22.1(WAN) >>> |172.16.0.1 >>> ------------- >>> 172.24.24.12_______|______ >>> ------|pfSense x2 |-----------------------------------| >>> ROUTER GW | >>> LAN |___________|172.24.24.20 (OPT2) | >>> |____________| >>> | | >>> | 192.168.212.20 >>> |192.168.212.254(OPT1) | | >>> | |172.24.24.0/24 >>> <http://172.24.24.0/24> <http://172.24.24.0/24> | >>> >>> | | >>> | | >>> |_______________________________________________| >>> | >>> | 192.168.212.0/24 >>> <http://192.168.212.0/24> <http://192.168.212.0/24> >>> >>> | >>> Requirements: >>> >>> Connection should alway go via ROUTER GW, but >>> default gateway for all machines in both networks should >>> be pfsense (OPT1 and OPT2) >>> If 172.24.24.12 is down conection should go via >>> pfSense WAN interface >>> If 192.168.212.20 is down conection should go via >>> pfSense WAN interface >>> >>> Interface LAN not used because Failover gateway cannot be >>> specified at pfSense 1.2.3 in LAN Interface >>> >>> I惴 stucked. I followed MutiWAN tutorial, but when I >>> >>> create Failover using gateways to monitor, I see the same >>> address for WAN an OPT1 in the pool... >>> >>> Any ideas >>> Thanks >>> >>> >>> -- dpc >>> >>> >>> I am afraid you have wrong understanding of MultiWAN. >>> >>> I think you should be doing the next: >>> >>> >>> ( ) ( ) >>> ( inet ) ( inet ) >>> (____) (____) >>> |22.22.22.4 |172.16.0.2 >>> | | >>> | | >>> |22.22.22.1(WAN) |172.16.0.1(OPT1) >>> | ------------- | >>> -----------|pfSense x2 |------- >>> |___________| >>> 172.24.24.20 (LAN) | |192.168.212.254(OPT2) >>> >>> | | >>> | | >>> 172.24.24.0/24 <http://172.24.24.0/24> ------------ | >>> 192.168.212.0/24 <http://192.168.212.0/24> >>> ----------------- >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> <mailto:[email protected]> >>> >>> For additional commands, e-mail: [email protected] >>> <mailto:[email protected]> >>> >>> >>> Commercial support available - https://portal.pfsense.org >>> >>> >>> >>> >>> -- >>> dpc >>> >> Please do not toppost. >> What you are trying to do is failover at PCs level THEY have to switch to >> different gateway, THEY somehow have to become aware that primary Internet >> link is down, you are taking away this from pfSense box, i.e. pfSense can >> not change default gateway on your workstations. >> With pfSense you still can use your ROUTER GW but not in scenario you >> described. Connect both lan segments to pfsense and have two links from >> pfSense upstream - one Internet and one to ROUTER GW. >> >> Evgeny. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> Commercial support available - https://portal.pfsense.org >> >> > I´m sorry about topposting (gmail is almost perfect ;-) > > That´s what I want. To have redundant internet connection, but > automatically managed. If everybody in his respective lan segment point to > pfsense as default gateway, and pfsense can route traffic depending of > availability of the WAN links, but in this case WAN links are in the oposite > segments > > Does this make sense? > > Regards > > > > -- > dpc > > Ok. I think you should build something like this: > ( ) ( ) > ( inet ) ( inet ) > (____) (____) > |22.22.22.4 |172.16.0.2 > | | > | | > |22.22.22.1(WAN) |172.16.0.1 > | ------------ OPT1 ------------- > ---|pfSense x2 |------- | ROUTER GW | > |___________| ------------- > > 172.24.24.20 (LAN) | |192.168.212.254(OPT2) > | | > 172.24.24.0/24 ---- | 192.168.212.0/24 > ----------------- > > Evgeny. > --------------------------------------------------------------------- To > unsubscribe, e-mail: [email protected] For additional > commands, e-mail: [email protected] Commercial support available - > https://portal.pfsense.org > Ok. I´ve been thinking about an example Consider we have to buildings One building (Building A) has got an internet conection connected to ROUTER GW and the other building (building B) is conected by a Point to Point with building A. Both buildings reach internet via ROUTER GW. One day in Building B a pfsense is plugged to corporate networks and a WAN link is attached to WAN interface. Everybody has to use the link of building A because the bandwidth is higher, but in case Building A is down, connection has to switch to Buidling B. I cannot make the load balance failover, because is not administered by me, and there is no possibility to use OSFP between router and pfsense Both networks are spread over the both buildings Thanks Regards -- dpc
