[Bug 283783] ipfw parser does not handle src-port keyword
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283783 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|i...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283785] Keyboard/Trackpad on HP OMEN Transcend Laptop 16-u0057nr (7K931UA) not working.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283785 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|multime...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 165059] vtnet(4): Networking breaks with a router using virtio net driver on KVM host
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165059 --- Comment #39 from John Nielsen --- (In reply to John Nielsen from comment #36) I was mistaken, my KVM-hosted router does suffer from this issue. So even more happy to test patches than previously stated. What needs to happen in terms of fixing (or ignoring) the bad checksums for the NAT case and where? In the firewall/NAT code? vtnet driver? Somewhere else? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283783] ipfw parser does not handle src-port keyword
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283783 Bug ID: 283783 Summary: ipfw parser does not handle src-port keyword Product: Base System Version: Unspecified Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: j...@jimby.name While the ipfw parser does handle the "dst-port" keyword, it seems it does not handle the "src-port" keyword. Steps to reproduce: # kldload ipfw # ipfw -q flush # ipfw add 1000 allow tcp from 203.0.113.10 to me dst-port 22 01000 allow tcp from 203.0.113.10 to me 22 # # ipfw add 1000 allow tcp from 203.0.113.10 src-port 3030 to me ipfw: missing ``to'' (Apologies if this is a known bug. I did not find it during a prior search.) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283785] Keyboard/Trackpad on HP OMEN Transcend Laptop 16-u0057nr (7K931UA) not working.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283785 --- Comment #1 from Vladimir Kondratyev --- Try to add following line to /boot/loader.conf: hw.usb.usbhid.enable=1 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283528] I need an alias for the symbol getaddrinfo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283528 Konstantin Belousov changed: What|Removed |Added CC||k...@freebsd.org --- Comment #1 from Konstantin Belousov --- If you have an object a.so that interposes symbol A, the usual way to access the symbol A from beneath a.so is using dlsym(RTLD_NEXT, "A"). To get guaranteed results for symbols exported from libc, like "getaddrinfo", ensure that your interposer is linked to libc. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 275086] Old i386 boot: CPU0: local APIC error 0x4 – Cannot boot any longer
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275086 b...@desync.com changed: What|Removed |Added CC||b...@desync.com --- Comment #3 from b...@desync.com --- Created attachment 256313 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=256313&action=edit fix The offending commit appears to be 279cd05b7e4d. 0x4 in the ECR is apparently: > Bit 2: Send Accept Error. > Set when the local APIC detects that a message it sent was not accepted by > any > APIC on the APIC bus. Used only on P6 family and Pentium processors. I guess pre-P4 systems don't like IPIs fired off into oblivion. Attached patch adds a check for multiple CPUs to match the one in smp_targeted_tlb_shootdown(), which seems to be the only other caller. Tested on single-CPU 440BX and multiprocessor i840. -- You are receiving this mail because: You are the assignee for the bug.
