Put that code inside an actual script somewhere and then call it. Not as nice as a shellcmd, but shellcmd wasn't really designed to handle those sorts of commands.
thank you very much, I think it's working now.
I did the Load Balance and it seems OK.
Doubt: it's necessary a rule to interface receive the pings request, isn't? Otherwise, the gateway status will appear offline.
Well, I made a rule that allows them (pings). Because I had a problem when I took the ethernet cable away. The gateway was offline even the interface (OPTx) status online.
not sure why it wouldn't. do you have vlans in place or anything like that?
i have my pfsense 2.1_x64 on esxi 5 and it runs flawlessly. my setup is slightly different in that my vdsl modem is physically connected to my switch and is vlan'd from there which frees up a nic on the esxi server as it doesn't have a dedicated wan. the virtual switch on esxi (which the nic is allocated to) is set to allow all vlans and the vlan's are set up in pfsense (rather than pfsense just have wan, lan and the vlans set on the virtual switch)
pppoe is set in pfsense so it definitely works a all i've done in effect with the above is change where the physical connection for the modem resides
usb_modeswitch is an executable. You may have to issue a rehash command if you've just installed it so FreeBSD knows where it is. However it isn't the complete solution that it is under Linux. The FreeBSD port is basically a utility for sending the USB codes to your modem. It doesn't load up drivers or get called automatically when the modem is inserted.
on the switch:
add all the same VLANs
make sure the port that goes to pfSense has a T (for tagged) for all those VLANs
then on each other port, have a U (for untagged) for one VLAN and set the PVID to the same
Setting it up with ssh and cron would be more secure and require no hacking. Have the firewall push its own config off to a box using an account that does ssh key only auth and upload the config to a write-only directory on the backup system. ACB isn't required, it just makes things easy/automatic.
If you have a router between your pfSense and the Internet you MIGHT need to configure a port forward in the router and appropriate firewall rule so the access attempt gets past the router. Then you need to configure a port forward on pfSense. A search on the pfsense forums for phrase "port forward" posted in the last 30 days should turn up at least entry with some more detail.
