From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Devesh Chipade <devesh@in-unison.com>
Cc: Paul Mackerras <paulus@ozlabs.org>, linux-ppp@vger.kernel.org
Subject: Re: PPP Modem Hangup
Date: Fri, 13 Sep 2024 19:03:01 -0400 [thread overview]
Message-ID: <550821.1726268581@dyas> (raw)
In-Reply-To: <CAPKvdWeC2AHc0eqieJAFXCaayyoU4zOSsGkDwDtK-xpDycYwsQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 923 bytes --]
Devesh Chipade <devesh@in-unison.com> wrote:
> On analyzing the logs further, I noticed that I can ping only from AOSP
> target device to Ubuntu Machine and not the other way around.
>> 11:29:02.068203 IP Devesh > 10.0.0.2: ICMP echo request, id 56351, seq
>> 5744, length 64 11:29:02.394650 IP 10.0.0.2 > Devesh: ICMP echo
>> request, id 32, seq 5882, length 64 11:29:02.394673 IP Devesh >
>> 10.0.0.2: ICMP echo reply, id 32, seq 5882, length 64 11:29:02.490505
Looks like it works that way.
>> cooked v1), snapshot length 262144 bytes 11:27:47.371173 IP 10.0.0.1 >
>> 10.0.0.2: ICMP echo reply, id 32, seq 5969, length 64 11:27:47.865949
>> IP 10.0.0.1 > 10.0.0.2: ICMP echo request, id 56351, seq 5830, length
And the other way too.
--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
-= IPv6 IoT consulting =- *I*LIKE*TRAINS*
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2024-09-13 23:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 22:55 PPP Modem Hangup Devesh Chipade
2024-09-10 12:39 ` Michael Richardson
2024-09-10 16:42 ` Devesh Chipade
2024-09-10 18:23 ` Michael Richardson
2024-09-10 18:30 ` Devesh Chipade
2024-09-10 23:53 ` Paul Mackerras
2024-09-11 0:10 ` Devesh Chipade
2024-09-13 1:43 ` Devesh Chipade
2024-09-13 18:00 ` Michael Richardson
2024-09-13 18:33 ` Devesh Chipade
2024-09-13 20:33 ` Devesh Chipade
2024-09-13 23:03 ` Michael Richardson [this message]
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=550821.1726268581@dyas \
--to=mcr+ietf@sandelman.ca \
--cc=devesh@in-unison.com \
--cc=linux-ppp@vger.kernel.org \
--cc=paulus@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).