Re: 8139 driver question
On Thu, Feb 02, 2012 at 08:43:09AM -0600, Matt Renzelmann wrote: Hello, This will seem a bit off the wall, but I just noticed a discrepancy between the registers defined in the pci/if_rlreg.h directory and those specified on the RealTek datasheets for the antique RealTek 8139. In particular, as defined in the header, the registers in question are: #define RL_CFG0 0x0051 /* config register #0 */ #define RL_CFG1 0x0052 /* config register #1 */ #define RL_CFG2 0x0053 /* config register #2 */ #define RL_CFG3 0x0054 /* config register #3 */ #define RL_CFG4 0x0055 /* config register #4 */ #define RL_CFG5 0x0056 /* config register #5 */ The RealTek data sheets for the 8139, however, all indicate that these should be set to something like this: #define RL_CFG0 0x0051 /* config register #0 */ #define RL_CFG1 0x0052 /* config register #1 */ // No Config2 #define RL_CFG3 0x0059 /* config register #3 */ #define RL_CFG4 0x005A /* config register #4 */ #define RL_CFG5 0x00D8 /* config register #5 */ The datasheets I'm referencing are available here: http://realtek.info/pdf/ Specifically: http://realtek.info/pdf/rtl8139d.pdf http://realtek.info/pdf/rtl8139cp.pdf I believe the registers currently used apply to the 8169, but not necessarily the 8139 family -- can someone, hopefully easily, verify that the 8139 driver is using the right registers? The 8139 series may need the slightly different values used above to enable functionality like wake-on-lan. Thanks for letting me know that. As you said RTL8139/RTL8139C+ use different config registers and it may affect WOL functionality. When I implemented WOL on rl(4), I remember WOL worked at that time. After reading your mail, I wonder how it would have worked at that time. :-( Thanks. Thanks and regards, Matt ___ 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
About the KAME project and automated testing IPv6
Hi, I have installed the FreeBSD 5.4, and make install the right version of mysql,php and httpd. How can I set up a web site like www.kame.net in a local network ,which is used to automated testing ipv6? Is there anyone have the source code of www.kame.net? Or does anyone know where to find the source code ? Looking forward to your reply Thanks! Henry ___ 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
Help : configuring wpa_suplpicant.conf for WEP + login/passwd
Hello, could someone provide me wit a hint how to get wpa_supplicant to work in the following environment : - standard : IEEE 802.11 (at least they pretend in the doc) -mode : infrastructure (?) -WEP: 128bit - Authent : open - and then username/password upon browser-launch (at least under Windows) When I put the following to wpa_suplicant.conf I get State : ASSOCIATED - COMPLETED : ssid=their-ID (unpublished) scan_ssid=1 key_mgmt=NONE wep_key0=part1 wep_key1=part2 wep_key2=part3 However, 'dhclient wlan0' says No DHCPOFFERS received Any help appreciated. Thanx in advance, regards, Arno ___ 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: 8139 driver question
You're welcome. For what it's worth, the Linux driver uses the second set of values referenced below. I think one of the two drivers likely has a bug, but I'm not currently in a position to test it on hardware, so you don't need to fix it on my account :) Thanks and regards, Matt -Original Message- From: YongHyeon PYUN [mailto:pyu...@gmail.com] Sent: Tuesday, February 14, 2012 8:45 PM To: Matt Renzelmann Cc: freebsd-net@freebsd.org Subject: Re: 8139 driver question On Thu, Feb 02, 2012 at 08:43:09AM -0600, Matt Renzelmann wrote: Hello, This will seem a bit off the wall, but I just noticed a discrepancy between the registers defined in the pci/if_rlreg.h directory and those specified on the RealTek datasheets for the antique RealTek 8139. In particular, as defined in the header, the registers in question are: #define RL_CFG0 0x0051 /* config register #0 */ #define RL_CFG1 0x0052 /* config register #1 */ #define RL_CFG2 0x0053 /* config register #2 */ #define RL_CFG3 0x0054 /* config register #3 */ #define RL_CFG4 0x0055 /* config register #4 */ #define RL_CFG5 0x0056 /* config register #5 */ The RealTek data sheets for the 8139, however, all indicate that these should be set to something like this: #define RL_CFG0 0x0051 /* config register #0 */ #define RL_CFG1 0x0052 /* config register #1 */ // No Config2 #define RL_CFG3 0x0059 /* config register #3 */ #define RL_CFG4 0x005A /* config register #4 */ #define RL_CFG5 0x00D8 /* config register #5 */ The datasheets I'm referencing are available here: http://realtek.info/pdf/ Specifically: http://realtek.info/pdf/rtl8139d.pdf http://realtek.info/pdf/rtl8139cp.pdf I believe the registers currently used apply to the 8169, but not necessarily the 8139 family -- can someone, hopefully easily, verify that the 8139 driver is using the right registers? The 8139 series may need the slightly different values used above to enable functionality like wake-on-lan. Thanks for letting me know that. As you said RTL8139/RTL8139C+ use different config registers and it may affect WOL functionality. When I implemented WOL on rl(4), I remember WOL worked at that time. After reading your mail, I wonder how it would have worked at that time. :-( Thanks. Thanks and regards, Matt ___ 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
mbuf evolution session at devsummit
I'm still working on attending but. even if I can't make it topic: Time for an mbuf re-evaluation chair: plenty to choose from but I can't guarantee I'll be there yet, Luigi will be guests: the usual cuplrits: bz, me, luigi, robert, marko if present, jeff if present, gnn, etc. etc. cheesecake: yes please agenda: what's wrong with the current mbufs what should we add? extended external references (queue Luigi entering stage left, singing:) tags and other extensibilies. fibs, multi cpus, jail based pools, pools per device.. etc. ___ 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: 9-stable - ifmedia_set: no match for 0x0/0xfffffff
On Sun, Jan 29, 2012 at 01:19:40PM +0900, Randy Bush wrote: What happens if you set hw.bge.allow_asf to 0 and use auto-negotiation on both sides? it works! the switch was already auto-neg, and i forced auto-neg on the server side. Apart from suspend/resume issue, bge(4) still needs more code to handle controllers with ASF/IPMI firmware. This part is mostly undocumented and hard to experiment due to lack of hardware access. Current IPMI/ASF handling code shows mixed results and setting hw.bge.allow_asf to 0 will break IPMI support. thanks. this was not pleasant. did i remember to whine that i am in tokyo and the server is on the beast coast of the states? :) i think a bit of a warning about hw.bge.allow_asf in UPDATING might help folk. thank you *very* much for your help. randy ___ 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: Help : configuring wpa_suplpicant.conf for WEP + login/passwd
Wep? With a username/password? I've not seen this. Does anyone have any ideas? Adrian On 14 February 2012 05:51, Arno J. Klaassen a...@heho.snv.jussieu.fr wrote: Hello, could someone provide me wit a hint how to get wpa_supplicant to work in the following environment : - standard : IEEE 802.11 (at least they pretend in the doc) - mode : infrastructure (?) - WEP : 128bit - Authent : open - and then username/password upon browser-launch (at least under Windows) When I put the following to wpa_suplicant.conf I get State : ASSOCIATED - COMPLETED : ssid=their-ID (unpublished) scan_ssid=1 key_mgmt=NONE wep_key0=part1 wep_key1=part2 wep_key2=part3 However, 'dhclient wlan0' says No DHCPOFFERS received Any help appreciated. Thanx in advance, regards, Arno ___ 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 ___ 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: Help : configuring wpa_suplpicant.conf for WEP + login/passwd
Is your DHCP daemon setup to listen on the interface where the AP is running? For username/password prompt upon browser launch, you'll need to configure a reverse proxy to get a cookie upon successful auth to pass through the proxy. ~Paul On Tue, Feb 14, 2012 at 09:49:01PM -0800, Adrian Chadd wrote: Wep? With a username/password? I've not seen this. Does anyone have any ideas? Adrian On 14 February 2012 05:51, Arno J. Klaassen a...@heho.snv.jussieu.fr wrote: Hello, could someone provide me wit a hint how to get wpa_supplicant to work in the following environment : ?- standard ?: IEEE 802.11 (at least they pretend in the doc) ?- ? ?mode ? : infrastructure (?) ?- ? ?WEP ? ?: 128bit ?- Authent ? : open ?- and then username/password upon browser-launch (at least under ? Windows) When I put the following to wpa_suplicant.conf I get State : ASSOCIATED - COMPLETED ?: ?ssid=their-ID ?(unpublished) ?scan_ssid=1 ?key_mgmt=NONE ?wep_key0=part1 ?wep_key1=part2 ?wep_key2=part3 However, 'dhclient wlan0' says No DHCPOFFERS received Any help appreciated. Thanx in advance, regards, Arno ___ 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 ___ 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 This message may contain confidential or privileged information. If you are not the intended recipient, please advise us immediately and delete this message. See http://www.datapipe.com/legal/email_disclaimer/ for further information on confidentiality and the risks of non-secure electronic communication. If you cannot access these links, please notify us by reply message and we will send the contents to you. ___ 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
