[Bug 234004] r342058 lib/libc/include/fpmath.h:36:10: fatal error: _fpmath.h: No such file or directory
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234004 Bug ID: 234004 Summary: r342058 lib/libc/include/fpmath.h:36:10: fatal error: _fpmath.h: No such file or directory Product: Base System Version: CURRENT Hardware: riscv OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: dcla...@blastwave.org Seen in the last few days : make buildworld -j 4 TARGET_ARCH=riscv64 CROSS_TOOLCHAIN=riscv64-gcc . . . --- lib/msun__L --- /usr/local/bin/riscv64-unknown-freebsd12.0-gcc --sysroot=/usr/obj/usr/src/head/riscv.riscv64/tmp -B/usr/local/riscv64-unknown-freebsd12.0/bin/ -O2 -pipe -I/usr/src/head/lib/msun/ld128 -I/usr/src/head/lib/msun/riscv -I/usr/src/head/lib/msun/src -I/usr/src/head/lib/libc/include -I/usr/src/head/lib/libc/riscv64 -march=rv64imafdc -mabi=lp64d -g -MD -MF.depend.s_clog.o -MTs_clog.o -std=gnu99 -fstack-protector-strong -Wsystem-headers -Werror -Wno-pointer-sign -Wno-error=address -Wno-error=array-bounds -Wno-error=attributes -Wno-error=bool-compare -Wno-error=cast-align -Wno-error=clobbered -Wno-error=enum-compare -Wno-error=extra -Wno-error=inline -Wno-error=logical-not-parentheses -Wno-error=strict-aliasing -Wno-error=uninitialized -Wno-error=unused-but-set-variable -Wno-error=unused-function -Wno-error=unused-value -Wno-error=misleading-indentation -Wno-error=nonnull-compare -Wno-error=shift-negative-value -Wno-error=tautological-compare -Wno-error=unused-const-variable -Wno-error=bool-operation -Wno-error=deprecated -Wno-error=expansion-to-defined -Wno-error=format-overflow -Wno-error=format-truncation -Wno-error=implicit-fallthrough -Wno-error=int-in-bool-context -Wno-error=memset-elt-size -Wno-error=noexcept-type -Wno-error=nonnull -Wno-error=pointer-compare -Wno-error=stringop-overflow -Wno-error=aggressive-loop-optimizations -Wno-error=cast-function-type -Wno-error=catch-value -Wno-error=multistatement-macros -Wno-error=restrict -Wno-error=sizeof-pointer-memaccess -Wno-error=stringop-truncation -Wno-unknown-pragmas -c /usr/src/head/lib/msun/src/s_clog.c -o s_clog.o --- lib/msun__L --- In file included from /usr/src/head/lib/msun/src/s_clog.c:33: /usr/src/head/lib/libc/include/fpmath.h:36:10: fatal error: _fpmath.h: No such file or directory #include "_fpmath.h" ^~~ compilation terminated. *** [s_clog.o] Error code 1 make[4]: stopped in /usr/src/head/lib/msun 1 error make[4]: stopped in /usr/src/head/lib/msun *** [lib/msun__L] Error code 2 make[3]: stopped in /usr/src/head --- secure/lib/libcrypto__L --- A failure has been detected in another branch of the parallel make make[4]: stopped in /usr/src/head/secure/lib/libcrypto *** [secure/lib/libcrypto__L] Error code 2 make[3]: stopped in /usr/src/head --- lib/ncurses/ncursesw__L --- A failure has been detected in another branch of the parallel make make[4]: stopped in /usr/src/head/lib/ncurses/ncursesw *** [lib/ncurses/ncursesw__L] Error code 2 make[3]: stopped in /usr/src/head --- lib/ncurses/ncurses__L --- A failure has been detected in another branch of the parallel make make[4]: stopped in /usr/src/head/lib/ncurses/ncurses *** [lib/ncurses/ncurses__L] Error code 2 make[3]: stopped in /usr/src/head 4 errors Seems repeatable. However there were no suhc issues with r341837. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 233994] boost::regex match but not std::regex
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233994 --- Comment #3 from georg-...@schorsch-tech.de --- I think it might be a bug in libc++ because on Windows(MSVC 2013 & MSVC 2017) and on Linux (gcc 8.2 + libstdc++) this regex (from std) matches with the global locale from boost. Also the regex from boost matches (replace std::regex by boost::regex). Do you think the other implementations are wrong? This bug triggers only (also on my box and only on freebsd with clang and libc++) when i use boost::locale. As you said, with std::locale() it matches. When i comment the locale out, and use the std locale, the regex matches. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 233994] boost::regex match but not std::regex
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233994 --- Comment #4 from georg-...@schorsch-tech.de --- I also don't understand why this regex is locale dependent and why it fails with the locale set from boost::locale. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 233994] boost::regex match but not std::regex
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233994 --- Comment #5 from Conrad Meyer --- Seems like it might be a Boost bug to me. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 213742] /etc/crontab $PATH modification
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213742 Kubilay Kocak changed: What|Removed |Added CC||ko...@freebsd.org Assignee|b...@freebsd.org|i...@freebsd.org --- Comment #4 from Kubilay Kocak --- Assign to committer that resolved. Unsure if this was eventually MFC'd to stable/11, but appears to be a good candidate. @Warner, can we re-open this and merge it there? [1] [1] https://twitter.com/socrueldotnu/status/1073538274449391616 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234010] Lack of Unicode support in strfmon breaks monitary formatting
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234010
Bug ID: 234010
Summary: Lack of Unicode support in strfmon breaks monitary
formatting
Product: Base System
Version: 11.2-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: misc
Assignee: b...@freebsd.org
Reporter: j...@herrskogen.se
This bug was manifested when using the PHP function money_format and
LC_MONETARY sv_SE.UTF-8 to format some currency. Instead of a space as the
thousand separator, it was a ?-symbol. I'm not very good at this, but this is
what I have come up with:
* FreeBSD is retrieving locale data from http://cldr.unicode.org
* In at least sv_SE.UTF-8, the value ending up as monitary thousand separator
is a unicode character (C2 A0).
* localeconv is fetching the data in /usr/share/locale/sv_SE.UTF-8/LC_MONETARY
and returning a pointer.
* __format_grouped_double (with the description "convert double to ASCII") is
calling localeconv to fetch the thousand separator and seems to only use the
first byte (C2).
* strfmon is calling __format_grouped_double to format the grouping of the
string and returns bad strings when using locales with unicode characters.
How to reproduce:
setlocale(LC_MONETARY, "sv_SE.UTF-8");
int i;
strfmon(buf, sizeof(buf), "%i", money);
printf("%s\n", buf);
for(i=0; ihttps://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 221350] Unable to boot/install on HPE Proliant MicroServer Gen10 (AMD Opteron X3000): Hangs/Panics
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350 Kubilay Kocak changed: What|Removed |Added Severity|Affects Some People |Affects Many People Priority|--- |Normal -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 221350] Unable to boot/install on HPE Proliant MicroServer Gen10 (AMD Opteron X3000): Hangs/Panics
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350 Sean Bruno changed: What|Removed |Added CC||j...@freebsd.org, ||sbr...@freebsd.org Status|Open|In Progress --- Comment #53 from Sean Bruno --- John: This looks fairly trivial to commit. However, that usually means I misunderstand something. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230722] [nvme][resume] Delay and possible deadlock after resume
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230722 --- Comment #7 from mmata...@gmail.com --- Created attachment 200116 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=200116&action=edit Kernel Panic while resuming -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230722] [nvme][resume] Delay and possible deadlock after resume
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230722 --- Comment #8 from mmata...@gmail.com --- Created attachment 200117 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=200117&action=edit Kernel Panic while resuming 2 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230722] [nvme][resume] Delay and possible deadlock after resume
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230722 --- Comment #9 from mmata...@gmail.com --- I uploaded photos of what the kernel panic I get on resume. Hopefully that is useful. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234014] chown: ntpd: illegal user name -- after freebsd-update to 12.0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234014 Bug ID: 234014 Summary: chown: ntpd: illegal user name -- after freebsd-update to 12.0 Product: Base System Version: 12.0-RELEASE Hardware: i386 OS: Any Status: New Severity: Affects Many People Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: vangy...@freebsd.org I just updated an i386 machine (not amd64) from 11.2-RELEASE to 12.0-RELEASE using freebsd-update. On boot, the console says: chown: ntpd: illegal user name Sure enough, the ntpd user was in /etc/*passwd but _not_ in /etc/*pwd.db. # getent passwd ntpd # grep ntp master.passwd ntpd:*:123:123::0:0:NTP Daemon:/var/db/ntp:/usr/sbin/nologin # strings spwd.db | grep ntp # strings pwd.db | grep ntp Also, ntpd is running as root. The pwd db files were newer than the plain text files, so pwd_mkdb did run during the upgrade: # stat -x master.passwd passwd spwd.db pwd.db File: "master.passwd" Size: 3019 FileType: Regular File Mode: (0600/-rw---) Uid: (0/root) Gid: (0/ wheel) Device: 0,70 Inode: 1036545Links: 1 Access: Fri Dec 14 09:30:48 2018 Modify: Fri Dec 14 09:30:48 2018 Change: Fri Dec 14 09:32:39 2018 File: "passwd" Size: 2509 FileType: Regular File Mode: (0644/-rw-r--r--) Uid: (0/root) Gid: (0/ wheel) Device: 0,70 Inode: 1036629Links: 1 Access: Fri Dec 14 09:30:48 2018 Modify: Fri Dec 14 09:30:48 2018 Change: Fri Dec 14 09:32:39 2018 File: "spwd.db" Size: 40960FileType: Regular File Mode: (0600/-rw---) Uid: (0/root) Gid: (0/ wheel) Device: 0,70 Inode: 1036680Links: 1 Access: Fri Dec 14 09:48:57 2018 Modify: Fri Dec 14 09:30:50 2018 Change: Fri Dec 14 09:32:40 2018 File: "pwd.db" Size: 40960FileType: Regular File Mode: (0644/-rw-r--r--) Uid: (0/root) Gid: (0/ wheel) Device: 0,70 Inode: 1036668Links: 1 Access: Fri Dec 14 09:48:38 2018 Modify: Fri Dec 14 09:30:49 2018 Change: Fri Dec 14 09:32:40 2018 I wonder if pwd_mkdb ran against the wrong/old master.passwd file? Simply running pwd_mkdb worked around the problem. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234014] chown: ntpd: illegal user name -- after freebsd-update to 12.0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234014 --- Comment #1 from Eric van Gyzen --- I didn't have this problem on systems that I upgraded with installworld, so I imagine it's a problem in freebsd-update. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234015] [patch] [nfe] Add nForce MCP89 Networking Adapter support
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234015 Bug ID: 234015 Summary: [patch] [nfe] Add nForce MCP89 Networking Adapter support Product: Base System Version: 12.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: sinchiroc...@gmail.com Created attachment 200120 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=200120&action=edit add support for MCP89 Ethernet Controller Please, add support for nVidia nForce MCP89 Networking Adapter in nfe driver. dmesg --- nfe0: port 0x22a0-0x22a7 mem 0xd3286000-0xd3287fff at device 9.0 on pci0 miibus0: on nfe0 --- pciconf -lv --- nfe0@pci0:0:9:0:class=0x02 card=0xcb89106b chip=0x0d7d10de rev=0xa1 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'MCP89 Ethernet' class = network subclass = ethernet --- I backported there changes from OpenBSD nfe driver. (https://github.com/openbsd/src/commits/master/sys/dev/pci/if_nfe.c) Tested changes in 12.0-RELEASE on Apple MacBook "Core 2 Duo" 2.4 13" (Mid-2010) with nForce MCP89 chipset: pciconf -lv | grep MCP --- device = 'MCP89 HOST Bridge' device = 'MCP89 Memory Controller' device = 'MCP89 LPC Bridge' device = 'MCP89 Memory Controller' device = 'MCP89 SMBus' device = 'MCP89 Memory Controller' device = 'MCP89 Co-Processor' device = 'MCP89 OHCI USB 1.1 Controller' device = 'MCP89 EHCI USB 2.0 Controller' device = 'MCP89 OHCI USB 1.1 Controller' device = 'MCP89 EHCI USB 2.0 Controller' device = 'MCP89 High Definition Audio' device = 'MCP89 Ethernet' device = 'MCP89 SATA Controller (AHCI mode)' device = 'MCP89 PCI Express Bridge' device = 'MCP89 [GeForce 320M]' --- Actually, just needed to add define for device id. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 221350] Unable to boot/install on HPE Proliant MicroServer Gen10 (AMD Opteron X3000): Hangs/Panics
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350 John Baldwin changed: What|Removed |Added CC||i...@freebsd.org --- Comment #54 from John Baldwin --- I think the patch is probably fine. This looks to be a BIOS bug. The failing memory BAR for the VGA device is '0xfeb0' with a size of 256K. However, ACPI reserves the first page of that range as a system resource (from devinfo -vr output without the patch): nexus0 ... acpi0 ... I/O memory addresses: ... 0xfeb0-0xfeb00fff FWIW, hw.pci.realloc_bars is a bit of a conservative knob that I had considered enabling by default. I've added Warner to see what he thinks about possibly enabling this knob by default in HEAD. The current patch is probably fine to commit as-is and is probably safe to MFC as well since it is specific to that device id. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234015] [patch] [nfe] Add nForce MCP89 Networking Adapter support
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234015 --- Comment #1 from Andrejs Bogdanovs --- ifconfig output. ifconfig nfe0 --- nfe0: flags=8843 metric 0 mtu 1500 options=8210b ether 70:cd:60:8c:e3:8e inet 192.168.1.51 netmask 0xff00 broadcast 192.168.1.255 media: Ethernet autoselect (1000baseT ) status: active nd6 options=29 --- -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234015] [patch] [nfe] Add nForce MCP89 Networking Adapter support
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234015 --- Comment #2 from commit-h...@freebsd.org --- A commit references this bug: Author: markj Date: Fri Dec 14 18:16:35 UTC 2018 New revision: 342086 URL: https://svnweb.freebsd.org/changeset/base/342086 Log: Add support for the nForce MCP89 adapter. PR: 234015 Submitted by: Andrejs Bogdanovs MFC after:1 week Changes: head/sys/dev/nfe/if_nfe.c head/sys/dev/nfe/if_nfereg.h -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234015] [patch] [nfe] Add nForce MCP89 Networking Adapter support
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234015 Mark Johnston changed: What|Removed |Added CC||ma...@freebsd.org Assignee|b...@freebsd.org|ma...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 213045] kldload vesa gives "error 19"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213045 Max Kostikov changed: What|Removed |Added CC||m...@kostikov.co --- Comment #9 from Max Kostikov --- Have the same error with Matrox MGA G200e [Pilot] ServerEngines (SEP1) on 12.0-RELEASE module_register_init: MOD_LOAD (vesa, 0x810f9770, 0) error 19 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234021] 12.0 gateway host with vnet jail running pf firewall & NAT has no internet access
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234021
Bug ID: 234021
Summary: 12.0 gateway host with vnet jail running pf firewall &
NAT has no internet access
Product: Base System
Version: 12.0-STABLE
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: b...@freebsd.org
Reporter: qja...@a1poweruser.com
Trying to get a vnet jail to access the public internet. Issuing "ping -c 2
8.8.8.8" returns 100.0% packet loss message.
The host running the vnet jail is a gateway host ie: connected directly to my
ISP. The pf firewall is running on the host and in the vnet jail. The host and
the lan behind it are functioning normally. The pf rules in the vnet jail are
doing NAT. The pflog in the vnet jail shows outbound packets only, never a
inbound reply. gateway_enable is in the vnet jails rc.conf plus the normal pf
enable statements. Not using the "service jail" command for starting or
stopping the vnet jail. I start and stop the vnet jail using the native jail(8)
jail command. Using bridge/epair method for vnet jail networking. Tried a
second variation where I ran ipfilter on the host and pf in the vnet jail with
the same out come.
Running this same setup on a LAN host works. IE; the vnet jail can ping the
public internet.
Reviewing google search results shows all the vnet jail examples are vnet jails
on lan hosts. Have suspicion that gateway vnet jails have never worked because
I have tested it my self in 10.x and 11.x. Never posted a bug report because
thought it was a vimage problem due to its experimental nature. Now that vimage
is included in the base kernel time for a bug report.
Need someone from the vimage kernel project or the pf vimage aware project to
perform their own test of vnet on a gateway host to verify if it works or not.
Also have same results if ipfw is the vnet jail firewall.
Below is some info about my setup that may help or may not.
/root >cat /etc/jail.vnetpf1.conf
vnetpf1 {
host.hostname = "vnetpf1";
path= "/usr/jails/vnetpf1";
exec.consolelog = "/var/log/jail.vnetpf1.console.log";
mount.devfs;
devfs_ruleset = "70";
vnet= "new";
vnet.interface = "epair15b";
exec.start = "ifconfig epair15b 10.0.110.25/24";
exec.start += "route add default 10.0.110.2";
exec.start += "/bin/sh /etc/rc";
exec.stop = "/bin/sh /etc/rc.shutdown";
}
Issued from the host console
>netstat -nr4
Routing tables
Internet:
DestinationGatewayFlags Netif Expire
default65.xxx.48.1UGSvge0
10.0.0.0/8 link#1 U em0
10.0.10.2 link#1 UHS lo0
65.xxx.48.0/20 link#2 U vge0
65.xxx.62.234 link#2 UHS lo0
127.0.0.1 link#3 UH lo0
Issued from the vnet jails console
vnetpf1 /root >netstat -nr4
Routing tables
Internet:
DestinationGatewayFlags Netif Expire
default10.0.110.2 UGSepair15b
10.0.110.0/24 link#3 U epair15b
10.0.110.25link#3 UHS lo0
127.0.0.1 link#1 UH lo0
# devfsrules for pf to function in a vnet jail.
[vnet_pf=70]
add include $devfsrules_hide_all
add include $devfsrules_unhide_basic
add include $devfsrules_unhide_login
add include $devfsrules_jail
add path 'bpf*' unhide
add path pf unhide
add path pflog unhide
add path pfsync unhide
Issued from the host with the vnet jail running
/root >ifconfig -a
em0: flags=8843 metric 0 mtu 1500
options=81249b
ether d0:50:99:93:75:98
inet 10.0.10.2 netmask 0xff00 broadcast 10.255.255.255
media: Ethernet autoselect (1000baseT )
status: active
nd6 options=29
vge0: flags=8943
metric 0 mtu 1500
options=3899
ether 10:00:60:21:00:93
inet 65.xxx.62.234 netmask 0xf000 broadcast 255.255.255.255
media: Ethernet autoselect (1000baseT )
status: active
nd6 options=29
pflog0: flags=141 metric 0 mtu 33160
groups: pflog
bridge10: flags=8843 metric 0 mtu 1500
ether 02:3a:f8:d2:63:0a
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: epair15a flags=143
ifmaxaddr 0 port 6 priority 128 path cost 2000
member: vge0 flags=143
ifmaxaddr 0 port 2 priority 128 path cost 2
groups: bridge
nd6 options=1
epair15a: flags=8943
metric 0 mtu 1500
options=8
ether 02:9b:6a:d0:c6:0a
inet6 fe80::9b:6aff:fed0:c60a%epair15
[Bug 234024] pf/ALTQ won't load, symbol altq_add undefined
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234024 Bug ID: 234024 Summary: pf/ALTQ won't load, symbol altq_add undefined Product: Base System Version: 12.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: um...@netvor.sk FreeBSD 12 (releng) kernel built with the following options, as documented in https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/firewalls-pf.html section "30.3.2. Enabling ALTQ": ALTQ ALTQ_CBQ ALTQ_RED ALTQ_RIO ALTQ_HFSC ALTQ_NOPCC ALTQ_PRIQ (extra option) This results in a failure to load the module: kernel: link_elf_obj: symbol altq_add undefined kernel: linker_load_file: /boot/kernel/pf.ko - unsupported file type -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230722] [nvme][resume] Delay and possible deadlock after resume
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230722 --- Comment #10 from Warner Losh --- (In reply to Alexandr Krivulya from comment #6) Just rebuild the kernel and/or module. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234021] 12.0 gateway host with vnet jail running pf firewall & NAT has no internet access
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234021 Kristof Provost changed: What|Removed |Added CC||k...@freebsd.org --- Comment #1 from Kristof Provost --- Why are you trying to do NAT in the jail when the host has the public IP? If you want to NAT in the jail and bridge you'll need to assign the public IP inside the jail, not on the host. Or even simpler, just assign vge0 to the jail. Or even simpler, do NAT on the host, because that's what your configuration suggests right now. Your jail has a private IP address, and a single interface. Your host has both WAN (vge0) and LAN (em0) interfaces. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234024] pf/ALTQ won't load, symbol altq_add undefined
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234024 Kristof Provost changed: What|Removed |Added CC||k...@freebsd.org Status|New |Closed Resolution|--- |Not A Bug --- Comment #1 from Kristof Provost --- Did you remember to install the kernel and reboot the machine? That's the only way I could reproduce this. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 157802] [dummynet] [panic] kernel panic in dummynet
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=157802 Eugene Grosbein changed: What|Removed |Added CC||eu...@freebsd.org Status|Open|Closed Resolution|--- |Feedback Timeout -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234027] [ioat] ioat man page belongs in section 9
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234027 Bug ID: 234027 Summary: [ioat] ioat man page belongs in section 9 Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Manual Pages Assignee: b...@freebsd.org Reporter: asom...@freebsd.org CC: d...@freebsd.org The ioat(4) driver can only be accessed from kernelspace, so it should probably be moved to section 9. Also, the cross-referenced program ioatcontrol(8) is a dead link. That program doesn't get installed and neither does its man page. ioat(4) should probably just refer to its source location instead: tools/tools/dev/ioat/ioatcontrol. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234028] Openssl cannot decrypt properly
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234028 Bug ID: 234028 Summary: Openssl cannot decrypt properly Product: Base System Version: 12.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: bc...@lafn.org If I encrypt a file on 11.1 using aes256: master# openssl enc -aes256 -in xxx.c -out xxx.enc Then transfer xxx.enc to 12.0 and try to decrypt it, I get garbage with a couple of what appear to be warnings: test# openssl enc -d -aes256 -in xxx.enc enter aes-256-cbc decryption password: *** WARNING : deprecated key derivation used. Using -iter or -pbkdf2 would be better. s??6@TU?lPD?]+?'RPB^?"?wHC?^q۸??p5YkZ?t?/?iB#?%?8'??!NAZ`!?m??K^ -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234027] [ioat] ioat man page belongs in section 9
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234027 Conrad Meyer changed: What|Removed |Added CC||c...@freebsd.org --- Comment #1 from Conrad Meyer --- I'm not sure about the section 9 claim. Is there precedent one way or the other? As far as ioatcontrol(8): yeah, I agree that should be fixed — there's no reason that program should live outside of tools/ or tests/. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234027] [ioat] ioat man page belongs in section 9
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234027 --- Comment #2 from Conrad Meyer --- Btw, it looks like xdma(4) (undocumented entirely, of course) is the start of a generic DMA engine interface ioat(4) might implement. Unfortunately, last time I looked the interface wasn't general enough for ioat. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234027] [ioat] ioat man page belongs in section 9
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234027 Conrad Meyer changed: What|Removed |Added CC|d...@freebsd.org | Assignee|b...@freebsd.org|d...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234021] 12.0 gateway host with vnet jail running pf firewall & NAT has no internet access
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234021 --- Comment #2 from Joe Barbish --- (In reply to Kristof Provost from comment #1) I am having a real hard time trying to understand your comments. Its my understanding that because vnet jails have their own ip stack that's outside of the hosts ip stack, that they act like individual computers. This is the only difference between non-vnet jails and vnet jails. For network connectivity vnet jails use the bridge/epair or netgraph methods. Non-vnet jails uses the host network stack. This fact is well know by people who have read any of the vnet jail documentation. The whole reason for changing ipfw and pf firewalls was because vnet jails on gateway hosts need a vnet aware firewall to filter and NAT their traffic. Based on this information, I can not get a so configured vnet jail running on a gateway host to access the public internet. To verify this problems exist is the purpose of this bug report. See /usr/share/examples/jails for details and who wrote the content of the files. >From your comments you seem to be implying this is untrue. Please point me to vnet jail documentation that supports your position. I'm always ready to learn new things about vnet jails. A example of a working vnet jail setup environment would enable me to replicate it here. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234024] pf/ALTQ won't load, symbol altq_add undefined
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234024 --- Comment #2 from ultramage --- Ah, I see now. This happened after trying to recover from #233098 by booting off of the generic bootonly image, and mounting the root filesystem. I guess it used the generic kernel to boot but then proceeded to load modules from the disk... -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234028] Openssl cannot decrypt properly
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234028 --- Comment #3 from Conrad Meyer --- This is sort of documented in the HISTORY section of openssl-enc(1): HISTORY The default digest was changed from MD5 to SHA256 in Openssl 1.1.0. I guess it'd be nice if they had revved the format so new openssl could tell if the file had been produced by OpenSSL <1.1.0, but I guess they chose not to. This is an upstream OpenSSL behavior so I don't think we're going to change it. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234028] Openssl cannot decrypt properly
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234028 Conrad Meyer changed: What|Removed |Added Resolution|--- |Not A Bug Status|New |Closed --- Comment #4 from Conrad Meyer --- Not a bug. Pass an explicit key derivation method for encrypt and the same same method for decrypt to get consistent results as defaults change. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234028] Openssl cannot decrypt properly
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234028 --- Comment #1 from Conrad Meyer --- When I do the same thing on 11.2ish with a 16-byte plaintext file, it uses aes-256-cbc and produces a 48 byte output. I am able to reproduce, sort of — I don't get bogus output, but a decryption error instead. Because it may be useful, here is the output with '-v -v -v -debug' too: ENCRYPT, 11.x: == BIO[0x801816070]: ctrl(108) - FILE pointer BIO[0x801816070]: ctrl return 1 enter aes-256-cbc encryption password: Verifying - enter aes-256-cbc encryption password: BIO[0x8018160e0]: ctrl(108) - FILE pointer BIO[0x8018160e0]: ctrl return 1 BIO[0x8018160e0]: write(0,8) - FILE pointer BIO[0x8018160e0]: write return 8 BIO[0x8018160e0]: write(0,8) - FILE pointer BIO[0x8018160e0]: write return 8 BIO[0x801816150]: ctrl(6) - cipher BIO[0x8018160e0]: ctrl(6) - FILE pointer BIO[0x8018160e0]: ctrl return 0 BIO[0x801816150]: ctrl return 0 BIO[0x801816070]: read(0,8192) - FILE pointer BIO[0x801816070]: read return 16 BIO[0x801816150]: write(0,16) - cipher BIO[0x8018160e0]: write(0,16) - FILE pointer BIO[0x8018160e0]: write return 16 BIO[0x801816150]: write return 16 BIO[0x801816070]: read(0,8192) - FILE pointer BIO[0x801816070]: read return 0 BIO[0x801816150]: ctrl(11) - cipher BIO[0x8018160e0]: write(0,16) - FILE pointer BIO[0x8018160e0]: write return 16 BIO[0x8018160e0]: ctrl(11) - FILE pointer BIO[0x8018160e0]: ctrl return 1 BIO[0x801816150]: ctrl return 1 bytes read : 16 bytes written: 48 BIO[0x801816070]: Free - FILE pointer BIO[0x8018160e0]: Free - FILE pointer BIO[0x801816150]: Free - cipher DECRYPT, CURRENT: = bufsize=8192 enter aes-256-cbc decryption password: BIO[0x800aea180]: read(0,8) - FILE pointer BIO[0x800aea180]: read return 8 BIO[0x800aea180]: read(0,8) - FILE pointer BIO[0x800aea180]: read return 8 *** WARNING : deprecated key derivation used. Using -iter or -pbkdf2 would be better. BIO[0x800aea280]: ctrl(6) - cipher BIO[0x800aea200]: ctrl(6) - FILE pointer BIO[0x800aea200]: ctrl return 0 BIO[0x800aea280]: ctrl return 0 BIO[0x800aea180]: read(0,8192) - FILE pointer BIO[0x800aea180]: read return 32 BIO[0x800aea280]: write(0,32) - cipher BIO[0x800aea200]: write(0,16) - FILE pointer BIO[0x800aea200]: write return 16 BIO[0x800aea280]: write return 32 BIO[0x800aea180]: read(0,8192) - FILE pointer BIO[0x800aea180]: read return 0 BIO[0x800aea280]: ctrl(11) - cipher BIO[0x800aea280]: ctrl return 0 bad decrypt 34371153920:error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt:/usr/home/conrad/src/freebsd/crypto/openssl/crypto/evp/evp_enc.c:537: BIO[0x800aea180]: Free - FILE pointer BIO[0x800aea200]: Free - FILE pointer BIO[0x800aea280]: Free - cipher Additionally, running the same encryption command on CURRENT with the same plaintext produces a different ciphertext. But result is salted, so that isn't very surprising. CURRENT openssl is able to decrypt the output from the enc command on CURRENT. The debug output is identical, up to this point: BIO[0x800aea280]: write return 32 BIO[0x800aea180]: read(0,8192) - FILE pointer BIO[0x800aea180]: read return 0 BIO[0x800aea280]: ctrl(11) - cipher -- diverges BIO[0x800aea200]: ctrl(11) - FILE pointer BIO[0x800aea200]: ctrl return 1 BIO[0x800aea280]: ctrl return 1 bytes read : 48 bytes written: 16 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234028] Openssl cannot decrypt properly
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234028 --- Comment #2 from Conrad Meyer --- When I pass '-md md5', CURRENT is able to decrypt the encrypted file from 11.x just fine. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234031] loader can't traverse filesystem, LUA ERROR: cannot open /boot/lua/loader.lua
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234031 Bug ID: 234031 Summary: loader can't traverse filesystem, LUA ERROR: cannot open /boot/lua/loader.lua Product: Base System Version: 12.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: um...@netvor.sk Booting from a clean copy of /boot obtained from FreeBSD-12.0-RELEASE-amd64-bootonly.iso does not work. The BTX loader seems to have issues traversing the filesystem - when I poke around with 'ls', it sees the root, but can't enter subdirectories. The system disk uses BSD/UFS scheme. The loader however has no trouble browsing the storage disk, which is GPT/UFS. This has been previously reported a month ago in CURRENT as bug #233098 but was miscategorized and no additional info was provided. The issue is currently being discussed in https://forums.freebsd.org/threads/lua-error-can-not-open-boot-lua-loader-lua.68635/ I am currently working around this by booting off of the iso, then mounting the system disk. Interestingly, /dev/ada0 exists but dev/ada0a doesn't, and 'gpart list' does not even mention ada0. No idea what this means. I ran fsck just in case, all filesystems are clean. FreeBSD/x86 bootstrap loader. Revision 1.1 Startup error in /boot/lua/loader.lua: LUA ERROR: cannot open /boot/lua/loader.lua: no such file or directory. can't load 'kernel' Type '?' for a list of commands, 'help' for more detailed help. OK lsdev disk devices: disk0: BIOS drive C (16514064 x 512): disk0a: FreeBSD UFS disk1: BIOS drive D (3907029168 x 512): disk1p1: FreeBSD UFS OK ls disk1p1:/example disk1p1:/example d dir1 d dir2 OK ls disk0a:/boot open 'disk0a:/boot' failed: no such file or directory OK ls disk0a:/root open 'disk0a:/root' failed: no such file or directory -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234031] loader can't traverse filesystem, LUA ERROR: cannot open /boot/lua/loader.lua
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234031 Rodrigo N. Hernandez changed: What|Removed |Added Keywords||needs-qa See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=2330 ||98 CC||rodrigo.freebsd@minasambien ||te.com.br Status|New |Open Assignee|b...@freebsd.org|kev...@freebsd.org --- Comment #1 from Rodrigo N. Hernandez --- Installing from media FreeBSD-12.0-RELEASE-amd64-disc1.iso in a VM (VirtualBox), legacy BIOS mode and BSD disklabel resulted in the same error: Can't boot with "LUA ERROR: cannot open /boot/lua/loader.lua: no such file or directory." -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234028] Openssl cannot decrypt properly
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234028 --- Comment #5 from bc...@lafn.org --- It does seem to work when -md md5 is used. However, I point out that the -md parameter is not documented in the man page for enc on 11.1 or earlier. It does appear in 12.0. But it only lists the default for 12.0. Even if I knew about that parameter, I would have no idea what the default value would have been. The decryption with the wrong md does generate output, but it is not correct. enc even notifies you of this with the message "bad decrypt" which is in your output. Why it bothers to generate garbage output when it knows the decrypt failed is interesting. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 233098] can not find lua loader
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233098 Rodrigo N. Hernandez changed: What|Removed |Added CC||rodrigo.freebsd@minasambien ||te.com.br Assignee|b...@freebsd.org|kev...@freebsd.org Status|New |Open Keywords||needs-qa -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234031] loader can't traverse filesystem, LUA ERROR: cannot open /boot/lua/loader.lua
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234031 Kubilay Kocak changed: What|Removed |Added Assignee|kev...@freebsd.org |b...@freebsd.org CC||kev...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234010] Lack of Unicode support in strfmon breaks monitary formatting
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234010
Conrad Meyer changed:
What|Removed |Added
Version|11.2-RELEASE|CURRENT
CC||c...@freebsd.org
--- Comment #1 from Conrad Meyer ---
Present on CURRENT as well. Full reproducer program:
#include
#include
#include
int
main(void) {
char buf[80];
double money = 123456.78;
setlocale(LC_MONETARY, "sv_SE.UTF-8");
strfmon(buf, sizeof(buf), "%i", money);
printf("'%s'\n", buf);
return 0;
}
$ ./a.exe | hd
27 31 32 33 c2 34 35 36 2c 37 38 20 53 45 4b 20 |'123.456,78 SEK |
//1 2 3 ^^ 4 5 6 ...
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
