Re: networking problem and philosophy
Bret Comstock Waldow <email@example.com> writes:
> I'm trying to get Debian going on my Thinkpad T21, and synchronize with
> my Sony Clie PDA.
(This works fine for me, but I always build my own kernel. I've had
better luck using coldsync than pilot-link, and the first sync always
> I'm using the kernel-package and make-kpkg tools as shown in the Debian
> manual, and that part seems to work. I've got a kernel that may have
> what I need to sync my PDA.
> But it won't give me my network access.
> I've looked a bit at the 'netenv' stuff, and it seems to have created
> hard definitions of my network settings in /etc/netenv. I chose during
> install to use DHCP when it asked - the netenv settings don't seem to
> reflect this.
Hmm. Is there anything informative in /etc/network/interfaces (the
"normal" place for network settings under Debian)? You also might try
running your DHCP client by hand, and seeing if that works. Also,
check that your kernel configuration includes a driver for your
network card. I think the "Socket Filtering" option (CONFIG_FILTER)
is also required to use DHCP, even though that's not obvious from
anything in the kernel configuration.
> Clues, suggestions, explanations would be very welcome. Should I be
> accepting 'netenv' during the install? How can I get rid of it and use
> DHCP to configure my network on startup? Or...?
If you're always using DHCP and never a static address, netenv is
probably unnecessary. There's the minor question of whether your
network card is PCMCIA or not, but the basic Debian tools deal fine
with the case where you have a single network card that always gets
brought up using an address from DHCP.
David Maze firstname.lastname@example.org http://people.debian.org/~dmaze/
"Theoretical politics is interesting. Politicking should be illegal."
-- Abra Mitchell