Hi Jim,
> I am using diald .99.4, Redhat 6.1 (2.2.12-20).
> I've been trying to connect to the Internet from a
> client machine (W98) on my little network. I already
> have diald working somewhat from my Linux server. I
> have added the ip address of the Linux server to the
> gateway list in the TCP/IP properties tab in the
> Windows networking thingie.
1. [windows] did you set the DNS address in the Windows Networking
Properties dialog?
2. [linux] did you enable forwarding in the linux kernel?
3. [linux] did you enable forwarding to the diald device using ipchains?
4. [linux] did you remember to masquerade private addresses leaving the pppd
device?
> When I try to access a
> website from that machine, it dials the modem, but
> sometimes it hangs up because the connect script
> failed or it gives me errors (the page is never
> displayed on the browser):
How about a log listing without information like timing being removed.
I have no idea what program is putting out the messages much less what to
suggest to correct them (or more likely add more of them since this snippet
tells me nothing).
> I have also had trouble bringing up news-groups.
Is this on the linux machine or still on the Windows box?
> When
> I try to subscribe to one, netscape trys to bring up a
> list. There is furious activity (as shown by dctrl)
> and then it trails off. If I don't stop it, I can't do
> anything else with netscape. At this point, I'm
> guessing these problems might be related.
> Is there anything else you need to help me with this?
Configuration information, diald.conf, ipchains rules being run etc.
> Any help would be greatly appreciated
> Thanks,
--
#!/bin/sh
# [EMAIL PROTECTED] 2000-03-17
# only use this to debug connections
# then replace with a firewall script
# that actually protects your network
# rather than letting everything through.
path=/bin:/sbin/:/usr/sbin:/usr/bin
# enable the kernel changing the ipaddress on
# dynamic connections
echo 2 > /proc/sys/net/ipv4/ip_dynaddr
# enable the kernel to forward ip packets
# This should already be set by init scripts
# at boot when using RedHat as long as you set
# 'FORWARD_IP$="yes"' in /etc/sysconfig/network
echo 1 > /proc/sys/net/ipv4/ip_forward
# change these defines to match your setup
LOCALNET=192.168.0.1/24
EXTERN=ppp0
INTERN=eth0
DIALD-DEV=tap0
DIALD-IP=10.0.0.1
# First you set policies,
# this is what happens if a rule to match
# the packet is not found
ipchains -P input ACCEPT
ipchains -P output ACCEPT
ipchains -P forward DENY
# Then you clear out any existing rules
# this way you actually know what's happening
ipchains -F
# forward to the diald device
ipchains -A forward -i $DIALD-DEV -s $LOCALNET -j ACCEPT
# masq local traffic going out the external device
ipchains -A forward -i $EXTERN -s $LOCALNET -j MASQ
# this is required for traffic on the diald machine
# that brought up the link
ipchains -A forward -i $EXTERN -s $DIALD-IP -j MASQ
--
Hope this helps,
Lourdes
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
