| 1 |
I forgot to mention, my link looks normal: |
| 2 |
|
| 3 |
openvpn.client_clinic_atom -> /etc/init.d/openvpn |
| 4 |
|
| 5 |
-- |
| 6 |
Joseph |
| 7 |
|
| 8 |
On 12/26/12 22:52, Joseph wrote: |
| 9 |
>I'm having problem starting openvpn after recent upgrade. |
| 10 |
> |
| 11 |
>When I try to start it I get a normal respond: |
| 12 |
> |
| 13 |
>openvpn.client_clinic_atom start |
| 14 |
> * Starting openvpn.client_clinic_atom ... [ ok ] |
| 15 |
> * WARNING: openvpn.client_clinic_atom has started, but is inactive |
| 16 |
> |
| 17 |
>but ifconfig is not showing this connection in addition it looks strange, not as it used to: |
| 18 |
> |
| 19 |
>ifconfig |
| 20 |
>eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 |
| 21 |
> inet 10.0.0.100 netmask 255.255.255.0 broadcast 10.0.0.255 |
| 22 |
> inet6 fe80::21b:21ff:feb8:27b6 prefixlen 64 scopeid 0x20<link> |
| 23 |
> ether 00:1b:21:b8:27:b6 txqueuelen 1000 (Ethernet) |
| 24 |
> RX packets 16129 bytes 9087618 (8.6 MiB) |
| 25 |
> RX errors 0 dropped 0 overruns 0 frame 0 |
| 26 |
> TX packets 15573 bytes 2667489 (2.5 MiB) |
| 27 |
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 |
| 28 |
> device interrupt 16 memory 0xfddc0000-fdde0000 |
| 29 |
> |
| 30 |
>lo: flags=73<UP,LOOPBACK,RUNNING> mtu 16436 |
| 31 |
> inet 127.0.0.1 netmask 255.0.0.0 |
| 32 |
> inet6 ::1 prefixlen 128 scopeid 0x10<host> |
| 33 |
> loop txqueuelen 0 (Local Loopback) |
| 34 |
> RX packets 1218 bytes 1433926 (1.3 MiB) |
| 35 |
> RX errors 0 dropped 0 overruns 0 frame 0 |
| 36 |
> TX packets 1218 bytes 1433926 (1.3 MiB) |
| 37 |
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 |
| 38 |
> |
| 39 |
>-- |
| 40 |
>Joseph |
Archives