[Bug 278306] service netif start doesn't bring up the wireless interface if /etc/wpa_supplicant.conf is missing

2024-09-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278306

--- Comment #12 from Gleb Popov  ---
(In reply to Oleksandr Kryvulia from comment #9)
Hmm, I'm on 14.1-RELEASE and "up WPA DHCP" doesn't work me. The interface is
not up after "service netif restart" if there is no wpa_supplicant.conf

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 278306] service netif start doesn't bring up the wireless interface if /etc/wpa_supplicant.conf is missing

2024-09-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278306

--- Comment #13 from Gleb Popov  ---
Ah, disregard my previous comment, I have a problem with the driver itself.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 278306] service netif start doesn't bring up the wireless interface if /etc/wpa_supplicant.conf is missing

2024-09-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278306

--- Comment #14 from Gleb Popov  ---
Yes, adding the "up" word makes it work indeed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 279850] wireguard: wg(8) fails on INET6-only kernel

2024-09-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279850

--- Comment #4 from Lexi Winter  ---
the patch fixes wg(8) at least when no tunnels are configured:

[3!] daphne ~# uname -v
FreeBSD 15.0-CURRENT #4 lf/main-n269059-d5fdf4feedd2: Fri Sep  6 14:58:45 BST
2024
srcma...@daphne.eden.le-fay.org:/src/obj/src/freebsd/lf/main/arm64.aarch64/sys/LFV6
[4!] daphne ~# wg
[5!] daphne ~# 

i'm waiting for my amd64 build to finish at which point i can test this on a
system with IPv6-only tunnels configured.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 281211] MV88E6190X switch variant not supported by e6000sw

2024-09-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281211

Stas Alekseev  changed:

   What|Removed |Added

 Attachment #253336|0   |1
is obsolete||

--- Comment #5 from Stas Alekseev  ---
Created attachment 253377
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=253377&action=edit
Proposed patch rev 2

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 280701] FreeBSD-SA-24:05 fix breaks ICMP/ICMP6 states handling in pf firewall (ping, traceroute)

2024-09-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280701

--- Comment #80 from doktornotor  ---
As for the technical input: here is another *downstream* issue [1] with pf
debug log (i.e., set debug misc) getting flooded (300K+/day) with

> pf: ICMP error message too short (ip6)

from ND (NS/NA) packets. That *downstream* issue also surprisingly goes away
[2] when reverting [3] *all* those *upstream* patches related to
FreeBSD-SA-24:05.

H...

[1] https://github.com/opnsense/core/issues/7840
[2] https://forum.opnsense.org/index.php?topic=42632.msg211600#msg211600
[3] https://github.com/opnsense/src/commit/164bfe67604

-- 
You are receiving this mail because:
You are the assignee for the bug.


Ethernet device with shared mdio

2024-09-06 Thread Mike Belanger
The following device tree specifies a shared mdio.
The ffec driver uses miibus.
When there is a shared mdio, one of the device instances will not be able to 
properly configure the PHY, as it needs to use the other devices resource to 
read/write the PHY.

&fec1 {
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_fec1>;
phy-mode = "rgmii-id";
phy-handle = <ðphy0>;
fsl,magic-packet;
status = "okay";

mdio {
#address-cells = <1>;
#size-cells = <0>;

ethphy0: ethernet-phy@0 {
compatible = 
"ethernet-phy-ieee802.3-c22";
reg = <0>;
};

ethphy1: ethernet-phy@1 {
compatible = 
"ethernet-phy-ieee802.3-c22";
reg = <1>;
};
};
};

&fec2 {
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_fec2>;
phy-mode = "rgmii-txid";
phy-handle = <ðphy1>;
phy-supply = <®_fec2_supply>;
nvmem-cells = <&fec_mac1>;
nvmem-cell-names = "mac-address";
rx-internal-delay-ps = <2000>;
fsl,magic-packet;
status = "okay";
};

Does FreeBSD have any plans for supporting hardware that specifies a shared 
mdio in the dtb?
Just knowing the general approach being considered would be helpful.

--
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.


[Bug 279850] wireguard: wg(8) fails on INET6-only kernel

2024-09-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279850

--- Comment #5 from Lexi Winter  ---
already discussed this with Kevin^W Kyle on IRC, but for completeness, the
patch in comment #1 panics on boot on a system with tunnels configured:

Created clone interfaces: wg0 wg1 epair0a epair0b.
lo0: link state changed to UP
xn0: 2 link states coalesced
xn0: link state changed to UP


Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 02
fault virtual address   = 0x0
fault code  = supervisor write data, page not present
instruction pointer = 0x20:0x81e2a57f
stack pointer   = 0x28:0xfe0079d73a70
frame pointer   = 0x28:0xfe0079d73a80
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 331 (wg)
rdi: f80021e5d4d8 rsi: f80036b02800 rdx: f80021f46c48
rcx:   r8: f800074c8000  r9: 003a
rax:  rbx: f80036b02800 rbp: fe0079d73a80
r10:  r11: 0003 r12: f80036441c10
r13: f80021f4e1c0 r14: f80021f46c00 r15: 002f
trap number = 12
panic: page fault
cpuid = 1
time = 1725643323
KDB: stack backtrace:
#0 0x8045dccd at kdb_backtrace+0x5d
#1 0x80413b5f at vpanic+0x13f
#2 0x80413a13 at panic+0x43
#3 0x806954cb at trap_fatal+0x40b
#4 0x80695516 at trap_pfault+0x46
#5 0x8066c0f8 at calltrap+0x8
#6 0x81e284f1 at wg_ioctl+0x1531
#7 0x8051eed8 at ifioctl+0xd18
#8 0x8047f555 at kern_ioctl+0x255
#9 0x8047f29a at sys_ioctl+0x10a
#10 0x80695d85 at amd64_syscall+0x115
#11 0x8066ca0b at fast_syscall_common+0xf8
Uptime: 5s
Dumping 338 out of 6119 MB:..5%..15%..24%..34%..43%..53%..62%..71%..81%..95%
Dump complete

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 281211] MV88E6190X switch variant not supported by e6000sw

2024-09-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281211

Warner Losh  changed:

   What|Removed |Added

 CC||i...@freebsd.org
   Assignee|n...@freebsd.org |i...@freebsd.org

--- Comment #6 from Warner Losh  ---
Taken to coordinate with pull request.

-- 
You are receiving this mail because:
You are the assignee for the bug.