Menu
▾
▴
[coLinux-devel] Re: Two networking issues
|
From: Alejandro R. S. <as...@MI...> - 2004-04-05 20:28:24
|
You shouldn't need to turn off the Rx checksum offloading, just Tx, but it probably won't hurt to have it off. I built a new 2.4.25 kernel using the 0.6.0 config file + socket filtering. If you want to try it and see if that fixes dhcp, it's available at: http://web.mit.edu/asedeno/www/coLinux/my_0.6.0_kernel Be sure to keep your old kernel around just in case. -Alejandro On Mon, 2004-04-05 at 15:11, Robert Pang wrote: > Alejandro > > Yes. That's it. My NIC have "Rx Checksum Offload" and "Tx Checksum Offload" > options. After disabling them, I am able to TCP to and from my W2k host with > coLinux. I still get dup ping replies though. Not sure if it matters or not. > > As for the kernel, I am just using the kernel that comes with 0.6.0 install. > Don't know if it is compiled with packet filtering or not. It looks like it > takes quite a bit of effort to setup the env to build coLinux and I doubt if > I have the bandwidth to try building the kernel myself. > > Thanks for your help in any case. > > Rob > > ----- Original Message ----- > From: "Alejandro R. Sedeno" <as...@MI...> > To: "Robert Pang" <rob...@ho...> > Cc: <col...@li...> > Sent: Monday, April 05, 2004 11:36 AM > Subject: Re: [coLinux-devel] Two networking issues > > > > With the caveat that I've not used your particular NIC, nor have I used > > Fedora: > > > > DHCP - Does your kernel have Socket Filtering? I'm not sure if this is > > compiled into the coLinux kernel yet, but it caused some issues with > > dhcp for me. > > > > As far as host<->coLinux communications, I recently had issues with an > > integrated network card that offloaded TCP and IP checksums to the NIC. > > Check the NIC's configuration from the device manager and look under > > advanced to see if there are any options resembling "Offload Transmit IP > > Checksum". Disable checksum offloading for transmit on both TCP and IP > > if the options are there. > > > > Good luck! > > > > -Alejandro > > > > > > On Mon, 2004-04-05 at 14:05, Robert Pang wrote: > > > Hi folks, > > > > > > coLinux is great. I am able to set up and run Fedora Core 1 with the > 0.6.0 > > > build on Windows 2000. However, I run into 2 issues. > > > > > > First, I cannot use DHCP with FC1. I get the same error as described in > > > http://www.colinux.org/wiki/index.php/coLinuxIAQ#A1. Since there is no > pump > > > binary package for FC1, I haven't tried pump to see if will resolve the > > > issue. FC1 uses dhclient for DHCP and I am not how to set it up to use > pump. > > > > > > Second, using static IP, I cannot make a TCP connection from the W2k > host to > > > coLinux or vice versa. ping works but I got duplicate replies if I ping > the > > > W2k host (rpang-pc2) from coLinux: > > > > > > [rpang@colinux rpang]$ ping rpang-pc2 > > > PING rpang-pc2 (130.35.168.159) 56(84) bytes of data. > > > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=0 ttl=128 time=4.96 > ms > > > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=0 ttl=128 time=6.25 > ms > > > (DUP!) > > > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=1 ttl=128 time=1.11 > ms > > > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=1 ttl=128 time=1.91 > ms > > > (DUP!) > > > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=2 ttl=128 time=1.13 > ms > > > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=2 ttl=128 time=1.72 > ms > > > (DUP!) > > > .. > > > > > > ping from W2k to coLinux seems to be okay though: > > > > > > C:\Documents and Settings\rpang>ping lvbcheng-pc > > > > > > Pinging lvbcheng-pc.us.oracle.com [130.35.168.148] with 32 bytes of > data: > > > > > > Reply from 130.35.168.148: bytes=32 time=30ms TTL=64 > > > Reply from 130.35.168.148: bytes=32 time=10ms TTL=64 > > > Reply from 130.35.168.148: bytes=32 time<10ms TTL=64 > > > Reply from 130.35.168.148: bytes=32 time=10ms TTL=64 > > > > > > Ping statistics for 130.35.168.148: > > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > > > Approximate round trip times in milli-seconds: > > > Minimum = 0ms, Maximum = 30ms, Average = 12ms > > > > > > Because of this problem, I cannot make X connection from coLinux to my > > > cygwin/XFree86 running on my W2k host. Neither can I ssh from my W2k > host > > > back to coLinux. TCP connection to and from another machine on the > network > > > with coLinux is fine though. > > > > > > Here is my coLinux network setup: > > > > > > [rpang@colinux rpang]# ifconfig > > > eth0 Link encap:Ethernet HWaddr 00:43:4F:4E:45:30 > > > inet addr:130.35.168.148 Bcast:130.35.171.255 > Mask:255.255.252.0 > > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > > RX packets:1523574 errors:0 dropped:0 overruns:0 frame:0 > > > TX packets:4726 errors:0 dropped:0 overruns:0 carrier:0 > > > collisions:0 txqueuelen:1000 > > > RX bytes:104822082 (99.9 Mb) TX bytes:3234903 (3.0 Mb) > > > Interrupt:2 > > > > > > lo Link encap:Local Loopback > > > inet addr:127.0.0.1 Mask:255.0.0.0 > > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > > collisions:0 txqueuelen:0 > > > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > > > > > My W2k network setup: > > > > > > Windows 2000 IP Configuration > > > > > > Host Name . . . . . . . . . . . . : rpang-pc2 > > > Node Type . . . . . . . . . . . . : Hybrid > > > IP Routing Enabled. . . . . . . . : No > > > WINS Proxy Enabled. . . . . . . . : No > > > > > > Ethernet adapter Local Area Connection: > > > > > > Description . . . . . . . . . . . : 3Com 3C918 Integrated Fast > > > Ethernet > > > Controller (3C905B-TX Compatible) > > > Physical Address. . . . . . . . . : 00-C0-4F-5E-C2-DA > > > DHCP Enabled. . . . . . . . . . . : No > > > IP Address. . . . . . . . . . . . : 130.35.168.159 > > > Subnet Mask . . . . . . . . . . . : 255.255.252.0 > > > Default Gateway . . . . . . . . . : 130.35.168.1 > > > DNS Servers . . . . . . . . . . . : 130.35.249.41 > > > 138.2.202.15 > > > Primary WINS Server . . . . . . . : 138.2.202.14 > > > Secondary WINS Server . . . . . . : 130.35.62.34 > > > > > > And my default.colinux.xml: > > > > > > <?xml version="1.0" encoding="UTF-8"?> > > > <colinux> > > > <block_device index="0" path="\DosDevices\e:\fedora_root" > > > enabled="true"> > > > </block_device> > > > <block_device index="1" path="\DosDevices\e:\colinux_swap" > > > enabled="true"> > > > </block_device> > > > <bootparams>ro root=/dev/cobd0</bootparams> > > > <image path="vmlinux"></image> > > > <memory size="64"></memory> > > > <network index="0" type="bridged" name="3Com 3C918 Integrated Fast > > > Ethernet Controller (3C905B-TX Compatible)"></network> > > > </colinux> > > > > > > BTW, I am using the bridged network. I failed to setup NAT with W2k ICS. > > > Enabling W2k ICS always results with an error. It turns out that ICS > uses > > > DHCP implicitly and there is another DHCP server running in my network > so > > > ICS cannot be used (see the first common problem under > > > http://is-it-true.org/nt/nt2000/utips/utips11.shtml). > > > > > > Any take on these two issues? > > > > > > Thanks. > > > > > > Rob > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by: IBM Linux Tutorials > > > Free Linux tutorial presented by Daniel Robbins, President and CEO of > > > GenToo technologies. Learn everything from fundamentals to system > > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > > > _______________________________________________ > > > coLinux-devel mailing list > > > coL...@li... > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > |
