From: Stephan van Hienen <s.v.hienen@cable.a2000.nl>
To: ultralinux@vger.kernel.org
Subject: weird problems with ipmasq
Date: Wed, 20 May 1998 18:36:52 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-90222356531060@msgid-missing> (raw)
hi just looked at dmesg and saw this :
(what's up ? )
[ddx@ddx ddx]$ dmesg
Socket destroy delayed (r=0 w\x128)
TCPv4 bad checksum from 91.6.109.194:0077 to 27.24.108.62:0680,
len\x1480/1480/1500
TCPv4 bad checksum from 9.255.159.194:e829 to 27.24.108.62:0077,
len /20/40
TCPv4 bad checksum from 9.255.159.194:e829 to 27.24.108.62:0077,
len /20/40
Socket destroy delayed (r=0 w–)
Socket destroy delayed (r=0 w–)
TCPv4 bad checksum from 91.6.109.194:0077 to 27.24.108.62:0808,
len\x1480/1480/1500
TCPv4 bad checksum from 91.6.109.194:0077 to 27.24.108.62:09bf,
len€4/804/824
Socket destroy delayed (r=0 w–)
TCPv4 bad checksum from 9.255.159.194:1a0d to 27.24.108.62:0427,
lenh/68/88
TCPv4 bad checksum from 9.255.159.194:1e6a to 27.24.108.62:1244,
lens/73/93
TCPv4 bad checksum from 9.255.159.194:0035 to 27.24.108.62:0529,
len\x119/119/139
TCPv4 bad checksum from 9.255.159.194:044a to 27.24.108.62:0077,
lenS6/536/556
IP_MASQ:failed TCP/UDP checksum from 91.6.109.194!
IP_MASQ:failed TCP/UDP checksum from 91.6.109.194!
IP_MASQ:failed TCP/UDP checksum from 91.6.109.194!
IP_MASQ:failed TCP/UDP checksum from 91.6.109.194!
IP_MASQ:failed TCP/UDP checksum from 91.6.109.194!
IP_MASQ:failed TCP/UDP checksum from 91.6.109.194!
TCPv4 bad checksum from 9.255.159.194:0050 to 27.24.108.62:04eb,
len /20/40
Socket destroy delayed (r=0 w–)
Socket destroy delayed (r=0 w–)
IP_MASQ:masq_expire delayed: TCP C0A80075:3062->8BA5590A:0015 nlocks-1=0
masq.refcnt-1=2 masq.n_control\x13
IP_MASQ:masq_expire delayed: TCP C0A80075:3062->8BA5590A:0015 nlocks-1=0
masq.refcnt-1=2 masq.n_control=1
IP_MASQ:masq_expire delayed: TCP C0A80075:3062->8BA5590A:0015 nlocks-1=0
masq.refcnt-1=2 masq.n_control=1
IP_MASQ:masq_expire delayed: TCP C0A80075:3062->8BA5590A:0015 nlocks-1=0
masq.refcnt-1=2 masq.n_control=1
IP_MASQ:masq_expire delayed: TCP C0A80075:3062->8BA5590A:0015 nlocks-1=0
masq.refcnt-1=2 masq.n_control=1
IP_MASQ:masq_expire delayed: TCP C0A80075:3062->8BA5590A:0015 nlocks-1=0
masq.refcnt-1=2 masq.n_control=1
IP_MASQ:masq_expire delayed: TCP C0A80075:3062->8BA5590A:0015 nlocks-1=0
masq.refcnt-1=2 masq.n_control=1
IP_MASQ:masq_expire delayed: TCP C0A80075:3062->8BA5590A:0015 nlocks-1=0
masq.refcnt-1=2 masq.n_control=1
IP_MASQ:masq_expire delayed: TCP C0A80075:3062->8BA5590A:0015 nlocks-1=0
masq.refcnt-1=2 masq.n_control=1
IP_MASQ:masq_expire delayed: TCP C0A80075:3062->8BA5590A:0015 nlocks-1=0
masq.refcnt-1=2 masq.n_control=1
IP_MASQ:failed TCP/UDP checksum from 91.6.109.194!
IP_MASQ:masq_expire delayed: TCP C0A80075:3062->8BA5590A:0015 nlocks-1=0
masq.refcnt-1=2 masq.n_control=1
IP_MASQ:masq_expire delayed: TCP C0A80075:3062->8BA5590A:0015 nlocks-1=0
masq.refcnt-1=2 masq.n_control=1
IP_MASQ:masq_expire delayed: TCP C0A80075:3062->8BA5590A:0015 nlocks-1=0
masq.refcnt-1=2 masq.n_control=1
IP_MASQ:masq_expire delayed: TCP C0A80075:3062->8BA5590A:0015 nlocks-1=0
masq.refcnt-1=2 masq.n_control=1
IP_MASQ:masq_expire delayed: TCP C0A80075:3062->8BA5590A:0015 nlocks-1=0
masq.refcnt-1=2 masq.n_control=1
IP_MASQ:failed TCP/UDP checksum from 91.6.109.194!
IP_MASQ:failed TCP/UDP checksum from 91.6.109.194!
IP_MASQ:failed TCP/UDP checksum from 91.6.109.194!
IP_MASQ:failed TCP/UDP checksum from 91.6.109.194!
IP_MASQ:failed TCP/UDP checksum from 91.6.109.194!
TCPv4 bad checksum from 91.6.109.194:0077 to 27.24.108.62:1258,
len\x1480/1480/1500
TCPv4 bad checksum from 91.6.109.194:0077 to 27.24.108.62:1258,
len\x1480/1480/1500
TCPv4 bad checksum from 91.6.109.194:0077 to 27.24.108.62:133e,
len\x1274/1274/1294
TCPv4 bad checksum from 91.6.109.194:0077 to 27.24.108.62:1354,
len\x1480/1480/1500
IP_MASQ:masq_expire delayed: TCP C0A80075:0829->89E084D6:0015 nlocks-1=0
masq.refcnt-1=2 masq.n_control=5
TCPv4 bad checksum from 9.255.159.194:1e6a to 27.24.108.62:0a6f,
len /20/40
TCPv4 bad checksum from 91.6.109.194:0077 to 27.24.108.62:052f,
len\x1480/1480/1500
Socket destroy delayed (r=0 w\x1680)
reply other threads:[~1998-05-20 18:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ultrasparc-90222356531060@msgid-missing \
--to=s.v.hienen@cable.a2000.nl \
--cc=ultralinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.