|
From: Prasanna K. <pra...@gm...> - 2008-02-27 18:51:05
|
On Wed, Feb 27, 2008 at 10:20 PM, siegfried <sie...@he...> wrote: > > Thank you Prasanna. I'm sorry I posted twice, that was not intentional. > > > >> > >> I have an openvpn server that has been working for years in bridging > >> mode at xxx.xxx.xxx.xxx and is currently working from address > zzz.zzz.zzz.zzz. > >> However, an old key that was working from another address is not > >> working from yyy.yy.yy.yy as indicated by the error messages below. I > >> have searched the archives and searched with google. I tried searching > >> http://sourceforge.net/search/?group_id=48978&type_of_search=docs but > >> no luck there either. > >If your new server is multihomed, then you could have this problem. > > > > > >You will need to upgrade the server to 2.1rc and add "multihome" to > >the server conf. > > I wonder if this is going to be a problem for me since I (and my two > VPN clients "alpha" and "beta") are in WA and my bridging server is in > CO. My bridging server is a WRT54GS. Fortunately I left the ssh port > open so I can access it without the VPN (I hope). > > Assuming it is a problem: > > Can client "alpha" become VPN bridging server for "beta" (both in WA) > where "alpha" is simultaneously a bridging client to my WRT54Gs server > in CO? > You can run any system as a server, as long as you have port 1194 UDP open on the server firewall(s). Change your WRT54GS to a 2.0 client, if you can't upgrade it to 2.1rc. Then on the server end, specify 'float', because the WRT54GS might send outgoing packets on either interface - ideally you'd fix the outgoing interface, by specifying "local blah.blah.blah.blah" Actually, on your server conf right now, specify, "local xx.xx.x.x" and see if that fixes your problem. If you don't need real multihoming, then you should be able to make do with this change. Prasanna. -- www.elinanetworks.com Seamless, secure delivery of applications. |