Bug#820212: iproute2: Colons in ethernet names under /sbin/ifconfig and /sbin/ip are not being recognized in Stretch

Hello Bob, Now we're on the same page, that was an excellent read. If I could change the script, I would. But it's maintained by the company who makes the firewall agent and application, so a simple awk or cut will break the whole operation of the agent if it's not made upstream. Their source

Bug#820212: iproute2: Colons in ethernet names under /sbin/ifconfig and /sbin/ip are not being recognized in Stretch

reassign 820212 net-tools found 820212 1.60+git20150829.73cef8a-2 retitle 820212 ifconfig output format change breaks downstream programs thanks Hi Justin, Justin McZeal wrote: > Starting from the beginning, ... :-) > there is this firewall agent we have Reading your latest I think I

Bug#820212: iproute2: Colons in ethernet names under /sbin/ifconfig and /sbin/ip are not being recognized in Stretch

Hello Bob, I went ahead and removed eth0:1 as we don't use it. So let's negate that factor and start over. Starting from the beginning, there is this firewall agent we have installed that uses some custom coding to grab the interfaces on our server. Their agent is only working on Debian 8

Bug#820212: iproute2: Colons in ethernet names under /sbin/ifconfig and /sbin/ip are not being recognized in Stretch

Justin McZeal wrote: > and /sbin/ip -o link show eth0:1: to both come up without a > hitch. The ones without the colon have been tested to fully work on > a stock Debian 8 (jessie) image, not Debian 9 (stretch). I cannot reproduce this on stock Jessie 8.4. It needs "eth0" not "eth0:1". Note

Bug#820212: iproute2: Colons in ethernet names under /sbin/ifconfig and /sbin/ip are not being recognized in Stretch

Hello Andreas, The interface is actually auto-configured through Linode. The extra fake interface is not the concern, as we don't even use eth0:1. iface eth0 inet static address 96.126.108.191/24 gateway 96.126.108.1 up ip addr add 192.168.135.145/17 dev eth0 label eth0:1 down

Bug#820212: iproute2: Colons in ethernet names under /sbin/ifconfig and /sbin/ip are not being recognized in Stretch

Hello Justin McZeal. On Wed, Apr 06, 2016 at 11:31:01AM -0500, Justin McZeal wrote: > Package: iproute2 > Version: 4.3.0-1+b1 > Severity: normal > > Dear Maintainer, > I'm using Stretch packages and I see a fundamental difference in > ifconfig/ip between Debian 8 and Debian 9. There are extra

Bug#820212: iproute2: Colons in ethernet names under /sbin/ifconfig and /sbin/ip are not being recognized in Stretch

Package: iproute2 Version: 4.3.0-1+b1 Severity: normal Dear Maintainer, I'm using Stretch packages and I see a fundamental difference in ifconfig/ip between Debian 8 and Debian 9. There are extra colons being put in after the interface using /sbin/ifconfig and /sbin/ip. I'm using a third party