Re: Help : configuring wpa_suplpicant.conf for WEP + login/passwd
[ .. stuff deleted (WEP-128 problem) ] one more thing came to my mind: you don't need to use wpa_supplicant to get WEP support. AFAIK WEP128 is different name for 104-bits key and that might be supported without need of wpa_supplicant. man ifconfig might shed some light. I tried today both 'ifconfig' and 'wpa_supplicant'; I comme to 'associated/connected' , no IP that said, the key they provide me really is 26 characters, I have to split it in twice 13 to get it accepted both by 'ifconfig' and 'wpa_supplicant' which is very probably wrong Couldn't find (quickly) anything on iff and howto for 26 caracter keys Although wpa_supplicant message states that it connected successfully to the network. Can you try to set the address by hand(taking some earlier info from windows machine)? nope, 'ping' (probably filtered) to defaultroute and DNS-lookup both fail More later, thanx for your help. Kind 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: Help : configuring wpa_suplpicant.conf for WEP + login/passwd
Hello, Paul A. Procacci pproca...@datapipe.com writes: Is your DHCP daemon setup to listen on the interface where the AP is running? Dunno... How could eventually be sure Windows got it's IP-addres by DHCP? 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. Could you please explain me how to do this? Thanx, Arno ~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. -- Arno J. Klaassen SCITO S.A. 8 rue des Haies F-75020 Paris, France http://scito.com ___ 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
Hello, Maciej Milewski m...@dat.pl writes: Dnia wtorek, 14 lutego 2012 21:49:01 Adrian Chadd pisze: Wep? With a username/password? I've not seen this. Does anyone have any ideas? Adrian Probably WEP one for all users and username/password as an auth form for captive portal(Network Access Control). Looks close : this is on a site with very restricted (physical) access : each day I pass I get a WEP-key and username/password only valid during the day; the WEP-key (till now) still is the same As said, I can get the wlan0 interface up, but no idea how to assign it an IP-addres I haven't used that so I can't say anything more. Pity ;-) Thanx anyway. Regards, Arno Maciek 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 -- Pozdrawiam, Maciej Milewski ___ 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: ZFS and 'traditional' nfs-export
hello, Larry Rosenman l...@lerctr.org writes: ZFS makes its own version of the exports file. Just do it that way, and be safe. You can pass the full set of NFS options in the sharenfs parameter ah ok, I see. Thanks for answering. I got fooled by the man zfs(1M) example : zfs set sharenfs='r...@123.123.0.0/16,root=neo' tank/home This syntax does not seem to work for me (8.0RC2). Maybe an extra line could be added that one can just set the sharenfs property to exactly the same character string as in /etc/exports. Once again, merci. 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
ZFS and 'traditional' nfs-export
Hello, I googled a bit on this question but could not find a clear answer : is there any risk/inconvenience/advantage in exporting a ZFS-fs by just putting it in /etc/exports the old way and leaving the 'sharenfs' option on the filesystem off? I'd like to replace a UFS-based server serving mostly linux-clients which work well now with a ZFS-fs, and somehow am a bit waterfearing changing the nfsèoptions which worked great till now. Thank you 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: 7.1-PRERELEASE : bad network performance (nfe0)
Robert Watson [EMAIL PROTECTED] writes: On Mon, 29 Sep 2008, Arno J. Klaassen wrote: However, the request/respones tests are awfull for my notebook (test repeated on the notebook for the sake of conviction) : Is it possible to rerun these tests with a 7.0 kernel of the same general configuration? That would help us determine if it's a regression between 7.0 and 7.1, 7.0-RELEASE-p4 kernel (and 7.1 world) as well as 7.0-RELEASE life-cd give same results : great streaming, very poor request/response or perhaps a more general issue between 6.x and 7.x. nve(4) does not recognise this chip. If someone does have a bootable 6-stable .iso with a backported nfe(4) ... or email if_nfe.ko to me and I will tes under 6-stable For now I will test the patches Pyun and Luigi sent me and let you know. Best, arno ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1-PRERELEASE : bad network performance (nfe0)
Dear Pyun, thanx for your prompt answer (as usual). Pyun YongHyeon [EMAIL PROTECTED] writes: On Sat, Sep 27, 2008 at 11:21:00PM +0200, Arno J. Klaassen wrote: Hello, I've serious network performance problems on a HP Turion X2 based brand new notebook; I only used a 7-1Beta CD and 7-STABLE on this thing. Scp-ing ports.tgz from a rock-stable 7-STABLE server to it gives : # scp -p ports.tgz [EMAIL PROTECTED]:/tmp/ ports.tgz 100% 98MB 88.7KB/s 18:49 (doing the same thing by copy from an nfs-mounted disk even takes mores than an hour ...) Doing a top(1) aside, just shows the box 100% idle : PID USERNAME PRI NICE SIZERES STATE C TIME WCPU COMMAND 12 root 171 ki31 0K16K CPU0 0 38:55 100.00% idle: cpu0 11 root 171 ki31 0K16K RUN1 38:55 100.00% idle: cpu1 13 root -32- 0K16K WAIT 0 0:02 0.00% swi4: clock sio 29 root -68- 0K16K - 0 0:00 0.00% nfe0 taskq 34 root -64- 0K16K WAIT 1 0:00 0.00% irq23: atapci1 1853 root 80 7060K 1920K wait 0 0:00 0.00% sh 878 nono 440 8112K 2288K CPU1 1 0:00 0.00% top 884 root 8- 0K16K - 1 0:00 0.00% nfsiod 0 4 root -8- 0K16K - 1 0:00 0.00% g_down 16 root -16- 0K16K - 1 0:00 0.00% yarrow 46 root 20- 0K16K syncer 0 0:00 0.00% syncer 3 root -8- 0K16K - 0 0:00 0.00% g_up 30 root -68- 0K16K - 0 0:00 0.00% fw0_taskq I tested : Update Bios ULE /4BSD PREEMPTION on/off PREEMPTION + IPI_PREEMPTION hw.nfe.msi[x]_disable=1 ^^^ This has no effect as MCP65 lacks MSI/MSI-X capability. All don't seem to matter to the problem. I put two tcpdumps (server and client during another scp(1) ) on http://bare.snv.jussieu.fr/temp/tcpdump-s1518.server http://bare.snv.jussieu.fr/temp/tcpdump-s1518.client I'm far from an expert on TCP/IP, but wireshark expert info shows lots of sequences like : TCP Previous segment lost TCP Duplicate ACK 1 TCP Window update TCP Duplicate ACK 2 TCP Duplicate ACK 3 TCP Duplicate ACK 4 TCP Duplicate ACK 5 TCP Fast retransmission (suspected) TCP ... TCP Out-of-Order segment TCP ... As usual, feel free to contact me for further info/tests. AFAIK it seems that you're the first one that reports poor performance issue of MCP65. someone must be ;) no kiddin, I am not convinced this is (only) a driver issue (cf. bad NFS/UDP performance thread on -hackers). I just have no experience on this notebook, so I can't say it worked great before and my only other 7-stable-amd64 I have does not show the probs, having a cheap re0 *and* being UP. MCP65 has no checksum offload/TSO capability so nfe(4) never try to take advantage of the hardware capability. So you should have no checksum offload/TSO related issue here. Also note, checking network performance with scp(1) wouldn't show real numbers as scp(1) may involve other system activities. Use one of network benchmark programs in ports(e.g. benchmarks/netperf) to measure network performance. quite funny (even taken with lots of salt since the LAN is used for normal work as well in parallel, but differences are rather significant) : I test to same server (7-stable-amd64 from Jun 7 (using nfe0 as well btw, but another chip), either from a 6-stable-x86 (Jul 14, sk0) or the notebook (7-stable-x64 below), using for i in SOME-TESTS ; do echo $i; /usr/local/bin/netperf -H push -i 4,2 -I 95,10 -t $i; echo; done streaming results are OK for both : TCP_STREAM Throughput 10^6bits/sec 6-stable-x86 349.57 7-stable-x64 939.47 UDP_STREAM Throughput 10^6bits/sec 6-stable-x86 388.45 7-stable-x64 947.89 However, the request/respones tests are awfull for my notebook (test repeated on the notebook for the sake of conviction) : TCP_RR Trans. Rate per sec 6-stable-x86 9801.58 7-stable-x64 137.61 7-stable-x6489.35 7-stable-x64 102.29 TCP_CRR Trans. Rate per sec 6-stable-x86 4520.98 7-stable-x64 7.00 7-stable-x64 8.10 7-stable-x6418.49 UDP_RR Trans. Rate per sec 6-stable-x86 9473.20 7-stable-x64 9.60 7-stable-x64 0.90 7-stable-x64 0.10 I can send you complete results if wanted. Other possible cause of issue could be link
Re: IP-forwarding (help)
Bakul Shah [EMAIL PROTECTED] writes: On 05 Jun 2008 01:33:05 +0200 Arno J. Klaassen [EMAIL PROTECTED] wrote: Petar Bogdanovic [EMAIL PROTECTED] writes: On Wed, Jun 04, 2008 at 11:06:01PM +0200, Arno J. Klaassen wrote: [ problem description ] I feel this is /me still not fully understand routing tables. This is your topology, right? yes test-box main-box gateway [192.168.1.1]--[192.168.1.254 172.16.1.240]---[172.16.1.254 On the test-box set default route to 192.168.1.254. On the main-box set net.inet.ip.forwarding 1 but remove the static routes. But how would machines on the 172.16.1.0/24 net know they must send packets for 192.168.1.0/24 to 172.16.1.240? For that you need static routes on all the machines on 172.16.1.0/24 that need to read your test box. Yes, of course ... Thank you very much (I felt it were a simple problem, but somehow blocked finding the solution). Best regards, Arno ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to [EMAIL PROTECTED]
IP-forwarding (help)
Hello, this is probably a FAQ and/or I'm to tired, but I'd be pleased if anyone can tell me what I do wrong : I have a box with two interfaces, one connected to my lan (172.16. ), one to a test-box (192.168.1.1) : em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM ether xxx inet 172.16.1.240 netmask 0xff00 broadcast 172.16.1.255 media: Ethernet autoselect (1000baseTX full-duplex) status: active em1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM ether xxx inet 192.168.1.254 netmask 0xff00 broadcast 192.168.1.255 media: Ethernet autoselect (1000baseTX full-duplex) status: active I enable ip.forwarding : # sysctl net.inet.ip.forwarding net.inet.ip.forwarding: 1 And this is my routing table : Internet: DestinationGatewayFlagsRefs Use Netif Expire default172.16.1.254 UGS 0 20em0 127.0.0.1 127.0.0.1 UH 00lo0 172.16.1.0/24 link#3 UC 00em0 172.16.1.6 x UHLW1 87em0 1194 172.16.1.230 x UHLW1 286em0572 172.16.1.240 x UHLW10lo0 172.16.1.254 x UHLW20em0487 192.168.1.0/24 link#4 UC 00em1 192.168.1.1x UHLW12em1616 192.168.1.254 x UHLW10lo0 For this I added to rc.conf : static_routes=test lan route_test=-net 192.168.1.0/24 192.168.1.254 route_lan=-net 172.16.1.0/24 172.16.1.240 Now from my test-box 192.168.1.1 I can reach (of course) 192.168.1.254, I can reach 172.16.1.240, but no other IP. What do I wrong, please!? Thank you very much for any help in advance. Best regards, Arno ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IP-forwarding (help)
Petar Bogdanovic [EMAIL PROTECTED] writes: On Wed, Jun 04, 2008 at 11:06:01PM +0200, Arno J. Klaassen wrote: Hello, this is probably a FAQ and/or I'm to tired, but I'd be pleased if anyone can tell me what I do wrong : I have a box with two interfaces, one connected to my lan (172.16. ), one to a test-box (192.168.1.1) : em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM ether xxx inet 172.16.1.240 netmask 0xff00 broadcast 172.16.1.255 media: Ethernet autoselect (1000baseTX full-duplex) status: active em1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM ether xxx inet 192.168.1.254 netmask 0xff00 broadcast 192.168.1.255 media: Ethernet autoselect (1000baseTX full-duplex) status: active I enable ip.forwarding : # sysctl net.inet.ip.forwarding net.inet.ip.forwarding: 1 And this is my routing table : Internet: DestinationGatewayFlagsRefs Use Netif Expire default172.16.1.254 UGS 0 20em0 127.0.0.1 127.0.0.1 UH 00lo0 172.16.1.0/24 link#3 UC 00em0 172.16.1.6 x UHLW1 87em0 1194 172.16.1.230 x UHLW1 286em0572 172.16.1.240 x UHLW10lo0 172.16.1.254 x UHLW20em0487 192.168.1.0/24 link#4 UC 00em1 192.168.1.1x UHLW12em1616 192.168.1.254 x UHLW10lo0 For this I added to rc.conf : static_routes=test lan route_test=-net 192.168.1.0/24 192.168.1.254 route_lan=-net 172.16.1.0/24 172.16.1.240 I'm pretty sure that you don't need these three lines. Turning net.inet.ip.forwarding on should be enough. That's what I thought? Without the above lines it doesn't work either. And ip.forwarding works in the sense trafic goes from 192.168.1.254 forward to 172.16.1.240 over lo0, but then taking link#3 to go to 172.16.1.0/24 fails. I feel this is /me still not fully understand routing tables. NB, this is on 7-stable-amd64 Arno ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to [EMAIL PROTECTED]
nfs buildworld blocked by rpc.lockd ?
Hello, my buildworld on a 7-stable-amd64 blocks on the following line : TERM=dumb TERMCAP=dumb: ex - /files/bsd/src7/share/termcap/termcap.src /files/bsd/src7/share/termcap/reorder ex(1) stays in lockd state, and is unkillable, either by Ctl-C or kill -9 /files/bsd is nfs-mounted as follows : push:/raid1/bsd/files/bsd nfs rw,bg,soft,nfsv3,intr,noconn,noauto,-r=32768,-w=32768 0 0 I can provide tcpdumps on server and client if helpful. Thanx, Arno ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nfs-server silent data corruption
Kris Kennaway [EMAIL PROTECTED] writes: On Mon, Apr 21, 2008 at 01:02:33AM +0200, Arno J. Klaassen wrote: I didn't stress-test this MB for a while, but last time I did was with 7-PRELEASE/RC?/CANTremember-exactly-but-close-to-release and all worked great I did add 2G ECC to the 2nd CPU since, though I doubt that interferes with NFS. Uh, you're getting server-side data corruption, it could definitely be because of the memory you added. yop, though I'm still not convinced the memory is bad (the very same Kingston ECC as the 2*1G in use for about half a year already) : I added it directly to the 2nd CPU (diagram on page 9 of http://www.tyan.com/manuals/m_s2895_101.pdf) and the problem seems to be the interaction between nfe0 and powerd : - if I stop powerd, problems go away - I let run powerd but turn of txcsum and tso4 on the interface, the problem is a lot harder to produce (if ever this gives a hint to anyone) Device is : [EMAIL PROTECTED]:0:10:0: class=0x068000 card=0x289510f1 chip=0x005710de rev=0xa3 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce4 Ultra NVidia Network Bus Enumerator' class = bridge cap 01[44] = powerspec 2 supports D0 D1 D2 D3 current D0 (this is with the default BIOS setting LAN Bridge Enabled, disabling that setting makes pciconf say class = network but does not influence my problem) I will restart my tests now by populating all 4G to only CPU1 and say whether that matters. Best, Arno ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nfs-server silent data corruption
re, Jeremy Chadwick [EMAIL PROTECTED] writes: On Mon, Apr 21, 2008 at 04:52:55PM +0200, Arno J. Klaassen wrote: Kris Kennaway [EMAIL PROTECTED] writes: Uh, you're getting server-side data corruption, it could definitely be because of the memory you added. yop, though I'm still not convinced the memory is bad (the very same Kingston ECC as the 2*1G in use for about half a year already) : Can you download and run memtest86 on this system, with the added 2G ECC insalled? memtest86 doesn't guarantee showing signs of memory problems, but in most cases it'll start spewing errors almost immediately. it finished in a bit less than 3 hours without a single error/warning I feel pretty confident all memory is fine One thing I did notice in the motherboard manual below is something called Hammer Configuration. It appears to default to 800MHz, but there's an Auto choice. Does using Auto fix anything? Nope I added it directly to the 2nd CPU (diagram on page 9 of http://www.tyan.com/manuals/m_s2895_101.pdf) and the problem seems to be the interaction between nfe0 and powerd : That board is the weirdest thing I've seen in years. ;) I agree I lifted (?) my eye-brows the first time I saw that diagram Two separate CPUs using a single (shared) memory controller, two separate (and different!) nVidia chipsets, a SMSC I/O controller probably used for serial and parallel I/O, two separate nVidia NICs with Marvell PHYs (yet somehow you can bridge the two NICs and PHYs?), two separate PCI-e busses (each associated with a separate nVidia chipset), two separate PCI-X busses... the list continues. some may say it's just four wheels, an engine and a steer, she looks different compared to most others I know you don't need opinions at this point, but what a behemoth. I can't imagine that thing running reliably. though it does ;) (till the day I decided she deserved a -stable upgrade and 2 more gigs ...) - if I stop powerd, problems go away This would imply that clock frequency stepping is somehow attributing itself to the corruption. I don't see any BIOS options for controlling things related to AMD's Cool-n-Quiet or PowerNow! feature, which is usually what handles this. you can turn it on/off; anyway, the problem *seems* easy to reproduce when freq drops quickly form 2600Mhz to 1000Mhz I just inspected a few corrupted copies, but out of 10-200Mbytes just 1 byte was 0 iso \t - I let run powerd but turn of txcsum and tso4 on the interface, the problem is a lot harder to produce (if ever this gives a hint to anyone) Possibly shared interrupts are causing problems? don't think so; I first had two Promise TX4 cards in this box iso the Marvell 8port card; since I had problems with TX4 some time ago I first suspected them. The board is still running memtest86, but from the dmesg I posted I don't see a shared irq. MSI/MSI-X doing something odd? Have you tried disabling MSI/MSI-X and see if it makes a difference? MSI is disabled as is PCI-e Error reporting (or something like that) I think you mean MAC LAN Bridge, according to the motherboard manual. I'm not even sure what that really does; somehow trunks the two NICs together to give you the equivalent of 2000mbit of traffic? I don't know. probably; I never tried ;) I need the second NIC for a seperate subnet Does the corruption you see go away if you install a separate NIC (e.g. an Intel NIC) in a PCI or PCI-e slot, and disable the onboard NICs (should be MAC LAN: Disable on both the primary and slave)? Don't have one available right now (for a 2U server). I will test if I do not find another solution. Thanx, Arno ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to [EMAIL PROTECTED]
nfs-server silent data corruption
Hello, I've a strange problem with a box I'm setting up as nfs-server under 7-stable : - tyan S2895 MB, 2*285Dualcore Opteron, 4G-ECC, ahd-scsi, nfe-network - stripped GENERIC as kernel - sources as of last saturday afternoon (European time) I removed everything from /boot/loader.conf and /etc/sysctl.conf, still I get easily data corruption when exporting ahd-scsi over nfs (NB exporting geom_raid5 gives same data corruption) Testing with the following pseudo code : while checksum1 == checksum2 do create random file of $1 MBytes calculate md5 checksum1 copy calculate md5 checksum2 on copy Tested on both (as nfs-client) a 6-stable-i386 from a couple of weeks ago as well as a linux 2.6.15-gentoo-r1 of about two years ago : within half an hour the copy will be different ;( I played with nfs-options on client side (nfs[23], conn, intr, [udp|tcp], -r=, -w= ) but none seem to matter. Start/Stop rpc.lock/sttatd on server/client just provoked some : cp: utimes: BIG2: No such file or directory cp: chown: BIG2: Stale NFS file handle cp: chmod: BIG2: Stale NFS file handle cp: chflags: BIG2: Operation not supported cp: BIG2: Stale NFS file handle cp: setting permissions for `BIG2': Stale NFS file handle cp: closing `BIG2': Stale NFS file handle [and then the while loop continued ... as if the NFS handle where not that stale ..] Anyway, I'll try to nail this down more (e.g. nfs-write performance is horrible ... (nfsd falling down to 0% cpu and then after while 'wake up' and be at around 3-6% again)) I didn't stress-test this MB for a while, but last time I did was with 7-PRELEASE/RC?/CANTremember-exactly-but-close-to-release and all worked great I did add 2G ECC to the 2nd CPU since, though I doubt that interferes with NFS. Bref, if anyone has a suggestion (I will try downgrade to RELENG_7_0 iff noone has a new suggestion for RELENG_7, but I'd like to go forward and test some maybe suspect recent MFC or other suggestion) Thanx in advance, best, Arno ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sk ethernet driver: watchdog timeout
Hello, I have an ASUS motherboard A7V8X-E Deluxe with onboard 10/100/1000 Mbit/s NIC from Marvell Semiconductor. My problem is that it sometimes lock up with the error message sk0: watchdog timeout I have a similar problem with 3Com cards on an ASUS A7N266; I just post in case this might be related (and in hope for a hint for a solution ) This is a fresh FreeBSD 4-STABLE system. xl0 = 3c905C-TX xl1 = 3c900-COMBO switch = Netgear FS105 box netboots (using xl0) -Stable from a PPro server with same 3c905C-TX and works like a charm (network software development use, generating high network load) This weekend I pulled in an old scsi-card and disk and installed 5.2.1 and -current on it : - networking through xl0 gives me about 6Kbps throughput, unworkable but no freezes - networking through xl1 works more or less OK as long as I stick to NFS (udp-mounts), simple editing and serial makes; the first make -j X and/or ar srv mylib lots-of-ofiles generates : xl1: watchdog timeout system does not come back from lost network, at least not for the first couple of minutes whenever I try a cvsup -g -L 2 /etc/my-supfile or cvs -d faraway update I always get the same xl1: watchdog timeout after some dozens of seconds As said, same behaviour on 5.2.1 and -current from sunday. With or without acpi/apic/WITNESS does not make any difference. With or without CPUTYPE=athlon-xp either. Note, when I installed this system (at a co-worker) one year ago, I *had* to fix AGP Aperture size to 64M in the BIOS, otherwise the netboot failed. I just think about this, I did not test this weekend whether current -Stable (sic) works OK when changing this value. Thanx for your time, hope this helps to find a solution. I can bake a current kernel on another box and ask my coworker to test it. Regards, Arno ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to [EMAIL PROTECTED]
ntp problems; am i the only one?
Hello, I did not pay much attention, but since a couple of weeks (the latest daylight savings in Europe) mu ntp programs do not function anymore and host clocks drift further and further (both for machines I upgraded to -stable as for machines which have a couple a months old -stable ...). When I do: ntpdate -bv ntp1.oleane.net I get 15 Apr 01:53:24 ntpdate[14191]: ntpdate 4.1.0-a Sat Apr 13 21:23:32 MEST 2002 (1) 15 Apr 01:53:28 ntpdate[14191]: no server suitable for synchronization found When I do : ntpdate -bdv ntp1.oleane.net I get 15 Apr 01:53:33 ntpdate[14192]: ntpdate 4.1.0-a Sat Apr 13 21:23:32 MEST 2002 (1) transmit(194.2.0.58) receive(194.2.0.58) transmit(194.2.0.58) receive(194.2.0.58) transmit(194.2.0.58) receive(194.2.0.58) transmit(194.2.0.58) receive(194.2.0.58) transmit(194.2.0.58) server 194.2.0.58, port 123 stratum 2, precision -17, leap 00, trust 000 refid [192.36.143.152], delay 0.02751, dispersion 0.8 transmitted 4, in filter 4 reference time:c06494ad.61d3dc8b Mon, Apr 15 2002 1:52:13.382 originate timestamp: c0649517.53f7be12 Mon, Apr 15 2002 1:53:59.327 transmit timestamp: c06494fd.f09a133c Mon, Apr 15 2002 1:53:33.939 filter delay: 0.02794 0.02751 0.02791 0.02780 0.0 0.0 0.0 0.0 filter offset: 25.38715 25.38698 25.38685 25.38704 0.00 0.00 0.00 0.00 delay 0.02751, dispersion 0.8 offset 25.386989 15 Apr 01:53:33 ntpdate[14192]: step time server 194.2.0.58 offset 25.386989 sec i.e. looks like ntpdate finds the correct offset, but is no longer capable to apply it; I tried with ntpd -q but without succes as well. I am not aware of any changes I did, apart form the classical world-cycle on *part* of my boxes, but the problem exists on *all* boxes. This might be a firewall-issue of the university, but then, even ntpdate -v box-next-to-me gives the sames behaviour. I would be glad to know if there is another european FreeBSD sysadmin who can tell me if he is capable or not to use ntp. Thanx in advance. Arno -- Arno J. Klaassen INSERM U483 9 quai st bernard Paris [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-net in the body of the message
