Read everything still no success

terminaladdict

Yeah I know, I know .. RTFM … I read everything can't figure it out.

lan = 192.168.1.253
wan = 202.37.230.93 (pppoe)
opt1 = 203.96.212.68


Firewall->NAT->Outbound
Int	Source		Source Port		Dest	Dest Port	NAT Add  NAT Port	Static Port
OPT1 	192.168.1.0/24	*			*	*		*	*			NO
WAN 	192.168.1.0/24	*			*	*		*	*			NO

Services->Load Balancer
Name					Servers/Gateways			Port		Monitor		Description
LoadBalancetoWAN		202.37.230.93/210.48.22.38
				203.96.212.1/203.96.212.1

Note:
In the wiki it says
"in the IP box type in the IP address of the gateway (this has to be one of the gateways configured at WAN or OPTx's)"

I read this to mean use the gateway IP rather than the interface IP .. was I right?


Firewall->Rules->LAN
Proto	Source		Port		Dest	Port		Gateway
*	LAN Net		*		*	*		*

So to my knowledge everything should be setup correctly.
so a quick test.


links -source http://www.whatismyip.com | grep -i TITLE\> | sed "s/<title>//I" | sed "s/<\/title>//I" | sed "s/WhatIsMyIP.com\ -\ //"<br />202.37.230.93<br /></pre><br />I would expect the ip to change every now and then .. but it has never changed<br /><br />Can some one point out what I am doing wrong?<br /><br />Thanks<br />Paul.<br /></title>

billm

Yeah, use the gateway pool you created as your gateway. In this case, in your rule, select the "LoadBalancetoWAN" gateway.

–Bill

terminaladdict

if I change firwall->rules->LAN
and change the gateway to LoadBalanceToWAN everything stops working.
completely :(

I can still do Diagnose->ping->ping IP via interface
but from inside my lan I can't do anything

I suspect it has something to do with this
LoadBalancetoWAN 202.37.230.93/210.48.22.38
203.96.212.1/203.96.212.1

perhaps it doesn't like doing this with a pppoe connection because the default route and int ip are the same?

billm

Hmmm, what version are you running? The load balance pools screen you copy/pasted looks wrong - looks old. I bet you're running into bugs that have since been fixed. Run "cvs_sync.sh releng_1" from the shell to update to the latest cvs code if you're on a full install or wait until 1.0RC1 releases (hopefully it'll be in the next day or two - already versioned in CVS).

–Bill

terminaladdict

running beta2 on DOM

will the config be seamless?
can I install on another DOM … boot, then load my saved config
I assume the config defines interfaces rules, ipsec settings, static routes .. everything

hoba

Restoring config should work but I recommend to recreate the loadbalancing pool if it doesn't.

billm

@terminaladdict:

running beta2 on DOM

will the config be seamless?
can I install on another DOM … boot, then load my saved config
I assume the config defines interfaces rules, ipsec settings, static routes .. everything

no idea what DOM is, but you can restore your config.xml from beta2 to a beta4 or RC1 box. You will want to remove the load balancer config and recreate it. There were MAJOR load balancer fixes after beta2
Beta 3 summary: http://hitormiss.ucsecurity.com/index.php/2006/04/17/pfsense-10beta-3-is-out/
Beta 4 changelog (on vacation, I didn't write a summary): http://cvstrac.pfsense.com/rptview?rn=24
RC1 changelog (not yet released): http://cvstrac.pfsense.com/rptview?rn=25

–Bill