I have been trying to get my Bering setup with 1.98 ipsec and have been running into 
problems.  The first config I went for was the W2K road wariors but could never get 
that to work (shared secret)  I was able to get SSH Sentinal to work but I would 
rather use W2K built in.  I am also working to get Admit One client for Pocket PC to 
work.  My CEO has an Ipaq I'm trying to VPN in.  There are only two options for 
clients other than the extremly limiting built in VPN that only works in MS land, 
Admit one and Movian.
 
Any help you might offer on how you got yours up, especialy your script for W2K would 
be great!
I used the Bering UG as my bible and Lynn's guid, pluss many documents I found 
searching the Freeswan site.
Thanks!
 
Richard Amerman

        -----Original Message----- 
        From: Marco Cintolesi [mailto:[EMAIL PROTECTED]] 
        Sent: Thu 7/18/2002 6:14 AM 
        To: leaf 
        Cc: 
        Subject: Re: [leaf-user] problem starting ipsec with bering rc3 (RESOLVED)
        
        

        Ok , problem resolved......
        
        It works perfectly with the new packages (bering update, ipsec version 1.98)
        
        The problem is in the config of the interface eth0 (external network).......
        under interface config i never set the brodcast address and it seems that
        IPsec wants to know the broadcast......without he gives you the message
        "unable to dermine address of eth0".
        
        Now i have a perfectly running tunnel with our "roadrunners" with windows 2k
        on laptops computers.
        
        I also have a script (vbs)  that launch the vpn on the win2k machine,
        without have to set it manually (and without have to know the DYNAMIC ip of
        the roadrunner machine as on the config page in the bering User Guide [hey
        Jacques, if u want to add some "right stuff" about win2k config write me]).
        
        If anyone like to see (and use) the script i can also post it to the list
        (only a few kbytes).
        With this solution i (an maybe you) can run a GREAT vpn with freeswan and
        win2k machines.
        
        Thanks all for the support. And MANY thanks to the Open Source Software !!!!
        ;-)
        Bye
        Marco
        
        
        
        ----- Original Message -----
        From: "Ronny Aasen" <[EMAIL PROTECTED]>
        To: "leaf" <[EMAIL PROTECTED]>
        Cc: "Chad Carr" <[EMAIL PROTECTED]>
        Sent: Wednesday, July 17, 2002 3:35 PM
        Subject: Re: [leaf-user] problem starting ipsec with bering rc3
        
        
        > On Wed, 2002-07-17 at 15:04, Chad Carr wrote:
        > > On 17 Jul 2002 08:44:39 +0200
        > > "Ronny Aasen" <[EMAIL PROTECTED]> wrote:
        > >
        > > > On Tue, 2002-07-16 at 14:24, Marco Cintolesi wrote:
        > > > > When i try to start ipsec (/etc/init.d/ipsec start) i have the
        error:
        > > > >
        > > > > Unable to determine address of 'eth0', then ipsec0 interface dont go
        > > > > up.
        > > > >
        > > > > I tried with:
        > > > >
        > > > > interfaces="%defaultroute"
        > > > > and
        > > > > interfaces="ipsec0=eth0"
        > > > >
        > > > > but no luck......
        > > > > i have mawk.lrp succesfully installed with ipsec.lrp and module
        > > > > ipsec.o ok(with insmod i can load it without problems)
        > > > > same problem with the new packages on the Bering update page.
        > > > >
        > > > > anyone have ipsec working on bering RC3????
        > > > >
        > > > > Thanks
        > > > > Marco
        > > >
        > > > yes it works flawlessly here on nic's i have problem with xdsl
        > > > interfaces tho.
        > >
        > > On the xdsl interfaces, do you have the same problem as Marco is having,
        > > i.e. _startklips detects eth0 as your %defaultroute instead of ppp0?
        > >
        > > This is a problem.  It should not be happening.  Could you send a barf
        of
        > > your failed xdsl attempts?
        >
        > no it detects ppp0 as %defaultroute
        > but it dosn't detect an address on ppp0.
        >
        > the output of "ipsec setup restart" is
        >
        > ipsec_setup: Stopping FreeS/WAN IPsec...
        > ipsec_setup: stop ordered, but IPsec does not appear to be running!
        > ipsec_setup: doing cleanup anyway...
        > ipsec_setup: Starting FreeS/WAN IPsec 1.97...
        > ipsec_setup: Using /lib/modules/ipsec.o
        > ipsec_setup: unable to determine address of
        > `ppp0'
        >
        > I can't provide the barf yet, since the person having this box is on
        > vacation and i don't have a adsl line here.
        > (howcome everyone's on vacation except me ????)
        >
        >
        > mvh
        > Ronny Aasen
        >
        >
        >
        >
        >
        >
        >
        >
        >
        > -------------------------------------------------------
        > This sf.net email is sponsored by:ThinkGeek
        > Welcome to geek heaven.
        > http://thinkgeek.com/sf
        > ------------------------------------------------------------------------
        > leaf-user mailing list: [EMAIL PROTECTED]
        > https://lists.sourceforge.net/lists/listinfo/leaf-user
        > SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
        >
        >
        
        
        
        -------------------------------------------------------
        This sf.net email is sponsored by:ThinkGeek
        Welcome to geek heaven.
        http://thinkgeek.com/sf
        ------------------------------------------------------------------------
        leaf-user mailing list: [EMAIL PROTECTED]
        https://lists.sourceforge.net/lists/listinfo/leaf-user
        SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
        

+,~wzf+,좷o$yyzW(h礅zxm&yj)b    
b^izb,y+޶m+-.ǟ+-bا~yDPi^ik7ځv"w_=f


Reply via email to