From: Robert Penz <robert.penz@outertech.com>
To: lartc@vger.kernel.org
Subject: [LARTC] vtun - mtu problem
Date: Sun, 29 Sep 2002 19:36:31 +0000 [thread overview]
Message-ID: <marc-lartc-103332851005629@msgid-missing> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi!
I want to to that
local network ---eth0--- tunnel entry point ---- tunnel exit point.
(windows and linux pcs)
I'm using vtun and I'm masquerating on both tunnel machines, my problem is now
that a ping works also small packets but if the packet gets bigger I get that
with tcpdump on my tunnel exit point.
tcpdump -n -i eth0 host heise.de
21:03:32.595835 194.242.45.xxx > 193.99.144.71: icmp: 10.3.0.2 unreachable -
need to frag (mtu 1450) [tos 0xc0]
21:03:38.794269 193.99.144.71.80 > 194.242.45.xxx.32819: R
1387534372:1387534372(0) ack 3349554176 win 0
here the setup of my tunnel entry point:
eth0 Link encap:Ethernet HWaddr 00:00:CB:59:EE:85
inet addr:10.149.xx.xx Bcast:10.149.xx.255 Mask:255.255.240.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
tun0 Link encap:Point-to-Point Protocol
inet addr:10.3.0.2 P-t-P:10.3.0.1 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1450 Metric:1
I did a little searching on the internet, and the only stuff I found was from
2000, where something simlular happend, and the answer was to set the clients
to mtu 1450, is that the still the only way. (didn't try it sofar)
but what I don't understand, that the mtu is always 1450 .... so why is that
only a problem with my setup?
- --
Regards,
Robert
- ----------------
Robert Penz
robert.penz AT outertech.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9l1ZC8tTsQqJDUBMRAiLMAJ4mhO4FGkjXbYioRDyerl1nHboLcgCeNi+W
YLVA3MaoyN/bELX7g1OPw6k=
=UPRC
-----END PGP SIGNATURE-----
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-09-29 19: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-lartc-103332851005629@msgid-missing \
--to=robert.penz@outertech.com \
--cc=lartc@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.