>
>
> Hello folks; I am Linux newbie, so please be patient with me. I have
> struggled through getting my linux box set up to do ip masqerading and
> actually the biggest difficulty I've had is with DHCP on the @Home
> network. I have it working--sort of. I hope you all won't mind me asking
> this on this list, as the (only) two kind persons who did answer
> questions about DHCP on the comp.os.linux.networking newsgroup have not
> been able to help. I am running Debian 2.1 on (don't laugh) a MacII with
> two ethernet cards, eth0 being connected to the cable modem and eth1 to
> an internal hub.
>
> 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. I
> cannot however browse the web addresses from my internal machines. I
> suspect I have not done something correctly to permit the domain name
> services to get through properly. Can anyone guide me as to the likely
> source of this error? Also, given the machine is a bit slow, would
> setting up DNS caching be a good idea (how would I do this?) or be a
> solution to the problem set out above?
>
> I am using dhcp-client; I gave up on dhcpcd because I could not find any
> assistance to why it wasn't working (but I could find somewhat helpful
dhcpcd works just fine for me with @home. The only thing you need to
be aware of is that @home's dhcpd wants you to present your hostname,
so you must invoke it with the -h flag, for example "dhcpcd -h c80973-b",
the name is listed on your service contract. I do not know whether
giving the full domain name is harmful, but it's not necessary.
- Godmar
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
http://tiffany.indyramp.com/mailman/listinfo/masq
Admin requests can be handled by web (above) or [EMAIL PROTECTED]
