[Olsr-dev] SmartGW client side questions

[Sven-Ola Tuecke]

Yes - of course. A question: do we need that tnl_$%abcd name for the 
smargw-client tunnel interface? I only expect one iface (because only one 
default-route-via-tunnel at a time").

A fixed name e.g. "olsr-smartgw" is more easily to handle, e.g. "iptables -A 
FORWARD -o olsr-smartgw -p tcp --tcp-flags SYN,RST SYN -j 
TCPMSS --clamp-mss-to-pmtu" sits in the firewall list and waits for the 
interface to be created. If we use a fixed name, I would omit the mentioned 
"background" job.

// Sven-Ola

----- Original Message ----- 
From: "Henning Rogge" <(spam-protected)>
To: <(spam-protected)>
Cc: "Sven-Ola Tuecke" <(spam-protected)>
Sent: Wednesday, April 28, 2010 11:20 AM
Subject: Re: [Olsr-dev] SmartGW client side questions
[snip]
> d) For the stand-alone client (Notebook user running OLSRD in order to
> browse) the lowered IPIP tunnel MTU is no problem. If you do proxy
> routing, e.g. for attached LAN clients without OLSRD, you may want
> MSS-clamping for the tunnel interface created by OLSRD. This may require a
> background job monitoring tunnel interfaces, because OLSRD uses an
> arbitrary name for the interface.
> > </readme>
Shall we add this to the README-OLSR-Extensions file ?
[snap]