From nobody Tue Nov 12 20:54:04 2024 X-Original-To: questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4XnzDS5Dmsz5cbMp for ; Tue, 12 Nov 2024 20:54:16 +0000 (UTC) (envelope-from plmahan@gmail.com) Received: from mail-yb1-xb2b.google.com (mail-yb1-xb2b.google.com [IPv6:2607:f8b0:4864:20::b2b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XnzDS1jZVz4Gcx for ; Tue, 12 Nov 2024 20:54:16 +0000 (UTC) (envelope-from plmahan@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yb1-xb2b.google.com with SMTP id 3f1490d57ef6-e30cef4ac5dso5855545276.0 for ; Tue, 12 Nov 2024 12:54:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1731444855; x=1732049655; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=goLxMi2wes10b/osQGKhDXUQi2UjSjcdkP41ix3oaCQ=; b=f6Ay+8dvHk9ZZIQSVSYzBjIgK2GVt/0yK7gWrSlb47axCH7CDXeBuhgmTofZ0pnrcW YDDR/IY85KbmgigsJ20mUbF7DwY3fEPbxw+nfBINQ9jvZUilb70mTozHU8B/lnCb8QPI H8OtOM0Ac7H2j98jL9H/Pwnm9OaYgQycvgaUoS5oHkk1Au2S66B1PqCVbgsTiuXveCBn xnEyDUfSOEbjvw9IxDCWk8BNlxRgpqYun/+uS6EyaNy0R/9wm9D7oQTjEnH+XAvXaBdF 8Mtw9jAh2QH5Cxo8hAq201oe/hACNV78za35MYOwXI4pgugWGMVdzH9NEGkhY4yKGqu8 SQLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731444855; x=1732049655; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=goLxMi2wes10b/osQGKhDXUQi2UjSjcdkP41ix3oaCQ=; b=mlYyN2sSomjmIwaimkiHyX4xedsWwA/wrC2U7DuSyu5qxM50wYqD3frU6qI57xKKxD ujO6MmIMX+TiDTf9o5uAkBT5+FBT7YnoZqngHvZ9f01K/rH7emHosyRvqjkX+ob35mTV XJPYDRvuzLBcYcuQkIuP0/rp3n1WcboS1T5NeYpwLh2dgxDRQ+DU+yC6b5ScfCTF4ePo dLS/LBqPzKd/Iz6I2ZjdtjUt8kecJOqBkYrg6f3To7j13pl2l/7yeQeYZgdUSAh8kM9a iUIWfzYTsclwzk3UdeTZAf6dzXC9gGY8FasEKSKqEMF22V0OV2QcrdTjLAbRyofvfZuF x2kA== X-Gm-Message-State: AOJu0YyNxnvX1D1R4CKISCITjLHX5XJhy8+SKH3u3pDyE46559E1Gyw8 KtR6iNCvhPZ3t39opQDaY4XWBhNJW1HDgc/8Je1iIk83D/ZLmm7ntG//mXLnL65BbE/PA36cH5A hNbPVfaEh1vZ5mi8ki1mX8jTLmifV9A== X-Google-Smtp-Source: AGHT+IGAWZoOg6ZT2zpGij13a76NfuwYSiRPpFBAJp7Hj75kQEObKcgtl5gWG00EJPtSslWDTSQ7DwTPc4jWTh/lw9o= X-Received: by 2002:a05:6902:705:b0:e2e:3763:9068 with SMTP id 3f1490d57ef6-e35dc5e5b5amr4372029276.35.1731444855438; Tue, 12 Nov 2024 12:54:15 -0800 (PST) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 References: <0f00ea1a-8b62-4c0d-80ee-08721794483b@dreamchaser.org> <76101826-4507-4db4-b7dc-4abb90641713@dreamchaser.org> In-Reply-To: <76101826-4507-4db4-b7dc-4abb90641713@dreamchaser.org> From: Patrick Mahan Date: Tue, 12 Nov 2024 12:54:04 -0800 Message-ID: Subject: Re: missing ARP reply To: freebsd@dreamchaser.org Cc: questions@freebsd.org Content-Type: multipart/alternative; boundary="0000000000008e884e0626bd6b01" X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4XnzDS1jZVz4Gcx X-Spamd-Bar: ---- --0000000000008e884e0626bd6b01 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Nov 12, 2024 at 8:35=E2=80=AFAM Gary Aitken wrote: > On 11/11/24 21:36, Gary Aitken wrote: > > I'm having trouble with my solar inverter connecting to its home > > base somewhere in Germany and am suspecting a problem with a missing > > ARP reply. > ... > > xxx.yyy is the inverter on the local network xxx.zzz is the fbsd > > gateway/router on the local network > > > > #tcpdump -flnt -i fxp0 | grep 192.168.xxx.yyy ARP, Request who-has > > 192.168.xxx.zzz (aa:bb:cc:dd:ee:ff) tell 192.168.xxx.yyy, length 46 > > IP 192.168.xxx.yyy.3337 > 147.185.237.1.22222: Flags [.], seq > > 26043:26065, ack 708198036, win 2144, length 22 IP > > 147.185.237.1.22222 > 192.168.xxx.yyy.3337: Flags [P.], seq 1:23, ack > > 22, win 18410, length 22 IP 192.168.xxx.yyy.3337 > > > 147.185.237.1.22222: Flags [.], ack 23, win 2144, length 0 > > > > I'm guessing the 3 packets exchanged are a power optimizer reporting > > in, but may be the inverter doing something. > > > > The arp table on xxx.zzz has a permanent entry for itself on the > > interface, picked up from /etc/hosts: > > > > # arp -a ns.dreamchaser.org (192.168.xxx.zzz) at aa:bb:cc:dd:ee:ff on > > fxp0 permanent [ethernet] > > > > Thoughts on why I am not seeing a reply to the ARP request? > > My error; tcpdump does not print the destination host address in the ARP > reply, so grep didn't catch it. duh. Should have been > > tcpdump -flnt -i fxp0 | grep ARP > or > tcpdump -flnt -i fxp0 | grep aa:bb:cc:dd:ee:ff > > Also, tcpdump -e will print the ethernet header of the packet. Also, if you want to watch for only ARP requests then the filter 'arp' will limit the output to only ARP packets, e.g. - tcpdump -i fxp0 -eflnt arp will give you just the ARP traffic. Patrick --0000000000008e884e0626bd6b01 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Nov 12, 2024 at 8:35=E2=80=AFAM G= ary Aitken <freebsd@dreamchas= er.org> wrote:
On 11/11/24 21:36, Gary Aitken wrote:
> I'm having trouble with my solar inverter connecting to its home > base somewhere in Germany and am suspecting a problem with a missing > ARP reply.
...
> xxx.yyy is the inverter on the local network xxx.zzz is the fbsd
> gateway/router on the local network
>
> #tcpdump -flnt -i fxp0 | grep 192.168.xxx.yyy ARP, Request who-has
> 192.168.xxx.zzz (aa:bb:cc:dd:ee:ff) tell 192.168.xxx.yyy, length 46 > IP 192.168.xxx.yyy.3337 > 147.185.237.1.22222: Flags [.], seq
> 26043:26065, ack 708198036, win 2144, length 22 IP
> 147.185.237.1.22222 > 192.168.xxx.yyy.3337: Flags [P.], seq 1:23, a= ck
> 22, win 18410, length 22 IP 192.168.xxx.yyy.3337 >
> 147.185.237.1.22222: Flags [.], ack 23, win 2144, length 0
>
> I'm guessing the 3 packets exchanged are a power optimizer reporti= ng
> in, but may be the inverter doing something.
>
> The arp table on xxx.zzz has a permanent entry for itself on the
> interface, picked up from /etc/hosts:
>
> # arp -a ns.dreamchaser.org (192.168.xxx.zzz) at aa:bb:cc:dd:ee:ff= on
> fxp0 permanent [ethernet]
>
> Thoughts on why I am not seeing a reply to the ARP request?

My error; tcpdump does not print the destination host address in the ARP reply, so grep didn't catch it.=C2=A0 duh.=C2=A0 Should have been

=C2=A0 =C2=A0tcpdump -flnt -i fxp0 | grep ARP
or
=C2=A0 =C2=A0tcpdump -flnt -i fxp0 | grep aa:bb:cc:dd:ee:ff


Also, tcpdump -e will print the ethern= et header of the packet.=C2=A0 Also, if you want to watch for only ARP requ= ests then the filter 'arp' will limit the output to only ARP packet= s, e.g. - tcpdump -i fxp0 -eflnt arp will give you just the ARP traffic.

Patrick=C2=A0

--0000000000008e884e0626bd6b01--