Re: [DNG] what has gone wrong with networking in ascii?
I get some trouble with the network after updating to ascii and rebooting too on two computers. I found some messages in dmesg like Cannot rename eth0 to eth1, name already in use Cannot rename eth2 to eth0, name already in use It looks like udev change the name of the devices. I solved this editing the /etc/roules.d/peresist.rules and use names like nic0, nic1. And I changed the /etc/networking/interfaces to the new names. That work for me, but is not a good solution. I hope is helpful. Udo Am 14.07.2018 um 18:53 schrieb Hendrik Boom: > I upgraded my home serverto ascii a bit ore than a week ago, and then > proceeded to make a full backup of user files (and system files in case > I have to consult them on reinstallation if the system gets hoplessly > broken). > > I finally rebooted yesterday after a week of flawless running, only to > find that netwrking is completely nonfunctional. Afer a day of > struggling, I rebooted to an old copy of Debian wheezy I still had lying > around on the hard drive and networking worked perfectly. > > So the hardware appears to be OK. > > But software is another story. On ascii: > > my client laptops can connect to the wifi modem, but never get an IP > number assigned. > > My server normally uses pppoe to connect to my ISP. My script to > identity the access concentrator manages to connect to it, so the > hardware must be working even for proper pppoe operation, but I can > never manage to get a pppoe connection. > > So: > > (1) What has changed between jessie and ascii? Everything worked fine > on Jessie. Do pppoe and dhcpd need different configuration files or is > something else a problem? The files I'm using seem to have the same > chap and pap secrets as on ascii as on wheezy. > > (2) How should I go about tracking down the problem? > > I might add that ifconfig reports the usual interfaces of eth0, eth1, > and loopback, so I don't *seem* to be haveing problems with the systemd > and Debian's new interface naming conventions. > > Of course it's possible that I did something stupid after the upgrade. > > -- hendrik > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] what has gone wrong with networking in ascii?
On Sat, Jul 14, 2018 at 12:53:08PM -0400, Hendrik Boom wrote: > But software is another story. On ascii: > > my client laptops can connect to the wifi modem, but never get an IP > number assigned. The change I'm aware of for dhcpd between jessie and Ascii is that dhcpd on Ascii automatically does v4 and v6. You asked what changed, and that's the biggest change I'm aware of. That doesn't mean this is the cause of your problem. What does /var/log/daemon.log say when one of your machines attempts to obtain an IP address? > > My server normally uses pppoe to connect to my ISP. My script to > identity the access concentrator manages to connect to it, so the > hardware must be working even for proper pppoe operation, but I can > never manage to get a pppoe connection. What does /var/log/ppp-connect-errors say? What does /var/log/daemon.log say? Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] what has gone wrong with networking in ascii?
Am Samstag, 14. Juli 2018 schrieb Hendrik Boom: > (2) How should I go about tracking down the problem? > > I might add that ifconfig reports the usual interfaces of eth0, eth1, Have you checked they also have the same MAC address like before? Kind regards, Stefan ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] what has gone wrong with networking in ascii?
I upgraded my home serverto ascii a bit ore than a week ago, and then proceeded to make a full backup of user files (and system files in case I have to consult them on reinstallation if the system gets hoplessly broken). I finally rebooted yesterday after a week of flawless running, only to find that netwrking is completely nonfunctional. Afer a day of struggling, I rebooted to an old copy of Debian wheezy I still had lying around on the hard drive and networking worked perfectly. So the hardware appears to be OK. But software is another story. On ascii: my client laptops can connect to the wifi modem, but never get an IP number assigned. My server normally uses pppoe to connect to my ISP. My script to identity the access concentrator manages to connect to it, so the hardware must be working even for proper pppoe operation, but I can never manage to get a pppoe connection. So: (1) What has changed between jessie and ascii? Everything worked fine on Jessie. Do pppoe and dhcpd need different configuration files or is something else a problem? The files I'm using seem to have the same chap and pap secrets as on ascii as on wheezy. (2) How should I go about tracking down the problem? I might add that ifconfig reports the usual interfaces of eth0, eth1, and loopback, so I don't *seem* to be haveing problems with the systemd and Debian's new interface naming conventions. Of course it's possible that I did something stupid after the upgrade. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
