9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Pick <D.M.Pick@qmul.ac.uk>
To: <9fans@9fans.net>
Subject: Re: [9fans] Pi3 with 2 nics
Date: Sat, 15 Apr 2017 07:19:48 +0100	[thread overview]
Message-ID: <08ad023d-ce5d-9676-0363-9fa2d7627500@qmul.ac.uk> (raw)
In-Reply-To: <6c6ff42f-af6e-f413-969c-763b8cdd51e8@gmail.com>

On 14/04/17 23:37, Adriano Verardo wrote:

> I have a pi3 with normal and wifi eth interfaces under the same stack.
> Wifi address is 10.12.12.15/16, the address of the other nic is
> 10.11.12.15/16,
> /net seems to be correct, the connection to the AP is up and running.
> But:
>
> (1) ping wifi 10.12.12.15 doesn't work when the Rj45 is unplugged
> (2) ping wifi 10.12.12.15 works when the Rj45 is plugged
> (3) the arp tables on the net all have a correct 10.12.12.15 entry
> (4) ip/ping -a to 10.11.x.x or 10.12.x.x always displays
>      10.11.12.15 -> ...   and doesn't work when the cable is unplugged.
> (5) with/without cable, "snoopy /net/ether1" (wifi nic) shows
>      icmp packets when pinging.
>
> I'm quite confused.
> Could anyone kindly tell me where is my mistake  ?

When this situation occurs on *any* OS I'd check the "defaut" route
and/or the connectivity of the other end. You don't say what the
connectivity of the other end is for the tests you've performed
and it makes a difference to the ability of the pi3 to respond via
the correct interface.

--
David Pick
Network Security Manager, IT Services
Queen Mary University of London
TB202,  Mile End Road, London E1 4NS
Tel: +44 (0) 20 7882 7079
Mob: +44 (0) 7973 379 161
E-Mail: D.M.Pick@qmul.ac.uk

Normal working days are Monday to Wednesday inclusive

Worried about Cyber Security? Check out the
Cyber Security Information and Training described at
http://connect.qmul.ac.uk/qmandyou/staff/items/2016/item177974.html




      parent reply	other threads:[~2017-04-15  6:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-14 22:37 Adriano Verardo
2017-04-14 23:06 ` Jules Merit
2017-04-15  6:37   ` Steve Simon
     [not found]     ` <CAEVxPTONNM4qGyMPoJTg1164DzDgC_ykSKChYzJ7d5huiaQ2Zg@mail.gmail.com>
     [not found]       ` <CAEVxPTPo-C=VjpHEqq7Q=6BzxPLEfK0Eq6SGvap4E5BUdPSFTA@mail.gmail.com>
2017-04-18  4:37         ` Jules Merit
2017-04-18 18:44           ` Steve Simon
2017-04-15  6:19 ` David Pick [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=08ad023d-ce5d-9676-0363-9fa2d7627500@qmul.ac.uk \
    --to=d.m.pick@qmul.ac.uk \
    --cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).