Re: kern/119548: [pf] [ath] [patch] PF Altq with ath hostap problem
The following reply was made to PR kern/119548; it has been noted by GNATS. From: Mel <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: Subject: Re: kern/119548: [pf] [ath] [patch] PF Altq with ath hostap problem Date: Tue, 29 Jan 2008 17:04:42 +0100 On Friday 11 January 2008 18:44:19 [EMAIL PROTECTED] wrote: > Old Synopsis: [pf] [ath] PF Altq with ath hostap problem > New Synopsis: [pf] [ath] [patch] PF Altq with ath hostap problem > > State-Changed-From-To: open->feedback > State-Changed-By: linimon > State-Changed-When: Fri Jan 11 17:43:47 UTC 2008 > State-Changed-Why: > To submitter: a patch has been created, can you give it a try please? Sure, where is it? -- Mel ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kern/119548: [pf] [ath] [patch] PF Altq with ath hostap problem
On Friday 11 January 2008 18:44:19 [EMAIL PROTECTED] wrote: > Old Synopsis: [pf] [ath] PF Altq with ath hostap problem > New Synopsis: [pf] [ath] [patch] PF Altq with ath hostap problem > > State-Changed-From-To: open->feedback > State-Changed-By: linimon > State-Changed-When: Fri Jan 11 17:43:47 UTC 2008 > State-Changed-Why: > To submitter: a patch has been created, can you give it a try please? Sure, where is it? -- Mel ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kern/119548: [pf] [ath] [patch] PF Altq with ath hostap problem
The following reply was made to PR kern/119548; it has been noted by GNATS. From: Mel <[EMAIL PROTECTED]> To: "Sepherosa Ziehau" <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED], freebsd-net@freebsd.org, [EMAIL PROTECTED] Subject: Re: kern/119548: [pf] [ath] [patch] PF Altq with ath hostap problem Date: Tue, 29 Jan 2008 20:20:41 +0100 On Tuesday 29 January 2008 18:01:30 Sepherosa Ziehau wrote: > On Jan 29, 2008 8:53 PM, Mel <[EMAIL PROTECTED]> wrote: > > On Friday 11 January 2008 18:44:19 [EMAIL PROTECTED] wrote: > > > Old Synopsis: [pf] [ath] PF Altq with ath hostap problem > > > New Synopsis: [pf] [ath] [patch] PF Altq with ath hostap problem > > > > > > State-Changed-From-To: open->feedback > > > State-Changed-By: linimon > > > State-Changed-When: Fri Jan 11 17:43:47 UTC 2008 > > > State-Changed-Why: > > > To submitter: a patch has been created, can you give it a try please? > > > > Sure, where is it? > > http://people.freebsd.org/~sephe/ieee80211_input.c.6_3.diff Confirmed it fixes the problem. Thanks a bundle! -- Mel ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kern/119548: [pf] [ath] [patch] PF Altq with ath hostap problem
On Tuesday 29 January 2008 18:01:30 Sepherosa Ziehau wrote: > On Jan 29, 2008 8:53 PM, Mel <[EMAIL PROTECTED]> wrote: > > On Friday 11 January 2008 18:44:19 [EMAIL PROTECTED] wrote: > > > Old Synopsis: [pf] [ath] PF Altq with ath hostap problem > > > New Synopsis: [pf] [ath] [patch] PF Altq with ath hostap problem > > > > > > State-Changed-From-To: open->feedback > > > State-Changed-By: linimon > > > State-Changed-When: Fri Jan 11 17:43:47 UTC 2008 > > > State-Changed-Why: > > > To submitter: a patch has been created, can you give it a try please? > > > > Sure, where is it? > > http://people.freebsd.org/~sephe/ieee80211_input.c.6_3.diff Confirmed it fixes the problem. Thanks a bundle! -- Mel ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [Wireless] Can't connect to wlan
my girl came home from work and did the "down and list scan trick": Apr 1 17:53:06 laptop sudo: rachie : TTY=ttyp1 ; PWD=/home/rachie ; USER=root ; COMMAND=/sbi n/ifconfig wpi0 down Apr 1 17:53:06 laptop kernel: Disabling Firmware execution Apr 1 17:53:06 laptop kernel: wpi_newstate: AUTH -> INIT Apr 1 17:53:10 laptop sudo: rachie : TTY=ttyp1 ; PWD=/home/rachie ; USER=root ; COMMAND=/sbi n/ifconfig wpi0 up list scan Apr 1 17:53:11 laptop kernel: wpi0: timeout resetting Tx ring 1 Apr 1 17:53:11 laptop kernel: wpi0: timeout resetting Tx ring 3 Apr 1 17:53:11 laptop kernel: wpi0: timeout resetting Tx ring 4 Apr 1 17:53:11 laptop kernel: Disabling Firmware execution Apr 1 17:53:11 laptop kernel: wpi_newstate: INIT -> INIT Apr 1 17:53:11 laptop kernel: Resetting the card - clearing any uploaded firmware Apr 1 17:53:11 laptop kernel: Attempting Loading Firmware from wpi_fw module Apr 1 17:53:11 laptop kernel: Firmware Version: Major 2, Minor 14, Driver 4, Apr 1 17:53:11 laptop kernel: runtime (text: 80524, data: 32768) init (text: 2668, data 32768) boot (text 900) Apr 1 17:53:11 laptop kernel: rtext 0xf802020 Apr 1 17:53:11 laptop kernel: rdata 0x0 Apr 1 17:53:11 laptop kernel: itext 0xf802020 Apr 1 17:53:11 laptop kernel: idata 0x0 Apr 1 17:53:11 laptop kernel: btext 0xf802020 Apr 1 17:53:11 laptop kernel: Loading microcode size 0x384 Apr 1 17:53:11 laptop kernel: firmware status=0x, val=0x4040, result=0x4040 Apr 1 17:53:11 laptop kernel: Status Match! - ntries = 0 Apr 1 17:53:11 laptop kernel: microcode alive notification version 10e02 alive 1 Apr 1 17:53:11 laptop kernel: microcode alive notification version 10e02 alive 1 Apr 1 17:53:11 laptop kernel: Firmware loaded to driver successfully Apr 1 17:53:11 laptop kernel: wpi_newstate: INIT -> SCAN Apr 1 17:53:11 laptop kernel: wpi_ops: command: 1 Apr 1 17:53:11 laptop kernel: wpi_ops: command: 8 Apr 1 17:53:13 laptop kernel: scan finished nchan=1 status=1 chan=165 Apr 1 17:53:13 laptop kernel: wpi_newstate: SCAN -> AUTH Apr 1 17:53:13 laptop kernel: wpi_ops: command: 4 Apr 1 17:53:13 laptop kernel: wpi_ops: command: 8 Apr 1 17:53:13 laptop kernel: Ignoring WPI_SET_CHAN Apr 1 17:53:13 laptop kernel: wpi_ops: command: 8 Apr 1 17:53:13 laptop kernel: Ignoring WPI_SET_CHAN Apr 1 17:53:13 laptop kernel: wpi_ops: command: 16 Apr 1 17:53:13 laptop kernel: config chan 1 flags 8005 cck f ofdm 15 Apr 1 17:53:13 laptop kernel: wpi_newstate: AUTH -> ASSOC Apr 1 17:53:13 laptop kernel: wpi_newstate: ASSOC -> RUN Apr 1 17:53:13 laptop kernel: wpi_ops: command: 32 Apr 1 17:53:13 laptop kernel: config chan 1 flags 8035 Apr 1 17:53:13 laptop kernel: wpi0: link state changed to UP At this point it's working again, connection is flakey with packet loss ranging from 0 to 50% but it's working. This is wpi from 7-RELEASE with patch mentioned in this thread. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[panic] Kernel corruption of pppoe lists
>Submitter-Id: current-users >Originator: Mel Flynn >Confidential: no >Synopsis: [panic] Kernel corruption of pppoe lists >Severity: critical >Priority: low >Category: kern >Class: sw-bug >Release: FreeBSD 7.2-STABLE i386 >Environment: System: FreeBSD gate.rachie.is-a-geek.net 7.2-STABLE FreeBSD 7.2-STABLE #0: Sun Jun 28 00:01:59 AKDT 2009 m...@squish.rachie.is-a-geek.net:/data/obj/data/RELENG_7/src/sys/GATE i386 >Description: I realize the kernel is a bit old, but it also very hard to reproduce. Kernel was up 56 days and this crash happened shortly after a very long connect time, hangup by ISP and some renegotiation issues. I can provide the ppp.log of the incident if needed. What bothers me is the contents of the session list element, preceding the element cannot be accessed. Clearly, there is random kernel memory present there, judging from ether_dhost and ether_shost. # kgdb /boot/kernel/kernel /var/crash/vmcore.0 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd"... Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x2d465459 fault code = supervisor read, page not present instruction pointer = 0x20:0xc06cd0a0 stack pointer = 0x28:0xc3b86a98 frame pointer = 0x28:0xc3b86ac0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 35 (irq22: xl0) trap number = 12 panic: page fault Uptime: 56d6h29m38s Physical memory: 1007 MB Dumping 174 MB: 159 143 127 111 95 79 63 47 31 15 Reading symbols from /boot/kernel/geom_journal.ko...Reading symbols from /boot/kernel/geom_journal.ko.symbols...done. done. Loaded symbols for /boot/kernel/geom_journal.ko Reading symbols from /boot/kernel/wlan_xauth.ko...Reading symbols from /boot/kernel/wlan_xauth.ko.symbols...done. done. Loaded symbols for /boot/kernel/wlan_xauth.ko Reading symbols from /boot/kernel/acpi.ko...Reading symbols from /boot/kernel/acpi.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi.ko Reading symbols from /boot/kernel/if_bridge.ko...Reading symbols from /boot/kernel/if_bridge.ko.symbols...done. done. Loaded symbols for /boot/kernel/if_bridge.ko Reading symbols from /boot/kernel/bridgestp.ko...Reading symbols from /boot/kernel/bridgestp.ko.symbols...done. done. Loaded symbols for /boot/kernel/bridgestp.ko Reading symbols from /boot/kernel/ng_ether.ko...Reading symbols from /boot/kernel/ng_ether.ko.symbols...done. done. Loaded symbols for /boot/kernel/ng_ether.ko Reading symbols from /boot/kernel/ng_socket.ko...Reading symbols from /boot/kernel/ng_socket.ko.symbols...done. done. Loaded symbols for /boot/kernel/ng_socket.ko Reading symbols from /boot/kernel/daemon_saver.ko...Reading symbols from /boot/kernel/daemon_saver.ko.symbols...done. done. Loaded symbols for /boot/kernel/daemon_saver.ko #0 doadump () at pcpu.h:196 196 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:196 #1 0xc05ef5d3 in boot (howto=260) at /data/RELENG_7/src/sys/kern/kern_shutdown.c:418 #2 0xc05ef7de in panic (fmt=Variable "fmt" is not available. ) at /data/RELENG_7/src/sys/kern/kern_shutdown.c:574 #3 0xc085c72c in trap_fatal (frame=0xc3b86a58, eva=759583833) at /data/RELENG_7/src/sys/i386/i386/trap.c:938 #4 0xc085c9b0 in trap_pfault (frame=0xc3b86a58, usermode=0, eva=759583833) at /data/RELENG_7/src/sys/i386/i386/trap.c:851 #5 0xc085d339 in trap (frame=0xc3b86a58) at /data/RELENG_7/src/sys/i386/i386/trap.c:529 #6 0xc0844a4b in calltrap () at /data/RELENG_7/src/sys/i386/i386/exception.s:166 #7 0xc06cd0a0 in pppoe_findsession (privp=0xc4258000, wh=Variable "wh" is not available. ) at /data/RELENG_7/src/sys/netgraph/ng_pppoe.c:567 #8 0xc06ce1a0 in ng_pppoe_rcvdata_ether (hook=0xc41b6380, item=0xc4256120) at /data/RELENG_7/src/sys/netgraph/ng_pppoe.c:1612 #9 0xc06c566f in ng_apply_item (node=0xc4111e80, item=0xc4256120, rw=0) at /data/RELENG_7/src/sys/netgraph/ng_base.c:2336 #10 0xc06c47e0 in ng_snd_item (item=0xc4256120, flags=Variable "flags" is not available. ) at /data/RELENG_7/src/sys/netgraph/ng_base.c:2254 #11 0xc068de5f in ether_demux (ifp=0xc3dbb400, m=0xc8024d00) at /data/RELENG_7/src/sys/net/if_ethersubr.c:851 #12 0xc068e1b3 in ether_input (ifp=0xc3dbb400, m=0xc8024d00) at /data/RELENG_7/src/sys/net/if_ethersubr
Re: 6rd: when in Base FreeBSD?
On 10/11/2017 19:11, Don Lewis wrote: On 11 Oct, Larry Rosenman wrote: The WAN address is DHCP. The DHCP WAN address could be problematic. To do this with a DHCP WAN address, create a dhclient hook script that destroys and recreates the gif tunnel if the WAN address changes. I used to have to do something similar with my previous provider (they also used 6rd). ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Can Ethernet and wi-fi be used concurrently?
On 2019-06-22 18:24, Thomas Mueller wrote: I would like to know if it is possible to have both Ethernet and wi-fi running concurrently? Purpose would be, if the cable service is down, meaning no internet access but intranet OK, to continue to have intranet access while using wi-fi with a mobile phone as hotspot to aceess the internet. If you can keep the mobile hotspot disconnected until you need it, configure the wired interface with a higher metric than the wireless interface and routing will do the rest for you. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Can Ethernet and wi-fi be used concurrently?
On 2019-06-22 19:05, John Lyon wrote: You should be able to use the lagg driver to combine the two interfaces in failover mode to achieve your goal. lagg doesn't apply here because Thomas's issue is routing failover. The master interface would remain up for intranet access. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
IPv6-only network--is NAT64+DNS64 really this easy now?
I'm looking to set up a pure-IPv6 environment to test the viability of it. I tried this a few years ago and fell flat on my face due to the lack of NAT64 and DNS64 support. Reading through docs now, it looks like unbound has a DNS64 module, and NAT64 is baked into ipfw. Waving a hand at bug-hunting and lamentations over the inertia of embedded systems designers, has it really become this easy to turn up an IPv6-only site? ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: IPv6-only network--is NAT64+DNS64 really this easy now?
On 2019-06-24 19:33, Ultima wrote: Hello Mel, While it may be possible to have an IPv6 only environment, I don't think it is really viable. There are simply too many things that don't run on or have very limited support for IPv6 that it makes it very hard to drop IPv4 altogether and until something comes along forcing the move it likely won't happen for at least another decade at the minimum. Yes, that is why I wrote "Waving a hand at bug-hunting and lamentations over the inertia of embedded systems designers". This a lab experiment specifically to iron out the very wrinkles you just stated. On Mon, Jun 24, 2019 at 6:50 PM Mel Pilgrim wrote: I'm looking to set up a pure-IPv6 environment to test the viability of it. I tried this a few years ago and fell flat on my face due to the lack of NAT64 and DNS64 support. Reading through docs now, it looks like unbound has a DNS64 module, and NAT64 is baked into ipfw. Waving a hand at bug-hunting and lamentations over the inertia of embedded systems designers, has it really become this easy to turn up an IPv6-only site? ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: DHCPv6 Support in FreeBSD Base
On 2016-06-09 14:14, David Bright wrote: Following up on a conversation I started today at BSDCan 2016/DevSummit. I’d like to see support for DHCPv6 in the base system. I have made modifications to network.subr and the rc.d init scripts to allow configuring a network interface to use DHCPv6 in a manner very similar to that currently used for DHCPv4. This works assuming that you have a DHCPv6 client. For the purposes of my development I used the ISC client from ports. These changes were based on 10.0-RELEASE and I am in the process of adapting these changes to 11 so they can be pushed upstream. However, they will be unusable (albeit harmless) in the base system without a client. * Is there any barrier to updating the dhclient in base to the current ISC dhclient for both DHCPv4 & DHCPv6? * Is there any barrier to replacing the current dhclient-script with that that accompanies the ISC dhclient? The two scripts are quite different and my DHCPv6 changes currently are based on the ISC dhclient-script. As I’ve already done a fair amount of this work, I’d be happy to work on getting it in shape for pushing to HEAD. I had several people today at the devsummit indicate that they thought that would be a good idea, but I thought it would be a good idea to ask ahead of time if there were any known stumbling blocks to doing that. Could the WIDE client be used instead? Unlike the ISC client, it will configure downstream interfaces from PD prefixes without needing an external script. It also completely avoids the problem of trying to update the in-base dhclient. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
CenturyLink gigabit PPPoE/igb, are there still performance issues?
I have CenturyLink GPON service, which uses PPPoE. I've read about the performance bottleneck with PPPoE over igb interfaces limiting throughput to only a few hundred Mbps unless run on fairly capable hardware. Caveat: the posts that discuss this issue are a few years old. The hardware I have is a Xeon E3-1245v6 with igb interfaces. That seems like it should be beefy enough to handle a gigabit of PPPoE. In testing, I get 800+ Mbps when connected though the router provided by CenturyLink, but only 350 Mbps when connected directly to the ONT. If I add an em-based NIC, will that work around the issue? Is a cxgbe-based NIC the better choice? ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
RealTek 2.5 GbE (RTL8125) support?
Are RealTek 2.5 GbE NICs (RTL8125) supported? I don't see RLT8125 parts listed in if_re(4) or if_re.c, and that appears to be the only driver for RealTek gigabit NICs? ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
RealTek 2.5 GbE (RTL8125) support?
Are RealTek 2.5 GbE NICs (RTL8125) supported? I don't see RLT8125 parts listed in if_re(4) or if_re.c, and that appears to be the only driver for RealTek gigabit NICs? ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
