Again, thanks for the help; please stick with me as I battle this out.
"David A. Ranch" wrote:
> >My Mac II (8 mb ram, 500 mb hd) runs Debian at 3.80 bogomips.
>
> Eouch!
I agree. It is only however for one job--sharing my cable modem access.
Configuring and doing just about anything is very slow. But I am stubborn.
> >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
>
> This is good except your default GW should point to eth0. BUT..
> don't run this route until the eth0 interface is configured by
> DHCP first.
>
> >dhclient eth0
>
> Does this work?
Not anymore; and this is the problem. It DID work; I _was_ getting the IP on eth0
from @Home; but I evidently screwed it up. dhcpcd has never worked, and I don't
know why; so my question is over whether I can get one or the other to work; I
don't care which.
1. dhcpcd
The Mini-Howto (http://metalab.unc.edu/LDP/HOWTO/mini/DHCP.html) suggests that
the configuration is largely automatic on Debian, but dhcpcd has never acquired
an IP on my machine. It was set up with its configuration file having as its only
entry "IFACE=eth0" ; dhcpcd starts on the computer's startup; but it will not
give eth0 an IP. I tried to give eth0 a temporary IP (10.0.0.1) as is suggested
in the mini-howto; this didn't work. In either case, syslog reports
'dhcpdStart:socket:Invalid argument.' I previously had eth0 be the connection to
my local network, so I know the card works.
If anyone has a working example with Debian, I would appreciate it if you could
tell me how to configure /etc/init.d/network and /etc/dhcpc/config to work. This
would avoid me having to deal with:
2. dhclient
I installed dhclient to get around dhcpcd not working. The only documentation of
any use I found was on NetBSD's site:
http://www.netbsd.org/Documentation/network/dhcp.html.
This worked; but as I said, I messed it up but I'm not sure how. dhclient starts
and now reports in syslog:
dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval [varying
number]
dhclient: send packet: network is unreachable
dhclient: No DHCPOFFERS received.
My dhclient.conf file reads as follows:
Send host-name "server.techne.home";
send dhcp-client-identifier "CSxxxxxx-A";
request subnet-mask, broadcast-address, routers, domain-name-servers;
timeout 30;
retry 60;
select-timeout 5;
script "/etc/dhclient-script";
lease {
interface "eth0";
option host-name "server.techne.home";
option subnet-mask 255.255.255.0;
option domain-name "techne.home";
option domain-name-servers 127.0.0.1;
renew 2 2000/1/12 00:00:01;
rebind 2 2000/1/12 00:00:01;
expire 2 2000/1/12 00:00:01;
}
>
> >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
>
> Is this all the statements you have? What are your policies on
> INPUT and OUTPUT?
>
> >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.
>
> This is because of your default GW statement being hosed.
>
> --David
> .----------------------------------------------------------------------------.
> | David A. Ranch - Linux/Networking/PC hardware [EMAIL PROTECTED] |
> !---- ----!
> `----- For more detailed info, see http://www.ecst.csuchico.edu/~dranch -----'
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
http://tiffany.indyramp.com/mailman/listinfo/masq
Admin requests can be handled by web (above) or [EMAIL PROTECTED]
