public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Axel Neumann <axel@open-mesh.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] two-way-tunnel quirks
Date: Sat, 1 Dec 2007 21:41:59 +0100	[thread overview]
Message-ID: <200712012141.59334.axel@open-mesh.net> (raw)
In-Reply-To: <200712011834.54327.lindner_marek@yahoo.de>

Hi,

perhaps this has something to do with the reduced maximum-transfer-unit (mtu) 
which ist left for the tunnel interfaces. Since the one-way-tunnel do only 
tunnel the upling-traffic but NOT tunnel the downlink traffic this is not a 
problem when trying to connect to a intractable www server.

Did I understand you correct, that these problems only occurs when surfing to 
a few webservers, but not to all webservers?

Can you try what happens if you reduce the mtu of the outgoing interface at 
the upstream gateway (e.g. ifconfig ethX mtu 1400). I think there might be 3 
possible results:
 1) everything remains as before, there is another reason
 2) the hotmai/msn/live.com or pop services are not reachable anymore from the 
upstream gw. Then we have at least a hint. 
 3) Now these services also work inside the mesh. Maybe the icmp messages 
which are supposed to communicate the path-mtu-problem were not correctly 
transmitted from the tunnel interface but succeed from the upstream gw 
interface to the server. 

ciao,
axel


On Samstag 01 Dezember 2007, Marek Lindner wrote:
> > now i found an issue which i didn't relate with batman
> > first. I got several reports of users, hotmail/msn/live.com
> > not being accessible anymore...
> > Yesterday i found out theres also problems with some pop server
> > not beeing accessible, but everything works fine directly at the
> > upstream gw, without any batmand involved.
>
> Unfortunately, it is too few information to do anything about it. Could you
> describe your experiences in more detail. Here some questions on the way:
>
> - When did you notice the problem for the first time ?
> - Which revision was used ?
> - What exactely is your problem ?
> - Can you describe it in way that i can reproduce it ?
>
> Greetings,
> Marek
>
>
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n



  reply	other threads:[~2007-12-01 20:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30 23:28 [B.A.T.M.A.N.] two-way-tunnel quirks Jan Hetges
2007-12-01 17:34 ` Marek Lindner
2007-12-01 20:41   ` Axel Neumann [this message]
2007-12-02  5:39     ` Jan Hetges
2007-12-06  3:18       ` Marek Lindner
2007-12-02  4:32   ` Jan Hetges
2007-12-02 18:54     ` Axel Neumann
2007-12-03 17:47       ` Predrag Balorda
2007-12-04  4:03       ` Jan Hetges
2007-12-04  9:05         ` Axel Neumann
2007-12-04 13:00           ` Jan Hetges
2007-12-04 15:05             ` Axel Neumann
2007-12-04 10:01     ` Axel Neumann
2007-12-04 12:37       ` Axel Neumann

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=200712012141.59334.axel@open-mesh.net \
    --to=axel@open-mesh.net \
    --cc=b.a.t.m.a.n@open-mesh.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox