IP packet with unknown IP version=15 seen

vieri

Hi,

I'm getting the following messages in my log every minute (but I don't think there's a client trying to connect every minute, 24h/day):

Fri Oct 21 09:27:32 2016 IP packet with unknown IP version=15 seen
Fri Oct 21 09:28:33 2016 IP packet with unknown IP version=15 seen
Fri Oct 21 09:29:33 2016 IP packet with unknown IP version=15 seen
Fri Oct 21 09:30:33 2016 IP packet with unknown IP version=15 seen
Fri Oct 21 09:31:33 2016 IP packet with unknown IP version=15 seen
Fri Oct 21 09:32:33 2016 IP packet with unknown IP version=15 seen
Fri Oct 21 09:33:33 2016 IP packet with unknown IP version=15 seen
Fri Oct 21 09:34:34 2016 IP packet with unknown IP version=15 seen
Fri Oct 21 09:35:34 2016 IP packet with unknown IP version=15 seen
Fri Oct 21 09:36:34 2016 IP packet with unknown IP version=15 seen
Fri Oct 21 09:37:34 2016 IP packet with unknown IP version=15 seen
Fri Oct 21 09:38:34 2016 IP packet with unknown IP version=15 seen

My server config has "verb 0" (see below). Shouldn't this message be suppressed or is it important?
local 172.16.0.1
port 61196
proto tcp-server
dev tun148
ca /etc/ssl/CA-H1/cacert.pem
dh /etc/ssl/CA-H1/dh2048.pem
cert /etc/ssl/openvpn/openvpnservers_OVPN1_cert.pem
key /etc/ssl/openvpn/openvpnservers_OVPN1_key.pem
tls-auth /etc/ssl/openvpn/ta-evpn.key 0
cipher AES-256-CBC
tls-cipher TLS-DHE-RSA-WITH-AES-256-CBC-SHA256
mode server
tls-server
topology subnet
push "topology subnet"
ifconfig 192.168.148.1 255.255.252.0
ifconfig-pool 192.168.148.2 192.168.148.254 255.255.252.0
push "route-gateway 192.168.148.1"
route-gateway 192.168.148.2
persist-key
persist-tun
client-config-dir /etc/openvpn/ccd-evpn
script-security 2
client-connect "/etc/openvpn/client-up.sh evpn"
client-disconnect "/etc/openvpn/client-down.sh evpn"
ifconfig-pool-persist /var/log/openvpn/H1-evpn_ipp.txt
push "route 10.215.0.0 255.255.0.0"
push "dhcp-option DNS 10.215.144.31"
push "dhcp-option DNS 10.215.144.35"
push "dhcp-option DOMAIN mydomain.org"
keepalive 10 120
comp-lzo
user openvpn
group openvpn
status /var/log/openvpn/H1-evpn.status
log /var/log/openvpn/H1-evpn.log
# verb 0: production-ready
# verb 4: general usage
# verb 6: debug connection problems
# verb 9: extremely verbose
verb 0
username-as-common-name
plugin /usr/lib/openvpn/openvpn-plugin-auth-pam.so openvpn-evpn I've read somewhere that "comp-lzo" can generate that message in the log but it's unclear as to what one should do to avoid it.
I guess the message would disappear if I used "comp-lzo no" on both server and clients but then again I would like to let the algo decide whether to enable compression or not.

Any ideas?

TinCanTech

Please see:
HOWTO: Request Help !

vieri

openvpn-2.3.11 community edition
server log and conf file posted.
client conf files and logs apparently irrelevant since I'm getting these messages even when no known clients are connecting.

TinCanTech

vieri wroteMy server config has "verb 0"

TinCanTech wrote

verb 4                         #  Make sure to use --verb 4

:geek:

vieri

I set verb 4 but I'm still getting these messages in the log with no extra info:

Fri Oct 21 23:15:42 2016 us=651406 IP packet with unknown IP version=15 seen
Fri Oct 21 23:16:42 2016 us=808494 IP packet with unknown IP version=15 seen
etc...

So I set verb 9 and this is what I see in the log:

Fri Oct 21 23:19:43 2016 us=239509 MULTI: REAP range 144 -> 160
Fri Oct 21 23:19:43 2016 us=239584 MULTI TCP: multi_tcp_action a=TA_TIMEOUT p=0
Fri Oct 21 23:19:43 2016 us=239604 MULTI TCP: multi_tcp_dispatch a=TA_TIMEOUT mi=0x00000000
Fri Oct 21 23:19:43 2016 us=239621 MULTI TCP: multi_tcp_post TA_TIMEOUT -> TA_UNDEF
Fri Oct 21 23:19:43 2016 us=239641 SCHEDULE: schedule_find_least NULL
Fri Oct 21 23:19:43 2016 us=279581 EP_WAIT[0] rwflags=0x0001 ev=0x00000001 arg=0x00000002
Fri Oct 21 23:19:43 2016 us=279659 MULTI TCP: multi_tcp_action a=TA_TUN_READ p=0
Fri Oct 21 23:19:43 2016 us=279713 MULTI TCP: multi_tcp_dispatch a=TA_TUN_READ mi=0x00000000
Fri Oct 21 23:19:43 2016 us=279740  read from TUN/TAP returned 32
Fri Oct 21 23:19:43 2016 us=279761 IP packet with unknown IP version=15 seen
Fri Oct 21 23:19:43 2016 us=279778 MULTI TCP: multi_tcp_post TA_TUN_READ -> TA_UNDEF
Fri Oct 21 23:19:43 2016 us=279794 SCHEDULE: schedule_find_least NULL
Fri Oct 21 23:19:53 2016 us=299024 MULTI: REAP range 160 -> 176
Fri Oct 21 23:19:53 2016 us=299099 MULTI TCP: multi_tcp_action a=TA_TIMEOUT p=0
Fri Oct 21 23:19:53 2016 us=299119 MULTI TCP: multi_tcp_dispatch a=TA_TIMEOUT mi=0x00000000
Fri Oct 21 23:19:53 2016 us=299136 MULTI TCP: multi_tcp_post TA_TIMEOUT -> TA_UNDEF
Fri Oct 21 23:19:53 2016 us=299174 SCHEDULE: schedule_find_least NULL
Fri Oct 21 23:20:03 2016 us=318529 MULTI: REAP range 176 -> 192
Fri Oct 21 23:20:03 2016 us=318605 MULTI TCP: multi_tcp_action a=TA_TIMEOUT p=0
Fri Oct 21 23:20:03 2016 us=318626 MULTI TCP: multi_tcp_dispatch a=TA_TIMEOUT mi=0x00000000
Fri Oct 21 23:20:03 2016 us=318643 MULTI TCP: multi_tcp_post TA_TIMEOUT -> TA_UNDEF
Fri Oct 21 23:20:03 2016 us=318661 SCHEDULE: schedule_find_least NULL
Fri Oct 21 23:20:13 2016 us=338051 MULTI: REAP range 192 -> 208
Fri Oct 21 23:20:13 2016 us=338124 MULTI TCP: multi_tcp_action a=TA_TIMEOUT p=0
Fri Oct 21 23:20:13 2016 us=338142 MULTI TCP: multi_tcp_dispatch a=TA_TIMEOUT mi=0x00000000
Fri Oct 21 23:20:13 2016 us=338158 MULTI TCP: multi_tcp_post TA_TIMEOUT -> TA_UNDEF
Fri Oct 21 23:20:13 2016 us=338176 SCHEDULE: schedule_find_least NULL
Fri Oct 21 23:20:23 2016 us=357553 MULTI: REAP range 208 -> 224
Fri Oct 21 23:20:23 2016 us=357696 MULTI TCP: multi_tcp_action a=TA_TIMEOUT p=0
Fri Oct 21 23:20:23 2016 us=357718 MULTI TCP: multi_tcp_dispatch a=TA_TIMEOUT mi=0x00000000
Fri Oct 21 23:20:23 2016 us=357735 MULTI TCP: multi_tcp_post TA_TIMEOUT -> TA_UNDEF
Fri Oct 21 23:20:23 2016 us=357752 SCHEDULE: schedule_find_least NULL
Fri Oct 21 23:20:33 2016 us=377053 MULTI: REAP range 224 -> 240
Fri Oct 21 23:20:33 2016 us=377123 MULTI TCP: multi_tcp_action a=TA_TIMEOUT p=0
Fri Oct 21 23:20:33 2016 us=377141 MULTI TCP: multi_tcp_dispatch a=TA_TIMEOUT mi=0x00000000
Fri Oct 21 23:20:33 2016 us=377157 MULTI TCP: multi_tcp_post TA_TIMEOUT -> TA_UNDEF
Fri Oct 21 23:20:33 2016 us=377173 SCHEDULE: schedule_find_least NULL
Fri Oct 21 23:20:43 2016 us=396567 MULTI: REAP range 240 -> 256
Fri Oct 21 23:20:43 2016 us=396625 MULTI TCP: multi_tcp_action a=TA_TIMEOUT p=0
Fri Oct 21 23:20:43 2016 us=396644 MULTI TCP: multi_tcp_dispatch a=TA_TIMEOUT mi=0x00000000
Fri Oct 21 23:20:43 2016 us=396662 MULTI TCP: multi_tcp_post TA_TIMEOUT -> TA_UNDEF
Fri Oct 21 23:20:43 2016 us=396682 SCHEDULE: schedule_find_least NULL
Fri Oct 21 23:20:43 2016 us=436705 EP_WAIT[0] rwflags=0x0001 ev=0x00000001 arg=0x00000002
Fri Oct 21 23:20:43 2016 us=436735 MULTI TCP: multi_tcp_action a=TA_TUN_READ p=0
Fri Oct 21 23:20:43 2016 us=436752 MULTI TCP: multi_tcp_dispatch a=TA_TUN_READ mi=0x00000000
Fri Oct 21 23:20:43 2016 us=436771  read from TUN/TAP returned 32
Fri Oct 21 23:20:43 2016 us=436790 IP packet with unknown IP version=15 seen
Fri Oct 21 23:20:43 2016 us=436806 MULTI TCP: multi_tcp_post TA_TUN_READ -> TA_UNDEF
Fri Oct 21 23:20:43 2016 us=436821 SCHEDULE: schedule_find_least NULL

TinCanTech

A common problem is when compression has not been configured correctly ..

vieri

hmm, I don't think the forum moderator should have censored the last two posts by deleting them... They weren't nasty, really...

Anyway, if "compression has not been configured correctly" then what's wrong with my server config in my first post?
comp-lzo's default parameter is "adaptive".
The log message comes up even when no openvpn clients connect, once a minute.

TinCanTech

vieri wroteI don't think the forum moderator should have censored the last two posts by deleting them... They weren't nasty, really..

I think I was unnecessarily off-hand .. my apologies.

vieri wroteAnyway, if "compression has not been configured correctly" then what's wrong with my server config

But what about the client config ?

As a tip, you can --push "comp-lzo X" from the server and you can even do it on a per client basis in a CCD file, so long as something eg: --comp-lzo is configured in the client config. If it is not there then your error will probably arise.