3 Oct
2005
3 Oct
'05
12:03 p.m.
Greetings:
How do I set up the networking in AGNULA/Demudi 1.2.1 ?
I've installed the system on a second disk in my desktop system. I
want to sh*tcan the 2.6.12 kernel asap, but I have no network
connection. I fixed /etc/network/interfaces and can see eth0 in
ifconfig's report, but where is the tool to configure the interface ??
Best,
dp
3 Oct
3 Oct
1:06 p.m.
On 10/3/05, Dave Phillips <dlphillips(a)woh.rr.com> wrote:
Greetings:
How do I set up the networking in AGNULA/Demudi 1.2.1 ?
I've installed the system on a second disk in my desktop system. I
want to sh*tcan the 2.6.12 kernel asap, but I have no network
connection. I fixed /etc/network/interfaces and can see eth0 in
ifconfig's report, but where is the tool to configure the interface ??
The hardway would be with ifconfig and route, no?
I've never run Agnula so I couldn't guess at the 'right' way. Sorry.
1:51 p.m.
Hi Mark:
Thanks for the note, but the utterly non-obvious solution was to run
pump, watch it fail, then run '/etc/init.d/networking restart'.
Yep, clear as mud.
Best,
dp
Mark Knecht wrote:
On 10/3/05, Dave Phillips <dlphillips(a)woh.rr.com>
wrote:
Greetings:
How do I set up the networking in AGNULA/Demudi 1.2.1 ?
I've installed the system on a second disk in my desktop system. I
want to sh*tcan the 2.6.12 kernel asap, but I have no network
connection. I fixed /etc/network/interfaces and can see eth0 in
ifconfig's report, but where is the tool to configure the interface ??
The hardway would be with ifconfig and route, no?
I've never run Agnula so I couldn't guess at the 'right' way. Sorry.
4 Oct
4 Oct
6:23 a.m.
On Monday 03 October 2005 16:58, Dave Phillips was like:
Yep, clear as mud.
Please suggest what could be added to this to make it more clear.
http://demudi.agnula.org/wiki/DocumentsFaq#Icantconnecttothenetwork
--
cheers,
tim hall
http://glastonburymusic.org.uk/tim
4:42 p.m.
On Tuesday 04 October 2005 08:23, tim hall wrote:
On Monday 03 October 2005 16:58, Dave Phillips was
like:
Hi Tim. As you've spent all afternoon waiting for the big music remix fracas
to start again, and Dave Philips hasn't come back on what additions to make
to the wiki, I thought I'd put my 2 cents worth in. The man page is fine if
you are really up to speed with Linux, but having looked through it earlier
on, I wouldn't know where to start with a blank page
in /etc/network/interfaces, as with roll your own Gentoo. Admittadly most
distro's have a partially contructed page. I think an addition could be made
regarding a nameserver entry in /etc/resolv.conf, also, perhaps, an example
of an /etc/network/interfaces file, with instructions to change IP address
and gateway if necessary for static setups. Perhaps showing changes that need
to be made if wanting to use dhcp. Personally I don't see any point in using
dhcp unless you are using more than 10 or so machines. I've put
my /etc/network/interfaces file below from one of my Debian installs if you
want to add it to the wiki as an example.
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
# The loopback interface
auto lo
iface lo inet loopback
# The first network card - this entry was created during the Debian
installation
# (network, broadcast and gateway are optional)
auto eth0
iface eth0 inet static
address 192.168.0.7
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.1
iface dsl-provider inet ppp
provider dsl-provider
# please do not modify the following line
pre-up /sbin/ifconfig eth0 up # line maintained by pppoeconf
This is on a client machine going through a layer 2 switch to a Smoothwall
Express 2 firewall, connected to the net by serial modem.
You're free to use this to update the wiki, as no ones going to hack my
private address. I'd do it myself, but have never updated wiki pages before.
All the best. Nigel.
Yep, clear as mud.
Please suggest what could be added to this to make it more clear.
http://demudi.agnula.org/wiki/DocumentsFaq#Icantconnecttothenetwork
5 Oct
5 Oct
8:25 a.m.
On Tuesday 04 October 2005 12:34, Nigel Henry was like:
Hi Tim. As you've spent all afternoon waiting for
the big music remix
fracas to start again,
Or possibly the opposite. ;)
and Dave Philips hasn't come back on what
additions
to make to the wiki, I thought I'd put my 2 cents worth in. The man page is
fine if you are really up to speed with Linux, but having looked through it
earlier on, I wouldn't know where to start with a blank page
in /etc/network/interfaces, as with roll your own Gentoo. Admittadly most
distro's have a partially contructed page. I think an addition could be
made regarding a nameserver entry in /etc/resolv.conf, also, perhaps, an
example of an /etc/network/interfaces file, with instructions to change IP
address and gateway if necessary for static setups. Perhaps showing changes
that need to be made if wanting to use dhcp. Personally I don't see any
point in using dhcp unless you are using more than 10 or so machines. I've
put
my /etc/network/interfaces file below from one of my Debian installs if you
want to add it to the wiki as an example.
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
# The loopback interface
auto lo
iface lo inet loopback
# The first network card - this entry was created during the Debian
installation
# (network, broadcast and gateway are optional)
auto eth0
iface eth0 inet static
address 192.168.0.7
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.1
iface dsl-provider inet ppp
provider dsl-provider
# please do not modify the following line
pre-up /sbin/ifconfig eth0 up # line maintained by pppoeconf
This is on a client machine going through a layer 2 switch to a Smoothwall
Express 2 firewall, connected to the net by serial modem.
You're free to use this to update the wiki, as no ones going to hack my
private address. I'd do it myself, but have never updated wiki pages
before.
Thanks for your suggestions Nigel. I'll mull this over. Most of this stuff is
fairly clearly documented in Debian reference and most network cards get
auto-configured. Also, the GNOME guis are very good for relative newbies.
That said, I will add a little more info and pointers to this section as it
obviously isn't that clear.
--
cheers,
tim hall
http://glastonburymusic.org.uk/tim
9:40 a.m.
tim hall wrote:
On Monday 03 October 2005 16:58, Dave Phillips was
like:
Hi Tim:
Well, a number of interesting observations came to me while reading
that document. For example: Were you (or whoever wrote it) aware that
the pcmcia-cs package wasn't included in 1.2.1 ? Thus the advice to use
the utility was untested, no-one actually tried it.
GNOME is indeed installed on my system, but network-admin is not. The
wiki page does not provide enough information on what to do when
everything on the page fails. No reference to pump or the dhcp stuff.
Linux naming conventions sometimes seem to delight in confusing users.
Is there some obvious connection between a utility named pump and a
network configuration tool ? You don't wanna know what I think when I
see 'pump'... ;-) A more complete list of the tools needed/supplied to
set up PPP, PPPoe, DSL, cable connections, etc. would be nice.
How about advising users who will not be using either X or GNOME ?
The installer failed to configure eth0. This problem is dealt with in
a FAQ for 1.2.0 but there's no mention that the problem still exists in
1.2.1.
Generally speaking, there needs to be much more foresight WRT things
going wrong. More detailed troubleshooting advice is needed.
And the next time someone answers a question re: a failed networking
connection with "Well, just fire up apt-get..." I'm going to say
something I'm sure I'll regret. Apt-get isn't very useful when you can't
connect to the network in the first place...
Btw, I will be overjoyed to discover that I'm an utter lunkhead who
just can't read instructions clearly. I'm not trying to denigrate
anyone's work, but I am genuinely dismayed by the number and kinds of
difficulties I've faced with Demudi.
Don't even ask me about ALSA's virtual MIDI module...
Best regards,
dp
Yep, clear as mud.
Please suggest what could be added to this to make it more clear.
http://demudi.agnula.org/wiki/DocumentsFaq#Icantconnecttothenetwork
6 Oct
6 Oct
2:19 a.m.
On Wednesday 05 October 2005 12:47, Dave Phillips was like:
tim hall wrote:
To be honest, no I wasn't aware of this beyond the reports that you have made.
I tend to respond to queries rather than be that pro-active about the FAQ. As
I'm sure you're aware, this can be hard when one doesn't get feedback. See
below for why I didn't personally test it. I'm sure many people do use DeMuDi
on laptops, I'm confused as to why you are the only person to have asked this
question.
On Monday 03 October 2005 16:58, Dave Phillips was
like:
Hi Tim:
Well, a number of interesting observations came to me while reading
that document. For example: Were you (or whoever wrote it) aware that
the pcmcia-cs package wasn't included in 1.2.1 ? Thus the advice to use
the utility was untested, no-one actually tried it. Yep, clear as mud.
Please suggest what could be added to this to make it more clear.
http://demudi.agnula.org/wiki/DocumentsFaq#Icantconnecttothenetwork GNOME is indeed installed on my system, but
network-admin is not. The
wiki page does not provide enough information on what to do when
everything on the page fails. No reference to pump or the dhcp stuff.
Point taken. network-admin should be installed by default, but yes, I had to
ask some pointed questions before this was made clear. This should probably
be considered a bug. Is it not even on the CD?
Linux naming conventions sometimes seem to delight
in confusing users.
Is there some obvious connection between a utility named pump and a
network configuration tool ? You don't wanna know what I think when I
see 'pump'... ;-) A more complete list of the tools needed/supplied to
set up PPP, PPPoe, DSL, cable connections, etc. would be nice.
OK, thanks. I'll have to find out WTH pump is then won't I?
How about advising users who will not be using
either X or GNOME ?
That's what the reference to man interfaces is for. I'll try to expand on
that. I don't really want to have to duplicate material that already exists in
say, Debian Reference, or whatever. I think it's appropriate to assume that
every Debian user has read that. I'm interested in well worded explanations
of why that might not be so. I'll include some specific links anyway.
The installer failed to configure eth0. This problem
is dealt with in
a FAQ for 1.2.0 but there's no mention that the problem still exists in
1.2.1.
This not specifically a problem with the A/DeMuDi release. It uses the
Sarge installer, which does configure most cards out of the box.
Generally speaking, there needs to be much more
foresight WRT things
going wrong. More detailed troubleshooting advice is needed.
ack.
I will say, however, that FAQs generally work on hindsight and people actually
asking questions, preferably more than once. You're asking for proper
documentation here. I'll see if I can find some.
And the next time someone answers a question re: a
failed networking
connection with "Well, just fire up apt-get..." I'm going to say
something I'm sure I'll regret. Apt-get isn't very useful when you can't
connect to the network in the first place...
No, it's next to useless.
Btw, I will be overjoyed to discover that I'm an
utter lunkhead who
just can't read instructions clearly. I'm not trying to denigrate
anyone's work, but I am genuinely dismayed by the number and kinds of
difficulties I've faced with Demudi.
I am equally dismayed with the difficulties you've had to face. I don't use
laptops (not through any deliberate policy) so I have not been able to
troubleshoot laptop specific problems. If anyone wants to give me a laptop on
which to test things I will happily do so. Heh. ;)
I do understand your frustrations, I have a similar sized bag of frustrations
with the effort it takes to get anything changed in Debian. Some of these
questions you would need to ask Free about directly. I think I have moved far
enough from being a newbie now that I have begun to forget how confusing this
can all be for the neophyte. Thanks for your observations, they will be
extremely useful. I shall work through them slowly, probably unpredictably
and eventually get round to updating the FAQ. :)
That is, assuming I don't lose the will to live while I'm waiting for the page
to display in my browser.
--
cheers,
tim hall
http://glastonburymusic.org.uk/tim
1:19 p.m.
>>>> "th" == tim hall
<tech(a)glastonburymusic.org.uk> writes:
th> That is, assuming I don't lose the will to live while I'm
th> waiting for the page to display in my browser.
Yes, when I tried to display the page to see what Dave was talking
about, I kept wondering how anyone even got as far as being able to
complain about it.
--
Laura (mailto:lconrad@laymusic.org , http://www.laymusic.org/ )
(617) 661-8097 fax: (501) 641-5011
233 Broadway, Cambridge, MA 02139
1:49 p.m.
On Thursday 06 October 2005 16:19, Laura Conrad was like:
th> That is, assuming I don't lose the will
to live while I'm
th> waiting for the page to display in my browser.
Yes, when I tried to display the page to see what Dave was talking
about, I kept wondering how anyone even got as far as being able to
complain about it.
This is now in the process of being fixed along with various other
glitches. :)
--
cheers,
tim hall
http://glastonburymusic.org.uk/tim
FUNEX? 9VFNNEX! FUNEM? 9VFNNEM! RIP RB
5:32 p.m.
On Thursday 06 October 2005 15:49, tim hall wrote:
On Thursday 06 October 2005 16:19, Laura Conrad was
like:
Hi Tim. This is always a problem when running a webserver off a dialup
connection. Joking aside, and back to the big AGNULA nightmares problem.
I trolled around a bit on my Debian Sarge's synaptic. Pump is described as a
tool for retrieving IP addresses, using dhcp or bootp. (don't know what bootp
is, perhaps someone will tell me). The word pump, thinking back to old-time
detective movies is to do with obtaining information from informants.
Something like "lets pump the guy and see what he comes up with" . I suppose
this fits in quite well with the Linux useage of the word. Like. Lets pump
the dhcp server and see what IP address it throws back. The only other
network config tools I could find on Sarge were "network-console-config"
which appears to be tied into running base-config, and "netapplet" , which
to quote says "USER-FRIENDLY NETWORK INTERFACE CONTROL APPLET" "Network
applet allows the user to control the currently active network interface and
perform a small amount of run-time configuration. It is primarily aimed at
laptop users who need to be able to switch between different network setups
and wireless networks" . That sounds like it coiuld be quite usefull to
laptop users. Of course I don't know if either of these programs are on
DeMuDi. I did DL the iso,but can't remember where I've put it, and didn't
have any CDR's at the time to burn it to. When I find it I'll try it, and see
what networking stuff came down with it. May the force be with you. Nigel.
th> That is, assuming I don't lose the
will to live while I'm
th> waiting for the page to display in my browser.
Yes, when I tried to display the page to see what Dave was talking
about, I kept wondering how anyone even got as far as being able to
complain about it.
This is now in the process of being fixed along with various other
glitches. :) 
3 Oct
3 Oct
1:32 p.m.
Dave Phillips wrote:
Greetings:
How do I set up the networking in AGNULA/Demudi 1.2.1 ?
I've installed the system on a second disk in my desktop system. I want
to sh*tcan the 2.6.12 kernel asap, but I have no network connection. I
fixed /etc/network/interfaces and can see eth0 in ifconfig's report, but
where is the tool to configure the interface ??
Best,
dp
On the command-line network-admin
robin
5:20 p.m.
On Monday 03 October 2005 16:22, Dave Phillips wrote:
robin wrote:
Hi Dave. If you want to have a go at a "roll your own" Gentoo style config,
I'm sending my /etc/network/interfaces file. This is from my Debian Sarge
install, set up statically (no dhcp) . You'll need to change "Address" to
the
IPaddress you want to use for the machine, and maybe the gateway if you're
not using 192.168.0.1. The rest should be ok if you're using addresses in the
range 192.168.x.x. The entry "auto eth0" is to start the network at bootup.
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
# The loopback interface
auto lo
iface lo inet loopback
# The first network card - this entry was created during the Debian
installation
# (network, broadcast and gateway are optional)
auto eth0
iface eth0 inet static
address 192.168.0.7
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.1
iface dsl-provider inet ppp
provider dsl-provider
# please do not modify the following line
pre-up /sbin/ifconfig eth0 up # line maintained by pppoeconf
You will also need to edit /etc/resolv.conf adding your DNS IP address, which
should be showing on your other install. Mine is.
nameserver 213.36.80.1
Just change the address to that supplied by you're ISP.
Otherwise just copy what is in those two files on your other machine, changing
the address line to a different IP address specific to the machine that the
OS is on.
You'll probably need to re-boot the machine after making the changes.
Fedora Core has a nice interface for setting up the network, and Gentoo, if I
remember correctly uses the same one. Debian has something called DSL/PPPoE
configuration tool, which I havn't tried as the network was setup on install,
but I have changed the IP address of the machine with no problem
in /etc/network/interfaces. It's a pity that some distro's make it so
difficult to setup something so necessary as the network.
Another thing to consider is if your network card is detected, and the driver
loaded at bootup. I use Realtek 8139 cards and the driver is 8139too.
Running /sbin/lsmod should identify the NIC's driver on your other install.
With the 2.6 kernel I had to add the driver to /etc/modules. Post back if
I've missed anything or am insulting you're inteligence. All the best. Nigel.
On the command-line network-admin
That would have been easy, but no such utility exists for this
installation.
Best,
dp
6:12 p.m.
Nigel Henry wrote:
Hi Dave. If you want to have a go at a "roll your
own" Gentoo style config,
I'm sending my /etc/network/interfaces file. This is from my Debian Sarge
install, set up statically (no dhcp). [snip]
Hi Nigel:
Thank you for the detailed conf file, I've saved it for future
reference if/when necessary. I did get the network up & running after
fixing /etc/network/interfaces to see eth0 at boot and running the pump
utility. Curiously, pump said it failed but brought up and connected the
interface anyway.
Post back if I've missed anything or am insulting
you're inteligence. All the best. Nigel.
My girlfriend says it's impossible to insult my intelligence. I think
she means something rather disparaging by that comment... ;)
Thank you again for the file.
Best,
dp
4 Oct
4 Oct
5:49 a.m.
Hallo,
Dave Phillips hat gesagt: // Dave Phillips wrote:
Nigel Henry wrote:
I've never used pump, but if you'd use dhcp (whose Debian package I
think conflicts with pump) you could instead manage the dhcp
configuration inside /etc/network/interfaces as well. Just replace
iface eth0 inet static
# ...
with
iface eth0 inet dhcp
# without addresses etc.!
To manually start a dhcp lookup, you can still use "sudo dhclient
eth0" similar to how pump is used AFAIK.
Ciao
--
Frank Barknecht _ ______footils.org_ __goto10.org__
Hi Dave. If you want to have a go at a "roll
your own" Gentoo style
config, I'm sending my /etc/network/interfaces file. This is from my
Debian Sarge install, set up statically (no dhcp). [snip]
Hi Nigel:
Thank you for the detailed conf file, I've saved it for future
reference if/when necessary. I did get the network up & running after
fixing /etc/network/interfaces to see eth0 at boot and running the pump
utility. Curiously, pump said it failed but brought up and connected the
interface anyway. 
12:30 p.m.
On Tue, 4 Oct 2005 at 09:45 +0200, Frank Barknecht wrote:
I've never used pump, but if you'd use dhcp
(whose Debian package I
think conflicts with pump) you could instead manage the dhcp
configuration inside /etc/network/interfaces as well. Just replace
iface eth0 inet static
# ...
with
iface eth0 inet dhcp
# without addresses etc.!
This is actually also the case for pump and any other dhcp client on
debian. My personal favorite is udhcpc, and it takes a very compelling
reason to get me to use the bloatware that is dhclient.
--
Hans Fugal ; http://hans.fugal.net
There's nothing remarkable about it. All one has to do is hit the
right keys at the right time and the instrument plays itself.
-- Johann Sebastian Bach
4:50 p.m.
Hallo,
Hans Fugal hat gesagt: // Hans Fugal wrote:
On Tue, 4 Oct 2005 at 09:45 +0200, Frank Barknecht
wrote:
Ah, cool, so if I want to dump the big dhcp package and install, say,
udhcpc, then my /etc/network/interfaces-line will still work as
before, right? Hm, I might try udhcpc on my laptop then.
Ciao
--
Frank Barknecht _ ______footils.org_ __goto10.org__
I've never used pump, but if you'd use
dhcp (whose Debian package I
think conflicts with pump) you could instead manage the dhcp
configuration inside /etc/network/interfaces as well. Just replace
iface eth0 inet static
# ...
with
iface eth0 inet dhcp
# without addresses etc.!
This is actually also the case for pump and any other dhcp client on
debian. My personal favorite is udhcpc, and it takes a very compelling
reason to get me to use the bloatware that is dhclient.
5:59 p.m.
On Tue, 4 Oct 2005 at 20:46 +0200, Frank Barknecht wrote:
Ah, cool, so if I want to dump the big dhcp package
and install, say,
udhcpc, then my /etc/network/interfaces-line will still work as
before, right? Hm, I might try udhcpc on my laptop then.
Yup.
--
Hans Fugal ; http://hans.fugal.net
There's nothing remarkable about it. All one has to do is hit the
right keys at the right time and the instrument plays itself.
-- Johann Sebastian Bach
6:14 p.m.
robin wrote:
Dave Phillips wrote:
No. :(
But I did get the network connection going. Now I need to replace my DVD
drive that just puked and died...
It has not been a nice day.
Best,
dp
robin wrote:
Not on the installation cd?
On the command-line network-admin
That would have been easy, but no such utility exists for this
installation.
Best,
dp
4 Oct
4 Oct
2:31 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Dave, hi Robin,
> Dave Phillips wrote:
>
>> robin wrote:
>>
>>> On the command-line network-admin
'network-admin' is a Gnome-based tool. I'd never use these... (no KDE
tool as well)
>> That would have been easy, but no such utility
exists for this
>> installation.
You don't habe Gnome installed, right?
> Not on the installation cd?
Should be there if you used Agnula/Demudi. If not, it's just an 'apt-get
install gnome' away.
But like someone posted here already, /etc/network/interfaces and
/etc/resolv.conf are your friends, followed by /etc/init.d/networking
restart.
cheers,
wjl
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDQgX4qrjTanKNm9ARAg3RAJ9oNpxOZmI+8b0m2f2HcRnx6F3fjgCfW9us
Ix4H3PHlN0LAU9QcYSYPN4k=
=9hNO
-----END PGP SIGNATURE-----
3 Oct
3 Oct
2:21 p.m.
ifdown eth0; ifup eth0
Or as you said, /etc/init.d/networking restart usually works too.
On Mon, 3 Oct 2005 at 10:10 -0400, Dave Phillips wrote:
Greetings:
How do I set up the networking in AGNULA/Demudi 1.2.1 ?
I've installed the system on a second disk in my desktop system. I
want to sh*tcan the 2.6.12 kernel asap, but I have no network
connection. I fixed /etc/network/interfaces and can see eth0 in
ifconfig's report, but where is the tool to configure the interface ??
Best,
dp
--
Hans Fugal ; http://hans.fugal.net
There's nothing remarkable about it. All one has to do is hit the
right keys at the right time and the instrument plays itself.
-- Johann Sebastian Bach
4 Oct
4 Oct
6:19 a.m.
On Monday 03 October 2005 15:10, Dave Phillips was like:
How do I set up the networking in AGNULA/Demudi
1.2.1 ?
I've installed the system on a second disk in my desktop system. I
want to sh*tcan the 2.6.12 kernel asap, but I have no network
connection. I fixed /etc/network/interfaces and can see eth0 in
ifconfig's report, but where is the tool to configure the interface ??
A/DeMuDi uses the GNOME guis
Debian Menu > Apps > System > Network Admin
... & > GNOME Network Tool
--
cheers,
tim hall
http://glastonburymusic.org.uk/tim
7037
days inactive
7040
days old
linux-audio-user@lists.linuxaudio.org
23 comments
9 participants
participants (9)
-
Dave Phillips -
Frank Barknecht -
Hans Fugal -
Laura Conrad -
Mark Knecht -
Nigel Henry -
robin -
tim hall -
Wolfgang Lonien