Not ment to be a flame or anything.... :)

But when corresponding with mailing lists, you should always start a new topic for a new issue. There is actually a term for what you just did: "Off-Topic"

http://en.wikipedia.org/wiki/Off-topic





On 11/2/06, Kyle Mott < [EMAIL PROTECTED]> wrote:
I've also been losing my WAN IP lately. Every 1-2 hours since I updated
to 1.0.1, my WAN IP won't renew. I have to in to the Interface status
and manually renew it by clicking "renew". Has anybody seen this
behaviour before?


-Kyle

Captain Bablam wrote:
> This is exactly what I saw on both RC3 and 1.0
>
>      Wade B
>
> On 11/1/06, Kyle Mott <[EMAIL PROTECTED]> wrote:
>
>> Hi Guys,
>>
>> I recently updated to 1.0.1, but my OpenVPN config stopped working.
>> Naturally, I rebooted, and it worked for a while, then stopped again.
>> So, I disabled/enabled the tunnel, and that didn't get it working
>> either. I noticed the following in the OpenVPN logging tab:
>> Nov 1 22:27:51  openvpn[23771]: Exiting
>> Nov 1 22:27:51  openvpn[23771]: TCP/UDP: Socket bind failed on local
>> address [undef]:443: Address already in use
>> Nov 1 22:27:51  openvpn[23771]: WARNING: file
>> '/var/etc/openvpn_server0.key' is group or others accessible
>> Nov 1 22:27:51  openvpn[23771]: OpenVPN 2.0.6 i386-portbld-freebsd6.1
>> [SSL] [LZO] built on Apr 6 2006
>>
>> This sounds vaguely familiar, do we know if it's possible back on 1.0.1?
>> I don't have any tun0 interfaces defined or assigned under Interfaces ->
>> (assign).
>>
>> Here's that's listening on :443 on my system:
>> # sockstat -4 | grep "443\|PID"
>> USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS    FOREIGN ADDRESS
>> root     sleep      24383 10 tcp4   *:443            *:*
>> root     sh         15501 10 tcp4   *:443            *:*
>> root     racoon     15479 10 tcp4   *:443            *:*
>> dhcpd    dhcpd      1173  10 tcp4   *:443            *:*
>> nobody   dnsmasq    1102  2  udp4   *:64436          *:*
>> root     check_relo 454   10 tcp4   *:443            *:*
>>
>>
>> -Kyle
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to