[Olsr-users] Delivery Status Notification (Failure)

[Sahana k.srinivas]

Hi,

Yes, R1 and R2 announce the corresponding IP's as HNA.

And about the default route of the clients, could you please let me know as
to how to check it?


Sahana

On Fri, Dec 26, 2014 at 11:01 AM, Mail Delivery Subsystem <
(spam-protected)> wrote:

> Delivery to the following recipient failed permanently:
>
>      (spam-protected)
>
> Technical details of permanent failure:
> Google tried to deliver your message, but it was rejected by the server
> for the recipient domain lists.olsr.org by lists.olsr.org.
> [78.41.115.254].
>
> The error that the other server returned was:
> 550-policyd-weight said: temporarily blocked because of previous errors -
> 550 retrying too fast. penalty: 30 seconds x 0 retries.
>
>
> ----- Original message -----
>
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
>         d=gmail.com; s=20120113;
>
> h=mime-version:in-reply-to:references:date:message-id:subject:from:to
>          :content-type;
>         bh=Dul2vQntTD3k1V/UvjlohZuyNaIs6v91LQQJeSroaJo=;
>
> b=SNSQ3b9643GrhT5P/QlE7mQo9gsFJsPoOORfaAqbMjrnfw1kGDTaS3qScRc7d2Yiqd
>
>  nBuWPEMlFbzH9rgAB1RcXSHThQcB/I7+emVld1+sQZuynpHRlspIT/C9jzLUp2J4iTUt
>
>  PUsohirmq6B4wAbteLpaYFcnoTyxdzKsgWCaN3oLf37v1x+tn05aYYCNQyfDwq4eqsEs
>
>  /fC5AEIemVgeAn/a+6WXyqGSwPNpHh3D2vwb4+S5EGefBtg33hEhxhilmNiTmrNX1b1w
>
>  kBIGpFAGigedsaPikaE2wOjvCPbtuxvJ96ROnh+kZfPMEOOHUqtxnDdw2Mg9PT0nB2A0
>          uqiA==
> MIME-Version: 1.0
> X-Received: by 10.68.65.16 with SMTP id t16mr65580138pbs.70.1419571898796;
>  Thu, 25 Dec 2014 21:31:38 -0800 (PST)
> Received: by 10.70.38.173 with HTTP; Thu, 25 Dec 2014 21:31:38 -0800 (PST)
> In-Reply-To: <CAJd3i8sa9dQEXZZLeWi_LF1dmccCd8frYO9N-Bci5r=
> (spam-protected)>
> References: <CAJd3i8t8GKaS2ozkEiU=
> (spam-protected)>
>         <
> (spam-protected)>
>         <
> (spam-protected)>
>         <CAGnRvup=1p=Kpn2bTC1c06F=n3QrXB=
> (spam-protected)>
>         <
> (spam-protected)>
>         <
> (spam-protected)>
>         <(spam-protected)>
>         <
> (spam-protected)>
>         <CAJd3i8vmgK0uZ9Nh69N62qfFCciz+E6wqqkn=
> (spam-protected)>
>         <(spam-protected)>
>         <CAJd3i8vQQzcQB14mJe76k+UvnfZOi6i3E=
> (spam-protected)>
>         <CAGnRvuqqfTm7Q-QaAq3iJGdyKoFkKJaWDU17ay_8+H24=
> (spam-protected)>
>         <CAJd3i8sa9dQEXZZLeWi_LF1dmccCd8frYO9N-Bci5r=
> (spam-protected)>
> Date: Fri, 26 Dec 2014 11:01:38 +0530
> Message-ID: <CAJd3i8vFHVhgGtn7qh700f-L20ipA_Md7CBz8UjHmP6=
> (spam-protected)>
> Subject: Re: Mesh network
> From: "Sahana k.srinivas" <(spam-protected)>
> To: (spam-protected)
> Content-Type: multipart/alternative; boundary=001a11381972c2d1a7050b17d64e
>
> Hi,
>
> Yes, R1 and R2 announce the corresponding IP's as HNA.
>
> And about the default route of the clients, could you please let me know as
> to how to check it?
>
>
> Sahana
>
> On Fri, Dec 26, 2014 at 9:24 AM, Sahana k.srinivas <(spam-protected)>
> wrote:
>
> > Hi,
> >
> > Yes, R1 and R2 announce the corresponding IP's as HNA.
> >
> > And about the default route of the clients, could you please let me know
> > as to how to check it?
> >
> > Sahana
> > On Dec 26, 2014 2:48 AM, "Henning Rogge" <(spam-protected)> wrote:
> >
> >> On Wed, Dec 24, 2014 at 4:59 PM, Sahana k.srinivas
> >> <(spam-protected)> wrote:
> >> > Hi,
> >> >
> >> > Thank you for your response :)
> >> > We tried the things you said using this topology
> >> >
> >> (192.168.2.101/24)          (192.168.2.1/24)            (10.0.0.1/24)
> >>        (10.0.0.111/24)
> >>
> >>
> C1<------------------------->R1<------------------------>R2<------------------->C2
> >>                                     (192.168.1.1/24)          (
> >> 192.168.1.45/24)
> >>
> >> Lets map my questions to this configuration.
> >>
> >> Does C1 have a default (0.0.0.0/0) route to R1?
> >>
> >> Does R1 announce 192.168.2.0/24 as a HNA?
> >>
> >> Does R2 announce 10.0.0.0/24 as a HNA?
> >>
> >> Does C2 have a default (0.0.0.0/0) route to R2?
> >>
> >> Henning Rogge
> >>
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20141226/c607dec6/attachment.html>