From ibsens at ripsbusker.no.eu.org  Wed Jul  1 18:49:27 2020
From: ibsens at ripsbusker.no.eu.org (Ibsen S Ripsbusker)
Date: Wed, 01 Jul 2020 22:49:27 +0000
Subject: [talk] Tonight meeting
Message-ID: <20200701224928.6F18F328005A@mailuser.nyi.internal>

I'm going to keep this open for a while:
https://jitsi.member.fsf.org/PlasticCandidatesCircleBadly

You are welcome to talk about my computer junk or about other things.

With distinguished salutations,
Ibsen



From ibsens at ripsbusker.no.eu.org  Thu Jul  2 19:01:28 2020
From: ibsens at ripsbusker.no.eu.org (ibsens at ripsbusker.no.eu.org)
Date: Thu, 02 Jul 2020 23:01:28 +0000
Subject: [talk] Free computers
In-Reply-To: <20200624235638.07FFD306770C@mailuser.nyi.internal>
References: <20200624235638.07FFD306770C@mailuser.nyi.internal>
Message-ID: <20200702230129.059B9328005E@mailuser.nyi.internal>

I list below some things I don't want anymore. It happens there are some
related things I want to receive, so I have listed those too.



Here are some of the things I could give away today.

* Laser printer
* Networking-enabled scanner that unfortunately requires Windows
  for setup
* PCIe Radeon video cards
* SAS LTO-3 drive and tapes
* Fibre channel LTO-5 drive and tapes
* PCIe fibre channel card
* 12U 2-post rack
* supposedly-managed gigabit ethernet switches
* rackmount 8 port KVM switch with USB and HDMI
* rack panels, screws, &c.
* cables
* Two Dell T5600

It all should work with *BSD operating systems. In practice I have had
trouble with the laser printer, the tape drives, and of course the
scanner.



And here things I want. Once I have these, I can give away more stuff.

* 3TB hard drives, either SAS or SATA
* VGA monitor with a VESA mount and 4:3 aspect ratio



From george at ceetonetechnology.com  Thu Jul  2 19:59:39 2020
From: george at ceetonetechnology.com (George Rosamond)
Date: Thu, 2 Jul 2020 19:59:39 -0400
Subject: [talk] cable modems
Message-ID: <979044ac-3ed3-0282-6e64-c830b6930adc@ceetonetechnology.com>

I assume some people onlist have replaced their leased cable modems.

I'm looking at the arris touchstone tm1602a for Optimum.

Thoughts?

Better alternatives?

g



From nonesuch at longcount.org  Thu Jul  2 20:50:11 2020
From: nonesuch at longcount.org (Mark Saad)
Date: Thu, 2 Jul 2020 20:50:11 -0400
Subject: [talk] cable modems
In-Reply-To: <979044ac-3ed3-0282-6e64-c830b6930adc@ceetonetechnology.com>
References: <979044ac-3ed3-0282-6e64-c830b6930adc@ceetonetechnology.com>
Message-ID: <523B8451-7705-47E7-9F02-4D6BDD2A9EA2@longcount.org>

George
  I replaced my modem in 2018/2019 with a arris sb6183. It?s docsis 3.0 with gig Ethernet . It?s been good With the 400mbps optimum service . It tends to over heat at about 85/90 F; so I have a small usb powered fan attached to one side to cool it . The only other issue I have ; the status page on prior models was easier to parse and graph. It?s about  $65 On average . 

---
Mark Saad | nonesuch at longcount.org

> On Jul 2, 2020, at 8:00 PM, George Rosamond <george at ceetonetechnology.com> wrote:
> 
> ?I assume some people onlist have replaced their leased cable modems.
> 
> I'm looking at the arris touchstone tm1602a for Optimum.
> 
> Thoughts?
> 
> Better alternatives?
> 
> g
> 
> _______________________________________________
> talk mailing list
> talk at lists.nycbug.org
> http://lists.nycbug.org:8080/mailman/listinfo/talk



From rick at aliwalas.com  Fri Jul  3 15:51:24 2020
From: rick at aliwalas.com (Rick Aliwalas)
Date: Fri, 3 Jul 2020 15:51:24 -0400 (EDT)
Subject: [talk] cable modems
In-Reply-To: <979044ac-3ed3-0282-6e64-c830b6930adc@ceetonetechnology.com>
References: <979044ac-3ed3-0282-6e64-c830b6930adc@ceetonetechnology.com>
Message-ID: <alpine.BSO.2.20.9.2007031540050.3218@victoria.noyage.com>

I checked after reading this and it looks like our Arris SB6121
is no longer supported by comcast. No complaints though. I'll
probably shop for something on their "approved" list. I buy instead
of lease though. Not sure if you have that option w/ optimum.

On Thu, 2 Jul 2020, George Rosamond wrote:

> I assume some people onlist have replaced their leased cable modems.
>
> I'm looking at the arris touchstone tm1602a for Optimum.
>
> Thoughts?
>
> Better alternatives?
>
> g
>
> _______________________________________________
> talk mailing list
> talk at lists.nycbug.org
> http://lists.nycbug.org:8080/mailman/listinfo/talk
>



From nonesuch at longcount.org  Sat Jul 11 12:32:31 2020
From: nonesuch at longcount.org (Mark Saad)
Date: Sat, 11 Jul 2020 12:32:31 -0400
Subject: [talk] LACP debug question
Message-ID: <906D4A4A-95E1-4AB3-9D64-44DBC3987E51@longcount.org>

All
  This is a repost from net . I am looking for someone who can help me better understand this LACP disconnect that I am seeing on 12-stable . The server is a router with Solarflare nics attached to a Pair of arista 7050?s . 

Can you help me understand what I am looking at here. I enabled the lacp debug until I finally saw the issue I noted before. Due to some log rotation part of the message is clipped.
Here is a part the full thing is on patebin https://pastebin.com/BGtbxcBf


30 2020-07-09T15:47:04.145885+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0: lacp_sm_rx_timer: CURRENT -> EXPIRED
31 2020-07-09T15:47:04.145895+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0: Interface stopped DISTRIBUTING, possible flapping
32 2020-07-09T15:47:04.145895+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0: collecting enabled
33 2020-07-09T15:47:04.145896+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0: disable distributing on aggregator [(8000,00-0F-53-69-7C-20,00F2,0000,0000),(8000,46-4C-A8-68-13-47,006A,0000,0000)], nports 2 -> 1
34 2020-07-09T15:47:04.145911+00:00 ch1-c104-sdn02-mgmt kernel: sfxge1: lacp_select_tx_port: waiting transit
35 2020-07-09T15:47:04.145912+00:00 ch1-c104-sdn02-mgmt kernel: marker transmit, port=6, sys=00:0f:53:69:7c:20, id=487
36 2020-07-09T15:47:04.145912+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0: sfxge1: lacp_select_tx_port: waiting transit
37 2020-07-09T15:47:04.145913+00:00 ch1-c104-sdn02-mgmt kernel: marker transmit, port=5, sys=00:0f:53:69:7c:20, id=487
38 2020-07-09T15:47:04.145914+00:00 ch1-c104-sdn02-mgmt kernel: marker response, port=6, sys=00:0f:53:69:7c:20, id=487
39 2020-07-09T15:47:04.145914+00:00 ch1-c104-sdn02-mgmt kernel: [(8000,00-0F-53-69-7C-20,00F2,0000,0000),(8000,46-4C-A8-68-13-47,006A,0000,0000)], speed=10000000000, nports=1
40 2020-07-09T15:47:04.145922+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0: lacp_select_tx_port: waiting transit
41 2020-07-09T15:47:04.145923+00:00 ch1-c104-sdn02-mgmt kernel: lacp_select_tx_port: waiting transit
42 2020-07-09T15:47:04.145923+00:00 ch1-c104-sdn02-mgmt kernel: active aggregator not changed
43 2020-07-09T15:47:04.145924+00:00 ch1-c104-sdn02-mgmt kernel: lacp_select_tx_port: waiting transit
44 2020-07-09T15:47:04.145925+00:00 ch1-c104-sdn02-mgmt kernel: marker response, port=5, sys=00:0f:53:69:7c:20, id=487
45 2020-07-09T15:47:04.145925+00:00 ch1-c104-sdn02-mgmt kernel: lacp_select_tx_port: waiting transit
46 2020-07-09T15:47:04.145926+00:00 ch1-c104-sdn02-mgmt kernel: new [(8000,00-0F-53-69-7C-20,00F2,0000,0000),(8000,46-4C-A8-68-13-47,006A,0000,0000)]
47 2020-07-09T15:47:04.145926+00:00 ch1-c104-sdn02-mgmt kernel: Set table 1 with 1 ports
48 2020-07-09T15:47:04.145927+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0: mux_state 4 -> 3
49 2020-07-09T15:47:04.145928+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0: collecting disabled
50 2020-07-09T15:47:04.145930+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0: mux_state 3 -> 2
51 2020-07-09T15:47:04.145931+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0: lacpdu transmit
52 2020-07-09T15:47:04.145931+00:00 ch1-c104-sdn02-mgmt kernel: actor=(8000,00-0F-53-69-7C-20,00F2,8000,0005)
53 2020-07-09T15:47:04.145932+00:00 ch1-c104-sdn02-mgmt kernel: actor.state=8d<ACTIVITY,AGGREGATION,SYNC,EXPIRED>
54 2020-07-09T15:47:04.145932+00:00 ch1-c104-sdn02-mgmt kernel: partner=(8000,46-4C-A8-68-13-47,006A,8000,0006)
55 2020-07-09T15:47:04.145933+00:00 ch1-c104-sdn02-mgmt kernel: partner.state=37<ACTIVITY,TIMEOUT,AGGREGATION,COLLECTING,DISTRIBUTING>
56 2020-07-09T15:47:04.145935+00:00 ch1-c104-sdn02-mgmt kernel: maxdelay=0
57 2020-07-09T15:47:04.145937+00:00 ch1-c104-sdn02-mgmt kernel: queue flush complete
---
Mark Saad | nonesuch at longcount.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.nycbug.org:8443/pipermail/talk/attachments/20200711/314f7014/attachment.htm>

From kmsujit at gmail.com  Sun Jul 12 06:22:11 2020
From: kmsujit at gmail.com (Sujit K M)
Date: Sun, 12 Jul 2020 15:52:11 +0530
Subject: [talk] LACP debug question
In-Reply-To: <906D4A4A-95E1-4AB3-9D64-44DBC3987E51@longcount.org>
References: <906D4A4A-95E1-4AB3-9D64-44DBC3987E51@longcount.org>
Message-ID: <CA+6mNep5=-R41pPdEn8yLFoCvDa1E1Ew_8YYcS9U2LB7C7hTGg@mail.gmail.com>

On Sat, Jul 11, 2020, 10:03 PM Mark Saad <nonesuch at longcount.org> wrote:

> All
>   This is a repost from net . I am looking for someone who can help me
> better understand this LACP disconnect that I am seeing on 12-stable . The
> server is a router with Solarflare nics attached to a Pair of arista 7050?s
> .
>
> Can you help me understand what I am looking at here. I enabled the lacp
> debug until I finally saw the issue I noted before. Due to some log
> rotation part of the message is clipped.
> Here is a part the full thing is on patebin https://pastebin.com/BGtbxcBf
>
>
> 30 2020-07-09T15:47:04.145885+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0:
> lacp_sm_rx_timer: CURRENT -> EXPIRED
> 31 2020-07-09T15:47:04.145895+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0:
> Interface stopped DISTRIBUTING, possible flapping
> 32 2020-07-09T15:47:04.145895+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0:
> collecting enabled
>

https://en.m.wikipedia.org/wiki/Link_aggregation#:~:text=Within%20the%20IEEE%20specification%2C%20the,form%20a%20single%20logical%20channel
.

The expired and stopped distribution might beat the purpose of LACP.

>
> 33 2020-07-09T15:47:04.145896+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0:
> disable distributing on aggregator
> [(8000,00-0F-53-69-7C-20,00F2,0000,0000),(8000,46-4C-A8-68-13-47,006A,0000,0000)],
> nports 2 -> 1
> 34 2020-07-09T15:47:04.145911+00:00 ch1-c104-sdn02-mgmt kernel: sfxge1:
> lacp_select_tx_port: waiting transit
> 35 2020-07-09T15:47:04.145912+00:00 ch1-c104-sdn02-mgmt kernel: marker
> transmit, port=6, sys=00:0f:53:69:7c:20, id=487
> 36 2020-07-09T15:47:04.145912+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0:
> sfxge1: lacp_select_tx_port: waiting transit
> 37 2020-07-09T15:47:04.145913+00:00 ch1-c104-sdn02-mgmt kernel: marker
> transmit, port=5, sys=00:0f:53:69:7c:20, id=487
> 38 2020-07-09T15:47:04.145914+00:00 ch1-c104-sdn02-mgmt kernel: marker
> response, port=6, sys=00:0f:53:69:7c:20, id=487
> 39 2020-07-09T15:47:04.145914+00:00 ch1-c104-sdn02-mgmt kernel:
> [(8000,00-0F-53-69-7C-20,00F2,0000,0000),(8000,46-4C-A8-68-13-47,006A,0000,0000)],
> speed=10000000000, nports=1
> 40 2020-07-09T15:47:04.145922+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0:
> lacp_select_tx_port: waiting transit
> 41 2020-07-09T15:47:04.145923+00:00 ch1-c104-sdn02-mgmt kernel:
> lacp_select_tx_port: waiting transit
> 42 2020-07-09T15:47:04.145923+00:00 ch1-c104-sdn02-mgmt kernel: active
> aggregator not changed
> 43 2020-07-09T15:47:04.145924+00:00 ch1-c104-sdn02-mgmt kernel:
> lacp_select_tx_port: waiting transit
> 44 2020-07-09T15:47:04.145925+00:00 ch1-c104-sdn02-mgmt kernel: marker
> response, port=5, sys=00:0f:53:69:7c:20, id=487
> 45 2020-07-09T15:47:04.145925+00:00 ch1-c104-sdn02-mgmt kernel:
> lacp_select_tx_port: waiting transit
> 46 2020-07-09T15:47:04.145926+00:00 ch1-c104-sdn02-mgmt kernel: new
> [(8000,00-0F-53-69-7C-20,00F2,0000,0000),(8000,46-4C-A8-68-13-47,006A,0000,0000)]
> 47 2020-07-09T15:47:04.145926+00:00 ch1-c104-sdn02-mgmt kernel: Set table
> 1 with 1 ports
> 48 2020-07-09T15:47:04.145927+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0:
> mux_state 4 -> 3
> 49 2020-07-09T15:47:04.145928+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0:
> collecting disabled
> 50 2020-07-09T15:47:04.145930+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0:
> mux_state 3 -> 2
> 51 2020-07-09T15:47:04.145931+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0:
> lacpdu transmit
> 52 2020-07-09T15:47:04.145931+00:00 ch1-c104-sdn02-mgmt kernel:
> actor=(8000,00-0F-53-69-7C-20,00F2,8000,0005)
> 53 2020-07-09T15:47:04.145932+00:00 ch1-c104-sdn02-mgmt kernel:
> actor.state=8d<ACTIVITY,AGGREGATION,SYNC,EXPIRED>
> 54 2020-07-09T15:47:04.145932+00:00 ch1-c104-sdn02-mgmt kernel:
> partner=(8000,46-4C-A8-68-13-47,006A,8000,0006)
> 55 2020-07-09T15:47:04.145933+00:00 ch1-c104-sdn02-mgmt kernel:
> partner.state=37<ACTIVITY,TIMEOUT,AGGREGATION,COLLECTING,DISTRIBUTING>
> 56 2020-07-09T15:47:04.145935+00:00 ch1-c104-sdn02-mgmt kernel: maxdelay=0
> 57 2020-07-09T15:47:04.145937+00:00 ch1-c104-sdn02-mgmt kernel: queue
> flush complete
> ---
> Mark Saad | nonesuch at longcount.org
> _______________________________________________
> talk mailing list
> talk at lists.nycbug.org
> http://lists.nycbug.org:8080/mailman/listinfo/talk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.nycbug.org:8443/pipermail/talk/attachments/20200712/8a68fc39/attachment.htm>

From nonesuch at longcount.org  Sun Jul 12 11:58:23 2020
From: nonesuch at longcount.org (Mark Saad)
Date: Sun, 12 Jul 2020 11:58:23 -0400
Subject: [talk] LACP debug question
In-Reply-To: <CA+6mNep5=-R41pPdEn8yLFoCvDa1E1Ew_8YYcS9U2LB7C7hTGg@mail.gmail.com>
References: <CA+6mNep5=-R41pPdEn8yLFoCvDa1E1Ew_8YYcS9U2LB7C7hTGg@mail.gmail.com>
Message-ID: <F2E6ECD9-8C81-4A4A-AD5D-4B6C6BF14E95@longcount.org>

Sujit
  I know that this is LACP debug . I am trying to understand the specific conditions that this LACP disconnect sequence is occurring.  It?s a odd thing, it?s happening during times of relatively low was tcp traffic . The router and is not highly loaded and I can?t find a reason why this is occurring . 


---
Mark Saad | nonesuch at longcount.org

On Jul 12, 2020, at 6:22 AM, Sujit K M <kmsujit at gmail.com> wrote:
> 
> ?
> 
> 
>> On Sat, Jul 11, 2020, 10:03 PM Mark Saad <nonesuch at longcount.org> wrote:
>> All
>>   This is a repost from net . I am looking for someone who can help me better understand this LACP disconnect that I am seeing on 12-stable . The server is a router with Solarflare nics attached to a Pair of arista 7050?s . 
>> 
>> Can you help me understand what I am looking at here. I enabled the lacp debug until I finally saw the issue I noted before. Due to some log rotation part of the message is clipped.
>> Here is a part the full thing is on patebin https://pastebin.com/BGtbxcBf
>> 
>> 
>> 30 2020-07-09T15:47:04.145885+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0: lacp_sm_rx_timer: CURRENT -> EXPIRED
>> 31 2020-07-09T15:47:04.145895+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0: Interface stopped DISTRIBUTING, possible flapping
>> 32 2020-07-09T15:47:04.145895+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0: collecting enabled
> 
> 
> https://en.m.wikipedia.org/wiki/Link_aggregation#:~:text=Within%20the%20IEEE%20specification%2C%20the,form%20a%20single%20logical%20channel.
> 
> The expired and stopped distribution might beat the purpose of LACP.
>> 
>> 33 2020-07-09T15:47:04.145896+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0: disable distributing on aggregator [(8000,00-0F-53-69-7C-20,00F2,0000,0000),(8000,46-4C-A8-68-13-47,006A,0000,0000)], nports 2 -> 1
>> 34 2020-07-09T15:47:04.145911+00:00 ch1-c104-sdn02-mgmt kernel: sfxge1: lacp_select_tx_port: waiting transit
>> 35 2020-07-09T15:47:04.145912+00:00 ch1-c104-sdn02-mgmt kernel: marker transmit, port=6, sys=00:0f:53:69:7c:20, id=487
>> 36 2020-07-09T15:47:04.145912+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0: sfxge1: lacp_select_tx_port: waiting transit
>> 37 2020-07-09T15:47:04.145913+00:00 ch1-c104-sdn02-mgmt kernel: marker transmit, port=5, sys=00:0f:53:69:7c:20, id=487
>> 38 2020-07-09T15:47:04.145914+00:00 ch1-c104-sdn02-mgmt kernel: marker response, port=6, sys=00:0f:53:69:7c:20, id=487
>> 39 2020-07-09T15:47:04.145914+00:00 ch1-c104-sdn02-mgmt kernel: [(8000,00-0F-53-69-7C-20,00F2,0000,0000),(8000,46-4C-A8-68-13-47,006A,0000,0000)], speed=10000000000, nports=1
>> 40 2020-07-09T15:47:04.145922+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0: lacp_select_tx_port: waiting transit
>> 41 2020-07-09T15:47:04.145923+00:00 ch1-c104-sdn02-mgmt kernel: lacp_select_tx_port: waiting transit
>> 42 2020-07-09T15:47:04.145923+00:00 ch1-c104-sdn02-mgmt kernel: active aggregator not changed
>> 43 2020-07-09T15:47:04.145924+00:00 ch1-c104-sdn02-mgmt kernel: lacp_select_tx_port: waiting transit
>> 44 2020-07-09T15:47:04.145925+00:00 ch1-c104-sdn02-mgmt kernel: marker response, port=5, sys=00:0f:53:69:7c:20, id=487
>> 45 2020-07-09T15:47:04.145925+00:00 ch1-c104-sdn02-mgmt kernel: lacp_select_tx_port: waiting transit
>> 46 2020-07-09T15:47:04.145926+00:00 ch1-c104-sdn02-mgmt kernel: new [(8000,00-0F-53-69-7C-20,00F2,0000,0000),(8000,46-4C-A8-68-13-47,006A,0000,0000)]
>> 47 2020-07-09T15:47:04.145926+00:00 ch1-c104-sdn02-mgmt kernel: Set table 1 with 1 ports
>> 48 2020-07-09T15:47:04.145927+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0: mux_state 4 -> 3
>> 49 2020-07-09T15:47:04.145928+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0: collecting disabled
>> 50 2020-07-09T15:47:04.145930+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0: mux_state 3 -> 2
>> 51 2020-07-09T15:47:04.145931+00:00 ch1-c104-sdn02-mgmt kernel: sfxge0: lacpdu transmit
>> 52 2020-07-09T15:47:04.145931+00:00 ch1-c104-sdn02-mgmt kernel: actor=(8000,00-0F-53-69-7C-20,00F2,8000,0005)
>> 53 2020-07-09T15:47:04.145932+00:00 ch1-c104-sdn02-mgmt kernel: actor.state=8d<ACTIVITY,AGGREGATION,SYNC,EXPIRED>
>> 54 2020-07-09T15:47:04.145932+00:00 ch1-c104-sdn02-mgmt kernel: partner=(8000,46-4C-A8-68-13-47,006A,8000,0006)
>> 55 2020-07-09T15:47:04.145933+00:00 ch1-c104-sdn02-mgmt kernel: partner.state=37<ACTIVITY,TIMEOUT,AGGREGATION,COLLECTING,DISTRIBUTING>
>> 56 2020-07-09T15:47:04.145935+00:00 ch1-c104-sdn02-mgmt kernel: maxdelay=0
>> 57 2020-07-09T15:47:04.145937+00:00 ch1-c104-sdn02-mgmt kernel: queue flush complete
>> ---
>> Mark Saad | nonesuch at longcount.org
>> _______________________________________________
>> talk mailing list
>> talk at lists.nycbug.org
>> http://lists.nycbug.org:8080/mailman/listinfo/talk
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.nycbug.org:8443/pipermail/talk/attachments/20200712/b56f7a3f/attachment.htm>

From pete at nomadlogic.org  Mon Jul 13 19:51:42 2020
From: pete at nomadlogic.org (Pete Wright)
Date: Mon, 13 Jul 2020 16:51:42 -0700
Subject: [talk] LACP debug question
In-Reply-To: <906D4A4A-95E1-4AB3-9D64-44DBC3987E51@longcount.org>
References: <906D4A4A-95E1-4AB3-9D64-44DBC3987E51@longcount.org>
Message-ID: <c99b357d-cded-e235-1f3c-0edb8a974555@nomadlogic.org>



On 7/11/20 9:32 AM, Mark Saad wrote:
> All
> ? This is a repost from net . I am looking for someone who can help me 
> better understand this LACP disconnect that I am seeing on 12-stable . 
> The server is a router with Solarflare nics attached to a Pair of 
> arista 7050?s .
>
> Can you help me understand what I am looking at here. I enabled the 
> lacp debug until I finally saw the issue I noted before. Due to some 
> log rotation part of the message is clipped.
> Here is a part the full thing is on patebin https://pastebin.com/BGtbxcBf
>

ouch this looks like a PITA to debug.? were you able to make any 
progress?? in the past when i ran into LACP issues on arista (both using 
linux and bsd) i had to fight issues with bad optics or cables.? i'm 
guessing the logs from the switch aren't too helpful either?

i've used the sfxge cards before and found them to be pretty darn stable...

is this happening in any of the LACP modes, or just one of them?

-p

-- 
Pete Wright
pete at nomadlogic.org
@nomadlogicLA

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.nycbug.org:8443/pipermail/talk/attachments/20200713/0594a16f/attachment.htm>

From nonesuch at longcount.org  Tue Jul 14 16:02:35 2020
From: nonesuch at longcount.org (Mark Saad)
Date: Tue, 14 Jul 2020 16:02:35 -0400
Subject: [talk] LACP debug question
In-Reply-To: <c99b357d-cded-e235-1f3c-0edb8a974555@nomadlogic.org>
References: <906D4A4A-95E1-4AB3-9D64-44DBC3987E51@longcount.org>
 <c99b357d-cded-e235-1f3c-0edb8a974555@nomadlogic.org>
Message-ID: <CAMXt9NbR=zz5dp_P9ChvOskmdpqQtvE+qE1wye=u497otyxi6g@mail.gmail.com>

On Mon, Jul 13, 2020 at 7:51 PM Pete Wright <pete at nomadlogic.org> wrote:
>
>
>
> On 7/11/20 9:32 AM, Mark Saad wrote:
>
> All
>   This is a repost from net . I am looking for someone who can help me better understand this LACP disconnect that I am seeing on 12-stable . The server is a router with Solarflare nics attached to a Pair of arista 7050?s .
>
> Can you help me understand what I am looking at here. I enabled the lacp debug until I finally saw the issue I noted before. Due to some log rotation part of the message is clipped.
> Here is a part the full thing is on patebin https://pastebin.com/BGtbxcBf
>
>
> ouch this looks like a PITA to debug.  were you able to make any progress?  in the past when i ran into LACP issues on arista (both using linux and bsd) i had to fight issues with bad optics or cables.  i'm guessing the logs from the switch aren't too helpful either?

Switch logs are saying that the server disconnected. At this point I
know Its not the cables, I use 10G DAC's and I have a variety in use
Arisa, Fiberstore, and Mellanox .  To be clear I am seeing this across
a bunch of routers. The only commonality here is that it breaking on
routers on Arista EOS  4.20.12M or later. It does not happen on
4.18.5M or earlier.  Arista has said there was no changes in how LACP
works between versions but I can't put my finger on it.  Maybe the
timing has changed ?

> i've used the sfxge cards before and found them to be pretty darn stable...
>

I have found them to be fairly consistent . The only thing that sounds
like it could be related was this thread

https://www.mail-archive.com/freebsd-net at freebsd.org/msg62552.html

> is this happening in any of the LACP modes, or just one of them?

I only use Active / Active

>
> -p
>
> --
> Pete Wright
> pete at nomadlogic.org
> @nomadlogicLA



-- 
mark saad | nonesuch at longcount.org



From nonesuch at longcount.org  Tue Jul 14 16:26:22 2020
From: nonesuch at longcount.org (Mark Saad)
Date: Tue, 14 Jul 2020 16:26:22 -0400
Subject: [talk] LACP debug question
In-Reply-To: <CAMXt9NbR=zz5dp_P9ChvOskmdpqQtvE+qE1wye=u497otyxi6g@mail.gmail.com>
References: <906D4A4A-95E1-4AB3-9D64-44DBC3987E51@longcount.org>
 <c99b357d-cded-e235-1f3c-0edb8a974555@nomadlogic.org>
 <CAMXt9NbR=zz5dp_P9ChvOskmdpqQtvE+qE1wye=u497otyxi6g@mail.gmail.com>
Message-ID: <CAMXt9NYj6c6YuHEqHumtSXuOTN4o+gt5LUyuZMyREYhD3_xDWQ@mail.gmail.com>

Pete
   I believe that what the issue could be is LACP  responses are not
being prioritized when being sent out.  Do you know of a way to make
the sfxge driver reserve queue 0 for now flowid packets. This is what
was done in the chelsio fix above.

Anyone have a clue how to do this in the driver  ?

On Tue, Jul 14, 2020 at 4:02 PM Mark Saad <nonesuch at longcount.org> wrote:
>
> On Mon, Jul 13, 2020 at 7:51 PM Pete Wright <pete at nomadlogic.org> wrote:
> >
> >
> >
> > On 7/11/20 9:32 AM, Mark Saad wrote:
> >
> > All
> >   This is a repost from net . I am looking for someone who can help me better understand this LACP disconnect that I am seeing on 12-stable . The server is a router with Solarflare nics attached to a Pair of arista 7050?s .
> >
> > Can you help me understand what I am looking at here. I enabled the lacp debug until I finally saw the issue I noted before. Due to some log rotation part of the message is clipped.
> > Here is a part the full thing is on patebin https://pastebin.com/BGtbxcBf
> >
> >
> > ouch this looks like a PITA to debug.  were you able to make any progress?  in the past when i ran into LACP issues on arista (both using linux and bsd) i had to fight issues with bad optics or cables.  i'm guessing the logs from the switch aren't too helpful either?
>
> Switch logs are saying that the server disconnected. At this point I
> know Its not the cables, I use 10G DAC's and I have a variety in use
> Arisa, Fiberstore, and Mellanox .  To be clear I am seeing this across
> a bunch of routers. The only commonality here is that it breaking on
> routers on Arista EOS  4.20.12M or later. It does not happen on
> 4.18.5M or earlier.  Arista has said there was no changes in how LACP
> works between versions but I can't put my finger on it.  Maybe the
> timing has changed ?
>
> > i've used the sfxge cards before and found them to be pretty darn stable...
> >
>
> I have found them to be fairly consistent . The only thing that sounds
> like it could be related was this thread
>
> https://www.mail-archive.com/freebsd-net at freebsd.org/msg62552.html
>
> > is this happening in any of the LACP modes, or just one of them?
>
> I only use Active / Active
>
> >
> > -p
> >
> > --
> > Pete Wright
> > pete at nomadlogic.org
> > @nomadlogicLA
>
>
>
> --
> mark saad | nonesuch at longcount.org



-- 
mark saad | nonesuch at longcount.org



From pete at nomadlogic.org  Tue Jul 14 20:44:24 2020
From: pete at nomadlogic.org (Pete Wright)
Date: Tue, 14 Jul 2020 17:44:24 -0700
Subject: [talk] LACP debug question
In-Reply-To: <CAMXt9NYj6c6YuHEqHumtSXuOTN4o+gt5LUyuZMyREYhD3_xDWQ@mail.gmail.com>
References: <906D4A4A-95E1-4AB3-9D64-44DBC3987E51@longcount.org>
 <c99b357d-cded-e235-1f3c-0edb8a974555@nomadlogic.org>
 <CAMXt9NbR=zz5dp_P9ChvOskmdpqQtvE+qE1wye=u497otyxi6g@mail.gmail.com>
 <CAMXt9NYj6c6YuHEqHumtSXuOTN4o+gt5LUyuZMyREYhD3_xDWQ@mail.gmail.com>
Message-ID: <6fd33420-86e9-0224-f4f8-b12ce376d3ed@nomadlogic.org>



On 7/14/20 1:26 PM, Mark Saad wrote:
> Pete
>     I believe that what the issue could be is LACP  responses are not
> being prioritized when being sent out.  Do you know of a way to make
> the sfxge driver reserve queue 0 for now flowid packets. This is what
> was done in the chelsio fix above.
>
> Anyone have a clue how to do this in the driver  ?

i seem to remember doing something similar with the solarflare sfctool 
in their utilities package, but that is linux only unfortunately :/

-pete

-- 
Pete Wright
pete at nomadlogic.org
@nomadlogicLA



From callab5 at rpi.edu  Wed Jul 15 18:36:08 2020
From: callab5 at rpi.edu (Callahan, Brian Robert)
Date: Wed, 15 Jul 2020 22:36:08 +0000
Subject: [talk] A FreeBSD phone lives
Message-ID: <911B5DC0C5580D42B53878CB5930DCB49ACDCE70@EX14MB5.win.rpi.edu>

Not sure how many people noticed this on our dmesgd:
https://dmesgd.nycbug.org/index.cgi?do=view&id=5574

@nrgmilk_, if you're on this list, reply and tell us more about your work!

~Brian

________________________________
Brian Robert Callahan, Ph.D.
Lecturer, ITWS at RPI
Office: Amos Eaton 132
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.nycbug.org:8443/pipermail/talk/attachments/20200715/d32e1759/attachment.htm>

From pete at nomadlogic.org  Wed Jul 15 20:48:37 2020
From: pete at nomadlogic.org (Pete Wright)
Date: Wed, 15 Jul 2020 17:48:37 -0700
Subject: [talk] A FreeBSD phone lives
In-Reply-To: <911B5DC0C5580D42B53878CB5930DCB49ACDCE70@EX14MB5.win.rpi.edu>
References: <911B5DC0C5580D42B53878CB5930DCB49ACDCE70@EX14MB5.win.rpi.edu>
Message-ID: <5755d866-7bcd-ba32-0b4f-6d6612d84629@nomadlogic.org>



On 7/15/20 3:36 PM, Callahan, Brian Robert wrote:
> Not sure how many people noticed this on our dmesgd:
> https://dmesgd.nycbug.org/index.cgi?do=view&id=5574
>
> @nrgmilk_, if you're on this list, reply and tell us more about your work!

hey that's awesome!

-pete


-- 
Pete Wright
pete at nomadlogic.org
@nomadlogicLA

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.nycbug.org:8443/pipermail/talk/attachments/20200715/7dfd7932/attachment.htm>

From Assafr at protonmail.com  Thu Jul 16 13:52:23 2020
From: Assafr at protonmail.com (assaf)
Date: Thu, 16 Jul 2020 17:52:23 +0000
Subject: [talk] A FreeBSD phone lives
In-Reply-To: <911B5DC0C5580D42B53878CB5930DCB49ACDCE70@EX14MB5.win.rpi.edu>
References: <911B5DC0C5580D42B53878CB5930DCB49ACDCE70@EX14MB5.win.rpi.edu>
Message-ID: <LG7zDnRJvtbeHul-Sk2abx6_40EShat_YNUFfg7_1cX2zXBZlaUDH-Z12Y3PRqQJf9Dp60zROtnRp_XV8ND7I3Gi99gmJ3ilDR9lijsrnTY=@protonmail.com>

Very cool indeed!

Sent from ProtonMail mobile

-------- Original Message --------
On Jul 15, 2020, 5:36 PM, Callahan, Brian Robert wrote:

> Not sure how many people noticed this on our dmesgd:
> https://dmesgd.nycbug.org/index.cgi?do=view&id=5574
>
> @nrgmilk_, if you're on this list, reply and tell us more about your work!
>
> ~Brian
>
> ---------------------------------------------------------------
> Brian Robert Callahan, Ph.D.
> Lecturer, ITWS at RPI
> Office: Amos Eaton 132
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.nycbug.org:8443/pipermail/talk/attachments/20200716/b200ce97/attachment.htm>

From gnn at neville-neil.com  Thu Jul 16 17:06:57 2020
From: gnn at neville-neil.com (George Neville-Neil)
Date: Thu, 16 Jul 2020 17:06:57 -0400
Subject: [talk] A FreeBSD phone lives
In-Reply-To: <LG7zDnRJvtbeHul-Sk2abx6_40EShat_YNUFfg7_1cX2zXBZlaUDH-Z12Y3PRqQJf9Dp60zROtnRp_XV8ND7I3Gi99gmJ3ilDR9lijsrnTY=@protonmail.com>
References: <911B5DC0C5580D42B53878CB5930DCB49ACDCE70@EX14MB5.win.rpi.edu>
 <LG7zDnRJvtbeHul-Sk2abx6_40EShat_YNUFfg7_1cX2zXBZlaUDH-Z12Y3PRqQJf9Dp60zROtnRp_XV8ND7I3Gi99gmJ3ilDR9lijsrnTY=@protonmail.com>
Message-ID: <9F26D5A3-01B6-41BA-84A2-20B7E70F75CF@neville-neil.com>

Note that it "works" because it's the same as something we already run 
on, but it doesn't actually work as a FreeBSD phone.  A few of us have 
reached out to the tweeter to encourage and see where they're going with 
this.

Best,
George


On 16 Jul 2020, at 13:52, assaf wrote:

> Very cool indeed!
>
> Sent from ProtonMail mobile
>
> -------- Original Message --------
> On Jul 15, 2020, 5:36 PM, Callahan, Brian Robert wrote:
>
>> Not sure how many people noticed this on our dmesgd:
>> https://dmesgd.nycbug.org/index.cgi?do=view&id=5574
>>
>> @nrgmilk_, if you're on this list, reply and tell us more about your 
>> work!
>>
>> ~Brian
>>
>> ---------------------------------------------------------------
>> Brian Robert Callahan, Ph.D.
>> Lecturer, ITWS at RPI
>> Office: Amos Eaton 132


> _______________________________________________
> talk mailing list
> talk at lists.nycbug.org
> http://lists.nycbug.org:8080/mailman/listinfo/talk
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.nycbug.org:8443/pipermail/talk/attachments/20200716/893a2b47/attachment.htm>

From george at ceetonetechnology.com  Thu Jul 16 22:29:53 2020
From: george at ceetonetechnology.com (George Rosamond)
Date: Thu, 16 Jul 2020 22:29:53 -0400
Subject: [talk] A FreeBSD phone lives
In-Reply-To: <9F26D5A3-01B6-41BA-84A2-20B7E70F75CF@neville-neil.com>
References: <911B5DC0C5580D42B53878CB5930DCB49ACDCE70@EX14MB5.win.rpi.edu>
 <LG7zDnRJvtbeHul-Sk2abx6_40EShat_YNUFfg7_1cX2zXBZlaUDH-Z12Y3PRqQJf9Dp60zROtnRp_XV8ND7I3Gi99gmJ3ilDR9lijsrnTY=@protonmail.com>
 <9F26D5A3-01B6-41BA-84A2-20B7E70F75CF@neville-neil.com>
Message-ID: <04b7d9f1-e9b8-1b92-8148-7230b6e8031c@ceetonetechnology.com>

On 7/16/20 5:06 PM, George Neville-Neil wrote:
> Note that it "works" because it's the same as something we already run
> on, but it doesn't actually work as a FreeBSD phone.? A few of us have
> reached out to the tweeter to encourage and see where they're going with
> this.

Right, I think it's relatively simple to run a BSD that has an arm64
port on the PinePhone.

https://www.pine64.org/pinephone/

But yes, as GNN said, modem support is another story, and those are
mostly proprietary binaries AFAIK.

OTOH, what's wrong with a device with a phone footprint that can run a
BSD in your pocket, just using wireless, assuming that chipset is
supported?  A good option for $150, especially compared to the GPD or
something.

But oddly, the dmesgd lists the awg driver but no man page?

awg0: <Allwinner Gigabit Ethernet> mem 0x1c30000-0x1c3ffff irq 43 on
simplebus0
awg0: cannot allocate resources for device

The other issue is ACPI/power management/hibernation. I know the dev
versions of the default Linux on the PinePhone have pretty crappy
battery life, but even the stable version isn't too grand IIRC.

Regardless, I really give huge props to the Pine64 people. They deserve
support, and we'll all be better off if *BSD devs can put time into
their devices.

g



From spork at bway.net  Thu Jul 16 23:01:56 2020
From: spork at bway.net (Charles Sprickman)
Date: Thu, 16 Jul 2020 23:01:56 -0400
Subject: [talk] A FreeBSD phone lives
In-Reply-To: <04b7d9f1-e9b8-1b92-8148-7230b6e8031c@ceetonetechnology.com>
References: <911B5DC0C5580D42B53878CB5930DCB49ACDCE70@EX14MB5.win.rpi.edu>
 <LG7zDnRJvtbeHul-Sk2abx6_40EShat_YNUFfg7_1cX2zXBZlaUDH-Z12Y3PRqQJf9Dp60zROtnRp_XV8ND7I3Gi99gmJ3ilDR9lijsrnTY=@protonmail.com>
 <9F26D5A3-01B6-41BA-84A2-20B7E70F75CF@neville-neil.com>
 <04b7d9f1-e9b8-1b92-8148-7230b6e8031c@ceetonetechnology.com>
Message-ID: <176B46D7-6F59-41CD-825D-46A5668DF887@bway.net>



> On Jul 16, 2020, at 10:29 PM, George Rosamond <george at ceetonetechnology.com> wrote:
> 
> On 7/16/20 5:06 PM, George Neville-Neil wrote:
>> Note that it "works" because it's the same as something we already run
>> on, but it doesn't actually work as a FreeBSD phone.  A few of us have
>> reached out to the tweeter to encourage and see where they're going with
>> this.
> 
> Right, I think it's relatively simple to run a BSD that has an arm64
> port on the PinePhone.
> 
> https://www.pine64.org/pinephone/
> 
> But yes, as GNN said, modem support is another story, and those are
> mostly proprietary binaries AFAIK.
> 
> OTOH, what's wrong with a device with a phone footprint that can run a
> BSD in your pocket, just using wireless, assuming that chipset is
> supported?  A good option for $150, especially compared to the GPD or
> something.

This looks interesting too - a perhaps-BSD-friendly tablet for a bit over $100:

https://webcache.googleusercontent.com/search?q=cache:wQMLqGOVkn0J:https://store.pine64.org/product/pinetab-10-1-linux-tablet-with-detached-backlit-keyboard/+&cd=2&hl=en&ct=clnk&gl=us&client=safari <https://webcache.googleusercontent.com/search?q=cache:wQMLqGOVkn0J:https://store.pine64.org/product/pinetab-10-1-linux-tablet-with-detached-backlit-keyboard/+&cd=2&hl=en&ct=clnk&gl=us&client=safari> (their site is down currently)

https://store.pine64.org/product/pinetab-10-1-linux-tablet-with-detached-backlit-keyboard/ <https://store.pine64.org/product/pinetab-10-1-linux-tablet-with-detached-backlit-keyboard/>

Charles

> 
> But oddly, the dmesgd lists the awg driver but no man page?
> 
> awg0: <Allwinner Gigabit Ethernet> mem 0x1c30000-0x1c3ffff irq 43 on
> simplebus0
> awg0: cannot allocate resources for device
> 
> The other issue is ACPI/power management/hibernation. I know the dev
> versions of the default Linux on the PinePhone have pretty crappy
> battery life, but even the stable version isn't too grand IIRC.
> 
> Regardless, I really give huge props to the Pine64 people. They deserve
> support, and we'll all be better off if *BSD devs can put time into
> their devices.
> 
> g
> 
> _______________________________________________
> talk mailing list
> talk at lists.nycbug.org
> http://lists.nycbug.org:8080/mailman/listinfo/talk

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.nycbug.org:8443/pipermail/talk/attachments/20200716/7b9b9dbb/attachment.htm>

From callab5 at rpi.edu  Fri Jul 31 17:44:26 2020
From: callab5 at rpi.edu (Callahan, Brian Robert)
Date: Fri, 31 Jul 2020 21:44:26 +0000
Subject: [talk] dual band usb wifi
Message-ID: <911B5DC0C5580D42B53878CB5930DCB49ACDDF23@EX14MB5.win.rpi.edu>

Hi talk --

The question of USB wifi comes up from time to time. Usually people recommend urtwn(4) devices because they are small and cheap and readily available. But they are 2.4 GHz only.

If you're looking for a dual band USB wifi device, google BCM43236. I picked one up from aliexpress. Works ootb on OpenBSD with bwfm(4). It's definitely not small (mine even has a 7" sma antenna!) but it is nice to know that I have a usb wifi adapter that can use the 5 GHz band.

~Brian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.nycbug.org:8443/pipermail/talk/attachments/20200731/000505ea/attachment.htm>