[DNG] live-sdk or live-build repos to use?
I just want to clarify which are the best repos to use to build an live and or installable image from? I've done a number of build recently using these repos. But this is currently broken. I've tried other combinations of repos, but they had missing packages. _MIRROR_BINARY="http://pkgmaster.devuan.org/merged; _INSTALLER_MIRROR="http://pkgmaster.devuan.org/devuan; I found I had to do it this way because not all of the d-i, including initrd and vmlinuz, were in the same repo. the packages in http://pkgmaster.devuan.org/devuan are currently being update/changed so I can't build atm. I'm looking for some clarification on which repos I should/shouldn't use ozi ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ethernet interface name swap (WAS: what has gone wrong with networking in ascii?
Rick Moen wrote on 16/07/18 07:44: Quoting Hendrik Boom (hend...@topoi.pooq.com): But I wold like to be able to run wheezy very occasionally -- there's an application I have that suffered the end-of-days in wheezy -- so I'd like to find another solution. http://www.enterprisenetworkingplanet.com/netos/article.php/3586546/Nail-Down-Network-Interface-Names-with-ifrename.htm Yes, "ifrename" is capable and easy to use for this purpose. However, one must make sure it runs before interfaces are configured, which unfortunately is not the default case for a choice of using "eudev" for configuration. (Primarily because "e" is before "i" in the natural ordering of startup script invocations). Thus, if your "/etc/network/interfaces" declares "allow-hotplug" for the interface(s) concerned, you need to take extra steps. For example, you can add "ifrename" as a required facility in "/etc/init/eudev" before enabling it. In other words, it's the four steps of a) disabling ifrename, b) do the edit, c) enable ifrenam, and d) update initramfs. (There are many other ways to achieve the same result of course) On the other hand, if your "interfaces" file declares "auto" for the interface(s) concerned, you don't need to correct anything, but it would suffice with steps c and d. Also, if your "interfaces" file is quiet about the interface(s) concerned, typically because you use one of the handy network management daemons, you still need to ensure that the ifrename facility is started before the network management daemon. This is likely to also be the default setting, so steps c and d would suffice. Ralph. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ethernet interface name swap (WAS: what has gone wrong with networking in ascii?
Quoting Hendrik Boom (hend...@topoi.pooq.com): > But I wold like to be able to run wheezy very occasionally -- there's an > application I have that suffered the end-of-days in wheezy -- so I'd > like to find another solution. http://www.enterprisenetworkingplanet.com/netos/article.php/3586546/Nail-Down-Network-Interface-Names-with-ifrename.htm ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Unswapping interface namesRe: (WAS: what has gone wrong with networking in ascii?
On Sunday 15 July 2018 at 22:03:23, Hendrik Boom wrote: > I got all local services, includig wifi, to work. > > The last holdout seems to have been /etc/ppp/peers/dsl-provider > > It would have been fouond with one more *: /etc/*/*/* > If this message gets out, it worked. Well done :) Antony. -- A few words to be cautious of between American and English: - momentarily - suspenders - chips - pants - jelly - pavement - vest - pint (and gallon) - pissed Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Unswapping interface namesRe: (WAS: what has gone wrong with networking in ascii?
Hendrik Boom wrote on 15.07.2018 22:03: [...] > And I found a number of other eth's in /etc/* and /etc/*/* using grep. [...] > It would have been fouond with one more *: /etc/*/*/* Hi Hendrik, you may find that using grep's -r or -R option can make your life a lot easier. Quoting the man page: -r, --recursive Read all files under each directory, recursively, following symbolic links only if they are on the command line. Note that if no file operand is given, grep searches the working directory.This is equivalent to the -d recurse option. -R, --dereference-recursive Read all files under each directory, recursively. Follow all symbolic links, unlike -r. HTH, best regards Urban -- Sapere aude! signature.asc Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Unswapping interface namesRe: (WAS: what has gone wrong with networking in ascii?
On Sun, Jul 15, 2018 at 09:31:25PM +0200, Stefan Krusche wrote: > Am Sonntag, 15. Juli 2018 schrieb Hendrik Boom: > > But there is a /etc/udev/rules.d/70-persistent-net.rules > > so I'll try editing that. > > That is the one, or at least one you can use. Just change the interface names > with keyword NAME="net0" (for example) to your liking and paired with your > desired MAC address. > > Then change interface names accordingly in /etc/network/interfaces. And I found a number of other eth's in /etc/* and /etc/*/* using grep. Most were comments, but some were live. I got all local services, includig wifi, to work. The last holdout seems to have been /etc/ppp/peers/dsl-provider It would have been fouond with one more *: /etc/*/*/* If this message gets out, it worked. -- hendrik > > Have a look for more detailed explanations at man udev(7). > > Kind regards, > Stefan > > > > ___ > 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] Unswapping interface namesRe: (WAS: what has gone wrong with networking in ascii?
On Sun, Jul 15, 2018 at 09:31:25PM +0200, Stefan Krusche wrote: > Am Sonntag, 15. Juli 2018 schrieb Hendrik Boom: > > But there is a /etc/udev/rules.d/70-persistent-net.rules > > so I'll try editing that. > > That is the one, or at least one you can use. Just change the interface names > with keyword NAME="net0" (for example) to your liking and paired with your > desired MAC address. > > Then change interface names accordingly in /etc/network/interfaces. And, presumably, grep /etc/* and /etc/*/* for every mention of "eth" anywhere. And in any other scripts I've written myself. I've now achieved LAN connectivity but not yet external internet connectivity via pppoe. It looks as if there are a few more to track down. -- hendrik > > Have a look for more detailed explanations at man udev(7). > > Kind regards, > Stefan > > > > ___ > 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] Unswapping interface namesRe: (WAS: what has gone wrong with networking in ascii?
Am Sonntag, 15. Juli 2018 schrieb Hendrik Boom: > But there is a /etc/udev/rules.d/70-persistent-net.rules > so I'll try editing that. That is the one, or at least one you can use. Just change the interface names with keyword NAME="net0" (for example) to your liking and paired with your desired MAC address. Then change interface names accordingly in /etc/network/interfaces. Have a look for more detailed explanations at man udev(7). Kind regards, Stefan ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Unswapping interface namesRe: (WAS: what has gone wrong with networking in ascii?
On 2018-07-15 13:37, Hendrik Boom wrote: On Sun, Jul 15, 2018 at 02:27:26PM -0400, Hendrik Boom wrote: On Sun, Jul 15, 2018 at 12:41:21PM +0200, Udo Hennig wrote: > 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. That seems to be what happened here. > 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. Those files done't seem to exists in my /etc. But there is a /etc/udev/rules.d/70-persistent-net.rules so I'll try editing that. -- hendrik You might want to look at this thread: https://dev1galaxy.org/viewtopic.php?id=2216 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Unswapping interface namesRe: (WAS: what has gone wrong with networking in ascii?
On Sun, Jul 15, 2018 at 02:27:26PM -0400, Hendrik Boom wrote: > On Sun, Jul 15, 2018 at 12:41:21PM +0200, Udo Hennig wrote: > > 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. > > That seems to be what happened here. > > > 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. > > Those files done't seem to exists in my /etc. But there is a /etc/udev/rules.d/70-persistent-net.rules so I'll try editing that. > > -- 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
[DNG] Unswapping interface namesRe: (WAS: what has gone wrong with networking in ascii?
On Sun, Jul 15, 2018 at 12:41:21PM +0200, Udo Hennig wrote: > 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. That seems to be what happened here. > 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. Those files done't seem to exists in my /etc. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] ethernet interface name swap (WAS: what has gone wrong with networking in ascii?
On Sat, Jul 14, 2018 at 07:03:13PM +0200, Stefan Krusche wrote: > 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? The MAC addresses got swapped. Or rather, I suppose, the deignation eth0 and eth1 got swapped. I seem to remember somethign like that happened to me ten or fifteen years ago. Long enough ago that I forgot that this was a thing that might happen. That time I swapped the ethernet cables. But I wold like to be able to run wheezy very occasionally -- there's an application I have that suffered the end-of-days in wheezy -- so I'd like to find another solution. I suppose I'll have to find a way to define new device names for the physical ports and use those in all my configurations. Finding all explicit references to eth0 and eth1 in /etc is probably the esy part. I'm not sure how to time interfaces to physical ports. Some black magic incolcing udev? or vdev? or any of Devuan's udev replacements? -- hendrik > > Kind regards, > Stefan > > ___ > 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?
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] Web browser needed
Ralph Ronnquist wrote: >> Since the HTTPS certification principle is based on domain names, it's hard >> to understand in general how routers would be able to hold such certificates >> (installed by vendors), and if they could, what value that would have in >> terms of security. They don't, and it doesn't ! IME, typical home routers tend to give the local lan a TLD like ".lan", and when offline have a nasty "user friendly" feature or screwing with the DNS to point the user's browsers at something like router.lan which resolves to itself. Thus the router only needs a cert for router.lan - which as Adam points out is worthless for security since anyone could extract the private keys from a firmware update image. And in practice, I doubt that the cert ever gets renewed - by the time it expires, the vendor will consider the model obsolete. Adam Borowski wrote: > The only problem here is renewal of those certs -- a router that was offline > for a while or is in a network that doesn't allow phoning home risks having > its cert expire. As above, I doubt if many, if any, actually bother to update the cert. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] data reliability (was: Home server replacement hardware suggestions?)
On Sat, 7 Jul 2018 20:56:46 -0700 spiralofhope wrote: > I understand there are problems with USB sticks, but what's wrong with > that connection for a drive? (assuming cabling won't get kicked > out) This isn't Devuan-related, but as I had been given a flat dictate I did some research and hoped to bend an ear on this. What I can tell these are the main issues: - Storage reliability - Storage temperature (e.g. sustained-usage storage is not properly cooled and will cook) - Temperature of the USB area itself - Frail cabling or seating of the device - Device removal without unmounting/ejecting - Device removal while the device/area is hot So for a low-quality server, it seems to me that this is the chain: computer -> usb 3.1 -> drive (dock) The only problems I would have with this are: - Temperature of the USB area on the computer - eSata adapter or USB dock trustworthiness - Hard drive cooling (Is a passively-cooled vertical drive okay?) Am I missing something? With backups, I'd be fine with the above risks. Also, I reproduced a heat issue with the worst offender and worst conditions I could manage.. a shit usb 2.0 key in a 3.1 port situated above a battery. Heat issues were solved using either a cable or a hub. I can only guess why that worked.. -- An M.2 to SATA hack was mentioned, but basic searching for a simple conversion method came up dry. I'll keep that in mind for when I retire my low-end laptop and convert it into a torrent box. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
