Re: bin/132798: [patch] ggatec(8): ggated/ggatec connection slowdown problem
Old Synopsis: ggated/ggatec New Synopsis: [patch] ggatec(8): ggated/ggatec connection slowdown problem Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Thu Mar 19 11:17:00 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=132798 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: ae(4) Wake-on-Lan MFC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 18 Mar 2009 17:15:05 + Bruce Simpson mentioned: > Pyun YongHyeon wrote: > > Do you have ae(4) hardware? I'm not sure why stas@ removed WOL part > > in the MFC but it could be lack of testing(CCed to stas@). I've > > attached diff that includes WOL support from HEAD. > > > > > > Thanks. I tested this OK on the EeePC 701 so I've committed it! > So, basically WOL works on 7.1 with ae and the PC resumes correctly? Thanks for committing this! - -- Stanislav Sedov ST4096-RIPE -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAknCT8IACgkQK/VZk+smlYHk6gCeMI1lvEnr/FTYwNgZSHEruD+h OTQAnRDWyKNEv3qF5jZONvlhJhWCFs4h =IUCd -END PGP SIGNATURE- !DSPAM:49c24f14967005928620533! ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
802.1x broken after SVN rev 189592
Hello. I do not really sure in this, but : after the current updated to 20090309 Merge IGMPv3 and Source-Specific Multicast (SSM) to the FreeBSD IPv4 stack. I can't use any wpa_supplicant related networks. It faulted in any WPA authentications , that i tried. Also it faulted when i try to login via 802.1x in my job network. All happens after i starts wpa_supplicant and looks like these: #11 0xc05cabec in panic (fmt=0xc08b16e9 "sbappendaddr_locked") at /opt/src/sys/kern/kern_shutdown.c:559 #12 0xc061fd40 in sbappendaddr_locked (sb=0xc66dd670, asa=0xc09021b4, m0=0xce435b00, control=0x0) at /opt/src/sys/kern/uipc_sockbuf.c:632 #13 0xc0620418 in sbappendaddr (sb=0xc66dd670, asa=0xc09021b4, m0=0xce435b00, control=0x0) at /opt/src/sys/kern/uipc_sockbuf.c:679 #14 0xc0671be4 in raw_input (m0=0xc64b0100, proto=0xe664ec60, src=0xc09021b4) at /opt/src/sys/net/raw_usrreq.c:96 #15 0xc06749e7 in rts_input (m=0xc64b0100) at /opt/src/sys/net/rtsock.c:151 #16 0xc066f752 in swi_net (dummy=0x0) at /opt/src/sys/net/netisr.c:145 #17 0xc05aa148 in intr_event_execute_handlers (p=0xc61617ec, ie=0xc61a2d00) at /opt/src/sys/kern/kern_intr.c:1134 #18 0xc05ab4d4 in ithread_loop (arg=0xc60ec660) at /opt/src/sys/kern/kern_intr.c:1147 #19 0xc05a7ac9 in fork_exit (callout=0xc05ab469 , arg=0xc60ec660, frame=0xe664ed38) at /opt/src/sys/kern/kern_fork.c:821 #20 0xc0833170 in fork_trampoline () at /opt/src/sys/i386/i386/exception.s:270 -- Vany Serezhkin. Yandex. http://yandex.ru/ ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
El día Tuesday, March 17, 2009 a las 11:56:24AM -0700, Sam Leffler escribió: > His setup is static key wep; not wpa so I don't think wpa_supplicant is > the issue. > > Matthias, your tcpdump of the dhclient packets isn't usable; please try: > > tcpdump -i ath0 -n -y IEEE802_11_RADIO > > I reviewed the driver to the code in HEAD and the only difference in the > crypto area should not matter in this case. It's possible wme is > somehow enabled and causing problems but the ifconfig output doesn't > indicate that. > > If you can find out the model of ap that might be helpful. > Unfortunately the best thing to try is HEAD. I will try to collect a better tcpdump of the dhclient packets on the weekend and as well figure out what kind of model the AP is; would it be helpful to connect with a Windows XP laptop (which seems to work) to gather some information of the Wifi and other network parameters? how this could be seen in Windows? maybe there is some special compression of the payload of the packages in place? I have seen such 'options' in another AP (a Netgear WGT624 v3), the option was called "[ ] Disable Advanced 108Mbps Features" and this must be checked (i.e. disabled) to make DHCP happy with the ath0 EeePC; unfortunately I can't look into the AP about this problem is :-( thx matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.oclc.org/ http://www.UnixArea.de/ ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
multiple interfaces and pf rdr bug
When configuring a system with three interfaces, two of them as a transparent bridge and a management interface one could configure the rules to allow users to connect to the management interface from being behind the bridge. However, if an rdr rule is applied to force this then, the clients connections time out. If the clients with this rule applied attempt to go directly to the management interface they are able to and if the rdr rule is changed to anything other than the management interface it works. There are allow rules created on the inside interface of the bridge and all other interfaces are set to skip. Can anyone else confirm this is a bug or correct me on my logic? ~Patrick ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
Matthias Apitz wrote: El día Tuesday, March 17, 2009 a las 11:56:24AM -0700, Sam Leffler escribió: His setup is static key wep; not wpa so I don't think wpa_supplicant is the issue. Matthias, your tcpdump of the dhclient packets isn't usable; please try: tcpdump -i ath0 -n -y IEEE802_11_RADIO I reviewed the driver to the code in HEAD and the only difference in the crypto area should not matter in this case. It's possible wme is somehow enabled and causing problems but the ifconfig output doesn't indicate that. If you can find out the model of ap that might be helpful. Unfortunately the best thing to try is HEAD. I will try to collect a better tcpdump of the dhclient packets on the weekend and as well figure out what kind of model the AP is; would it be helpful to connect with a Windows XP laptop (which seems to work) to gather some information of the Wifi and other network parameters? how this could be seen in Windows? maybe there is some special compression of the payload of the packages in place? Having a packet trace of a working connection to compare would be very helpful. I have seen such 'options' in another AP (a Netgear WGT624 v3), the option was called "[ ] Disable Advanced 108Mbps Features" and this must be checked (i.e. disabled) to make DHCP happy with the ath0 EeePC; That controls SuperG support in Atheros-based ap's and is unrelated. There is a known problem with SuperG support that has been fixed in HEAD but not yet backmerged. For reasons unknown your (apparently) simple setup is not working. I do not use RELENG_7 w/ the stock wireless and have no familiarity with it's status so it's more likely there's just some bug fix not back-merged. unfortunately I can't look into the AP about this problem is :-( thx matthias ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: 802.1x broken after SVN rev 189592
Vany Serezhkin wrote: Hello. I do not really sure in this, but : after the current updated to 20090309 Merge IGMPv3 and Source-Specific Multicast (SSM) to the FreeBSD IPv4 stack. I can't use any wpa_supplicant related networks. It faulted in any WPA authentications , that i tried. Also it faulted when i try to login via 802.1x in my job network. All happens after i starts wpa_supplicant and looks like these: #11 0xc05cabec in panic (fmt=0xc08b16e9 "sbappendaddr_locked") at /opt/src/sys/kern/kern_shutdown.c:559 #12 0xc061fd40 in sbappendaddr_locked (sb=0xc66dd670, asa=0xc09021b4, m0=0xce435b00, control=0x0) at /opt/src/sys/kern/uipc_sockbuf.c:632 #13 0xc0620418 in sbappendaddr (sb=0xc66dd670, asa=0xc09021b4, m0=0xce435b00, control=0x0) at /opt/src/sys/kern/uipc_sockbuf.c:679 #14 0xc0671be4 in raw_input (m0=0xc64b0100, proto=0xe664ec60, src=0xc09021b4) at /opt/src/sys/net/raw_usrreq.c:96 #15 0xc06749e7 in rts_input (m=0xc64b0100) at /opt/src/sys/net/rtsock.c:151 #16 0xc066f752 in swi_net (dummy=0x0) at /opt/src/sys/net/netisr.c:145 #17 0xc05aa148 in intr_event_execute_handlers (p=0xc61617ec, ie=0xc61a2d00) at /opt/src/sys/kern/kern_intr.c:1134 #18 0xc05ab4d4 in ithread_loop (arg=0xc60ec660) at /opt/src/sys/kern/kern_intr.c:1147 #19 0xc05a7ac9 in fork_exit (callout=0xc05ab469 , arg=0xc60ec660, frame=0xe664ed38) at /opt/src/sys/kern/kern_fork.c:821 #20 0xc0833170 in fork_trampoline () at /opt/src/sys/i386/i386/exception.s:270 Are you certain it's that revision? Have you tried r189931 which worked around certain problems in the initial commit? Can you provide sufficient info to reproduce your problem? Filing a PR for reference is likely the best thing to do. Sam ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: ae(4) Wake-on-Lan MFC
Stanislav Sedov wrote: So, basically WOL works on 7.1 with ae and the PC resumes correctly? That's what I saw. Video is still broken for me on resume, though everything else on the EeePC 701 resumed OK. cheers, BMS ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: 802.1x broken after SVN rev 189592
Hi, Based on the backtrace you've provided, this doesn't seem like a multicast related issue. I skimmed wpa_supplicant and I see that whilst it requests a link-layer multicast address, it does not use IPv4 multicast. Vany Serezhkin wrote: Hello. I do not really sure in this, but : after the current updated to 20090309 Merge IGMPv3 and Source-Specific Multicast (SSM) to the FreeBSD IPv4 stack. I can't use any wpa_supplicant related networks. It faulted in any WPA authentications , that i tried. Also it faulted when i try to login via 802.1x in my job network. General questions: Are you running any routing protocols on this machine, or anything which opens a multicast socket at system startup? Do you have more than one processor core enabled? Can you transcribe the console panic message so we can see which process has panicked in the routing socket path? thanks, BMS ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: ae(4) Wake-on-Lan MFC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 19 Mar 2009 16:13:18 + Bruce Simpson mentioned: > Stanislav Sedov wrote: > > > > So, basically WOL works on 7.1 with ae and the PC resumes correctly? > > > > That's what I saw. Video is still broken for me on resume, though everything > else on the EeePC 701 resumed OK. > For video you will probably need sysctl hw.acpi.asus.lcd_brightness=8 in rc.resume. At least, this is required to bring the screen back to light. - -- Stanislav Sedov ST4096-RIPE -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAknCdrcACgkQK/VZk+smlYH+HACfYBiDVlymoUTr2weNn3A+2ZT0 v50AnRGpfsGEJz5mMJ5PzvPfFC+ek17b =XgJ0 -END PGP SIGNATURE- !DSPAM:49c27609967005190327887! ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: 802.1x broken after SVN rev 189592
Hello again. Bruce Simpson wrote: General questions: Are you running any routing protocols on this machine, or anything which opens a multicast socket at system startup? No, any it is a simple work notebook. May be it avahi or hald starts something, but i think they isn't. Do you have more than one processor core enabled? Yes, dualcore T7500 on i945. Can you transcribe the console panic message so we can see which process has panicked in the routing socket path? Please help me, i not too familiar with kdb, I can only type panic and kernel dumps to file, an then use kgdb. Is it enough ? Now i update system to current state and try this manipulations again. -- Vany Serezhkin. Yandex. http://yandex.ru/ ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: kern/122427: [apm] [panic] apm and mDNSResponder cause panic during shutdown (multicast)
Synopsis: [apm] [panic] apm and mDNSResponder cause panic during shutdown (multicast) State-Changed-From-To: open->closed State-Changed-By: bms State-Changed-When: Thu 19 Mar 2009 17:45:25 UTC State-Changed-Why: fixed in RELENG_6 and up http://www.freebsd.org/cgi/query-pr.cgi?pr=122427 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: kern/122839: [multicast] FreeBSD 7 multicast routing problem
The following reply was made to PR kern/122839; it has been noted by GNATS. From: Bruce Simpson To: Eugene <4...@legis.krsn.ru>, freebsd-gnats-sub...@freebsd.org Cc: Subject: Re: kern/122839: [multicast] FreeBSD 7 multicast routing problem Date: Thu, 19 Mar 2009 17:47:38 + Hi, Have you managed to chase the em(4) patch upstream? It would be great if you could let me know so this PR can either be closed, or assigned to the em(4) driver maintainer. thanks, BMS ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
kern/122839: [multicast] FreeBSD 7 multicast routing problem
Hi, As i wrote before, based on the patch, suggested by Tomas Svensson, we have made our version of that patch. And about a year already we using it on a production inside core router without any problems. Also we patched if_msk.c, and it also working just fine same amount of time on the same router. Both our patches for if_em.c and if_msk.c i have posted to the list. So i did not chased the em or msk patch upstream. Thanks, Eugene H. Brezin Bruce Simpson 20.03.2009 00:47 Кому: Eugene <4...@legis.krsn.ru>, freebsd-gnats-sub...@freebsd.org Копия: Тема: Re: kern/122839: [multicast] FreeBSD 7 multicast routing problem Hi, Have you managed to chase the em(4) patch upstream? It would be great if you could let me know so this PR can either be closed, or assigned to the em(4) driver maintainer. thanks, BMS ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
kern/122839: [multicast] FreeBSD 7 multicast routing problem
The following reply was made to PR kern/122839; it has been noted by GNATS. From: 4...@legis.krsn.ru To: bug-follo...@freebsd.org, b...@freebsd.org, freebsd-net@FreeBSD.org Cc: Subject: kern/122839: [multicast] FreeBSD 7 multicast routing problem Date: Fri, 20 Mar 2009 12:54:41 +0700 SGksIA0KDQpBcyBpIHdyb3RlIGJlZm9yZSwgYmFzZWQgb24gdGhlIHBhdGNoLCBzdWdnZXN0ZWQg YnkgVG9tYXMgU3ZlbnNzb24sIHdlIA0KaGF2ZSBtYWRlIG91ciB2ZXJzaW9uIG9mIHRoYXQgcGF0 Y2guIEFuZCBhYm91dA0KYSB5ZWFyIGFscmVhZHkgd2UgdXNpbmcgaXQgb24gYSBwcm9kdWN0aW9u IGluc2lkZSBjb3JlIHJvdXRlciB3aXRob3V0IGFueSANCnByb2JsZW1zLiBBbHNvIHdlIHBhdGNo ZWQgIGlmX21zay5jLCBhbmQgaXQgYWxzbw0Kd29ya2luZyBqdXN0IGZpbmUgc2FtZSBhbW91bnQg b2YgdGltZSBvbiB0aGUgc2FtZSByb3V0ZXIuIEJvdGggb3VyIHBhdGNoZXMgDQpmb3IgaWZfZW0u YyBhbmQgaWZfbXNrLmMgaSBoYXZlIHBvc3RlZCB0byB0aGUgbGlzdC4NClNvIGkgZGlkIG5vdCBj aGFzZWQgdGhlIGVtIG9yIG1zayBwYXRjaCB1cHN0cmVhbS4NCg0KVGhhbmtzLCANCkV1Z2VuZSBI LiBCcmV6aW4NCg0KDQoNCg0KDQpCcnVjZSBTaW1wc29uIDxibXNAaW5jdW5hYnVsdW0ubmV0Pg0K MjAuMDMuMjAwOSAwMDo0Nw0KIA0KICAgICAgICDrz83VOiAgIEV1Z2VuZSA8NHByQGxlZ2lzLmty c24ucnU+LCANCmZyZWVic2QtZ25hdHMtc3VibWl0QGZyZWVic2Qub3JnDQogICAgICAgIOvP0MnR OiANCiAgICAgICAg9MXNwTogICBSZToga2Vybi8xMjI4Mzk6IFttdWx0aWNhc3RdIEZyZWVCU0Qg NyBtdWx0aWNhc3Qgcm91dGluZyANCnByb2JsZW0NCg0KDQpIaSwNCg0KSGF2ZSB5b3UgbWFuYWdl ZCB0byBjaGFzZSB0aGUgZW0oNCkgcGF0Y2ggdXBzdHJlYW0/DQoNCkl0IHdvdWxkIGJlIGdyZWF0 IGlmIHlvdSBjb3VsZCBsZXQgbWUga25vdyBzbyB0aGlzIFBSIGNhbiBlaXRoZXIgYmUgDQpjbG9z ZWQsDQpvciBhc3NpZ25lZCB0byB0aGUgZW0oNCkgZHJpdmVyIG1haW50YWluZXIuDQoNCnRoYW5r cywNCkJNUw0KDQoNCg== ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
