Re: 13.1R problems on Pi3

On 7/4/2022 14:25, bob prohaska wrote:
> On Mon, Jul 04, 2022 at 12:17:15PM -0400, Karl Denninger wrote:
>> On 7/4/2022 11:28, bob prohaska wrote:
>>> On Sun, Jul 03, 2022 at 10:36:35PM -0400, Karl Denninger wrote:
>>>
>>> Can any sense be made of the few ping responses obtained when ntp
>>> is coming up? It's looks as if something happens after ntp runs
>>> that blocks subsequent network traffic, but why starting an outbound
>>> ping should partly unblock things is obscure to me.
>> Yes.?? The odds are reasonably high that there is confusion as to which MAC
>> address maps to which device.?? This implies there's a loop between the two
>> switches (e.g. there is more than one way for packets to get into and out of
>> each said switch to the other) or the two devices are claiming the same MAC
>> address and thus when each "speaks" and performs ARP it "grabs" the map
>> which works until the next one pipes up and it grabs it.
>>
>   
> Looks like that's the problem. There's only one cable between switches, but
> here's what I get from ifconfig on each host:

"ifconfig ue0 ether xx:xx:xx:xx:xx:xx" (or the stanza "ether xxxxx" in 
the ifconfig line in /etc/rc.conf to set the address) SHOULD work.  Be 
aware that if it scrambles things you'll have to either use a console 
cable or pull power but that is supposed to work.  You may also have to 
drop the connection to the switch (either with power or by pulling the 
ethernet cable) for it to recognize that the port has "reset" and should 
be re-learned although once again that's not SUPPOSED to be required.

I recommend using the first three octets of some manufacturer that is 
basically impossible for you ever see on your network to prevent the 
possibility of stomping on something in the future by accident.  The 
list of manufacturers can be found here:

https://gist.github.com/aallan/b4bb86db86079509e6159810ae9bd3e4

-- 
Karl Denninger
karl@denninger.net
/The Market Ticker/
/[S/MIME encrypted email preferred]/