Re: Network config

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sat, Aug 05, 2017 at 10:37:42AM -0400, Gene Heskett wrote:
> On Saturday 05 August 2017 04:13:24 to...@tuxteam.de wrote:
> 
> > On Sat, Aug 05, 2017 at 12:11:28AM +1000, Zenaan Harkness wrote:
> > > On Fri, Aug 04, 2017 at 10:14:20AM +0200, to...@tuxteam.de wrote:
> >
> > [chattr]
> >
> > > Another command that could be add to /e/n/i :)
> >
> > you nasty ;-)
> >
> > cheers
> > -- t
> 
> Why do you say that Tomas?

Mind the smilie. Zenaan's post has also one.

This chattr thing is a good way to get out of trouble in a pinch
("who the %&@$!# is overvriting my /etc/ponies.d/foo file?"). It
might even help finding out the root cause (once you find it,
you'll also discover the small print in the man page, which was
stating clearly what's up.

Zenaan idea of perpetuating this (useful but ugly) hack in e/n/i
seemed... well, nasty. But funny :-)

> I've been using it precisely because the early 
> versions of network mangler could not be removed without emasculating 
> the whole system, AND it couldn't find a dhcpd server with both hands 
> even if it was nailed to its ass. So it would tear down a working 
> network config and leave you stuck.
> 
> My address  = hostname based home network, several machines, Just 
> Works(TM).  So I sit here and wonder why an estimated 50% of the posts 
> here are network failures. But I got tired of advising how to make it 
> Just Work(TM) and being called an idiot for doing so. So I sit, read, 
> and chuckle.

That's OK, and works... for fixed networks. Networks I have control
over are like that. Each machine there has a static IP address. Only
laptops (which come and go, and are sometimes on other nets) get
an address via DHCP.

No idea why anyone would want to call you an idiot for that.

Cheers
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlmF3HoACgkQBcgs9XrR2kZgowCbBGjeUBeNW0B3wbLrRQH981My
2aQAoIIHLFMR8lYcerZQBf0Vbg5K9G2D
=o3Sm
-END PGP SIGNATURE-

Re: Network config

[Gene Heskett]

On Saturday 05 August 2017 04:13:24 to...@tuxteam.de wrote:

> On Sat, Aug 05, 2017 at 12:11:28AM +1000, Zenaan Harkness wrote:
> > On Fri, Aug 04, 2017 at 10:14:20AM +0200, to...@tuxteam.de wrote:
>
> [chattr]
>
> > Another command that could be add to /e/n/i :)
>
> you nasty ;-)
>
> cheers
> -- t

Why do you say that Tomas? I've been using it precisely because the early 
versions of network mangler could not be removed without emasculating 
the whole system, AND it couldn't find a dhcpd server with both hands 
even if it was nailed to its ass. So it would tear down a working 
network config and leave you stuck.

My address  = hostname based home network, several machines, Just 
Works(TM).  So I sit here and wonder why an estimated 50% of the posts 
here are network failures. But I got tired of advising how to make it 
Just Work(TM) and being called an idiot for doing so. So I sit, read, 
and chuckle.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

Re: Network config

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sat, Aug 05, 2017 at 12:11:28AM +1000, Zenaan Harkness wrote:
> On Fri, Aug 04, 2017 at 10:14:20AM +0200, to...@tuxteam.de wrote:

[chattr]

> Another command that could be add to /e/n/i :)

you nasty ;-)

cheers
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlmFfiQACgkQBcgs9XrR2kYTgACfXqQfkrNsHoIrcZb6jGyVywwC
UogAnRT9hQJ0ly979kDQVpaSwqqKWUK1
=XWhS
-END PGP SIGNATURE-

Re: Network config

[Zenaan Harkness]

On Fri, Aug 04, 2017 at 09:01:32AM +0100, Joe wrote:
> On Fri, 4 Aug 2017 10:59:13 +1000
> Zenaan Harkness  wrote:
> > Given the uniqueness of how you seem to want to do your networking,
> > perhaps that's the best option to make it less abnormal - looks like
> > it to me.
> 
> I don't think it's really all that unique, or unreasonable, for a
> computer user to want to specify a particular DNS server. If an

That is absolutely true, and does not discount at all my implication
that "copying my own file over the top of /etc/resolv.conf after
dhclient runs and hoping there's no other race conditions that catch
me out", is perhaps a little "abnormal" in terms of a networking
setup.


> operating system file needs to be made immutable in order to achieve
> this, some programmer somewhere has... made a mistake, to put it kindly.

Or the user is not achieving their outcome due to not using the
installed software in the way it was designed.


> I wasted twenty minutes the other day, because a functional network
> switch connected to a couple of PCs had lost its wired connection to
> the rest of the network, which had been OK half an hour earlier. This
> simple fault was concealed by the way my Windows laptop was behaving in
> the absence of a DHCP server. Despite my efforts, it was ignoring its
> previous DHCP address, and my manually entered address, and was
> acquiring an APIPA address, thus guaranteeing no possible network
> connection ever.

:D - my condolences for your achievement in "using" some feature of
some version of Windows I had never even heard of before :D

> Eventually I worked out that there was a bug causing even worse
> misbehaviour than usual, and forced a suitable IP address onto the
> machine, when I quickly discovered a lack of connectivity... but if the
> damn thing hadn't been so *helpful*, I'd have fixed it much quicker.
> There appears to be no way to tell a Windows computer that you never,
> ever, *ever* want to see an APIPA address anywhere.
> 
> Yes, there's the perpetual argument about how much hand-holding a
> non-IT person needs, and it's a lot, and how much should be left to the
> user, but whatever the decision, it should always be possible for a
> user to insist 'I want it done *this* way'. If that lands him in
> trouble, tough, but foot-shooting must *always* be allowed, without an
> enormous struggle.

Indeed, there are many ways to sking this cat - network manager,
chattr, cp -o "with-crossed fingers" my-resolv.conf /etc/resolv.conf,
manual commands added in /e/n/i, /etc/resolvconf/resolv.conf.d/ -
even the Windows IT guys from the other department of the OP might be
able to update their DHCPd settings to deliver the desired DNS
server, when the MAC addresses get configured - do 2 things at the
same time.

Really, it would be easy to argue there are too many ways to skin
this cat.

Good luck all,

Re: Network config

[Zenaan Harkness]

On Fri, Aug 04, 2017 at 10:14:20AM +0200, to...@tuxteam.de wrote:
> On Thu, Aug 03, 2017 at 08:49:05PM +0200, Pascal Hambourg wrote:
> > Le 03/08/2017 à 15:52, Zenaan Harkness a écrit :
> > >On Thu, Aug 03, 2017 at 08:53:27AM -0400, Greg Wooledge wrote:
> > >>But the problem is, various Unix DHCP client daemons do *too much*.
> > >>All I want them to do is set the IP address, netmask, and gateway.
> > >>I *don't* want them to change the system hostname, or the system
> > >>resolv.conf (in which I have hand-placed *our* DNS search domain and
> > >>*our* DNS resolvers).
> > >
> > >Well, making /etc/resolv.conf read-only, owned by root.root
> > 
> > ... is just useless. resolv.conf is already owned by root, DCHP
> > client daemons run as root and on Linux systems root (uid 0) ignores
> > read/write permissions.
> 
> That's what chattr +i is for. Don't forget to do chattr -i on the file
> whenever *you* want to change it :-)

Another command that could be add to /e/n/i :)

Re: Network config

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Aug 03, 2017 at 08:49:05PM +0200, Pascal Hambourg wrote:
> Le 03/08/2017 à 15:52, Zenaan Harkness a écrit :
> >On Thu, Aug 03, 2017 at 08:53:27AM -0400, Greg Wooledge wrote:
> >>But the problem is, various Unix DHCP client daemons do *too much*.
> >>All I want them to do is set the IP address, netmask, and gateway.
> >>I *don't* want them to change the system hostname, or the system
> >>resolv.conf (in which I have hand-placed *our* DNS search domain and
> >>*our* DNS resolvers).
> >
> >Well, making /etc/resolv.conf read-only, owned by root.root
> 
> ... is just useless. resolv.conf is already owned by root, DCHP
> client daemons run as root and on Linux systems root (uid 0) ignores
> read/write permissions.

That's what chattr +i is for. Don't forget to do chattr -i on the file
whenever *you* want to change it :-)

(For me, it's a satisfying feeling when I see the culprits whining
in the logs that they cannot write to the file, but that may be
my hidden sadistic alter ego).

Cheers
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlmELNwACgkQBcgs9XrR2kYNMACfSv64NQre+qFfAXONWOEdADtm
jIoAn3rP30lR8UAeYqvKSrZt55GgM4gU
=SZVO
-END PGP SIGNATURE-

Re: Network config

[Joe]

On Fri, 4 Aug 2017 10:59:13 +1000
Zenaan Harkness  wrote:


> 
> Given the uniqueness of how you seem to want to do your networking,
> perhaps that's the best option to make it less abnormal - looks like
> it to me.
> 

I don't think it's really all that unique, or unreasonable, for a
computer user to want to specify a particular DNS server. If an
operating system file needs to be made immutable in order to achieve
this, some programmer somewhere has... made a mistake, to put it kindly.

I wasted twenty minutes the other day, because a functional network
switch connected to a couple of PCs had lost its wired connection to
the rest of the network, which had been OK half an hour earlier. This
simple fault was concealed by the way my Windows laptop was behaving in
the absence of a DHCP server. Despite my efforts, it was ignoring its
previous DHCP address, and my manually entered address, and was
acquiring an APIPA address, thus guaranteeing no possible network
connection ever.

Eventually I worked out that there was a bug causing even worse
misbehaviour than usual, and forced a suitable IP address onto the
machine, when I quickly discovered a lack of connectivity... but if the
damn thing hadn't been so *helpful*, I'd have fixed it much quicker.
There appears to be no way to tell a Windows computer that you never,
ever, *ever* want to see an APIPA address anywhere.

Yes, there's the perpetual argument about how much hand-holding a
non-IT person needs, and it's a lot, and how much should be left to the
user, but whatever the decision, it should always be possible for a
user to insist 'I want it done *this* way'. If that lands him in
trouble, tough, but foot-shooting must *always* be allowed, without an
enormous struggle.

-- 
Joe

Re: Network config

[Zenaan Harkness]

On Thu, Aug 03, 2017 at 08:49:05PM +0200, Pascal Hambourg wrote:
> Le 03/08/2017 à 15:52, Zenaan Harkness a écrit :
> > On Thu, Aug 03, 2017 at 08:53:27AM -0400, Greg Wooledge wrote:
> > > But the problem is, various Unix DHCP client daemons do *too much*.
> > > All I want them to do is set the IP address, netmask, and gateway.
> > > I *don't* want them to change the system hostname, or the system
> > > resolv.conf (in which I have hand-placed *our* DNS search domain and
> > > *our* DNS resolvers).
> > 
> > Well, making /etc/resolv.conf read-only, owned by root.root
> 
> ... is just useless. resolv.conf is already owned by root, DCHP client 
> daemons run as root and on Linux systems root
> (uid 0) ignores read/write permissions.
> 
> > uninstalling resolvconf should also solve your problem.
> 
> No, it solves nothing. Without resolvonf the DHCP client will write directly 
> in resolv.conf.
> 
> > If you in this last (laptop) scenario need specific addition of your
> > static nameserver, on top of the DHCP nameservers (e.g. one
> > nameserver might resolve some internal names, the others might
> > recursively resolve internet names)
> 
> This does not work.
> The resolver stops as soon as it receives a positive (record exists) or 
> negative (record does not exist) answer. If it
> receives a negative answer from the first name server, it won't query the 
> next name server.
> 
> All name servers declared in resolv.conf must be equal and provide the same 
> answers, or unexpected behaviour will
> happen. Multiple name servers is only for redundancy and load balancing, not 
> to provide different answers.

What about putting your script lines (copying files around etc) into
your /etc/network/interfaces file?

Given the uniqueness of how you seem to want to do your networking,
perhaps that's the best option to make it less abnormal - looks like
it to me.

Good luck,

Re: Network config

[Henning Follmann]

On Thu, Aug 03, 2017 at 08:53:06PM +0200, Pascal Hambourg wrote:
> Le 03/08/2017 à 17:20, Joshua Schaeffer a écrit :
> > 
> > Configuration in /etc/network/interfaces only works when NetworkManager 
> > isn't installed,
> 
> Wrong. The default NetworkManager behaviour is not to manage interfaces
> defined in /etc/network/interfaces.
> 


Well, that is also partly wrong.
There was definitely an issue with a mix of /e/n/i and NM and systemd.
If the device couldn't be brought up during system start systemd would hang
sometimes for a very long time. This was at least true for Jessie.

-H

-- 
Henning Follmann   | hfollm...@itcfollmann.com

Re: Network config

[Pascal Hambourg]

Le 03/08/2017 à 17:20, Joshua Schaeffer a écrit :


Configuration in /etc/network/interfaces only works when NetworkManager isn't 
installed,


Wrong. The default NetworkManager behaviour is not to manage interfaces 
defined in /etc/network/interfaces.

Re: Network config

[Pascal Hambourg]

Le 03/08/2017 à 15:52, Zenaan Harkness a écrit :

On Thu, Aug 03, 2017 at 08:53:27AM -0400, Greg Wooledge wrote:

But the problem is, various Unix DHCP client daemons do *too much*.
All I want them to do is set the IP address, netmask, and gateway.
I *don't* want them to change the system hostname, or the system
resolv.conf (in which I have hand-placed *our* DNS search domain and
*our* DNS resolvers).


Well, making /etc/resolv.conf read-only, owned by root.root


... is just useless. resolv.conf is already owned by root, DCHP client 
daemons run as root and on Linux systems root (uid 0) ignores read/write 
permissions.



uninstalling resolvconf should also solve your problem.


No, it solves nothing. Without resolvonf the DHCP client will write 
directly in resolv.conf.



If you in this last (laptop) scenario need specific addition of your
static nameserver, on top of the DHCP nameservers (e.g. one
nameserver might resolve some internal names, the others might
recursively resolve internet names)


This does not work.
The resolver stops as soon as it receives a positive (record exists) or 
negative (record does not exist) answer. If it receives a negative 
answer from the first name server, it won't query the next name server.


All name servers declared in resolv.conf must be equal and provide the 
same answers, or unexpected behaviour will happen. Multiple name servers 
is only for redundancy and load balancing, not to provide different answers.

Re: Network config

[Joshua Schaeffer]

On 08/02/2017 06:56 PM, Zenaan Harkness wrote:
>
> I've preferred a static networking config for years, and resolvconf
> works well in this situation - but once resolvconf is configured,
> I've always put the dns setting in /etc/networks/interfaces

I agree with this as well. If you want to use static configuration and want 
resolvconf installed, you need to use the dns-* options in 
/etc/network/interfaces. resolvconf will then update your /etc/resolv.conf file 
with those options. If you change /etc/resolv.conf manually, resolvconf will 
override those settings periodically. The alternative is to simply uninstall 
resolvconf and set your DNS settings manually.

>  - the
> only time I put an entry in /etc/resolv.conf is when I'm testing
> stuff or doing a quick hack.
>
> Static network configs are quicker and give that sense of control -
> if the gui is down I can still fix things, and my knowledge applies
> in both gui and console scanerios.

Configuration in /etc/network/interfaces only works when NetworkManager isn't 
installed, which it typically is in GUI environments. If you don't have it 
installed in your GUI environment then yes, it works in both. If NetworkManager 
is installed then the nmcli command should be used and you shouldn't do any 
configuration in /etc/network/interfaces (although loopback is typically still 
controlled through this file).

Thanks,
Joshua Schaeffer

Re: Network config

[Zenaan Harkness]

On Thu, Aug 03, 2017 at 08:53:27AM -0400, Greg Wooledge wrote:
> But the problem is, various Unix DHCP client daemons do *too much*.
> All I want them to do is set the IP address, netmask, and gateway.
> I *don't* want them to change the system hostname, or the system
> resolv.conf (in which I have hand-placed *our* DNS search domain and
> *our* DNS resolvers).

Well, making /etc/resolv.conf read-only, owned by root.root, and
uninstalling resolvconf should also solve your problem.

Then programs won't write to the file.

Since you have a long term static nameserver, you're good.


Alternatively, if you might change your setup here and there for a
particular host, I find resolvconf to be the perfect middle ground -
and when it's meant to not update resolv.conf, that "NO" setting
looks like it should work a treat for you.

Or if you comission a laptop which might move daily between
locations, fully dynamic DHCP config might be best - just use network
manager and whatever it depends on, and the default "auto everything"
should work assuming DHCP is set up correctly at your site - just let
the auto-stuff do its auto stuff, and the laptop will mostly work.
Uninstall resolvconf since network manager does it all.

If you in this last (laptop) scenario need specific addition of your
static nameserver, on top of the DHCP nameservers (e.g. one
nameserver might resolve some internal names, the others might
recursively resolve internet names) then configuring resolvonf to
know about your static server and add it "on each dhcp
reconfiguration" will work when properly configured too - either
before or after the DHCP assigned servers (i.e. depending on the
precedence you need for the resolves), this could be another ideal
configuration well served by resolvconf.


That which is ideal, always depends on your requirements. I'm still
not clear on your requirements, but perhaps one of the above
scenarios will satisfy.


> On the HP-UX systems, I modified the boot scripts to accomodate all of
> the funky things that happen with DHCP.  I keep master copies of the true
> /etc/resolv.conf and /etc/hosts files (plus one other HP-UX-specific
> network config file), which all get overwritten by the DHCP client,
> and I restore them at just the right time.

That sounds ugly, and way overly hacky.

I suggest thoroughly reading the resolvconf man page to understand
its workings, and making use of that.

If you don't want to do that for any reason, that's also fine - just
remove resolvconf as suggested by someone else in this thread.


> I put the hostname and IP
> in /etc/hosts so that dtlogin can start.  Also, starting with an update
> of ITD's DHCP servers about 5 years ago, the HP-UX DHCP client started
> overwriting the system hostname with the one provided by the DHCP server.
>
> So I had to make more changes to work around that as well, restoring
> the correct hostname at just the right moment.

Surely this would be easier? :
chmod 400 /etc/hostname


I'm a sure fan of static network config (which includes hostname),
but sure sounds like you might be doing things the hard way.


> On the Debian systems, I learned through trial and error that this
> change works:
> 
> --- /etc/dhcp/dhclient.conf.20170410  2017-04-10 10:12:13.271209076 -0400
> +++ /etc/dhcp/dhclient.conf   2017-04-10 10:12:26.291209232 -0400
> @@ -14,8 +14,7 @@
>  
>  send host-name = gethostname();
>  request subnet-mask, broadcast-address, time-offset, routers,
> - domain-name, domain-name-servers, domain-search, host-name,
> - dhcp6.name-servers, dhcp6.domain-search, dhcp6.fqdn, dhcp6.sntp-servers,
> + dhcp6.sntp-servers,
>   netbios-name-servers, netbios-scope, interface-mtu,
>   rfc3442-classless-static-routes, ntp-servers;
> 
> If I simply don't ask for DNS nameserver addresses, the DHCP server
> doesn't provide them, and dhclient doesn't touch resolv.conf, and everyone
> is happy.  The Debian/ISC DHCP client is smart enough to ignore the
> hostname coming from DHCP, so I didn't have to do anything there.
> 
> (The HP-UX DHCP client does not have this level of control, so I have
> to fix things up after the fact.)

Possibly just compile the ISC DHCP client for HP-UX - a binary
compiled by someone else might even be available.


> Home system: the DHCP server is a Belkin plastic router.  The router
> silently forwards DNS queries to the ISP's nameserver, which is tolerable,
> but a bit slow.  I would prefer to run a local dnscache resolver (from
> djbdns).  The DHCP server provides a nameserver entry whether I request
> it or not, and a search domain of "Belkin".
> 
> I am not using djbdns from a Debian package.  It's pure upstream.

openresolv is a new package I haven't seen before

For DNS cache, I've installed dnsmasq many times over the years -
it's small an

Re: Network config

[Greg Wooledge]

On Thu, Aug 03, 2017 at 11:09:48AM +1000, Zenaan Harkness wrote:
> Perhaps in certain scenarios, yes - the world's full of wierd
> networks :)

Concrete examples?  OK.

Work system: the Information Technology Division (ITD) runs the DHCP
servers, which are basically built around the assumption that you
will be running the standard Windows 7 desktop PC.  The DHCP server
provides nameserver entries if requested, and a hostname whether you
want it or not.

Meanwhile, over in Unixland, my department has its own network
infrastructure which predates the central ITD infrastructure.  We were
the pioneers, not them.  We have our own subdomain (eeg.ccf.org), our
own authoritative DNS servers and caching resolvers.  Our DNS servers
include proper PTR records for our hosts (ITD's do not).

There is a sharing of responsibility between ITD and my department.
They control the allocation of IP addresses, but we are allowed to request
DHCP reservations.  There is a specific protocol for doing so: we put
our new computer on the network, and configure it as a DHCP client.
We get it all set up, with its DHCP-assigned address.  Then we send
an email to the ITD contact address requesting the DHCP reservation.
They put an entry in whatever software they use so the new system *keeps*
its IP address.

If someone moves the machine to a different floor (which will have a
different network address), then the fact that it's configured as a
DHCP client means it will at least *boot* and (hopefully) come up with
a new IP address.  Then they can call me, I can come down to the new
location, get the IP and MAC, update it in DNS, and send the new
DHCP reservation request to ITD.

But the problem is, various Unix DHCP client daemons do *too much*.
All I want them to do is set the IP address, netmask, and gateway.
I *don't* want them to change the system hostname, or the system
resolv.conf (in which I have hand-placed *our* DNS search domain and
*our* DNS resolvers).

On the HP-UX systems, I modified the boot scripts to accomodate all of
the funky things that happen with DHCP.  I keep master copies of the true
/etc/resolv.conf and /etc/hosts files (plus one other HP-UX-specific
network config file), which all get overwritten by the DHCP client,
and I restore them at just the right time.  I put the hostname and IP
in /etc/hosts so that dtlogin can start.  Also, starting with an update
of ITD's DHCP servers about 5 years ago, the HP-UX DHCP client started
overwriting the system hostname with the one provided by the DHCP server.
So I had to make more changes to work around that as well, restoring
the correct hostname at just the right moment.

(Thank goodness for non-parallel boot systems.)

On the Debian systems, I learned through trial and error that this
change works:

--- /etc/dhcp/dhclient.conf.201704102017-04-10 10:12:13.271209076 -0400
+++ /etc/dhcp/dhclient.conf 2017-04-10 10:12:26.291209232 -0400
@@ -14,8 +14,7 @@
 
 send host-name = gethostname();
 request subnet-mask, broadcast-address, time-offset, routers,
-   domain-name, domain-name-servers, domain-search, host-name,
-   dhcp6.name-servers, dhcp6.domain-search, dhcp6.fqdn, dhcp6.sntp-servers,
+   dhcp6.sntp-servers,
netbios-name-servers, netbios-scope, interface-mtu,
rfc3442-classless-static-routes, ntp-servers;

If I simply don't ask for DNS nameserver addresses, the DHCP server
doesn't provide them, and dhclient doesn't touch resolv.conf, and everyone
is happy.  The Debian/ISC DHCP client is smart enough to ignore the
hostname coming from DHCP, so I didn't have to do anything there.

(The HP-UX DHCP client does not have this level of control, so I have
to fix things up after the fact.)


Home system: the DHCP server is a Belkin plastic router.  The router
silently forwards DNS queries to the ISP's nameserver, which is tolerable,
but a bit slow.  I would prefer to run a local dnscache resolver (from
djbdns).  The DHCP server provides a nameserver entry whether I request
it or not, and a search domain of "Belkin".

I am not using djbdns from a Debian package.  It's pure upstream.

I have configured the router to assign my IP address to my MAC address.
I just don't want it to touch my resolv.conf file.

At first I tried doing what I did at work: removing lines from the
dhclient.conf file.  But the Belkin DHCP server doesn't stop sending
the nameserver, and dhclient continues to overwrite resolv.conf.

I ended up simply doing chattr +i.


> If you're wanting a static resolv.conf, are you manually
> running dhclient, or using /etc/network/interfaces ?

I use /etc/network/interfaces with

auto eth0
iface eth0 inet dhcp

> I.e. is this a one-shot scenario, or a "static" config situation?

It's "static" in the sense that the configuration is (supposed to
be) unchanging.  But not in the sense of "iface eth0 inet static".
The IP address, netmask and gateway come from DHCP.  The hostname,
name

Re: Network config

[Zenaan Harkness]

On Wed, Aug 02, 2017 at 02:55:50PM -0400, Greg Wooledge wrote:
> On Wed, Aug 02, 2017 at 08:10:23PM +0200, Pascal Hambourg wrote:
> > Le 02/08/2017 à 16:19, Greg Wooledge a écrit :
> > > 
> > > 1) Make sure the Debian "resolvconf" package is *not* installed.
> > 
> > You should reconsider this advice. resolvconf may be your best ally to
> > handle such a situation.
> 
> OK, I've scanned
>  and
> .
> 
> Looks complicated, with lots of specialized words being thrown around
> but not defined.
> 
> E.g. resolvconf(8) says "In some situations resolvconf needs to act as
> a deterrent to writing to /etc/resolv.conf. Where this file cannot be
> made immutable or you just need to toggle this behaviour, resolvconf
> can be disabled by adding resolvconf=NO to resolvconf.conf(5)."
> 
> Looks promising, eh?  But then resolvconf.conf(5) says "Set to NO to
> disable resolvconf from running any subscribers. Defaults to YES."
> 
> What is a "subscriber"?  Definitely not defined in (8).  There's a section
> called "SUBSCRIBER OPTIONS" in (5) but it still doesn't explain what they
> are.
> 
> Back to (8), it says "Where this file cannot be made immutable".  Is it
> *admitting*

To be precise, "implying" is perhaps accurate.


> that making the file immutable is the preferred solution, and
> resolvconf is just a backup plan?  That's what I'm getting out of it.

Perhaps in certain scenarios, yes - the world's full of wierd
networks :)

> I don't see the advantage of installing a package and configuring it
> in order to make it do *nothing*, when I can achieve the same thing
> by making the resolv.conf file immutable.  (On Linux.)
> 
> Don't get me wrong; I'm sure there is a genuine need for resolvconf
> and all this complexity on some systems.  Especially systems that are
> designed to be moved around, dynamically connecting and disconnecting
> various wireless networks, instantiating and decommissioning VPN sessions,
> and so on.
> 
> But for a great many *other* systems, we just want to be able edit the
> resolv.conf file by hand and have our changes *stay* there, untouched.
> We know what we are doing, and the DHCP server is not under our direct
> control, and we just need to make the DHCP client keep its hands OFF
> the god damned file.

If you're wanting a static resolv.conf, are you manually
running dhclient, or using /etc/network/interfaces ?

I.e. is this a one-shot scenario, or a "static" config situation?

> It should *not* be this hard to be allowed to edit a three line text
> file that has been in common use across every Unix-like operating system
> for decades.
> 
> Nevertheless, if someone can definitively state that the following
> is true:
> 
>"If you install resolvconf and then do:
>   echo resolvconf=NO >> /etc/resolvconf.conf
> no Debian package will ever modify your /etc/resolv.conf again."
> 
> then I will be glad to accept it as yet another alternative solution
> for some users/systems.

I'm not that knowledgeable, but dhclient is listen in the resolvconf
man page as a "^SUPPLIERS OF NAMESERVER INFORMATION"... so appears to
be intended to work together.

Have you tried also reading man dhclient.conf ?

Good luck,

Re: Network config

[Zenaan Harkness]

On Wed, Aug 02, 2017 at 05:44:50PM +0400, ruslan axundov wrote:
> Hi
> 
> I have a problem with debian 9 as static nameserver .
> So that I used before ubuntu 16.04  and I have configure satatic ip and dns
> and it worked perfectly  but today I tried to use debian 9 and  when I
> enter static dns server for debian in resolve.conf  then after reboot
> debian all dns ip removed from resolv.conf file. I tried multiple method to
> prevent this feature but nothing happen. what I must do ?

I've preferred a static networking config for years, and resolvconf
works well in this situation - but once resolvconf is configured,
I've always put the dns setting in /etc/networks/interfaces - the
only time I put an entry in /etc/resolv.conf is when I'm testing
stuff or doing a quick hack.

Static network configs are quicker and give that sense of control -
if the gui is down I can still fix things, and my knowledge applies
in both gui and console scanerios.

Good luck,

Re: Network config

[Greg Wooledge]

On Wed, Aug 02, 2017 at 08:10:23PM +0200, Pascal Hambourg wrote:
> Le 02/08/2017 à 16:19, Greg Wooledge a écrit :
> > 
> > 1) Make sure the Debian "resolvconf" package is *not* installed.
> 
> You should reconsider this advice. resolvconf may be your best ally to
> handle such a situation.

OK, I've scanned
 and
.

Looks complicated, with lots of specialized words being thrown around
but not defined.

E.g. resolvconf(8) says "In some situations resolvconf needs to act as
a deterrent to writing to /etc/resolv.conf. Where this file cannot be
made immutable or you just need to toggle this behaviour, resolvconf
can be disabled by adding resolvconf=NO to resolvconf.conf(5)."

Looks promising, eh?  But then resolvconf.conf(5) says "Set to NO to
disable resolvconf from running any subscribers. Defaults to YES."

What is a "subscriber"?  Definitely not defined in (8).  There's a section
called "SUBSCRIBER OPTIONS" in (5) but it still doesn't explain what they
are.

Back to (8), it says "Where this file cannot be made immutable".  Is it
*admitting* that making the file immutable is the preferred solution, and
resolvconf is just a backup plan?  That's what I'm getting out of it.

I don't see the advantage of installing a package and configuring it
in order to make it do *nothing*, when I can achieve the same thing
by making the resolv.conf file immutable.  (On Linux.)

Don't get me wrong; I'm sure there is a genuine need for resolvconf
and all this complexity on some systems.  Especially systems that are
designed to be moved around, dynamically connecting and disconnecting
various wireless networks, instantiating and decommissioning VPN sessions,
and so on.

But for a great many *other* systems, we just want to be able edit the
resolv.conf file by hand and have our changes *stay* there, untouched.
We know what we are doing, and the DHCP server is not under our direct
control, and we just need to make the DHCP client keep its hands OFF
the god damned file.

It should *not* be this hard to be allowed to edit a three line text
file that has been in common use across every Unix-like operating system
for decades.

Nevertheless, if someone can definitively state that the following
is true:

   "If you install resolvconf and then do:
  echo resolvconf=NO >> /etc/resolvconf.conf
no Debian package will ever modify your /etc/resolv.conf again."

then I will be glad to accept it as yet another alternative solution
for some users/systems.

Re: Network config

[Pascal Hambourg]

Le 02/08/2017 à 16:19, Greg Wooledge a écrit :


1) Make sure the Debian "resolvconf" package is *not* installed.


You should reconsider this advice. resolvconf may be your best ally to 
handle such a situation.



3) I have utterly no idea how Network-Manager works


Me neither, but I know one thing : it overwrites /etc/resolv.conf 
*unless resolvconf is installed* and properly configured.



5) Some DHCP servers send back a list of nameserver IPs even if you don't
ask for them.  The ISC DHCP client daemon *will* overwrite resolv.conf
if it receives them.


*Unless resolvconf is installed* and properly configured.

Re: Network config

[Greg Wooledge]

On Wed, Aug 02, 2017 at 05:44:50PM +0400, ruslan axundov wrote:
> I tried to use debian 9 and  when I
> enter static dns server for debian in resolve.conf  then after reboot
> debian all dns ip removed from resolv.conf file. I tried multiple method to
> prevent this feature but nothing happen. what I must do ?

 is the
best single starting point I have found so far.  It gives multiple
ways to attack the problem, and you can choose which one(s) seem best
for your situation.

Other tips I can give: 

1) Make sure the Debian "resolvconf" package is *not* installed.

2) If /etc/resolv.conf is a symlink (e.g. due to previous installation
   of the resolvconf package), remove it and recreate it as a file.

3) I have utterly no idea how Network-Manager works (never used it), so
   consider removing that too, unless you really need it.

4) systemd may have some other network configuratizing thinymajig.
   But you know better than to use *that*, right?

5) Some DHCP servers send back a list of nameserver IPs even if you don't
   ask for them.  The ISC DHCP client daemon *will* overwrite resolv.conf
   if it receives them.  So, simply configuring dhclient.conf not to
   ask for nameservers will work on some networks but not on others.

Network config

[ruslan axundov]

Hi

I have a problem with debian 9 as static nameserver .
So that I used before ubuntu 16.04  and I have configure satatic ip and dns
and it worked perfectly  but today I tried to use debian 9 and  when I
enter static dns server for debian in resolve.conf  then after reboot
debian all dns ip removed from resolv.conf file. I tried multiple method to
prevent this feature but nothing happen. what I must do ?


-- 
*Axundov Ruslan*
*Tel:* (050) 229 20 24
*Email:* raxun...@gmail.com
   r.axun...@live.com

new network config- WAS: Re: New User- Network Problem

[Paul Cartwright]

On Fri February 15 2008, Osamu Aoki wrote:
   link-local  169.254.0.0
 
   
   what is this   ^^^

 Per google and wikipedia.

 http://en.wikipedia.org/wiki/Link-local_address

 Quite normal though.

 I have not read the context but this is FYI.

ok, this seems to tell me when my eth0 is not working, then this defaults to 
the local 169.xxx internal subnet and I won't have internet access.



-- 
Paul Cartwright
Registered Linux user # 367800
Registered Ubuntu User #12459

Re: new network config- WAS: Re: New User- Network Problem

[Andrei Popescu]

On Fri, Feb 15, 2008 at 10:47:15AM -0500, Paul Cartwright wrote:
 On Fri February 15 2008, Osamu Aoki wrote:
link-local  169.254.0.0
  
    
    what is this   ^^^
 
  Per google and wikipedia.
 
  http://en.wikipedia.org/wiki/Link-local_address
 
  Quite normal though.
 
  I have not read the context but this is FYI.
 
 ok, this seems to tell me when my eth0 is not working, then this defaults to 
 the local 169.xxx internal subnet and I won't have internet access.

AFAIK link-local 169.254.xxx.xxx addresses are used when there is no 
server. Could it be that your router is not answering? Try setting 
everything to static and see if it works.

Regards,
Andrei
-- 
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)


signature.asc
Description: Digital signature

Re: boot disk for grub; network config; printer pb

[Andrew Sackville-West]

On Sun, Apr 30, 2006 at 08:42:34AM -0700, belahcene abdelkader wrote:
 
 Hi,
 
  i am using sarge, I want to create a boot disk from
 my distro, I tried mkboot, but it seems running with
 lilo and not grub
 
 network: there is no network configuring program, like
 netcardconfig, So I have to fill manually the
 /etc/network/interface file
 
 The configuration of printer seems difficult, what to
 use cups  or directjet,  my hp printer has a network
 card

with a network card in your printer, setting up cups for printing
should be trivial:

apt-get install cupsys cupsys-client

I think.

A


 
 
 thanks
 bela
 
 
 
 __
 Do You Yahoo!?
 Tired of spam?  Yahoo! Mail has the best spam protection around 
 http://mail.yahoo.com 
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 


signature.asc
Description: Digital signature

boot disk for grub; network config; printer pb

[belahcene abdelkader]

Hi,

 i am using sarge, I want to create a boot disk from
my distro, I tried mkboot, but it seems running with
lilo and not grub

network: there is no network configuring program, like
netcardconfig, So I have to fill manually the
/etc/network/interface file

The configuration of printer seems difficult, what to
use cups  or directjet,  my hp printer has a network
card


thanks
bela



__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: two basic new to Debian questions: network config RMS

[vineyard saker]

Thanks to all for your info and pointers!

VS

two basic new to Debian questions: network config RMS

[vineyard saker]

Hi everybody,

I just completed a switch from 5 years of Mandrake to Debian
GNU/Linux.  The install went well, although I had to use a couple of
tricks to configure X and my soundcard.  I now have to basic
questions:

1) during my install I was not connected to the Internet (I had
ordered the 14 Debian CDs from budgetlinuxcds) and I therefore did not
configure my network card.  Now I would like to connect my computer to
the rest of my computers on a home network.  What would you reccommend
as the best application to do this?

2) I vaguely remember hearing that there were some disagreements
between the Debian team and Richard Stallman but I do not remember
what caused it.  Could anyone point me to the right place to read up
on this?

Many thanks,

VS

Re: two basic new to Debian questions: network config RMS

[David Hugh-Jones]

Depends what kind of networking you want to do. If you are just
connecting to a LAN with a DHCP server running, then just run
/etc/init.d/networking start as root and see if it works. If you
want a static IP address and name servers, the easiest way is probably
to use the Gnome network tools - available in the Gnome menu under
system tools. Or if you prefer the command line, edit
/etc/network/interfaces - it's fairly simple, see man interfaces.

Or maybe you want something more complex, like to run a server, etc. etc...

As for RMS - no idea. (And personally, no interest either :-)) 

David

On 30/06/05, vineyard saker [EMAIL PROTECTED] wrote:
 Hi everybody,
 
 I just completed a switch from 5 years of Mandrake to Debian
 GNU/Linux.  The install went well, although I had to use a couple of
 tricks to configure X and my soundcard.  I now have to basic
 questions:
 
 1) during my install I was not connected to the Internet (I had
 ordered the 14 Debian CDs from budgetlinuxcds) and I therefore did not
 configure my network card.  Now I would like to connect my computer to
 the rest of my computers on a home network.  What would you reccommend
 as the best application to do this?
 
 2) I vaguely remember hearing that there were some disagreements
 between the Debian team and Richard Stallman but I do not remember
 what caused it.  Could anyone point me to the right place to read up
 on this?
 
 Many thanks,
 
 VS
 

Re: two basic new to Debian questions: network config RMS

[Stefan Muthers]

Hi,
vineyard saker [EMAIL PROTECTED] schrieb:

 I just completed a switch from 5 years of Mandrake to Debian
 GNU/Linux.  The install went well, although I had to use a couple of
 tricks to configure X and my soundcard.  I now have to basic
 questions:

 1) during my install I was not connected to the Internet (I had
 ordered the 14 Debian CDs from budgetlinuxcds) and I therefore did not

If you got debian 3.1_r0 then your version has a little bug.
Add 
http://security.debian.org/ stable/updates
to your /etc/apt/sources.list so that you will be able to get security
updates.

 configure my network card.  Now I would like to connect my computer to
 the rest of my computers on a home network.  What would you reccommend
 as the best application to do this?

I would edit /etc/networking/interfaces. Mine looks like this:

  __( '/etc/network/interfaces' )___
 /
| # This file describes the network interfaces available on your system
| # and how to activate them. For more information, see interfaces(5).
| 
| # The loopback network interface
| auto lo
| iface lo inet loopback
| 
| auto eth0
| iface eth0 inet static
|   address 192.168.0.3
|   netmask 255.255.255.0
|   broadcast 192.168.0.255
|   gateway 192.168.0.23
 \__
 
for more see man interfaces.
And, if you need to load some extra modules, add them to /etc/modules.

Stefan


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: two basic new to Debian questions: network config RMS

[Martin Dickopp]

vineyard saker [EMAIL PROTECTED] writes:

 1) during my install I was not connected to the Internet (I had
 ordered the 14 Debian CDs from budgetlinuxcds) and I therefore did not
 configure my network card.  Now I would like to connect my computer to
 the rest of my computers on a home network.  What would you reccommend
 as the best application to do this?

Definitely ifupdown -- that's The Debian Way of networking. Install
the 'ifupdown' package, read 'man 5 interfaces', and set up
/etc/network/interfaces.

 2) I vaguely remember hearing that there were some disagreements
 between the Debian team and Richard Stallman but I do not remember
 what caused it.  Could anyone point me to the right place to read up
 on this?

There are two disagreements I'm aware of. First of all, Debian thinks
works released under the GNU Free Documentation License (GFDL) are
non-free, while RMS thinks they are free or the freedoms they lack
don't matter (I forgot which one). Secondly, Debian distributes both
free software and proprietary software (the 'non-free' section) in the
same way. Debian doesn't consider this to be a problem, RMS does.

Search the Debian mailing list archive for posts from RMS.

Martin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: two basic new to Debian questions: network config RMS

[Marty]

s. keeling wrote:

RMS seems to have disagreements with just about everyone but himself.


RMS more than any public figure I know of, seems to generate these ad
hominem attacks against himself.  He's also the most intelligent and
relentlessly logical writer and speaker of any public figure I know of.

D'ya think there's a connection?  Naaah, couldn't be!


See the latest BS that's going on between Gnu and OpenBSD for
example.  As for where to go to look into it, Google,
lists.debian.org, and debian.org should get you there.


I didn't find anything on the controversy, but here's what I did find:

http://www.monkey.org/openbsd/archive/misc/0301/msg00038.html:
  * From: Theo de Raadt [EMAIL PROTECTED]
  * Date: Wed, 01 Jan 2003 23:34:03 -0700
  The FSF nearly goes out of their way to not credit other's efforts.  I
  say to hell with them.

http://www.fsf.org/news/fsaward2004.html
  Theo de Raadt presented with the 2004 Free Software Award

I post these for readers with an appreciation of irony.  On slashdot
these examples would be moderated +5 funny! :-)

Pattern.  No explanations needed.  If Stallman speaks up, it's just BS.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

running network config in Sarge

[john gennard]

How do I run network configuration in Sarge. I ignored it in
a recent install?
Would someone please let me know.
John.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: running network config in Sarge

[John Summerfield]

john gennard wrote:
How do I run network configuration in Sarge. I ignored it in
a recent install?
Would someone please let me know.
I edit /etc/network/interfaces with vim. I expect that vigor might do as 
well.

for more,
man interfaces
etc.
--
Cheers
John
-- spambait
[EMAIL PROTECTED]  [EMAIL PROTECTED]
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: running network config in Sarge

[John Floren]

john gennard wrote:
How do I run network configuration in Sarge. I ignored it in
a recent install?
Would someone please let me know.
John.

Probably the easiest way is to do apt-get install etherconf, which 
will give you a nice interface to network configuration.  If you need to 
change anything later, simply run dpkg-reconfigure etherconf to go 
through the configuration again.  Network configurations are stored in 
/etc/network/interfaces

Digi
--
http://nuwen.net/~digi/cluster
Anybody with money to burn will easily find someone to tend the fire.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: newbie network config

[Alan Chandler]

On Sunday 15 February 2004 01:28, Paul Johnson wrote:

 Ah. OK.  Is all this listed someplace and I somehow overlooked it?

F10;help; user manual  - scroll down to the section on searching


-- 
Alan Chandler
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: newbie network config

[Paul Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Feb 12, 2004 at 09:25:17PM -0500, Marty Landman wrote:
 I've just installed Woody from the mini-iso on a PI-166/32M ram/6GB ide 
 with a netgear FS310TX nic installed. The light from the cable on my lan 
 switch is lit but I couldn't find the nic on the config list, and attempting
 
 ifconfig eth0 192.168.0.3 netmask 255.255.255.0 up
 
 fails with 'no such device'.
 
 How can I go about connecting this box to my lan?

Make sure the correct module for your NIC is installed.

man 5 interfaces
editor /etc/network/interfaces

- -- 
 .''`. Paul Johnson [EMAIL PROTECTED]
: :'  :
`. `'` proud Debian admin and user
  `-  Debian - when you have better things to do than fix a system
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFALpFuUzgNqloQMwcRArPuAKDlz7s9mQrqYOhWJpj6Wd1yrh5toQCg2zCn
TYfP0VYU0HrSXHnX3+Uxx3A=
=Dt1g
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: newbie network config

[Paul Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, Feb 13, 2004 at 08:12:28PM -0600, Jacob S. wrote:
 Enjoy your new Debian machine! Oh, and if you have a decent 'net
 connection, use apt-get from your nearest mirror to download the extra
 packages you want... much easier than downloading/burning ISOs. 

You should be doing this anyway.  Downloading ISOs wastes a lot of
space and bandwidth on packages that you will likely never use.

- -- 
 .''`. Paul Johnson [EMAIL PROTECTED]
: :'  :
`. `'` proud Debian admin and user
  `-  Debian - when you have better things to do than fix a system
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFALpJGUzgNqloQMwcRAjkuAKCpRiGe2RxrdK/DHU7+NqM4oAAaEACfU0iv
JeUWzwOYWCmJjOWZZIJhquM=
=xqzM
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: newbie network config

[Paul Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, Feb 13, 2004 at 08:46:10PM -0600, Jacob S. wrote:
 Apt-get by itself is years beyond what rpm was, when I played around
 with it.

Well, that's comparing an apple to an orange, as well.  apt-get would
be closest to the cheap knockoff, apt-rpm.  rpm is closest to dpkg.

That being said, RPM is inheirently flawed by file (as opposed to
package) dependencies and inconsistent package names and file
locations.  See also: dependency hell.

- -- 
 .''`. Paul Johnson [EMAIL PROTECTED]
: :'  :
`. `'` proud Debian admin and user
  `-  Debian - when you have better things to do than fix a system
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFALpMSUzgNqloQMwcRAgLnAKCfm9qcGlVIYI0qWv3Rg9YugDdT0wCgps1r
ZbuRsfpJePS9T0eOfF9Kuwk=
=Edm/
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: newbie network config

[Paul Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sat, Feb 14, 2004 at 02:33:32PM +, Alan Chandler wrote:
 I used to use dselect quite a lot to search for packages - that was
 until I found aptitude.  Now I would live without it - the advantage
 over the command line tools is that you can browse for things.

On the other hand, there doesn't seem to be a good way to do an
apt-cache search from within aptitude.

- -- 
 .''`. Paul Johnson [EMAIL PROTECTED]
: :'  :
`. `'` proud Debian admin and user
  `-  Debian - when you have better things to do than fix a system
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFALpOVUzgNqloQMwcRAkxEAJ0Q2NtDRN/w6Roe/Fic9f/5av11xQCgur6L
ZPtbib2+k+MiS8ZsKFMBUL8=
=lL1I
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: newbie network config

[Jacob S.]

On Sat, 14 Feb 2004 13:28:50 -0800
Paul Johnson [EMAIL PROTECTED] wrote:

 On Fri, Feb 13, 2004 at 08:46:10PM -0600, Jacob S. wrote:
  Apt-get by itself is years beyond what rpm was, when I played around
  with it.
 
 Well, that's comparing an apple to an orange, as well.  apt-get would
 be closest to the cheap knockoff, apt-rpm.  rpm is closest to dpkg.

True, but the keywords in my statement were when I played around with
it. apt-rpm wasn't available when I played with Redhat, Mandrake and
SuSE (all of which use rpms), which is one of the reasons I switched to
Debian.

 That being said, RPM is inheirently flawed by file (as opposed to
 package) dependencies and inconsistent package names and file
 locations.  See also: dependency hell.

No disagreements there.

Jacob

- 
GnuPG Key: 1024D/16377135

Random .signature #43:
Q: How many Microsoft Programmers does it take to screw in a lightbulb?
A: It cannot be done. You will need to upgrade your house.

Q: How many Linux users does it take to change a lightbulb?
A: Two. One to write the HOWTO-LIGHTBULB-CRONJOB, and another to read
it. 


pgp0.pgp
Description: PGP signature

Re: newbie network config

[Alan Chandler]

On Saturday 14 February 2004 21:31, Paul Johnson wrote:

 On the other hand, there doesn't seem to be a good way to do an
 apt-cache search from within aptitude.

not sure what you mean since I don't use apt-cache

You can search for packages by typing
/ followed by the initial characters of the package name - it searches as you 
type.  There is a more complex search capability given in the help

you can repeat a search by typing \


-- 
Alan Chandler
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: newbie network config

[Paul Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sat, Feb 14, 2004 at 11:35:16PM +, Alan Chandler wrote:
 not sure what you mean since I don't use apt-cache
 
 You can search for packages by typing
 / followed by the initial characters of the package name - it searches as you 
 type.  There is a more complex search capability given in the help
 
 you can repeat a search by typing \

That only finds package names, doesn't bother searching descriptions.

- -- 
 .''`. Paul Johnson [EMAIL PROTECTED]
: :'  :
`. `'` proud Debian admin and user
  `-  Debian - when you have better things to do than fix a system
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFALrn2UzgNqloQMwcRAj9hAJ4oZ+69IDzxGPXc7xf20OTf2maN+wCg5GkT
nuPGMKYqGSkG3TH4dvDXPe0=
=SADf
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: newbie network config

[Alan Chandler]

On Sunday 15 February 2004 00:14, Paul Johnson wrote:


 That only finds package names, doesn't bother searching descriptions.

/~d

will find the next package with  in the description

\ will move to the next occurance



-- 
Alan Chandler
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: newbie network config

[Paul Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sun, Feb 15, 2004 at 01:21:53AM +, Alan Chandler wrote:
 On Sunday 15 February 2004 00:14, Paul Johnson wrote:
 
 
  That only finds package names, doesn't bother searching descriptions.
 
 /~d
 
 will find the next package with  in the description
 
 \ will move to the next occurance

Ah. OK.  Is all this listed someplace and I somehow overlooked it?

- -- 
 .''`. Paul Johnson [EMAIL PROTECTED]
: :'  :
`. `'` proud Debian admin and user
  `-  Debian - when you have better things to do than fix a system
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFALstWUzgNqloQMwcRApN/AKCDGMqYUQTU4NLg72pXTXA55nXUMgCgwJ/t
ZmnufuGt2NZfQVaLdcTSFsc=
=Axdd
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: newbie network config

[Marty Landman]

At 10:44 PM 2/12/2004, Jacob S. wrote:

Older 3coms are probably the easiest to recognize and install, of all the 
network cards I've known.
Ironic; with MS products I'm finding just the opposite i.e. older stuff is 
deprecated. This very same nic model is installed on my wife's w98 
workstation and I made it a dual boot system when installing an eval copy 
of Win 2003 server, but the darned thing won't recognize the nic so I'm now 
thinking of when to schedule a format/repartition/reinstall of W98 on it. 
It was getting cluttered up anyway. :)

Assuming it's a PCI card, try lspci and look for a Network/Ethernet 
controller ... [snip] ... also try a google search on the model of your card
Worked like a charm Jacob. I googled the LNE100TX that Debian said was 
installed; that got me to linksys' support page which under Linux said for 
RH to use the Tulip driver; so I went back and configured that driver and 
now I'm ssh'd into the box from my workstation.

I'm afraid I'm not familiar enough with Netgear cards to tell you which 
driver you need.
Well I'm not familiar enough with Unix to generalize for Debian... all I've 
got so far is the install manual and it doesn't seem enough. What else do 
you recommend and where can I d/l it from?

In particular - how do I get debian [woody] to know that the hosts and dns 
info is on 192.168.0.1 on my lan, and also where do I enable sftp? Oh, and 
since I installed from the mini-iso I've probably got next to nothing on my 
cd, so does debian use rpm's like redhat, packages like fbsd, or something 
else? I'm wanting to install apache1.3, php, mysql, mod_perl... all the 
usual suspects.

Cool homepage btw Jacob, my wife's family live in Houston I bet they'd get 
a kick out of it.

Marty Landman   Face 2 Interface Inc 845-679-9387
This Month's New Quiz --- Past Superbowl Winners
Make a Website: http://face2interface.com/Home/Demo.shtml
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: newbie network config

[Marty Landman]

At 06:10 PM 2/13/2004, Marty Landman wrote:

What else do you recommend and where can I d/l it from?
Nevermind, I found the doc page :)

Will post back with any details I can't figure out.

Marty Landman   Face 2 Interface Inc 845-679-9387
This Month's New Quiz --- Past Superbowl Winners
Make a Website: http://face2interface.com/Home/Demo.shtml
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: newbie network config

[Jacob S.]

On Fri, 13 Feb 2004 18:10:14 -0500
Marty Landman [EMAIL PROTECTED] wrote:

 At 10:44 PM 2/12/2004, Jacob S. wrote:
 
 Older 3coms are probably the easiest to recognize and install, of all
 the network cards I've known.
 
 Ironic; with MS products I'm finding just the opposite i.e. older
 stuff is deprecated. 
snip

:-) Welcome to the wonderful world of Linux. Now you know one of the
reasons it's so much fun to use old 486 machines for firewalls, routers,
dns, e-mail, web, etc.

 Assuming it's a PCI card, try lspci and look for a Network/Ethernet
 
 controller ... [snip] ... also try a google search on the model of
 your card
 
 Worked like a charm Jacob. I googled the LNE100TX that Debian said was
 
 installed; that got me to linksys' support page which under Linux said
 for RH to use the Tulip driver; so I went back and configured that
 driver and now I'm ssh'd into the box from my workstation.

Good! I thought for sure you had said it was a Netgear card... I've had
several Linksys LNE100TX cards, so I would've suggested trying the tulip
driver before you had to do too much searching. Sounds like you managed
and learned a little bit more about Debian in the process though.

snip

On Fri, 13 Feb 2004 19:00:44 -0500
Marty Landman [EMAIL PROTECTED] wrote:
 ...I found the doc page :)

 Will post back with any details I can't figure out.

Enjoy your new Debian machine! Oh, and if you have a decent 'net
connection, use apt-get from your nearest mirror to download the extra
packages you want... much easier than downloading/burning ISOs. 

Jacob

- 
GnuPG Key: 1024D/16377135

Random .signature #5:
Linux. Where do you want to go tomorrow? 


pgp0.pgp
Description: PGP signature

Re: newbie network config

[Jacob S.]

On Fri, 13 Feb 2004 21:32:12 -0500
Marty Landman [EMAIL PROTECTED] wrote:

 At 09:12 PM 2/13/2004, Jacob S. wrote:
 
 I thought for sure you had said it was a Netgear card...
 
 'Tis... fa310tx to be exact. Apparently it works with the tulip driver
 just fine, got 'top' running on an ssh session as I write this --
 watching my new debian box do essentially nothing at the moment. :)

Ah, ok. My guess would have been natsemi, for a Netgear card. 

 if you have a decent 'net connection, use apt-get from your nearest
 mirror to download the extra packages you want... much easier than 
 downloading/burning ISOs.
 
 So apt is what we use in debian; cool. Now all I need is to establish
 name recognition.

Well, it's actually just one of the tools. Apt-get is a front-end for
the dpkg package management system. If you want the Debian equivalent of
rpm-qa, use dpkg(-l). If you want something to hold your hand a little
more than apt-get, try aptitude (or so I'm told... I learned apt-get and
never felt like changing. Apt-get by itself is years beyond what rpm
was, when I played around with it.) There's also dselect, but it's
usually only referred to in nightmares... :-)

All the tools get their list of available packages for installation from
/etc/apt/sources.list. 

HTH,
Jacob

- 
GnuPG Key: 1024D/16377135

Random .signature #2:
Microsoft gives you Windows... Linux gives you the whole house. 


pgp0.pgp
Description: PGP signature

newbie network config

[Marty Landman]

I've just installed Woody from the mini-iso on a PI-166/32M ram/6GB ide 
with a netgear FS310TX nic installed. The light from the cable on my lan 
switch is lit but I couldn't find the nic on the config list, and attempting

ifconfig eth0 192.168.0.3 netmask 255.255.255.0 up

fails with 'no such device'.

How can I go about connecting this box to my lan?

Marty Landman   Face 2 Interface Inc 845-679-9387
This Month's New Quiz --- Past Superbowl Winners
Make a Website: http://face2interface.com/Home/Demo.shtml
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: newbie network config

[Jacob S.]

On Thu, 12 Feb 2004 21:25:17 -0500
Marty Landman [EMAIL PROTECTED] wrote:

 I've just installed Woody from the mini-iso on a PI-166/32M ram/6GB
 ide with a netgear FS310TX nic installed. The light from the cable on
 my lan switch is lit but I couldn't find the nic on the config list,
 and attempting
 
 ifconfig eth0 192.168.0.3 netmask 255.255.255.0 up
 
 fails with 'no such device'.
 
 How can I go about connecting this box to my lan?

First, check to make sure you have the kernel module for your NIC
installed. lsmod will show you all the kernel modules currently
loaded. You might also check dmesg for any output concerning your
network card. 

If, for some reason, the appropriate kernel module is installed but
dmesg doesn't say anything about which device it is, try an ifconfig
-a to see what network devices your system sees out there.

HTH,
Jacob

- 
GnuPG Key: 1024D/16377135

Random .signature #38:
Windows NT -- it'll drive you buggy!


pgp0.pgp
Description: PGP signature

Re: newbie network config

[Marty Landman]

At 09:46 PM 2/12/2004, Jacob S. wrote:

First, check to make sure you have the kernel module for your NIC 
installed. lsmod will show you all the kernel modules currently loaded.
lockd / sunrpc / nls_cp437 / pcmcia_core / af_packet / unix

You might also check dmesg for any output concerning your network card.
dmesg|grep eth gives nothing

If, for some reason, the appropriate kernel module is installed but dmesg 
doesn't say anything about which device it is, try an ifconfig -a to see 
what network devices your system sees out there.
Just shows localhost at lo

Funny thing, I've installed fbsd and rh9 on two machines on my lan and they 
both found the nics. I find it ironic because they both older, 3com nics 
while this box has a relatively newer netgear in it. Anyway, what can I do 
from here?

Thanks Jacob.

Marty Landman   Face 2 Interface Inc 845-679-9387
This Month's New Quiz --- Past Superbowl Winners
Make a Website: http://face2interface.com/Home/Demo.shtml
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: newbie network config

[Jacob S.]

On Thu, 12 Feb 2004 22:16:22 -0500
Marty Landman [EMAIL PROTECTED] wrote:

 At 09:46 PM 2/12/2004, Jacob S. wrote:
 
 First, check to make sure you have the kernel module for your NIC 
 installed. lsmod will show you all the kernel modules currently
 loaded.
 
 lockd / sunrpc / nls_cp437 / pcmcia_core / af_packet / unix

Ok, so there's obviously not any network card modules loaded (though
that by itself wouldn't rule out a driver being compiled into the
kernel, instead of as a module).

 You might also check dmesg for any output concerning your network
 card.
 
 dmesg|grep eth gives nothing

Ok, so 2 out of 2 are now indicating no network card recognized.
 
 If, for some reason, the appropriate kernel module is installed but
 dmesg doesn't say anything about which device it is, try an ifconfig
 -a to see what network devices your system sees out there.
 
 Just shows localhost at lo

Now 3 out of 3. Pretty safe to say nothing is recognizing the network
card yet.

 Funny thing, I've installed fbsd and rh9 on two machines on my lan and
 they both found the nics. I find it ironic because they both older,
 3com nics while this box has a relatively newer netgear in it. Anyway,
 what can I do from here?

Older 3coms are probably the easiest to recognize and install, of all
the network cards I've known. Being newer can narrow the Netgear's
chance of being recognized, depending on the chipset it uses.

Assuming it's a PCI card, try lspci and look for a Network/Ethernet
controller in it's lines of output. This should help you determine the
chipset and find which driver it needs. You might also try a google
search on the model of your card and see if you can find any tips/hints
and drivers that other Linux users are using for your card. I'm afraid
I'm not familiar enough with Netgear cards to tell you which driver you
need. 

At the least, you'll probably need to compile a module for your kernel,
but you may need to compile a new kernel as well.

 Thanks Jacob.

Any time. :-)

HTH,
Jacob

- 
GnuPG Key: 1024D/16377135

Random .signature #56:
Windows hasn't increased computer literacy. It's just lowered the
standard. 


pgp0.pgp
Description: PGP signature

Re: Debian Newbie Question on Network Config

[Alberto Tobias]

- Original Message - 
From: Joyce, Matthew [EMAIL PROTECTED]
To: 'Alberto Tobias' [EMAIL PROTECTED]; Debian-User
[EMAIL PROTECTED]
Sent: Tuesday, October 28, 2003 10:36 PM
Subject: RE: Debian Newbie Question on Network Config


 /etc/network/interfaces

 or, alternatively you can install etherconf.

 'apt-get install etherconf'

 this will lead you through a prompted setup.


 Matt


Thanks for the tip!

However, it does noet appear to solve my issue. After reboot I still need to
manually bring up the eth0 interface and configure it.

An ifconfig -a only shows the loopback interface. After I do a modprobe
tulip the eth0 interface appears as well and I only neede to assign it its
IP address and gateway and everything works again. What can I do to make
this automatic at boot time? Where can I find the error messages (if any)
the system geenrates while booting when it fails to bring up the interface?
I cannot see anything in /var/log/dmesg

Thanks in advance,
Alberto




 --

 -Original Message-
 From: Alberto Tobias [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, 29 October 2003 8:36 AM
 To: [EMAIL PROTECTED]
 Subject: Debian Newbie Question on Network Config


 Hi,

 I relatively new to LInux. The last couple of months I have been dabbling
 with some distributions, but right now I am staying with Debian.

 I have however one question. I have troubles with my network card. I can
get
 it up and running ok, using the tulip drivers from scyld.org. I can
 configure it, add the default routes etc etc. But I have to do this
 everytime I boot the system, because I don't know where to add the
 configuration so it is set up right when it boots.

 Where do I do this? Which startup scripts do I need to change?

 Thanks in advance,
 Alberto

 [EMAIL PROTECTED]





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Debian Newbie Question on Network Config

[Kent West]

Alberto Tobias wrote:

/etc/network/interfaces

or, alternatively you can install etherconf.

'apt-get install etherconf'

this will lead you through a prompted setup.

Matt
   



Thanks for the tip!

However, it does noet appear to solve my issue. After reboot I still need to
manually bring up the eth0 interface and configure it.
An ifconfig -a only shows the loopback interface. After I do a modprobe
tulip the eth0 interface appears as well and I only neede to assign it its
IP address and gateway and everything works again. What can I do to make
this automatic at boot time? Where can I find the error messages (if any)
the system geenrates while booting when it fails to bring up the interface?
I cannot see anything in /var/log/dmesg
Thanks in advance,
Alberto
 

Add the module tulip to /etc/modules, like this:

# /etc/modules: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line.  Comments begin with
# a #, and everything on the line after them are ignored.
tulip
via82cxxx_audio
visor


and edit /etc/network/interfaces, something like this:

# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)

# The loopback interface
# automatically added when upgrading
auto lo
iface lo inet loopback
# The first network card - this entry was created during the Debian 
installation
# (network, broadcast and gateway are optional)
# automatically added when upgrading
auto eth0
#iface eth0 inet static
#   address 192.168.123.2
#   netmask 255.255.255.0
#   network 192.168.123.0
#   broadcast 192.168.123.255
#   gateway 192.168.123.1

iface eth0 inet dhcp




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Debian Newbie Question on Network Config

[Alberto Tobias]

Hi,

I relatively new to LInux. The last couple of 
months I have been dabbling with some distributions, but right now I am staying 
with Debian.

I have however one question. I have troubles with 
my network card. I can get it up and running ok, using the tulip drivers from 
scyld.org. I can configure it, add the default routes etc etc. But I have to do 
this everytime I boot the system, because I don't know where to add the 
configuration so it is set up right when it boots.

Where do I do this? Which startup scripts do I need 
to change?

Thanks in advance,
Alberto

[EMAIL PROTECTED]

RE: Debian Newbie Question on Network Config

[Joyce, Matthew]

/etc/network/interfaces

or, alternatively you can install etherconf.

'apt-get install etherconf'

this will lead you through a prompted setup.


Matt


--

-Original Message-
From: Alberto Tobias [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, 29 October 2003 8:36 AM
To: [EMAIL PROTECTED]
Subject: Debian Newbie Question on Network Config


Hi,

I relatively new to LInux. The last couple of months I have been dabbling
with some distributions, but right now I am staying with Debian.

I have however one question. I have troubles with my network card. I can get
it up and running ok, using the tulip drivers from scyld.org. I can
configure it, add the default routes etc etc. But I have to do this
everytime I boot the system, because I don't know where to add the
configuration so it is set up right when it boots.

Where do I do this? Which startup scripts do I need to change?

Thanks in advance,
Alberto

[EMAIL PROTECTED]



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Debian Newbie Question on Network Config

[David Z Maze]

Alberto Tobias [EMAIL PROTECTED] writes:

 1.  (*) text/plain  ( ) text/html   

ObFormatting: please set your mailer to send plain text only, and wrap
lines at 72 characters.

 I have however one question. I have troubles with my network card. I
 can get it up and running ok, using the tulip drivers from
 scyld.org. I can configure it, add the default routes etc etc. But I
 have to do this everytime I boot the system, because I don't know
 where to add the configuration so it is set up right when it boots.

 Where do I do this? Which startup scripts do I need to change?

Edit /etc/network/interfaces.  There's a man page (interfaces(5)), and
a sample file in /usr/share/doc/ifupdown/examples/network-interfaces.gz.

-- 
David Maze [EMAIL PROTECTED]  http://people.debian.org/~dmaze/
Theoretical politics is interesting.  Politicking should be illegal.
-- Abra Mitchell


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: network config kernel 2.4.20

[steve downes]

On Wed, 2003-06-04 at 23:35, Frank Gevaerts wrote:
 On Wed, Jun 04, 2003 at 11:10:37PM +0100, steve downes wrote:
  On Wed, 2003-06-04 at 15:40, Kevin McKinley wrote:
   On 04 Jun 2003 14:30:50 +0100
   steve downes [EMAIL PROTECTED] wrote:
   
Anyone know how to get the kernel to see the right irq  io for a 3c509b
card with the above kernel. Windows, 2.2 kernel  ltsp all get it right
2.4 gets something completely different

Steve
   
   You can specify the IRQ and IO as options when the module is installed.
   
   Go here to see how:
   
   http://www.scyld.com/network/3c509.html
   
   I found that by googling on scyld 3c509 IRQ and following the first link.
   
   Kevin
  
  No. tried evry incantation I can think of in Lilo  read all the website
   compiled the test program. The card is where everything else says it
  is io (0x300 irq 10) nothing in lilo will make linux 2.4.20 look
  anywhere but io 0x220 irq 5. 
 
 If the driver is compiled in the kernel, it should be found
 automatically. If it is a module, lilo is not the place to specify
 parameters.
 
 What does lsmod say ?
 
 Frank

lsmod says :-

3c509 10420 1

Which I assume is all you need ie it is loading as a module. Sorry if
I'm sounding thick (getting used to it now) but where should I be
specifying parameters. I can't find anywhere. It is loading the module
but witht the wrong (or presumably default? parameters)

Steve


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: network config kernel 2.4.20

[steve downes]

On Thu, 2003-06-05 at 08:20, steve downes wrote:
 On Wed, 2003-06-04 at 23:35, Frank Gevaerts wrote:
  On Wed, Jun 04, 2003 at 11:10:37PM +0100, steve downes wrote:
   On Wed, 2003-06-04 at 15:40, Kevin McKinley wrote:
On 04 Jun 2003 14:30:50 +0100
steve downes [EMAIL PROTECTED] wrote:

 Anyone know how to get the kernel to see the right irq  io for a 3c509b
 card with the above kernel. Windows, 2.2 kernel  ltsp all get it right
 2.4 gets something completely different
 
 Steve

You can specify the IRQ and IO as options when the module is installed.

Go here to see how:

http://www.scyld.com/network/3c509.html

I found that by googling on scyld 3c509 IRQ and following the first link.

Kevin
   
   No. tried evry incantation I can think of in Lilo  read all the website
compiled the test program. The card is where everything else says it
   is io (0x300 irq 10) nothing in lilo will make linux 2.4.20 look
   anywhere but io 0x220 irq 5. 
  
  If the driver is compiled in the kernel, it should be found
  automatically. If it is a module, lilo is not the place to specify
  parameters.
  
  What does lsmod say ?
  
  Frank
 
 lsmod says :-
 
 3c509 10420 1
 
 Which I assume is all you need ie it is loading as a module. Sorry if
 I'm sounding thick (getting used to it now) but where should I be
 specifying parameters. I can't find anywhere. It is loading the module
 but witht the wrong (or presumably default? parameters)
 
 Steve

Having researched abit further I have sort of got it working. Many
thanks Frank for the above pointer.

Steve


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

network config kernel 2.4.20

[steve downes]

Anyone know how to get the kernel to see the right irq  io for a 3c509b
card with the above kernel. Windows, 2.2 kernel  ltsp all get it right
2.4 gets something completely different

Steve


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: network config kernel 2.4.20

[Kevin McKinley]

On 04 Jun 2003 14:30:50 +0100
steve downes [EMAIL PROTECTED] wrote:

 Anyone know how to get the kernel to see the right irq  io for a 3c509b
 card with the above kernel. Windows, 2.2 kernel  ltsp all get it right
 2.4 gets something completely different
 
 Steve

You can specify the IRQ and IO as options when the module is installed.

Go here to see how:

http://www.scyld.com/network/3c509.html

I found that by googling on scyld 3c509 IRQ and following the first link.

Kevin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: network config kernel 2.4.20

[steve downes]

On Wed, 2003-06-04 at 15:40, Kevin McKinley wrote:
 On 04 Jun 2003 14:30:50 +0100
 steve downes [EMAIL PROTECTED] wrote:
 
  Anyone know how to get the kernel to see the right irq  io for a 3c509b
  card with the above kernel. Windows, 2.2 kernel  ltsp all get it right
  2.4 gets something completely different
  
  Steve
 
 You can specify the IRQ and IO as options when the module is installed.
 
 Go here to see how:
 
 http://www.scyld.com/network/3c509.html
 
 I found that by googling on scyld 3c509 IRQ and following the first link.
 
 Kevin

No. tried evry incantation I can think of in Lilo  read all the website
 compiled the test program. The card is where everything else says it
is io (0x300 irq 10) nothing in lilo will make linux 2.4.20 look
anywhere but io 0x220 irq 5. 

Feel an attach f flying pc coming on

Steve


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: network config kernel 2.4.20

[Frank Gevaerts]

On Wed, Jun 04, 2003 at 11:10:37PM +0100, steve downes wrote:
 On Wed, 2003-06-04 at 15:40, Kevin McKinley wrote:
  On 04 Jun 2003 14:30:50 +0100
  steve downes [EMAIL PROTECTED] wrote:
  
   Anyone know how to get the kernel to see the right irq  io for a 3c509b
   card with the above kernel. Windows, 2.2 kernel  ltsp all get it right
   2.4 gets something completely different
   
   Steve
  
  You can specify the IRQ and IO as options when the module is installed.
  
  Go here to see how:
  
  http://www.scyld.com/network/3c509.html
  
  I found that by googling on scyld 3c509 IRQ and following the first link.
  
  Kevin
 
 No. tried evry incantation I can think of in Lilo  read all the website
  compiled the test program. The card is where everything else says it
 is io (0x300 irq 10) nothing in lilo will make linux 2.4.20 look
 anywhere but io 0x220 irq 5. 

If the driver is compiled in the kernel, it should be found
automatically. If it is a module, lilo is not the place to specify
parameters.

What does lsmod say ?

Frank


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: network config kernel 2.4.20

[Kenward Vaughan]

On Wed, Jun 04, 2003 at 11:10:37PM +0100, steve downes wrote:
 On Wed, 2003-06-04 at 15:40, Kevin McKinley wrote:
  On 04 Jun 2003 14:30:50 +0100
  steve downes [EMAIL PROTECTED] wrote:
  
   Anyone know how to get the kernel to see the right irq  io for a 3c509b
   card with the above kernel. Windows, 2.2 kernel  ltsp all get it right
   2.4 gets something completely different
   
   Steve
  
  You can specify the IRQ and IO as options when the module is installed.
  
  Go here to see how:
  
  http://www.scyld.com/network/3c509.html
  
  I found that by googling on scyld 3c509 IRQ and following the first link.
  
  Kevin
 
 No. tried evry incantation I can think of in Lilo  read all the website
  compiled the test program. The card is where everything else says it
 is io (0x300 irq 10) nothing in lilo will make linux 2.4.20 look
 anywhere but io 0x220 irq 5. 

I don't recall the early post on this, and whether you said other Linux
dists see the card or not, but I know on one of my machines (admittedly a
bit old... 486 vintage) works properly only when I disable the comm ports
and the parallel port in BIOS.  Linux still finds what it needs (esp. cards
plugged into the board).  My Realtek doesn't show up otherwise.

Have no idea what would have happened to Windoze under those circumstances,
but then again, Descent was a DOS game off the SB card.  ;-)


Kenward
-- 
In a completely rational society, the best of us would aspire to be 
_teachers_ and the rest of us would have to settle for something less, 
because passing civilization along from one generation to the next 
ought to be the highest honor and the highest responsibility anyone 
could have. - Lee Iacocca


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Network config help needed

[chris1622]

Yep, read Net-HOWTO, but still I can't get it to work. ...

Setting up the loopback and pingin it works fine, pinging into the 
machine also works fine (tried from an old win95 machine). But 
pinging out of the machine dosn't work, I'm getting the error message 
Unable to connect to remote host: No route to host when telnetting.

Is ifconfig eth0 192.168.0.1 netmask 255.255.255.0 up enough to 
set up the network, I don't have to edit /etc/hosts or something 
else?

On 2 Mar 2003, at 10:05, praveen kallakuri wrote:

 -BEGIN PGP SIGNED MESSAGE-
 
 you dont have a lo in ur route: loopback interface.
 
 check whether you can ping to yourself (lo) 127.0.0.1 on each pc.
 then configure pc1 as 192.168.0.1. repeat the two steps with pc2,
 only changing the ip address.
 
 the initial sections of Net-HOWTO must help.
 
 solong
 
 [EMAIL PROTECTED] wrote:
  
   Please help me
   I'm trying to connect two pc's, but I allways get the message
   unable to  connect to remote host: No route to host. What am I
   missing?
  
   My config for pc1 looks like this:
   ifconfig eth0 192.168.0.1 netmask 255.255.255.0 up
   rout add -host 192.168.0.2 eth0
  
   route -n output:
   192.168.0.2  0.0.0.0  255.255.255.255  UH  0  0  0  eth0
   192.168.0.0  0.0.0.0  255.255.255.0UH  0  0  0  eth0
  
   /etc/hosts
   domain home
   search home
   nameserver 10.0.0.1
   nameserver 10.0.0.2
  
  
 
 
 -BEGIN PGP SIGNATURE-
 Version: PGPfreeware 6.5.8 for non-commercial use http://www.pgp.com
 
 iQB1AwUBPmIrugSOhI6OETvlAQGXogMAxNdOci2Hq7P+oAsQgg2GF6Gdj6xKVwU4
 h7H9RNO+mOx7EG0ZllbKI40UY71th2+aUeQJnsOdOlGhC5s4MBMPnCFGaWQBvXIw
 8yZE0HdNJiuL39IZilLYW60WBrWWTQpv
 =EQvk
 -END PGP SIGNATURE-
 
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

RE: Network config help needed

[deFreese, Barry]

Barry deFreese
NTS Technology Services Manager
Nike Team Sports
 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, March 05, 2003 1:16 PM
 To: [EMAIL PROTECTED]
 Subject: Re: Network config help needed
 
 
 
 Yep, read Net-HOWTO, but still I can't get it to work. ...
 
 Setting up the loopback and pingin it works fine, pinging into the 
 machine also works fine (tried from an old win95 machine). But 
 pinging out of the machine dosn't work, I'm getting the error message 
 Unable to connect to remote host: No route to host when telnetting.
 
 Is ifconfig eth0 192.168.0.1 netmask 255.255.255.0 up enough to 
 set up the network, I don't have to edit /etc/hosts or something 
 else?
 

Chris,

Your /etc/network/interfaces should look like so:

iface eth0 inet static
address 192.168.0.1
netmask 255.255.255.0
network 192.168.0.0
broadcast   192.168.0.255
gateway 192.168.0.?? -- Whatever your default router/gateway
address is.

Actually the gateway shouldn't matter since the other host is on the same
subnet.  Again, you need to verify that the subnet mask for both hosts are
the same.

Barry deFreese
NTS Technology Services Manager
Nike Team Sports
(949)-616-4005
[EMAIL PROTECTED]

Technology doesn't make you less stupid; it just makes you stupid faster.
Jerry Gregoire - Former CIO at Dell



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Network config help needed

[Patrick Wiseman]

On Wed, 5 Mar 2003 at 9:00pm, [EMAIL PROTECTED] wrote:

:Setting up the loopback and pingin it works fine, pinging into the 
:machine also works fine (tried from an old win95 machine). But 
:pinging out of the machine dosn't work, I'm getting the error message 
:Unable to connect to remote host: No route to host when telnetting.

Does route -n show a gateway?  It should show something like:

Kernel IP routing table
Destination  Gateway  Genmask  Flags Metric RefUse Iface
192.168.1.0  0.0.0.0  255.255.255.0   U 00  0  eth1
0.0.0.0  192.168.1.1  0.0.0.0 UG00  0  eth1

If it shows something like

Destination  Gateway  Genmask  Flags Metric RefUse Iface
192.168.1.0 * 255.255.255.0   U 00  0  eth1

then you don't have a default gateway set up.  Do route add default gw
192.168.1.1 substituting the correct IP address for your gateway of
course.  Edit /etc/interfaces (as directed at man interfaces) to have it
work on boot.

Patrick

-- 
Patrick Wiseman   [EMAIL PROTECTED]
Linux user #17943 *Google First, Ask Later*



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Network config help needed

[praveen kallakuri]

-BEGIN PGP SIGNED MESSAGE-

you dont have a lo in ur route: loopback interface.

check whether you can ping to yourself (lo) 127.0.0.1 on each pc.
then configure pc1 as 192.168.0.1. repeat the two steps with pc2,
only changing the ip address.
the initial sections of Net-HOWTO must help.

solong

[EMAIL PROTECTED] wrote:

 Please help me
 I'm trying to connect two pc's, but I allways get the message
 unable to  connect to remote host: No route to host. What am I
 missing?

 My config for pc1 looks like this:
 ifconfig eth0 192.168.0.1 netmask 255.255.255.0 up
 rout add -host 192.168.0.2 eth0

 route -n output:
 192.168.0.2  0.0.0.0  255.255.255.255  UH  0  0  0  eth0
 192.168.0.0  0.0.0.0  255.255.255.0UH  0  0  0  eth0

 /etc/hosts
 domain home
 search home
 nameserver 10.0.0.1
 nameserver 10.0.0.2


-BEGIN PGP SIGNATURE-
Version: PGPfreeware 6.5.8 for non-commercial use http://www.pgp.com
iQB1AwUBPmIrugSOhI6OETvlAQGXogMAxNdOci2Hq7P+oAsQgg2GF6Gdj6xKVwU4
h7H9RNO+mOx7EG0ZllbKI40UY71th2+aUeQJnsOdOlGhC5s4MBMPnCFGaWQBvXIw
8yZE0HdNJiuL39IZilLYW60WBrWWTQpv
=EQvk
-END PGP SIGNATURE-


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Network config help needed

[Wilfried Essig]

Am Son, 2003-03-02 um 13.15 schrieb [EMAIL PROTECTED]:
 Please help me
 I'm trying to connect two pc's, but I allways get the message 
 unable to  connect to remote host: No route to host. What am I 
 missing?
 
 My config for pc1 looks like this:
 ifconfig eth0 192.168.0.1 netmask 255.255.255.0 up
 rout add -host 192.168.0.2 eth0

You don't need this special route to host .2 - it's alraedy fullfilled
with the standard-route to the network. But it should not disturb.

 route -n output:
 192.168.0.2  0.0.0.0  255.255.255.255  UH  0  0  0  eth0
 192.168.0.0  0.0.0.0  255.255.255.0UH  0  0  0  eth0
 
 /etc/hosts
 domainhome
 searchhome
 nameserver 10.0.0.1
 nameserver 10.0.0.2
Where is the route to your nameservers?

-- 
Wilfried Essig [EMAIL PROTECTED]
Familie Essig


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Network config help needed

[Barry deFreese]

[EMAIL PROTECTED] wrote:

Please help me
I'm trying to connect two pc's, but I allways get the message 
unable to  connect to remote host: No route to host. What am I 
missing?

My config for pc1 looks like this:
ifconfig eth0 192.168.0.1 netmask 255.255.255.0 up
rout add -host 192.168.0.2 eth0
route -n output:
192.168.0.2  0.0.0.0  255.255.255.255  UH  0  0  0  eth0
192.168.0.0  0.0.0.0  255.255.255.0UH  0  0  0  eth0
/etc/hosts
domain  home
search  home
nameserver 10.0.0.1
nameserver 10.0.0.2
 

You shouldn't need a route for the other host.  Because they are on the 
same subnet, broadcasts should see that machine.  Remove the route for 
192.168.0.2 and try it again.  If you still can't see it, I would guess 
that you have a subnet mask problem on one of the two machines.



--
Barry deFreese
Debian 3.0r1 Woody
Registered Linux Newbie #302256 - Debian Developer Wannabe
Programming today is a race between software engineers striving
to build bigger and better idiot-proof programs, and the Universe
trying to produce bigger and better idiots. So far, the Universe is
winning. Rich Cook.




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Network config - RPC timeout - what have I missed?

[Pigeon]

Hi,

I am setting up box pigeon as an NFS server from which to install
woody on box nestie via ethernet. I am attempting to make
/scsidrive/woody[1..7] available for export. Box nestie isn't up at
all yet, so I'm trying to test it by mounting the exported filesystem
locally.

I intend for pigeon to be 192.168.1.1, nestie to be 192.168.1.2. I can
ping both 127.0.0.1 and 192.168.1.0. If I try

mount 127.0.0.1:/scsidrive/woody1 /mnt -t nfs

it works, but if I try

mount 192.168.1.1:/scsidrive/woody1 /mnt -t nfs

I get mount: RPC: Timed out. By messing with the permissions in
/etc/exports or removing my entries in /etc/hosts.allow and
/etc/hosts.deny, I can change this to a permission denied by server
error. So some of it's working...

I must have missed something, any ideas what? I have set up the
following: (see below)

TIA,
Pigeon

#/etc/networks
loopnet 127.0.0.0
pigeonloft 192.168.1.0

#/etc/init.d/network
#! /bin/sh
ifconfig lo 127.0.0.1
route add -net 127.0.0.0
ifconfig eth0 192.168.1.1 netmask 255.255.255.0 up
route add -net 192.168.1.0 netmask 255.255.255.0 eth0

# /etc/exports: the access control list for filesystems which may be exported
#   to NFS clients.  See exports(5).
# this is for testing...
/scsidrive/woody1   pigeon(insecure)
# these (plus woody1) are what I intend to export when it's working
/scsidrive/woody2   nestie(ro)
/scsidrive/woody3   nestie(ro)
/scsidrive/woody4   nestie(ro)
/scsidrive/woody5   nestie(ro)
/scsidrive/woody6   nestie(ro)
/scsidrive/woody7   nestie(ro)

#/etc/hosts
127.0.0.1   pigeon  localhost
192.168.1.1 pigeon

# /etc/hosts.allow: list of hosts that are allowed to access the system.
#   See the manual pages hosts_access(5), hosts_options(5)
#   and /usr/doc/netbase/portmapper.txt.gz
#
# Example:ALL: LOCAL @some_netgroup
# ALL: .foobar.edu EXCEPT terminalserver.foobar.edu
#
# If you're going to protect the portmapper use the name portmap for the
# daemon name. Remember that you can only use the keyword ALL and IP
# addresses (NOT host or domain names) for the portmapper. See portmap(8)
# and /usr/doc/netbase/portmapper.txt.gz for further information.
#
rpc.mountd : 192.168.1

# /etc/hosts.deny: list of hosts that are _not_ allowed to access the system.
#  See the manual pages hosts_access(5), hosts_options(5)
#  and /usr/doc/netbase/portmapper.txt.gz
#
# Example:ALL: some.host.name, .some.domain
# ALL EXCEPT in.fingerd: other.host.name, .other.domain
#
# If you're going to protect the portmapper use the name portmap for the
# daemon name. Remember that you can only use the keyword ALL and IP
# addresses (NOT host or domain names) for the portmapper. See portmap(8)
# and /usr/doc/netbase/portmapper.txt.gz for further information.
#
# The PARANOID wildcard matches any host whose name does not match its
# address.
#ALL: PARANOID
rpc.mountd : ALL

# /etc/services:
# snip standard slink entries
# Local services
# Does This Help? test, using info from rpcinfo -p
# (doesn't seem to make any difference)
nfs 2049/tcp
nfs 2049/udp
mountd   938/udp
mountd   941/tcp


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: changed network config

[Jeff]

Yang Shouxun, 2002-Mar-19 13:48 +0800:
 Dear Debian Users,
 
 I'm using Debian GNU/Linux unstable. Recently I move to a new place and 
 the ethernet configuration changed as a result. I manually edited all 
 the files.
 
 It works fine except that each time when pcmcia service starts, the IP 
 address, network mask and other things are of the old version. I have to 
 restart the networking service by /etc/init.d/networking restart and 
 then eth0 uses the new configuration.
 
 Does anybody know what I miss so that I can put it right, save me from 
 manually restarting networking service each time I reboot and want to 
 connect to the network?

If you mean that you have static IP configurations for each
network you work on, schemes will help here.  In the
/etc/pcmcia/network.opts file, you can set different
configurations and name them.  Then, when you go to a different
network, change the scheme with

# cartctl scheme work  (where 'work' is the name of a scheme)

and the config will change.

The section for the schemes will look like:

case $ADDRESS in
auto,*,*,*)
IF_PORT=auto
# Use /sbin/pump for BOOTP/DHCP? [y/n]
DHCP=y
;;
work,*,*,*)
IF_PORT=auto
IPADDR=192.168.0.100
NETMASK=255.255.255.0
NETWORK=192.168.0.0
GATEWAY=192.168.0.1
DOMAIN=
SEARCH=
NAMESERVER=
;;
esac

I'm not positive the last 3 entries above are accurate.

jc

-- 
Jeff CoppockSystems Engineer
Diggin' Debian  Admin and User

Re: changed network config

[Yang Shouxun]

Panuganty, Ramesh wrote:
 What files did you change?
 
 /etc/network/interfaces or
  /etc/pcmcia/network.opts 
 
 Also look at your /etc/modules

Thanks very much to Ramesh, Troy and others responding. I changed
/etc/netowrk/interfaces but /etc/pcmcia/network.opts still has the old
information.

I certainly forgot I did put information there. A good lesson for me to
repeat the same lesson in multiple places and fail to synchronize.

changed network config

[Yang Shouxun]

Dear Debian Users,

I'm using Debian GNU/Linux unstable. Recently I move to a new place and 
the ethernet configuration changed as a result. I manually edited all 
the files.


It works fine except that each time when pcmcia service starts, the IP 
address, network mask and other things are of the old version. I have to 
restart the networking service by /etc/init.d/networking restart and 
then eth0 uses the new configuration.


Does anybody know what I miss so that I can put it right, save me from 
manually restarting networking service each time I reboot and want to 
connect to the network?


TIA!

about network config

[debianlist]

HI: 
 In win2k, I am using DHCP to connect 
internet. In Debian,can I use the information(ip,DNS Server..) get from in win2k 
to manual config network in Debian?

Thanks

Re: about network config

[Stephan Hachinger]

Hi!

Try to change /etc/network/interfaces like this:

# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
# The loopback interface
iface lo inet loopback
# The first network card - this entry was created during the Debian
installation
# (network, broadcast and gateway are optional)
iface eth0 inet dhcp

Also, dhcpcd or pump must be installed. Maybe you will have to configure
dhcpcd or pump further, but I'm quite sure I just attached my machine to a
friend's network, changed the above file and it worked fine. If anyone has
to add something or if it doesn't work, let me know.

Cheers,

Stephan

- Original Message -
From: debianlist
To: debian-user@lists.debian.org
Sent: Wednesday, February 27, 2002 3:38 PM
Subject: about network config


HI:
  In win2k, I am using DHCP to connect internet. In Debian,can I use the
information
(ip,DNS Server..) get from in win2k to manual config network in Debian?

Thanks

Re: about network config

[Alex Malinovich]

On Wed, 2002-02-27 at 08:38, debianlist wrote:

 In win2k, I am using DHCP to connect internet. In Debian,can I use the 
 information(ip,DNS Server..) get from in win2k to manual config network in 
 Debian?

Assuming you have your DHCP server configured properly, Debian can get
the same info from it that your W2K machine can. Thankfully, DHCP isn't
(yet... :) a proprietary M$ protocol. (Though I'm sure they're working
on it...) Just make sure you've got pump installed and you should be all
set.

-Alex 



signature.asc
Description: This is a digitally signed message part

Re: [SOLVED] Re: Network config problem

[Daniel Toffetti]

On Monday 10 December 2001 19:39, Mark Ferlatte wrote:
  Reading again /etc/init.d/dhcp I see the following:
 
  # Add all interfaces you want dhcpd to handle here

 Change the lines in /etc/init.d/dhcp that look like

 start-stop-daemon --start --quiet --pidfile $DHCPDPID
 \ --exec /usr/sbin/dhcpd

 to

 start-stop-daemon --start --quiet --pidfile $DHCPDPID
 \ --exec /usr/sbin/dhcpd -- eth0 eth1

That solved my problem, now everything works as I expected.

Thanks Michael and Mark !

Daniel
-- 
There is no spoon... - The Matrix

[PART-SOLVED] Re: Network config problem

[Daniel Toffetti]

On Sunday 09 December 2001 16:24, Michael Heldebrant wrote:
  It's strange to me that 'pump -i eth1 --status' shows correctly the
  gateway (10.7.2.1), nameservers, etc. So I tried to add the two
  missing entries, and it failed.
 
  root: route add default gw 10.7.2.1 dev eth1
  SIOCADDRT: Network is unreachable
 
  and:
 
  root: route add 10.7.2.1 netmask 255.255.255.255 dev eth1
  dboostrap_settings: Unknown host
 
  I guess perhaps the initialization scripts also tried to set up the
  correct routing entries and failed.

 Firstly, are you supposed to be sending pump as your hostname to
 request to your dhcp server?  hostname pump in your eth1 stanza does
 exactly that.

Yes, this is the way the hosts in my internal network were configured, 
and the proxy (with the old distro I used) assigned them properly 
internal IPs of the 192.168.0.0 subnet.

 then adding the default gateway?  If pump continually doesn't work
 I'd consider trying dhclient.  Pump always screwed up on my multiple
 iface machine.  It would never rebind for me.  Dhclient is much nicer
 in that respect.

I replaced pump for dhclient, and it worked smoothly. Now the routing 
table in the proxy looks exactly like the one of the old distro I used 
before, I can ping outside and (almost) everything seems to work OK.

But now (and this is why I say PART-SOLVED) the internal hosts are not 
assigned a valid internal IP from the proxy via pump. I even copied the 
file dhcpd.conf from my old proxy to the new, tried changing from pump 
to dhcpcd in the internal hosts, to no avail...

I'm still trying to understand what is the difference and what has 
changed, so I cannot give better symptoms yet and will post again soon.

Thanks for your help !!

Daniel
-- 
There is no spoon... - The Matrix

Re: [PART-SOLVED] Re: Network config problem

[Daniel Toffetti]

On Monday 10 December 2001 16:23, Daniel Toffetti wrote:
 But now (and this is why I say PART-SOLVED) the internal hosts are
 not assigned a valid internal IP from the proxy via pump. I even
 copied the file dhcpd.conf from my old proxy to the new, tried
 changing from pump to dhcpcd in the internal hosts, to no avail...

 I'm still trying to understand what is the difference and what has
 changed, so I cannot give better symptoms yet and will post again
 soon.

Now I got a clue. I've copied the file dhcpd.conf, but forgot to 
configure /etc/init.d/dhcp to make dhcpd actually start at boottime.

As detailed therein, I've set run_dhcpd = 1 and executed:

root:/etc/init.d/dhcp start

But it fails complaining that I must describe _all_ subnets in 
/etc/dhcpd.conf. But, hey, I don't want dhcpd to serve request coming 
from eth1 !!

Reading again /etc/init.d/dhcp I see the following:

# Add all interfaces you want dhcpd to handle here

My best guess is: since I haven't added interfaces there, the 
script/daemon assumes 'all', and since the subnet correspoding to eth1 
is not described in /etc/dhcpd.conf, it complains it should be.

Am I right ?? I haven't tried adding what interfaces I want dhcpd to 
handle since I don't know what is the proper syntax (there is no 
example in /etc/init.d/dhcp).

Thanks again !!

Daniel
-- 
There is no spoon... - The Matrix

Re: [PART-SOLVED] Re: Network config problem

[Mark Ferlatte]

On Mon, Dec 10, 2001 at 05:46:56PM -0300, Daniel Toffetti wrote (1.00):
 Reading again /etc/init.d/dhcp I see the following:
 
 # Add all interfaces you want dhcpd to handle here

Change the lines in /etc/init.d/dhcp that look like

start-stop-daemon --start --quiet --pidfile $DHCPDPID \
--exec /usr/sbin/dhcpd

to

start-stop-daemon --start --quiet --pidfile $DHCPDPID \
--exec /usr/sbin/dhcpd -- eth0 eth1

where eth0 eth1 are the interfaces you want the daemon to worry about.

M

Re: Network config problem

[Daniel Toffetti]

On Sunday 09 December 2001 02:53, Michael Heldebrant wrote:
 You want:
 auto ethWHATEVER
 iface inet dhcp ethWHATEVER
 instead of static dhcp which, I'm not even sure how it would be
 parsed by ifup.  ifconfig should tell you if your interface iseven
 being brought up.

My fault here, sorry, it is if fact configured that way:

iface eth1 inet dhcp
hostname pump

I read 'static' form the interface eth0 and wrote things down wrong.

 Assuming it's coming up and has an ip address, check your

As far as I can tell from ifconfig's output, it's up and has the 
correct IP, broadcast and netmask.

 /var/dhcp/dhclient.leases file for a routers entry.  If you have no

My system is now Potato 2.2r0 and this file doesn't even exist. Note 
that I'm using pump as dhcp client, I don't know if this is relevant. 
Querying pump for the status of the interface (pump -i eth1 --status) 
shows that eth1 is fully configured. 

 route add default ethWHATEVER

This is a good clue !!  My old one-diskette system has a routing 
table like this:

Destination Gateway NetmaskIface
10.7.2.1   *255.255.255.255eth1
192.168.0.0*255.255.255.0  eth0
200.70.32.0*255.255.255.0  eth1
default10.7.2.1 0.0.0.0eth1

The recently installed Potato system's table has:

Destination Gateway NetmaskIface
localnet   *255.255.255.0  eth0
200.70.32.0*255.255.255.0  eth1

It's strange to me that 'pump -i eth1 --status' shows correctly the 
gateway (10.7.2.1), nameservers, etc. So I tried to add the two missing 
entries, and it failed.

root: route add default gw 10.7.2.1 dev eth1
SIOCADDRT: Network is unreachable

and:

root: route add 10.7.2.1 netmask 255.255.255.255 dev eth1
dboostrap_settings: Unknown host

I guess perhaps the initialization scripts also tried to set up the 
correct routing entries and failed.

Any further suggestions ??

Thanks for your help !!

Daniel
-- 
There is no spoon... - The Matrix

Re: Network config problem

[Michael Heldebrant]

On Sun, 2001-12-09 at 12:50, Daniel Toffetti wrote:
 On Sunday 09 December 2001 02:53, Michael Heldebrant wrote:
  You want:
  auto ethWHATEVER
  iface inet dhcp ethWHATEVER
  instead of static dhcp which, I'm not even sure how it would be
  parsed by ifup.  ifconfig should tell you if your interface iseven
  being brought up.
 
 My fault here, sorry, it is if fact configured that way:
 
 iface eth1 inet dhcp
   hostname pump
 
 I read 'static' form the interface eth0 and wrote things down wrong.
 
  Assuming it's coming up and has an ip address, check your
 
 As far as I can tell from ifconfig's output, it's up and has the 
 correct IP, broadcast and netmask.
 
  /var/dhcp/dhclient.leases file for a routers entry.  If you have no
 
 My system is now Potato 2.2r0 and this file doesn't even exist. Note 
 that I'm using pump as dhcp client, I don't know if this is relevant. 
 Querying pump for the status of the interface (pump -i eth1 --status) 
 shows that eth1 is fully configured. 
 
  route add default ethWHATEVER
 
 This is a good clue !!  My old one-diskette system has a routing 
 table like this:
 
 Destination Gateway NetmaskIface
 10.7.2.1   *255.255.255.255eth1
 192.168.0.0*255.255.255.0  eth0
 200.70.32.0*255.255.255.0  eth1
 default10.7.2.1 0.0.0.0eth1
 
 The recently installed Potato system's table has:
 
 Destination Gateway NetmaskIface
 localnet   *255.255.255.0  eth0
 200.70.32.0*255.255.255.0  eth1
 
 It's strange to me that 'pump -i eth1 --status' shows correctly the 
 gateway (10.7.2.1), nameservers, etc. So I tried to add the two missing 
 entries, and it failed.
 
 root: route add default gw 10.7.2.1 dev eth1
 SIOCADDRT: Network is unreachable
 
 and:
 
 root: route add 10.7.2.1 netmask 255.255.255.255 dev eth1
 dboostrap_settings: Unknown host
 
 I guess perhaps the initialization scripts also tried to set up the 
 correct routing entries and failed.
 
Firstly, are you supposed to be sending pump as your hostname to request
to your dhcp server?  hostname pump in your eth1 stanza does exactly
that.

Have you tried route add -host 10.7.2.1 netmask 255.255.255.255 dev eth1
 ^

then adding the default gateway?  If pump continually doesn't work I'd
consider trying dhclient.  Pump always screwed up on my multiple iface
machine.  It would never rebind for me.  Dhclient is much nicer in that
respect.

--mike

Network config problem

[Daniel Toffetti]

Hi all !

I've a small diskless proxy booting from a floppy based distro called 
Coyote. Now I've got an old HDD and I'm installing Debian Potato, but 
I'm failing to get the access to the Net working.
Right now I get the external interface be assigned the valid IP address 
as before, configuring it as 'static dhcp - hostname pump' in 
/etc/interfaces. But when I try _any_ ping (any but my own address and 
localhost, of course), it fails with a Network is unreachable 
message. It's strange to me that the ping fails, but the names are 
correctly resolved to their respective IPs.
I hope this is a good enough description of my problem. I'm not any 
expert, so it's possible I'm missing something shamely (is this an 
english word ?) obvious, I'm tired of reading many HOWTOs and rebooting 
once and againg without success.

Thanks in advance !!

Daniel
-- 
There is no spoon... - The Matrix

Re: Network config problem

[ben]

On Saturday 08 December 2001 10:41 am, Daniel Toffetti wrote:
 Hi all !

 I've a small diskless proxy booting from a floppy based distro called
 Coyote. Now I've got an old HDD and I'm installing Debian Potato, but
 I'm failing to get the access to the Net working.
 Right now I get the external interface be assigned the valid IP address
 as before, configuring it as 'static dhcp - hostname pump' in
 /etc/interfaces. But when I try _any_ ping (any but my own address and
 localhost, of course), it fails with a Network is unreachable
 message. It's strange to me that the ping fails, but the names are
 correctly resolved to their respective IPs.
 I hope this is a good enough description of my problem. I'm not any
 expert, so it's possible I'm missing something shamely (is this an
 english word ?) obvious, I'm tired of reading many HOWTOs and rebooting
 once and againg without success.

 Thanks in advance !!

 Daniel

shouldn't the path be /etc/network/interfaces?

Re: Network config problem

[Daniel Toffetti]

On Saturday 08 December 2001 16:58, ben wrote:
  Right now I get the external interface be assigned the valid IP
  address as before, configuring it as 'static dhcp - hostname pump'
  in /etc/interfaces. But when I try _any_ ping (any but my own
  address and localhost, of course), it fails with a Network is
  unreachable message. It's strange to me that the ping fails, but
  the names are correctly resolved to their respective IPs.

 shouldn't the path be /etc/network/interfaces?

You are right, this is the correct name of the file, anyway this is of 
no much help to solve my problem... ::))

Thanks !

Daniel
-- 
There is no spoon... - The Matrix

Re: Network config problem

[Michael Heldebrant]

On Sat, 2001-12-08 at 23:14, Daniel Toffetti wrote:
 On Saturday 08 December 2001 16:58, ben wrote:
   Right now I get the external interface be assigned the valid IP
   address as before, configuring it as 'static dhcp - hostname pump'
   in /etc/interfaces. But when I try _any_ ping (any but my own
   address and localhost, of course), it fails with a Network is
   unreachable message. It's strange to me that the ping fails, but
   the names are correctly resolved to their respective IPs.
 
  shouldn't the path be /etc/network/interfaces?
 
 You are right, this is the correct name of the file, anyway this is of 
 no much help to solve my problem... ::))

Replace WHATEVER with your proper iface number.

You want:

auto ethWHATEVER
iface inet dhcp ethWHATEVER

instead of static dhcp which, I'm not even sure how it would be parsed
by ifup.  ifconfig should tell you if your interface iseven being
brought up.

Assuming it's coming up and has an ip address, check your
/var/dhcp/dhclient.leases file for a routers entry.  If you have no
routers or 0.0.0.0 listed then your dhcp provider is broken, let them
know.  Then check your route table for a default route for the rest of
the internet.  If you do have one something is wrong, report back with
that output.  If you don't (more than likely) add a default route with:

route add default ethWHATEVER

to fix the problem until your dhcp providers fix it since you don't
know your gateway.  You can take a good guess at the gateway by running
tcpdump |grep arp, looking for the major arp requestor(s) and setting
default route to that host but this isn't the correct way.

--mike

Network config tool

[Will Newton]

Is there such a thing?

Specifically a tool to edit /etc/network/interfaces. And before you say, 
yes, vim, I know it isn't that hard, but some people do find this 
difficult, and when I say Debian is great, install Debian I would like to 
be able to point them in the direction of simple tools to do this kind of 
thing.

BTW I am not interested in linuxconf, it is a waste of space.

Re: Network config tool

[Kurt Lieber]

www.webmin.com/webmin


On Tuesday 30 October 2001 08:50 am, Will Newton wrote:
 Is there such a thing?

Re: Network config tool

[D.]

If memory serves me correctly, during the installation
of Potato at the point of inserting/selecting modules,
if your nic card is on the list and you select it,
when you exit that portation of the install it will
ask you if you want to configure your network.  Saying
yes will start the process and the only question that
you need to answer is what is your Hostname? Then it
will ask you if you want the program to set up your
network automatically, saying yes will do this and if
the program is successful it will say congratulations
your network is set up. 
  What can be easier than that.
Don 
--- Will Newton [EMAIL PROTECTED] wrote:
 
 Is there such a thing?
 
 Specifically a tool to edit /etc/network/interfaces.
 And before you say, 
 yes, vim, I know it isn't that hard, but some
 people do find this 
 difficult, and when I say Debian is great, install
 Debian I would like to 
 be able to point them in the direction of simple
 tools to do this kind of 
 thing.
 
 BTW I am not interested in linuxconf, it is a waste
 of space.
 
 
 -- 
 To UNSUBSCRIBE, email to
 [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact
 [EMAIL PROTECTED]
 


__
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com

Re: Network config tool

[Will Newton]

On Tuesday 30 Oct 2001 7:20 pm, D. wrote:

 you need to answer is what is your Hostname? Then it
 will ask you if you want the program to set up your
 network automatically, saying yes will do this and if
 the program is successful it will say congratulations
 your network is set up.
   What can be easier than that.

I don't know, but what can be harder is if you install a NIC after installing 
the OS.

Install time config is no config.

Network config...why so many??

[Xucaen]

--- Terry Boon [EMAIL PROTECTED] wrote:

 /etc/network/interfaces is where you may want
 to look.  Here's mine as
 an example (with one ethernet card):
 
# /etc/network/interfaces -- configuration
 file for ifup(8), ifdown(8)
 
# The loopback interface
iface lo inet loopback
 
# The first network card - this entry was
 created during the Debian
# installation
# (network, broadcast and gateway are
 optional)
iface eth0 inet static
  address 172.16.0.2
  netmask 255.255.255.0
  network 172.16.0.0
  broadcast 172.16.0.255
#  gateway 172.16.0.1
 

Hi all, I'm just curious. why are there so many
files that apparently hold the same information?
I thought the network configuration were kept in
files hosts, hostname, gateways, route.something,
and a few others that I can't think of the
names..  now there's this file called interfaces?
how will I know which files to change and which
ones not to change? I have been looking through
many many books and docs and this is the first
time I've heard of the interfaces file. why have
all of the other files if everything can be
configured in this one interfaces file?

xucaen 

__
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/

Re: Network config...why so many??

[Phil Brutsche]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

A long time ago, in a galaxy far, far way, someone said...

 Hi all, I'm just curious. why are there so many files that apparently
 hold the same information? I thought the network configuration were
 kept in files hosts, hostname, gateways, route.something, and a few
 others that I can't think of the names..  now there's this file called
 interfaces?

There are really only two or three files that you need to pay attention
to.

1) /etc/hostname
2) /etc/hosts
3) /etc/network/interfaces

/etc/hostname is the computer's name

/etc/hosts is a local name database

/etc/network/interfaces contains

I've never needed to use /etc/gateways and I don't have any /etc/route.*
files

 how will I know which files to change and which ones not to change?

Experience and asking people questions

 I have been looking through many many books and docs and this is the
 first time I've heard of the interfaces file.

It's specific to Debian.  Besides, most of those books are specific to
RedHat.

 why have all of the other files if everything can be configured in
 this one interfaces file?

But that would make it too easy :)

- -- 
- --
Phil Brutsche   [EMAIL PROTECTED]

GPG fingerprint: 9BF9 D84C 37D0 4FA7 1F2D  7E5E FD94 D264 50DE 1CFC
GPG key id: 50DE1CFC
GPG public key: http://tux.creighton.edu/~pbrutsch/gpg-public-key.asc
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE6SLTk/ZTSZFDeHPwRAoqnAKCNoopwxjwziOaWsmNyV33jGaE4MgCffPUh
AsB/ddOJ0zJpuc11P/7fodU=
=9dOO
-END PGP SIGNATURE-

Network config easy question

[Robin Rowe]

Dumb question, how do I set the IP address, netmask, gateway, and dns host
on Debian? The docs say that I should edit a file named 'network' but I
don't find any such file.

Robin
[EMAIL PROTECTED]

Re: Network config easy question

[Pascal Hos]

Check man interfaces

On Monday 25 December 2000 04:27 pm, Robin Rowe wrote:
 Dumb question, how do I set the IP address, netmask, gateway, and
 dns host on Debian? The docs say that I should edit a file named
 'network' but I don't find any such file.

 Robin
 [EMAIL PROTECTED]

Pascal Hos
-- 
[EMAIL PROTECTED]

Re: Network config easy question

[Pierfrancesco Caci]

:- Robin == Robin Rowe [EMAIL PROTECTED] writes:


 Dumb question, how do I set the IP address, netmask, gateway, and dns host
 on Debian? The docs say that I should edit a file named 'network' but I
 don't find any such file.

the docs are outdated. check for a file named /etc/network/interfaces
it's format is described in man interfaces
the dns host is set up using /proc directly or by using
/etc/sysctl.conf

Pf



-- 

---
 Pierfrancesco Caci | ik5pvx | mailto:[EMAIL PROTECTED]  -  
http://gusp.dyndns.org
  Firenze - Italia  | Office for the Complication of Otherwise Simple Affairs 
 Linux penny 2.4.0-test10 #1 Wed Nov 8 22:58:01 CET 2000 i686 unknown

Re: Network config easy question

[Terry Boon]

On Mon, Dec 25, 2000 at 02:27:53PM -0800, Robin Rowe wrote:
 Dumb question, how do I set the IP address, netmask, gateway, and dns host
 on Debian? The docs say that I should edit a file named 'network' but I
 don't find any such file.

/etc/network/interfaces is where you may want to look.  Here's mine as
an example (with one ethernet card):

   # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)

   # The loopback interface
   iface lo inet loopback

   # The first network card - this entry was created during the Debian
   # installation
   # (network, broadcast and gateway are optional)
   iface eth0 inet static
   address 172.16.0.2
   netmask 255.255.255.0
   network 172.16.0.0
   broadcast 172.16.0.255
   #gateway 172.16.0.1

As an earlier respondent said, man interfaces is useful.

DNS hosts are specified in /etc/resolv.conf.  man resolv.conf is
useful here.

-- 
Terry Boon, Hertfordshire, UK
[EMAIL PROTECTED] 

Re: Network config easy question

[Pierfrancesco Caci]

:- Pierfrancesco == Pierfrancesco Caci [EMAIL PROTECTED] writes:


 the dns host is set up using /proc directly or by using
 /etc/sysctl.conf

duh... I meant dns domain name
the dns serving you is set in /etc/resolv.conf

Pf



-- 

---
 Pierfrancesco Caci | ik5pvx | mailto:[EMAIL PROTECTED]  -  
http://gusp.dyndns.org
  Firenze - Italia  | Office for the Complication of Otherwise Simple Affairs 
 Linux penny 2.4.0-test10 #1 Wed Nov 8 22:58:01 CET 2000 i686 unknown

Re: Network config easy question (solved)

[Robin Rowe]

Thank you!

Robin
- Original Message -
From: Terry Boon [EMAIL PROTECTED]
To: debian-user@lists.debian.org
Sent: Monday, December 25, 2000 2:58 PM
Subject: Re: Network config easy question


 On Mon, Dec 25, 2000 at 02:27:53PM -0800, Robin Rowe wrote:
  Dumb question, how do I set the IP address, netmask, gateway, and dns
host
  on Debian? The docs say that I should edit a file named 'network' but I
  don't find any such file.

 /etc/network/interfaces is where you may want to look.  Here's mine as
 an example (with one ethernet card):

# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)

# The loopback interface
iface lo inet loopback

# The first network card - this entry was created during the Debian
# installation
# (network, broadcast and gateway are optional)
iface eth0 inet static
address 172.16.0.2
netmask 255.255.255.0
network 172.16.0.0
broadcast 172.16.0.255
# gateway 172.16.0.1

 As an earlier respondent said, man interfaces is useful.

 DNS hosts are specified in /etc/resolv.conf.  man resolv.conf is
 useful here.

 --
 Terry Boon, Hertfordshire, UK
 [EMAIL PROTECTED]


 --
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact
[EMAIL PROTECTED]

Re: Network config

[Wayne Topa]

Subject: RE: Network config
Date: Tue, Nov 21, 2000 at 10:59:09AM +0800

In reply to:Gilbert.Li (??)

Quoting Gilbert.Li (??)([EMAIL PROTECTED]):
 
 I can't find this option( CONFIG_RTL8139 )  in network device section.Where
 is it?
 Thanks 
 
less /usr/src/linux/.config
/CONFIG_RTL8139

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
# CONFIG_RTL8139 is not set
# CONFIG_RTL8139TOO is not set
# CONFIG_NET_ISA is not set

-- 
Windows: the ultimate triumph of marketing over technology.
___

Re: Network config

[Moritz Schulte]

Wayne Topa [EMAIL PROTECTED] writes:

  I can't find this option( CONFIG_RTL8139 )  in network device section.Where
  is it?

You've to say 'yes' to CONFIG_EXPERIMENTAL, which shows you the
experimantel drivers, too.

moritz
-- 
Moritz Schulte [EMAIL PROTECTED] http://hp9001.fh-bielefeld.de/~moritz/
Debian/GNU supporter - http://www.debian.org/ http://www.gnu.org
GPG fingerprint = 3A14 3923 15BE FD57 FC06  B501 0841 2D7B 6F98 4199