David, thank you for responding. I have been reading your and Ambrose Au's
reference materials on IP masquerading religiously, but unfortunately I need
guidance in the true way :-) I would really appreciate your and other list
members' help.
"David A. Ranch" wrote:
> Curious.. what is your BogoMips rating on that box?
My Mac II (8 mb ram, 500 mb hd) runs Debian at 3.80 bogomips.
> >I can ping and telnet to the outside world from one of my internal
> >machines; and from my masq server, I can ping web addresses. I can ping
> >the ip number of outside web addresses from my internal machines.
Well, one step forward and two back. I blew it; thinking that it was routing that
I had setup incorrectly, I have undone myself. Now I cannot see the network
(192.168.1.0) from the Linux box; and dhclient is not aquiring anything from the
dhcp server at @Home. Blah. All I get is the shell giving me all sorts of data,
but nothing that tells me actually what is wrong.
> You can ping the IP addresses but not the names?
>
> If you can't ping names, what did you configure on the internal
> hosts for their DNS server? Unless you configured DNS on your
> MASQ server, the internal hosts should be configured to use
> @Home's DNS servers.
I did have the internal machines configured to use the @Home DNS, but that wasn't
working (new problems as indicated above). In the /etc/init.d/network file I
have:
#! /bin/sh
echo "1" > /proc/sys/net/ipv4/ip_forward
echo "1" > /proc/sys/net/ipv4/ip_dynaddr
ifconfig lo 127.0.0.1
route add -net 127.0.0.0 netmask 255.0.0.0 lo
IPADDR = 192.168.1.1
NETMASK = 255.255.255.0
NETWORK = 192.168.1.0
BROADCAST = 192.168.1.255
GATEWAY = 192.168.1.0
ifconfig eth1 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
route add -net ${NETWORK} netmask ${NETMASK} dev eth1
route add default gw ${GATEWAY} netmask ${NETMASK} dev eth1 metric 1
depmod -a
modprobe ip_masq_ftp
modprobe ip_masq_raudio
modprobe ip_masq_irc
modprobe ip_masq_vdolive
dhclient eth0
ipfwadm -I -a accept -S 0/0 68 -D 0/0 67 -W eth0 -P udp
ipfwadm -F -p deny
ipfwadm -F -a m -S 192.168.1.0/24 -D 0.0.0.0/0
> -snip-
>
> This would be a great idea. This topic is covered in the DNS-HOWTO doc
> usually found in /usr/doc/HOWTO
I will try it out; assuming I can get back to the point I was connected to the
internet, will this help resolve my problems in seeing web pages from masq'd
machines?
> Also.. about DHCP, I'm also on @home and though they use DHCP to delve
> out IP addresses, they do it in a static fashion. In the TriValley, CA
> area, the DHCP client says, "I'm c-123243-a, what is my IP address" and
> it will always give you out the same IP.
I tried to point to a static ip as a test; I am not getting out on the eth0 card
at all now. I tried turning off temporarily the ipfwadm rules, and am still
experiencing the same problem.
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
http://tiffany.indyramp.com/mailman/listinfo/masq
Admin requests can be handled by web (above) or [EMAIL PROTECTED]
