G R E A T, many thanks - this works out just like pointed out in this forum!!!
On Sat, Jan 31, 2009 at 11:22 AM, Ermal Luçi <[email protected]> wrote: > look at this http://forum.pfsense.org/index.php/topic,13847.0.html > > On Sat, Jan 31, 2009 at 10:37 AM, Michel Servaes <[email protected]> wrote: > > Hi, > > > > > > I've upgraded to the 1.2.3 version on one end, and have a monowall at my > > end... whenever I ping a host over the tunnel, they reply... > > But doing anything else (http, rdp, ...) it simply does nothing at all ! > > (eventually, I got a timeout) - but the tunnel is up, and I can ping. > > > > My rules on the firewall are on both ends setup to allow all traffic > (since > > both networks are trusted to each other) - any ideas ? > > > > > > The issue why I upgraded to 1.2.3 is somewhat funny... I had a 1.2.1rc1, > > that I wanted to upgrade to 1.2.2 remotely... but it never came up again > (so > > I drove over to the company, to do a manual upgrade, but since I had no > > internet at the office, and only my latest revision to test on my > home-box, > > I decided to put it on the production server) > > > > > > In my effort in trying to solve this, I removed the tunnel on both sides, > > deleted the rules - and recreated them... on the pfsense I got this when > > making a small change to the new tunnel : > > > > Warning: unlink(/tmp/spd.conf.reload.1233394121.y9DXI8): No such file or > > directory in /etc/inc/vpn.inc on line 1193 > > > > kind regards, > > Michel > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > Commercial support available - https://portal.pfsense.org > > > > > > > > -- > Ermal > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > Commercial support available - https://portal.pfsense.org > >
