Bug#1039928: ifupdown2: set-fec encoding auto not supported
Package: ifupdown2
Version: 3.0.0-1.1
Severity: normal
Tags: upstream
Dear Maintainer,
When using the latest ifupdown2 in Debian I get this error on an Nvidia SN2010
switch:
ifreload -a
error: swp4: cmd '/sbin/ethtool --set-fec swp4 encoding auto' failed: returned
83 (netlink error: Operation not supported)
It seems this attempts to set Forward Error Correction to Auto.
ifupdown2 version 3.0.0-1.1
ethtool version 6.1
The Spectrum (mlxsw) driver does not support --set-fec encoding auto
I can make the error go away by commenting this line:
/usr/share/ifupdown2/addons/ethtool.py
if feccmd:
try:
feccmd = ('%s --set-fec %s %s' %
(utils.ethtool_cmd, ifaceobj.name, feccmd))
#utils.exec_command(feccmd)
I asked the mlxsw developers and they responded with:
"The problem needs to be solved in ifupdown2, which should not assume that
every net device
implements these optional operations."
-- System Information:
Debian Release: 12.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-9-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_ZA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages ifupdown2 depends on:
ii iproute2 6.1.0-3
ii python3 3.11.2-1+b1
ifupdown2 recommends no packages.
Versions of packages ifupdown2 suggests:
pn bridge-utils
ii ethtool 1:6.1-1
ii isc-dhcp-client 4.4.3-P1-2
pn python3-gvgen
pn python3-mako
-- no debconf information
Bug#1005862: apt: Feature request - apt-get Source IP
Hi I figured out a temporary workaround using ‘ip netns exec’ It works, but things like apticron will still fail. -- Swimmingly, Joe swimgeek.com/blog +27 82 562 6167 instagram.com/joe.swimgeek "...all progress depends on the unreasonable man.” > On 16 Feb 2022, at 11:24, Joe Botha wrote: > > Hi > > Yes, sorry, should maybe have had title with Source _IP_address_ > > I think you should be able to specify a source IP when opening the tcp socket. > > Would probably need to add some code for IPv4 and IPv6 cases. > > -- > Swimmingly, > Joe > > swimgeek.com/blog +27 82 562 6167 instagram.com/joe.swimgeek > "...all progress depends on the unreasonable man.” > > > > >> On 16 Feb 2022, at 11:11, Julian Andres Klode wrote: >> >> On Wed, Feb 16, 2022 at 10:42:57AM +0200, Joe Botha wrote: >>> Package: apt >>> Version: 2.2.4 >>> Severity: wishlist >>> Tags: ipv6 >>> >>> Dear Maintainer, >>> >>> *** Reporter, please consider answering these questions, where appropriate >>> *** >>> >>> I use Debian on a server with multiple upstream internet links. Some of >>> these links have peering point IPs. >>> >>> It happens fairly often that apt-get traffic uses the source IP in a >>> peering point range and then downloads fail. >>> >>> Please consider adding a feature so I can configure apt-get to specify a >>> source IP or interface on the server. >>> >>> For example: traceroute has a -s option: "Chooses an alternative source >>> address." >> >> I was about to say that specifying ip addresses for sources needs to be >> solved at an RFC level (need to standardize URLs like http://foo[ip]/), >> but um now I understand that you don't want to configure the IP of the >> source, but the interface we send packets from. >> >> Probably should be retitled with a less ambiguous title :D >> >> Anyway, no idea how complex that feature is, I guess proof of >> concept patches welcome. >> >> -- >> debian developer - deb.li/jak | jak-linux.org - free software dev >> ubuntu core developer i speak de, en >
Bug#1005862: apt: Feature request - apt-get Source IP
Hi Yes, sorry, should maybe have had title with Source _IP_address_ I think you should be able to specify a source IP when opening the tcp socket. Would probably need to add some code for IPv4 and IPv6 cases. -- Swimmingly, Joe swimgeek.com/blog +27 82 562 6167 instagram.com/joe.swimgeek "...all progress depends on the unreasonable man.” > On 16 Feb 2022, at 11:11, Julian Andres Klode wrote: > > On Wed, Feb 16, 2022 at 10:42:57AM +0200, Joe Botha wrote: >> Package: apt >> Version: 2.2.4 >> Severity: wishlist >> Tags: ipv6 >> >> Dear Maintainer, >> >> *** Reporter, please consider answering these questions, where appropriate >> *** >> >> I use Debian on a server with multiple upstream internet links. Some of >> these links have peering point IPs. >> >> It happens fairly often that apt-get traffic uses the source IP in a peering >> point range and then downloads fail. >> >> Please consider adding a feature so I can configure apt-get to specify a >> source IP or interface on the server. >> >> For example: traceroute has a -s option: "Chooses an alternative source >> address." > > I was about to say that specifying ip addresses for sources needs to be > solved at an RFC level (need to standardize URLs like http://foo[ip]/), > but um now I understand that you don't want to configure the IP of the > source, but the interface we send packets from. > > Probably should be retitled with a less ambiguous title :D > > Anyway, no idea how complex that feature is, I guess proof of > concept patches welcome. > > -- > debian developer - deb.li/jak | jak-linux.org - free software dev > ubuntu core developer i speak de, en
Bug#1005862: apt: Feature request - apt-get Source IP
Package: apt Version: 2.2.4 Severity: wishlist Tags: ipv6 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** I use Debian on a server with multiple upstream internet links. Some of these links have peering point IPs. It happens fairly often that apt-get traffic uses the source IP in a peering point range and then downloads fail. Please consider adding a feature so I can configure apt-get to specify a source IP or interface on the server. For example: traceroute has a -s option: "Chooses an alternative source address." -- Package-specific info: -- (no /etc/apt/preferences present) -- -- (no /etc/apt/preferences.d/* present) -- -- (/etc/apt/sources.list present, but not submitted) -- -- (/etc/apt/sources.list.d/grafana.list present, but not submitted) -- -- (/etc/apt/sources.list.d/influxdb.list present, but not submitted) -- -- (/etc/apt/sources.list.d/ookla_speedtest-cli.list present, but not submitted) -- -- (/etc/apt/sources.list.d/saltstack.list present, but not submitted) -- -- (/etc/apt/sources.list.d/stretch-backports.list present, but not submitted) -- -- System Information: Debian Release: 11.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-11-amd64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_ZA:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages apt depends on: ii adduser 3.118 ii debian-archive-keyring 2021.1.1 ii gpgv2.2.27-2 ii libapt-pkg6.0 2.2.4 ii libc6 2.31-13+deb11u2 ii libgcc-s1 10.2.1-6 ii libgnutls30 3.7.1-5 ii libseccomp2 2.5.1-1+deb11u1 ii libstdc++6 10.2.1-6 ii libsystemd0 247.3-6 Versions of packages apt recommends: ii ca-certificates 20210119 Versions of packages apt suggests: pn apt-doc pn aptitude | synaptic | wajig ii dpkg-dev 1.20.9 ii gnupg2.2.27-2 ii powermgmt-base 1.36 -- no debconf information
Bug#958529: RFP: routinator -- Routinator 3000 is RPKI Relying Party software
Package: wnpp Severity: wishlist * Package name: routinator Version : 0.6.4 Upstream Author : Name * URL : https://www.nlnetlabs.nl/projects/rpki/routinator/ * License : BSD Programming Lang: Rust Description : Routinator 3000 is free, open source RPKI Relying Party software Routinator 3000 is RPKI Relying Party software, also known as an RPKI Validator. It is designed to have a small footprint and great portability. Routinator 3000 connects to the Trust Anchors of the five Regional Internet Registries (RIRs) — APNIC, AFRINIC, ARIN, LACNIC and RIPE NCC — downloads all of the certificates and ROAs in the various repositories and validates the signatures. It can feed the validated information to hardware routers supporting Route Origin Validation such as Juniper, Cisco and Nokia, as well as serving software solutions like BIRD, OpenBGPD, GoBGP and VyOS. Alternatively, Routinator can output the validated data in a number of useful formats, such as CSV, JSON and RPSL.
Bug#887051: RFP: openr -- Open/R extensible network routing platform Package: wnpp
Package: wnpp Severity: wishlist * Package name : openr * Upstream Author : Facebook * URL : https://github.com/facebook/openr * License : MIT * Programming Lang: C++, Python * Description : Open/R extensible network routing platform OpenR is Facebook's internally designed and developed routing protocol/platform. Originally built for performing routing on the Terragraph network, its awesome design and flexibility have led to its adoption in other networks at Facebook including our new WAN network, Express Backbone. OpenR is a free, open and extensible routing protocol/platform which provides features similar to OSPF and IS-IS. Any network with Linux based routers could benefit from this project.
Bug#523978: gqview: upgrade to v2.1.5
Hi! Please upgrade this package. 2.1.5 seems to support the CR2 (Canon RAW) format and I need that. -- Regards JoeThe reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt (.)~(.) the world to himself. Therefore all progress depends (---) on the unreasonable man. -- George Bernard Shaw -ooO-Ooo frogfoot networks +27 21 448 7225 www.frogfoot.com ( ) ( ) http://www.swimgeek.com/blog/ /|\ /|\ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
