Re: network trouble on stretch

Very sorry. I told you guys some horrible lies yesterday about Buster. ifupdown is there. route is back. ifconfig is back. Thanks much, Fungi4All, for the name fix, I haven't implemented it yet, and I'm not sure I will because who knows what'll happen in the next release. I'm going to try to li

Re: network trouble on stretch

Fungi4All composed on 2017-09-04 07:16 (UTC-0400): >> From: mrma...@earthlink.net To: debian-user@lists.debian.org >> Erik Christiansen composed on 2017-09-04 18:06 (UTC+1000): >>> But Fungi4All"s solution is so easy to use that I"m won over, and have >>> implemented it here. >> I think I start

Re: network trouble on stretch

> From: mrma...@earthlink.net > To: debian-user@lists.debian.org > > Erik Christiansen composed on 2017-09-04 18:06 (UTC+1000): > >> But Fungi4All"s solution is so easy to use that I"m won over, and >> have implemented it here. > > I think I started putting net.ifnames=0 on the kernel command line

Re: network trouble on stretch

On 04.09.17 04:42, Felix Miata wrote: > Erik Christiansen composed on 2017-09-04 18:06 (UTC+1000): > > > But Fungi4All's solution is so easy to use that I'm won over, and > > have implemented it here. > > I think I started putting net.ifnames=0 on the kernel command line close to 3 > years ago.

Re: network trouble on stretch

Erik Christiansen composed on 2017-09-04 18:06 (UTC+1000): > But Fungi4All's solution is so easy to use that I'm won over, and > have implemented it here. I think I started putting net.ifnames=0 on the kernel command line close to 3 years ago. :-) More than that it's been around:

Re: network trouble on stretch

On 03.09.17 20:09, Glenn English wrote: > I looked on the 'Net, asking why the interface names were changed. I > found a good reason: sometimes the ethn names aren't reliably > consistent. Fine, I say, you've figured how to make them consistent. > That's no reason to change the names from a meaning

Re: network trouble on stretch

On 04/09/17 10:27, Fungi4All wrote: Before you get a long lecture on the merits of long unique names try this: Edit your /etc/default/grub change GRUB_CMDLINE_LINUX=”” to : GRUB_CMDLINE_LINUX="net.ifnames=0" If the biosdevname is installed you need to add : GRUB_CMDLINE_LINUX="net.ifnames=0 bios

Re: network trouble on stretch

On Sun, Sep 03, 2017 at 06:27:12PM -0400, Fungi4All wrote: > > From: ghe2...@gmail.com > > The WiFi works, but the Ethernet doesn"t, and I can"t figure out why. > > ip addr: ... > Before you get a long lecture on the merits of long unique names try this: > > Edit your /etc/default/grub change GRU

Re: network trouble on stretch

On 9/3/17, Glenn English wrote: > Working on a Dell 5414 laptop, Stretch. > > The WiFi works, but the Ethernet doesn't, and I can't figure out why. > > ip addr: > > 1: lo: mtu 65536 qdisc noqueue state UNKNOWN > group default qlen 1 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >

Re: network trouble on stretch

> From: ghe2...@gmail.com > To: debianUsers > > Working on a Dell 5414 laptop, Stretch. > > The WiFi works, but the Ethernet doesn"t, and I can"t figure out why. > > ip addr: > > 1: lo: mtu 65536 qdisc noqueue state UNKNOWN > group default qlen 1 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:

Re: network trouble: dhcp works, resolv.conf correct, ping doesn't work

(Sorry about the delay!) On Mon, 2007.08.20 21:37, Joachim Fahnenmüller wrote: > On Mon, Aug 20, 2007 at 09:26:11AM -0500, Owen Heisler wrote: > > I'm having trouble with the internet connection on a Lenny/Sid system. > > It is a very simple connection to a cable modem via an ethernet > > cable.

Re: network trouble: dhcp works, resolv.conf correct, ping doesn't work

On Mon, Aug 20, 2007 at 09:26:11AM -0500, Owen Heisler wrote: > I'm having trouble with the internet connection on a Lenny/Sid system. > It is a very simple connection to a cable modem via an ethernet > cable. > > /etc/network/interfaces includes the lo interface and "iface eth0 inet dhcp". > >

Re: network trouble: dhcp works, resolv.conf correct, ping doesn't work

On 8/20/07, Owen Heisler <[EMAIL PROTECTED]> wrote: > I'm having trouble with the internet connection on a Lenny/Sid system. > It is a very simple connection to a cable modem via an ethernet > cable. > "ping google.com" returns "unknown host". Here's a bit more: Pinging a nameserver returns "pin

Re: Network trouble

On 5 Jan 2003, at 14:37, Tim Dijkstra wrote: > On Sun, 5 Jan 2003 12:56:57 +0100 > [EMAIL PROTECTED] wrote: > > > > Im using a winmodem and wvdial for internetconnections. i don't > > think it should matter but I'm using wvdial from debian-potato, since > > the woody release didn't work. > >

Re: Network trouble

On Sun, 5 Jan 2003 12:56:57 +0100 [EMAIL PROTECTED] wrote: > Im using a winmodem and wvdial for internetconnections. i don't > think it should matter but I'm using wvdial from debian-potato, since > the woody release didn't work. > ... > --> > /etc/resolv.conf has t

Re: Syslogd trouble (was: Re: Network trouble (?) with kernel 2.0.27)

> On the following problem, I just found out that this is a syslogd > internal message. It comes after syslogd restarts. It's like this: > > - Dec 22 06:49:31 blackbird syslogd 1.3-0#11: restart. > - Dec 22 06:49:31 blackbird syslogd: select: Bad file number > - Dec 22 06:50:02 blackbird last mess

Re: Syslogd trouble (was: Re: Network trouble (?) with kernel 2.0.27)

In your email to me, F. Fernandez, you wrote: > > Hi! > > On the following problem, I just found out that this is a syslogd > internal message. It comes after syslogd restarts. It's like this: > > - Dec 22 06:49:31 blackbird syslogd 1.3-0#11: restart. > - Dec 22 06:49:31 blackbird syslogd: selec

Syslogd trouble (was: Re: Network trouble (?) with kernel 2.0.27)

Hi! On the following problem, I just found out that this is a syslogd internal message. It comes after syslogd restarts. It's like this: - Dec 22 06:49:31 blackbird syslogd 1.3-0#11: restart. - Dec 22 06:49:31 blackbird syslogd: select: Bad file number - Dec 22 06:50:02 blackbird last message rep

Re: Network trouble (?) with kernel 2.0.27

> I've been working with a fresh instalation of 1.2 including a > reconfigured kernel 2.0.27. I'm getting lots of messages like > the following in /var/adm/messages: > > >Dec 19 22:37:19 blackbird last message repeated 569167 times > >Dec 19 22:38:19 blackbird last message repeated 577432 ti