From: Bernd B. <bb...@fr...> - 2005-12-18 16:41:36
|
Hi, I have finally managed to set up an NFS server via colinux-slirp. Using pcap-bridge or tuntap is unfortunately not an option. Mounting the NFS share on a remote Linux host and retrieving the directory listing works fine, but when I try to copy files over to the remote host, after a few files I keep getting a crash in colinux-slirp-net-daemon.exe accompanied by the following message: The instruction at "0x77f83905" referenced memory at "0x20302030". The memory could not be "written". This is with devel-colinux-20051013, kernel 2.6.12-co-0.7.1 Any ideas? Regards, Bernd |
From: <Chr...@sk...> - 2005-12-19 09:01:54
|
>I have finally managed to set up an NFS server via colinux-slirp. Using >pcap-bridge or tuntap is unfortunately not an option. Can you give me specifics about how you acchieved that? Thanks, Chris col...@li... 2005.12.18 17:41 Please respond to bb...@fr... To col...@li... cc Subject [coLinux-devel] Crash in colinux-slirp-net-daemon during nfs file copy Hi, I have finally managed to set up an NFS server via colinux-slirp. Using pcap-bridge or tuntap is unfortunately not an option. Mounting the NFS share on a remote Linux host and retrieving the directory listing works fine, but when I try to copy files over to the remote host, after a few files I keep getting a crash in colinux-slirp-net-daemon.exe accompanied by the following message: The instruction at "0x77f83905" referenced memory at "0x20302030". The memory could not be "written". This is with devel-colinux-20051013, kernel 2.6.12-co-0.7.1 Any ideas? Regards, Bernd ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ coLinux-devel mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-devel |
From: Bernd B. <bb...@fr...> - 2005-12-19 18:37:39
|
Hi Christian. On Monday 19 December 2005 08:52, Chr...@sk... wrote: > >I have finally managed to set up an NFS server via colinux-slirp. Using > >pcap-bridge or tuntap is unfortunately not an option. > > Can you give me specifics about how you acchieved that? > Actually it's not that difficult. You just have to make sure that all daemons involved in NFS (portmap, nfsd, statd, mountd, lockd) get fixed port numbers assigned. Have a look at the Linux NFS HOWTO available at http://nfs.sourceforge.net/nfs-howto/ Section 6.4 "NFS and firewalls" describes how to achieve this. Then you simply have to specify all those ports in the slirp configuration (both tcp:x:x and udp:x:x). Regards, Bernd |
From: Henry N. <Henry.Ne@Arcor.de> - 2005-12-30 22:08:51
|
Bernd Brandstetter wrote: > Hi, > > I have finally managed to set up an NFS server via colinux-slirp. Using > pcap-bridge or tuntap is unfortunately not an option. > Mounting the NFS share on a remote Linux host and retrieving the directory > listing works fine, but when I try to copy files over to the remote host, > after a few files I keep getting a crash in colinux-slirp-net-daemon.exe > accompanied by the following message: > > The instruction at "0x77f83905" referenced memory at "0x20302030". The > memory could not be "written". > > This is with devel-colinux-20051013, kernel 2.6.12-co-0.7.1 > > Any ideas? This is perhaps a buffer overrun in slirp code. Limit please the rsize or wsize or both (1024, 2048, 4096), this is typical for slow bandwide networks. Try the options tcp or udp. A sample in fstab: server:/pub /pub nfs rsize=1024,wsize=1024,timeo=14,intr,tcp How is the direction for file transfers? From coLinux to the world? Is coLinux your NFS-Server? If yes, please say what is the config for slirp? And please give us a sample of /etc/exports and your mount on the other side of this nfs session. -- Henry Nestler |
From: Bernd B. <bb...@fr...> - 2005-12-31 12:33:44
|
On Friday 30 December 2005 23:08, Henry Nestler wrote: > This is perhaps a buffer overrun in slirp code. > > Limit please the rsize or wsize or both (1024, 2048, 4096), this is > typical for slow bandwide networks. > > Try the options tcp or udp. > > A sample in fstab: > server:/pub /pub nfs rsize=1024,wsize=1024,timeo=14,intr,tcp After explicitly setting both rsize and wsize to 1024 it works fine :-) (Though I find it a little surprising since my NFS documentation states that 1024 were the defaults if rsize and wsize are not set explicitly.) Anyway, many thanks! Begards, Bernd |