Bug#728374: freebsd-net-tools: /sbin/ifconfig is missing options for pfsync
Package: freebsd-net-tools Version: 9.0+ds1-11~deb7u1 Severity: normal Tags: patch -- System Information: Debian Release: 7.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages freebsd-net-tools depends on: ii libbsd0 0.4.2-1 ii libc0.1 2.13-38 ii libexpat1 2.1.0-1 ii libipx2 9.0+ds1-4 ii libkvm0 9.0+ds1-4 ii libmemstat3 9.0+ds1-4 ii libnetgraph4 9.0+ds1-4 ii libsbuf6 9.0+ds1-4 ii pf9.0+ds1-11~deb7u1 freebsd-net-tools recommends no packages. freebsd-net-tools suggests no packages. -- no debconf information diff -Nur orig/freebsd-utils-9.0+ds1/debian/local/include/netinet/in.h pha/freebsd-utils-9.0+ds1/debian/local/include/netinet/in.h --- orig/freebsd-utils-9.0+ds1/debian/local/include/netinet/in.h 2013-03-18 11:32:54.0 +0100 +++ pha/freebsd-utils-9.0+ds1/debian/local/include/netinet/in.h 2013-10-31 11:08:44.0 +0100 @@ -2,3 +2,7 @@ #ifndef IPPORT_MAX #define IPPORT_MAX 65535 #endif + +#ifndef INADDR_PFSYNC_GROUP +#define INADDR_PFSYNC_GROUP (uint32_t)0xf0e0 +#endif diff -Nur orig/freebsd-utils-9.0+ds1/sbin/ifconfig/Makefile pha/freebsd-utils-9.0+ds1/sbin/ifconfig/Makefile --- orig/freebsd-utils-9.0+ds1/sbin/ifconfig/Makefile 2013-10-31 10:34:55.0 +0100 +++ pha/freebsd-utils-9.0+ds1/sbin/ifconfig/Makefile2013-10-31 10:40:56.0 +0100 @@ -38,6 +38,7 @@ SRCS+= ifcarp.c# SIOC[GS]VH support SRCS+= ifgroup.c # ... +SRCS+= ifpfsync.c SRCS+= ifbridge.c # bridge support SRCS+= iflagg.c# lagg support -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131031110710.2605.44297.report...@ext-fw3.wikon.de
Bug#728326: istgt: abysmal error reporting
Excerpts from Steven Chamberlain's message of Wed Oct 30 23:22:41 +0100 2013: > Hi Michal, > > On 30/10/13 17:57, Michal Suchanek wrote: > > I get this error in log: > > Oct 30 18:49:15 OptiPlex960 istgt[11969]: Login from > > iqn.1994-05.com.redhat:82afc45e9e1c (10.10.10.2) on > > iqn.2001-04.optiplex960.uvt316-2.ruk.cuni.cz:rhev LU1 (10.10.10.10:3260,1), > > ISID=23d0b, TSIH=2, CID=0, HeaderDigest=on, DataDigest=on > > Oct 30 18:49:15 OptiPlex960 istgt[11969]: istgt_iscsi.c:5223:worker: > > ***ERROR*** conn->state = 2 > > > > WTF is conn->state = 2? > > I agree that's not very clear, but at least it gave a source code line > number! And: > > src/istgt_iscsi.h: > > CONN_STATE_EXITING = 2, > > That situation can happen for many reasons during istgt_iscsi_read_pdu() > and suggests it didn't like something about a packet it just received. > > It seems istgt has a 'TRACELOG' with extra debugging messages. You > could enable it using "-t net" or "-t all" on the command line when > starting istgt; that may give you some further info. There is something wrong with the -t argument. Seems like the first -t is ignored. eg. -t all does nothing, -t net does nothing, -t net -t iscsi shows some info, -t net -t iscsi -t all even more. and this is what I get: Oct 31 16:37:07 OptiPlex960 istgt[31997]: Login from iqn.1994-05.com.redhat:82afc45e9e1c (10.10.10.2) on iqn.2001-04.optiplex960.uvt316-2.ruk.cuni.cz:rhev LU1 (10.10.10.10:3260,1), ISID=23d17, TSIH=1, CID=0, HeaderDigest=on, DataDigest=on istgt_iscsi.c: 433:istgt_iscsi_read_pdu: BHS read 48 istgt_iscsi.c: 189:istgt_iscsi_read: Read EOF istgt_iscsi.c: 451:istgt_iscsi_read_pdu: iscsi_read() EOF istgt_iscsi.c:5223:worker: ***ERROR*** conn->state = CONN_STATE_EXITING So it seems like the initiator just disconnects shortly after login. The initiator disconnecting is something that could perhaps be reported without enabling tracing. Thanks Michal -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1383233895-sup-7...@virtual.ruk.cuni.cz
Bug#728374: freebsd-net-tools: /sbin/ifconfig is missing options for pfsync
Hi! On 31/10/2013 12:07, Peter Hachenberg wrote: > diff -Nur orig/freebsd-utils-9.0+ds1/debian/local/include/netinet/in.h > pha/freebsd-utils-9.0+ds1/debian/local/include/netinet/in.h > --- orig/freebsd-utils-9.0+ds1/debian/local/include/netinet/in.h > 2013-03-18 11:32:54.0 +0100 > +++ pha/freebsd-utils-9.0+ds1/debian/local/include/netinet/in.h 2013-10-31 > 11:08:44.0 +0100 This header is a bit more generic now than it was in the version you've modified. It is now used on GNU/Linux, and intends to serve other packages than just freebsd-utils. (hence the questions below, please answer if possible!). > @@ -2,3 +2,7 @@ > #ifndef IPPORT_MAX > #define IPPORT_MAX 65535 > #endif > + > +#ifndef INADDR_PFSYNC_GROUP > +#define INADDR_PFSYNC_GROUP (uint32_t)0xf0e0 > +#endif This is an IPv4 address right? Any idea what is it used for? What's special about packets sent to / received from this address? Btw, what about the other groups not defined by Glibc? Should these be added too? #define INADDR_ALLRPTS_GROUP(u_int32_t)0xe016 /* 224.0.0.22, IGMPv3 */ #define INADDR_CARP_GROUP (u_int32_t)0xe012 /* 224.0.0.18 */ #define INADDR_PFSYNC_GROUP (u_int32_t)0xe0f0 /* 224.0.0.240 */ #define INADDR_ALLMDNS_GROUP(u_int32_t)0xe0fb /* 224.0.0.251 */ Thanks! -- Robert Millan -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5272b54c.30...@debian.org
Bug#728374: freebsd-net-tools: /sbin/ifconfig is missing options for pfsync
On 31/10/13 19:53, Robert Millan wrote: >> > +#ifndef INADDR_PFSYNC_GROUP >> > +#define INADDR_PFSYNC_GROUP (uint32_t)0xf0e0 >> > +#endif > This is an IPv4 address right? Any idea what is it used for? What's > special about packets sent to / received from this address? In network byte order that's 224.0.0.240 (actually the FreeBSD header shows this in a comment), which is a local multicast group address, chosen for pfsync because 240 is also its IP protocol number. All hosts running pfsync send and listen for shared state information there. Real example: > 20:50:56.486456 IP 192.168.11.1 > 224.0.0.240: ip-proto-240 360 > 20:50:56.486694 IP 192.168.11.3 > 224.0.0.240: ip-proto-240 412 > 20:50:56.488372 IP 192.168.11.1 > 224.0.0.240: ip-proto-240 1132 INADDR_CARP_GROUP does pretty much the same thing. It's using 224.0.0.18 although its protocol number is 112. These were chosen to deliberately clobber what Cisco used for patent-encumbered VRRP :) I'm surprised Linux doesn't define at least the first three groups; I'm not familiar with the others. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5272c54e.6000...@pyro.eu.org
