ok what i have setup is a small home lan using verizon dsl, westell external modem, pppoe, tyring to set it up so this machine, running redhat 7.1 can share internet with 2 win machiens (1 95 and one 98)

dsl is working fine on redhat machine.

i have the following lines in rc.local, i have

echo "Loading the ipchains rules.."
echo 1 > /proc/sys/net/ipv4/ip_forward
echo 1 > /proc/sys/net/ipv4/ip_dynaddr

/sbin/ipchains -A forward -s 192.168.1.0/24 -j MASQ
/sbin/ipchains -P forward DENY

and i ./rc.local and it works ok.

on the 95 machine, (have not touched the 98 machine) i have its ip address set to 192.168.1.2 (98 will be 1.3, ip for linux machine is 1.1), its subnet mask to 255.255.255.0, its dns to my isp's dns, and i made up some things for domain and host.
all this is in tcp/ip options for the network adapter on the 95 machine

on the 95 machine i can ping 192.168.1.1 and it works ok, but when i load internet explorer and try to go to a site it is EXTREMELY slow, and aim just stays at 'connecting' for minutes upon end, never loading up.

any clues to whats causing htis massive slowdown?
maybe some win settings or another line i'm missing in rc.local ???

any help would be much appreciated
nick (quoting his roomate ray, who posted the same thing on dslreports)

Do you get a webpage up onscreen on the win95 box at all???

And have you set a gateway on the win95 machine. if not do this:-

Goto network properties
select NIC TCP/IP protocol
Select gateway tab
add the ip address of the linux box (192.168.1.1)

Hope this helps

_______________________________________
Have Fun

yeah, we did that already. I had to go to bed last night while my roommate carried the torch and worked on it so i am not 100% sure on the details. In a text message he left on my screen (which i only gave a cursory glance because i had to leave for work, where i am now) he had said that the internet DOES work only incredibly slow. I tried it real quick on the win95 machine and nothing came up in about 20-30 seconds so i left for work. I would assume though that he was able to get something to come up in the browser after a while, or at least ping a website, or something.

-nick

well see

i can ping the linux machine 192.168.1.1 and it responds quickly and works

when i try to go to a webpage it just says finding site, and never connects

maybe we have the wrong dns servers in?

does the host and domain on the win95 machine have to be localhost and localdomain?

hmmm
i forget where i got those dns servers from. it was some text file... conf.dns or dns.conf or something, perhaps in /etc/bin or just /etc or i dont know. Try going to network configuration (kde menu --> system --> network configuration or something similar) and looking in there. I believe they may be listed in there.

hmm maybe try uncommenting the rc.firewall line and running that? i'm not sure how to fun it though because eye ehm dumm. looky at things on http://www.linuxdoc.org/HOWTO/IP-Masquerade-HOWTO.html
bb i dont know

Does the linux box connect to the web fine on its own, say using Lynx or are things slow there too? I'd advise you check your DNS settings (as previously mentioned), and I've only ever tried setting the policy for ipchains before setting up any rules on the chain, you may want to look at that. I've never had to use ip_dynaddr before either.

HTH - good luck

Jamie...

yeah, the linux box is fine on the internet itself, dsl and all (i was on it when i posted that last message)

what do you mean by setting the policy for ipchains before setting the rules? we're basically going off of what someone i talked to on aim told us to do, not fully awayre of *what* it is that we were doing

i'll check the dns i guess

You currently use

/sbin/ipchains -A forward -s 192.168.1.0/24 -j MASQ
/sbin/ipchains -P forward DENY

which sets the policy of the chain (... -P forward DENY) after you setup the first rule of the chain (... -A forward -s .... -j MASQ). I've only ever seen it done around the otherway:

/sbin/ipchains -P forward DENY
/sbin/ipchains -A forward -s 192.168.1.0/24 -j MASQ

Although I would have thought that ipchains would have warned you if this caused a problem. As previously mentioned check out the IP-Masquerading HOWTO and also look at the one for ipchains at http://www.linuxdoc.org/HOWTO/IPCHAINS-HOWTO.html

HTH

Jamie...

ray: all the ip masq lines are in that /etc/rc.d/rc.firewall file that we commented out when working on it the other day. i'd say to try deleting (or just commenting out) those other lines and re-enabling the rc.firewall and follow the instructions at http://www.linuxdoc.org/HOWTO/IP-Mas...O-3.html#ss3.3 to make it an executable and execute it and such, than doe the tests in that page to try to test it. Whatever, you're probably at work now anyway, and i will be home in a few hours. we will get this working tonight by crikey.