No quick answer, but I don't want this thread to die because...
I have the same problem. There is a Linux/Netscape client on
my LAN also which works fine. The Win3.11/TCP32b client
is really slow, gets stuck but hitting reload a few times ends up
geting the page. My setup is a 2.0.32 RedHat 5.0 out-of-the box
kernel, a caching nameserver but without:
echo 1 > /proc/sys/net/ipv4/ip_dynaddr
I suspect the problem is a MTU length problem or the lack of packet
reassembly on the diald/ipfw server. How does one know if
the kernel has that set - without rebuilding it and perhaps
changing a heap of other settings in the process?
I need time to investigate further.
David R. Forrest wrote:
>
> Hello,
> I'm having more of a forwarding problem than a diald problem
>
> I'm using the following as my ipforrwading setup:
>
> #
> /sbin/ipfwadm -F -f
> /sbin/ipfwadm -I -f
> /sbin/ipfwadm -O -f
> /sbin/ipfwadm -F -p deny
> /sbin/ipfwadm -F -a m -S 192.168.102.0/24 -D 0.0.0.0/0
> echo 1 > /proc/sys/net/ipv4/ip_dynaddr
> # enable re-writing per http://www.linuxhq.com/patch/20-p0468.html
>
> with kernel 2.0.35, with cacheing named, and sometimes it works well, and
> sometimes not. What doesn't work well is a Win 95 box on my network
> looking at http://www.linuxhq.com (and many others). The www connection
> will hang, waiting for the data, but http://www.linuxhq.com/no_file will
> serve up the file not existing message. From this I know the server is
> talking, but the page isn't making it through the ipfw setup.
------------------------------------------------------------------------
Ralph Billes, | Phone: +61 (0) 8 9389 1680
Echo Labs. | Mobile: +61 (0) 41985 9603
Turnkey Internet Connections, | WWW: http://www.iinet.net.au/~echo/
Firewalls, Web Devices, | Email: [EMAIL PROTECTED]
Systems Programming Contracts, | Mail : 29 Weld St, Nedlands, WA 6009
Computer Networking. | Perth, Australia.
------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
