>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.
I would think that a box that slow will impact your cablemodem performance.
No?
>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.
Follow Robert's setup:
http://rlz.ne.mediaone.net/linux/index.html
>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" ;
>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.
What if you manually setup your IP? say your IP is 24.1.1.10
ifconfig eth0 24.1.1.10 netmask 255.255.255.0
route add -net 24.1.1.0 netmask 255.255.255.0 eth0
>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.
Don't use this.. its not Linux specific and you'll have a tough time
finding anyone else that uses it.
Also.. there is docs on DHCPcd..
http://metalab.unc.edu/pub/Linux/docs/HOWTO/mini/DHCPcd
>dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval [varying
>number]
>dhclient: send packet: network is unreachable
You might be filtering 0.0.0.0 traffic to ports 67 and 68.
>> >ipfwadm -I -a accept -S 0/0 68 -D 0/0 67 -W eth0 -P udp
Also allow OUT:
This is what is in TrinityOS:
/etc/services
--
bootps 67/tcp
bootps 67/udp
bootpc 68/tcp
bootpc 68/udp
--
--
$extif=eth0
$universe=0.0.0.0
$broadcast=255.255.255.255
## DHCP - CLIENT - if you get a dynamic IP address for your ADSL or Cablemodem
# connection
/sbin/ipfwadm -I -a accept -W $extif -P udp -S $universe/0 bootps -D
$broadcast/0 bootpc
/sbin/ipfwadm -I -a accept -W $extif -P tcp -S $universe/0 bootps -D
$broadcast/0 bootpc
## DHCP - CLIENT - if you get a dynamic IP address for your ADSL or Cablemodem
# connection
/sbin/ipfwadm -O -a accept -W $extif -P udp -S $universe/0 bootpc -D
$broadcast/0 bootps
/sbin/ipfwadm -O -a accept -W $extif -P tcp -S $universe/0 bootpc -D
$broadcast/0 bootps
--
--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]
