Bug#765588: pfctl does not work after upgrade
True, works after reboot,didnt notice kernel switch due to 10.0.1 being installed and 10.1 being the new :) I apologize for reporting a nonbug. On Oct 16, 2014 4:07 PM, Christoph Egger christ...@debian.org wrote: Hi! Lars Lansink cry...@cryptr.net writes: * What led up to the situation? A regular apt-get upgrade * What exactly did you do (or not do) that was effective (or ineffective)? sudo apt-get upgrade --yes * What was the outcome of this action? pf version 10.1~svn272167-1 was installed * What outcome did you expect instead? pf was upgraded, but I did not expect it to break. It's kind of expected to not work if kernel and userland don't match -- pf seems to be quite tightly coupled. Does pfctl work again for you after booting into the 10.1 kernel? Christoph
Bug#765588: pfctl does not work after upgrade
Package: pf
Version: 10.1~svn272167-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
A regular apt-get upgrade
* What exactly did you do (or not do) that was effective (or
ineffective)?
sudo apt-get upgrade --yes
* What was the outcome of this action?
pf version 10.1~svn272167-1 was installed
* What outcome did you expect instead?
pf was upgraded, but I did not expect it to break.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: kfreebsd-amd64 (x86_64)
Kernel: kFreeBSD 10.0-1-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages pf depends on:
ii libbsd00.7.0-2
ii libc0.12.19-11
ii libfreebsd-glue-0 0.2.20
ii libutil-freebsd-9 10.1~svn272464-1
pf recommends no packages.
pf suggests no packages.
-- Configuration Files:
/etc/pf.conf changed:
ext_if0=em0
ext_if1=vlan100
int_if0=vlan165
int_if1=vlan130
set skip on lo
scrub in
nat on $ext_if0 from !($ext_if0) - ($ext_if0:0)
block in
pass out
pass quick on { $int_if0 $int_if1 } no state
pass quick on { $ext_if1 }
antispoof quick for { lo $int_if0 $int_if1 $ext_if1 }
pass in on $ext_if0 proto tcp to ($ext_if0) port ssh
pass in on $ext_if0 proto tcp to ($ext_if0) port 5001
pass in on $ext_if0 proto tcp to ($ext_if0) port 5666
pass in on $ext_if0 proto tcp to ($ext_if0) port 6667
pass in on $ext_if0 proto tcp to ($ext_if0) port 9001
pass in on $ext_if0 proto tcp to ($ext_if0) port 64738
pass in on $ext_if0 proto udp to ($ext_if0) port 64738
pass in on $ext_if0 proto tcp to ($ext_if0) port www
pass in on $ext_if0 proto icmp to ($ext_if0)
pass in on $ext_if1 proto icmp to ($ext_if1)
pass in on { $int_if0 $int_if1 }
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/20141016122945.75796.5540.report...@trashcan.cryptr.net
Bug#718490: freebsd-net-tools: ifconfig segfaults on Jessie
Package: freebsd-net-tools Version: 9.1-2 Severity: normal Dear Maintainer, After upgrade to Jessie ifconfig started to segfault. /sbin/ifconfig segfaults when given no options or just interface as option. You can however perform options like # ifconfig vlan20 create # ifconfig vlan20 vlan 20 vlandev nfe0 # ifconfig vlan20 10.0.0.1/24 After this you cannot check the interface however. # ifconfig vlan20 vlan20: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 Segmentation fault FreeBSD 9.1 binaries in a chroot works. # freebsd ifconfig vlan20 vlan20: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:30:05:fa:70:14 inet 10.0.0.1 netmask 0xff00 broadcast 10.0.0.255 inet6 fe80::230:5ff:fefa:7014%vlan20 prefixlen 64 scopeid 0x7 nd6 options=23PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL media: Ethernet autoselect (100baseTX full-duplex) status: active vlan: 20 parent interface: nfe0 # ifconfig nfe0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=82008VLAN_MTU,WOL_MAGIC,LINKSTATE Segmentation fault # freebsd ifconfig nfe0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=82008VLAN_MTU,WOL_MAGIC,LINKSTATE ether 00:30:05:fa:70:14 inet6 fe80::230:5ff:fefa:7014%nfe0 prefixlen 64 scopeid 0x3 inet XXX.XXX.XXX.X netmask 0xff00 broadcast XXX.XXX.X.255 nd6 options=23PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL media: Ethernet autoselect (100baseTX full-duplex) status: active pflog0: flags=0 metric 0 mtu 33152 nd6 options=23PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL pfsync0: flags=0 metric 0 mtu 1500 nd6 options=23PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL syncpeer: 0.0.0.0 maxupd: 128 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=63RXCSUM,TXCSUM inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 64 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.1-1-amd64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages freebsd-net-tools depends on: ii libbsd0 0.6.0-1 ii libc0.1 2.17-7 ii libexpat1 2.1.0-4 ii libipx2 9.1+ds1-3 ii libkvm0 9.1+ds1-3 ii libmemstat3 9.1+ds1-3 ii libnetgraph4 9.1+ds1-3 ii libsbuf6 9.1+ds1-3 freebsd-net-tools recommends no packages. freebsd-net-tools suggests no packages. -- no debconf information -- 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/2013080930.16287.72597.report...@trashcan.cryptr.net
Bug#718490: More info
Seems that lo0, pflog0 and pfsync0 can be checked. I think I managed to debug some but not sure if it is useful. $ gdb ifconfig GNU gdb (GDB) 7.6 (Debian 7.6-5) Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-kfreebsd-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /sbin/ifconfig...(no debugging symbols found)...done. (gdb) run lo0 Starting program: /sbin/ifconfig lo0 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=63RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 64 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL [Inferior 1 (process 18483) exited normally] (gdb) run nfe0 Starting program: /sbin/ifconfig nfe0 nfe0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=82008VLAN_MTU,WOL_MAGIC,LINKSTATE Program received signal SIGSEGV, Segmentation fault. 0x0008010c88ec in _IO_vfprintf_internal (s=optimized out, format=optimized out, ap=ap@entry=0x7fffd148) at vfprintf.c:1649 1649vfprintf.c: No such file or directory. (gdb) run vlan20 The program being debugged has been started already. Start it from the beginning? (y or n) y Starting program: /sbin/ifconfig vlan20 vlan20: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 Program received signal SIGSEGV, Segmentation fault. 0x0008010c88ec in _IO_vfprintf_internal (s=optimized out, format=optimized out, ap=ap@entry=0x7fffd148) at vfprintf.c:1649 1649vfprintf.c: No such file or directory. (gdb)
Bug#718490: More info
:28, Lars Lansink wrote: Program received signal SIGSEGV, Segmentation fault. 0x0008010c88ec in _IO_vfprintf_internal (s=optimized out, format=optimized out, ap=ap@entry=0x7fffd148) at vfprintf.c:1649 1649vfprintf.c: No such file or directory. (gdb) At the gdb prompt 'bt full' might show what led to this. On 01/08/13 13:52, Lars Lansink wrote: Seems similar to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696514 Yes I thought so at first, but this feature seems to be working on 8.3 and 9.0 kernels so it is likely a kernel ABI change instead. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- Lars (cry...@cryptr.net a gmail powered domain)
Bug#718490: More info
I admit I am not a very experience debian hacker but I tried adding this to ifconfig.c and rebuild the package with dpkg-buildpackage. BUILDDIR/sbin/ifconfig/ifconfig still segfaults though so I have not tried to replace the standard package yet. 2013/8/1 Petr Salinger petr.salin...@seznam.cz Seems similar to http://bugs.debian.org/cgi-**bin/bugreport.cgi?bug=696514http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696514 Yes I thought so at first, but this feature seems to be working on 8.3 and 9.0 kernels so it is likely a kernel ABI change instead. But it suffices to add #include netinet/ether.h and segfault of ifconfig is gone. Petr -- Lars (cry...@cryptr.net a gmail powered domain)
Bug#718490: freebsd-net-tools: ifconfig segfaults on Jessie
Do correct me if I am doing it wrong now but after reading Robert's mail I uncommented the -Werror... in debian/rules. When I started building the package again and it seems that quite a few files unde sbin/ifconfig/ is missing netinet/ether.h. sbin/ifconfig/ifbridge.c sbin/ifconfig/ifieee80211.c sbin/ifconfig/af_link.c Also a few in usr.bin and usr.sbin complained and failed to build, but build with netinet/ether.h. usr.bin/netstat/if.c usr.bin/netstat/route.c usr.sbin/arp/arp.c Arp is also broken in jessie. $ arp -a Segmentation fault usr.sbin/ppp/tty.c also complains and fails on lines 244. With these changes though both arp and ifconfig works. # ./sbin/ifconfig/ifconfig nfe0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=82008VLAN_MTU,WOL_MAGIC,LINKSTATE ether 0:30:5:fa:70:14 inet6 fe80::230:5ff:fefa:7014%nfe0 prefixlen 64 scopeid 0x3 inet XXX.XXX.XXX.X netmask 0xff00 broadcast XXX.XXX.X.255 media: Ethernet autoselect (100baseTX full-duplex) status: active nd6 options=23PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL pflog0: flags=0 metric 0 mtu 33152 nd6 options=23PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL pfsync0: flags=0 metric 0 mtu 1500 nd6 options=23PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=63RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 64 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL vlan20: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 0:30:5:fa:70:14 inet 10.0.0.1 netmask 0xff00 broadcast 10.0.0.255 inet6 fe80::230:5ff:fefa:7014%vlan20 prefixlen 64 scopeid 0x7 vlan: 20 parent interface: nfe0 media: Ethernet autoselect (100baseTX full-duplex) status: active nd6 options=23PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL # ./usr.sbin/arp/arp -a ? (X) at 0:1c:7f:33:ba:4a on nfe0 expires in seconds [ethernet] ? (X) at 0:19:6:60:23:40 on nfe0 expires in 1197 seconds [ethernet] ? (X) at 0:1c:7f:33:ba:4a on nfe0 expires in 1034 seconds [ethernet] gateway (X) at 0:1c:7f:33:ba:4a on nfe0 expires in seconds [ethernet] trashcan (X) at 0:30:5:fa:70:14 on nfe0 permanent [ethernet] PS: I apologize for spamming Robert personally. 2013/8/1 Robert Millan r...@debian.org 2013/8/1 Lars Lansink cry...@cryptr.net: # ifconfig nfe0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=82008VLAN_MTU,WOL_MAGIC,LINKSTATE Segmentation fault Probably my mistake. It might be due to some of the implicit function declarations coming back during upgrade. -Werror=implicit-function-declaration was clearly a good idea for freebsd-libs, I'll see if I can enable it on freebsd-utils as well... -- Lars (cry...@cryptr.net) Proud user of Debian GNU/Linux and Debian GNU/kFreeBSD.
Bug#718490: freebsd-net-tools: ifconfig segfaults on Jessie
Confirmed, it works now. PS I just noticed I wrote Jessie but I am of corse running a Sid system, but seems we all understood that anyway :) On Aug 1, 2013 9:52 PM, Robert Millan r...@debian.org wrote: severity 718490 grave thanks 2013/8/1 Lars Lansink cry...@cryptr.net: When I started building the package again and it seems that quite a few files unde sbin/ifconfig/ is missing netinet/ether.h. sbin/ifconfig/ifbridge.c sbin/ifconfig/ifieee80211.c sbin/ifconfig/af_link.c Yes, associated fixes were needed (in CFLAGS, freebsd-glue and kfreebsd-kernel-headers). Please can you try with 9.1-3? It's just been uploaded. With these changes though both arp and ifconfig works. Good to hear. Please do confirm with 9.1-3 so we can close the bug. Thanks! PS: I apologize for spamming Robert personally. No big deal ;-)
Re: Bug#718250: kfreebsd-image-9.1-1-amd64: attaching USB keyboard makes system reboot
I can confirm that it works on my system now. On Jul 29, 2013 11:34 PM, Robert Millan r...@debian.org wrote: 2013/7/29 Steven Chamberlain ste...@pyro.eu.org: Meanwhile I have added that to the new trunk/kfreebsd-9.1/ Robert: I think we're ready for an upload of this to stable. We can try to tackle GCC issues another time, even after this has migrated. Ack. I was already running dput when you guys fixed this. Oh well, I guess I can't complain. Nice job ;-) Please bear with me as I have to rebuild and test all over again. I'm on my way. -- 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/CAOfDtXNkQD+O4D31Fq4TPENmwXwfmObGu-vMVE1jqESG1p=s...@mail.gmail.com
Bug#718250: kfreebsd-image-9.1-1-amd64: attaching USB keyboard makes system reboot
Package: kfreebsd-image-9.1-1-amd64 Version: 9.1-3 Severity: important Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? After upgrading a headless wheezy to jessie and after the reboot attaching a USB keyboard. * What exactly did you do (or not do) that was effective (or ineffective)? Powered down the system, attached keyboard and screen, powered on. * What was the outcome of this action? Endless reboot loop due to KBD: stack traceback. * What outcome did you expect instead? Usable keyboard. *** End of the template - remove these lines *** -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.1-1-amd64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kfreebsd-image-9.1-1-amd64 depends on: ii devd 9.1-2 ii freebsd-utils 9.1-2 ii kbdcontrol 9.1-2 ii kldutils 9.1-2 kfreebsd-image-9.1-1-amd64 recommends no packages. kfreebsd-image-9.1-1-amd64 suggests no packages. -- no debconf information -- 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/20130729103518.6110.67128.report...@trashcan.cryptr.net
Re: Xterm and GNU/kFreeBSD
Hi,
I installed a fresh kfreebsd-i386 squeeze last night and I also tested xorg.
I used,
apt-get install xserver-xorg-video-via xterm openbox xinit
Ofcourse a lot of more stuff went in..
Anyways, My x works flawless and so does xterm, I had no problems
using openbox to launch a working xterm.
On Tue, Dec 7, 2010 at 21:33, Mats Erik Andersson
mats.anders...@gisladisker.se wrote:
(Repeating this seemingly lost message, with an important addition.)
tisdag den 7 december 2010 klockan 19:59 skrev Cyril Brulebois detta:
Hi,
Mats Erik Andersson mats.anders...@gisladisker.se (07/12/2010):
Dear all,
with the risk of making a fool of myself, I need to address an issue.
Is Xorg/Xterm really working impeccably within GNU/kFreeBSD? Are all
dependencies brought in as needed?
In essence, I started with
# apt-get install xserver-xorg-video-vesa twm xterm
Still it is not possible to access Xterm, neither from Twm, nor after
$ startx xterm
The terminal window is created, but no user input is possible.
In another effort I have patched Xvt for GNU/kFreeBSD. Originally,
it was was able to complain on the lack of controlling terminal,
but after patching which amends this, this complaint disappears.
Thus I know that Xorg/startx cat execute applications, but there
seems to be deficiencies on the event level. Or?
You installed a video driver, and clients. You probably want to
install xserver-xorg-input-{mouse,kbd} as well. If those are installed
as well, please run the X bug script, and attach its output:
/usr/share/bug/xorg/script 3/tmp/script.log
That's why we have metapackages like xorg and xserver-xorg.
The packages x-x-input-all, x-x-input-kbd, and x-x-input-mouse
were brought in without my interaction (As far as I recall now).
That is not the problem. In contrast, I imported xinit myself.
A most remarkable behaviour is this:
$ startx xterm
produces a display with a rapidly blinking/glimmering and only
outlines cursor, no prompt. Then the X server is shutting itself
down after a few seconds. The call
$ startx /usr/bin/xterm
arrives at a rock solid terminal window, displaying a prompt,
and a steady, outlined cursor. It does not accept any input.
These are the available phenomena. Neither is expected. Right?
Once I reconfigure hal, the call
$ startx /usr/bin/xterm
reproducibly leads to success with functional keyboard and mouse.
Equally reproducible, the call with implied path
$ startx xterm
fails to produce a functional terminal window. Afterwards,
xorg-vesa-aborted-with-restarted-hal.txt
is recorded using the debug script.
Best regards,
Mats E A
--
Lars @ lansink.se powered by gmail.com
--
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/aanlkti=ulm4qqh0usbs5h14am7qm5dq9nfarv0v+u...@mail.gmail.com
