Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #201420 > unrolled thread

Migrating Debian installation to a new motherboard

Back to article view | Back to linux.debian.user

Contents

  Migrating Debian installation to a new motherboard local10 <local10@tutanota.com> - 2018-10-18 23:40 +0200
    Re: Migrating Debian installation to a new motherboard Felix Miata <mrmazda@earthlink.net> - 2018-10-19 00:50 +0200
      Re: Migrating Debian installation to a new motherboard local10 <local10@tutanota.com> - 2018-10-19 01:20 +0200
        Re: Migrating Debian installation to a new motherboard local10 <local10@tutanota.com> - 2018-10-31 17:40 +0100
        Re: Migrating Debian installation to a new motherboard local10 <local10@tutanota.com> - 2018-10-31 21:20 +0100
          Re: Migrating Debian installation to a new motherboard Dan Ritter <dsr@randomstring.org> - 2018-10-31 23:10 +0100
            Re: Migrating Debian installation to a new motherboard local10 <local10@tutanota.com> - 2018-10-31 23:50 +0100
              Re: Migrating Debian installation to a new motherboard Michael Stone <mstone@debian.org> - 2018-11-01 00:40 +0100
                Re: Migrating Debian installation to a new motherboard local10 <local10@tutanota.com> - 2018-11-01 15:20 +0100
                  Re: Migrating Debian installation to a new motherboard Pascal Hambourg <pascal@plouf.fr.eu.org> - 2018-11-01 15:20 +0100
                    Re: Migrating Debian installation to a new motherboard local10 <local10@tutanota.com> - 2018-11-01 17:20 +0100
                      Re: Migrating Debian installation to a new motherboard Dan Ritter <dsr@randomstring.org> - 2018-11-01 17:20 +0100
                        Re: Migrating Debian installation to a new motherboard local10 <local10@tutanota.com> - 2018-11-01 17:50 +0100
                          Re: Migrating Debian installation to a new motherboard Michael Stone <mstone@debian.org> - 2018-11-01 19:00 +0100
                            [SOLVED] Re: Migrating Debian installation to a new motherboard local10 <local10@tutanota.com> - 2018-11-01 19:30 +0100
                              Re: [SOLVED] Re: Migrating Debian installation to a new motherboard Brian <ad44@cityscape.co.uk> - 2018-11-01 20:10 +0100
                              Re: [SOLVED] Re: Migrating Debian installation to a new motherboard Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2018-11-02 03:30 +0100
                                Re: [SOLVED] Re: Migrating Debian installation to a new motherboard David Wright <deblis@lionunicorn.co.uk> - 2018-11-02 04:20 +0100
                                  Re: [SOLVED] Re: Migrating Debian installation to a new motherboard Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2018-11-02 05:00 +0100
                                  Re: [SOLVED] Re: Migrating Debian installation to a new motherboard Michael Stone <mstone@debian.org> - 2018-11-02 12:10 +0100
                                    Re: [SOLVED] Re: Migrating Debian installation to a new motherboard David Wright <deblis@lionunicorn.co.uk> - 2018-11-03 02:30 +0100
                                      Re: [SOLVED] Re: Migrating Debian installation to a new motherboard David Christensen <dpchrist@holgerdanske.com> - 2018-11-03 04:20 +0100
                                        Re: [SOLVED] Re: Migrating Debian installation to a new motherboard David Wright <deblis@lionunicorn.co.uk> - 2018-11-03 05:00 +0100
                                          Re: [SOLVED] Re: Migrating Debian installation to a new motherboard David Christensen <dpchrist@holgerdanske.com> - 2018-11-03 07:10 +0100
                                            Re: [SOLVED] Re: Migrating Debian installation to a new motherboard David Wright <deblis@lionunicorn.co.uk> - 2018-11-04 16:30 +0100
                                              Re: [SOLVED] Re: Migrating Debian installation to a new motherboard David Christensen <dpchrist@holgerdanske.com> - 2018-11-05 01:50 +0100
                                                Re: [SOLVED] Re: Migrating Debian installation to a new motherboard David Wright <deblis@lionunicorn.co.uk> - 2018-11-05 16:20 +0100
                                                Re: [SOLVED] Re: Migrating Debian installation to a new motherboard Celejar <celejar@gmail.com> - 2018-11-05 19:50 +0100
                            Re: Migrating Debian installation to a new motherboard mick crane <mick.crane@gmail.com> - 2018-11-02 08:30 +0100
                              Re: Migrating Debian installation to a new motherboard Felix Miata <mrmazda@earthlink.net> - 2018-11-02 08:40 +0100
                                Re: Migrating Debian installation to a new motherboard mick crane <mick.crane@gmail.com> - 2018-11-02 09:00 +0100
                                  Re: Migrating Debian installation to a new motherboard Curt <curty@free.fr> - 2018-11-02 10:00 +0100
                                  Re: Migrating Debian installation to a new motherboard Michael Stone <mstone@debian.org> - 2018-11-02 12:20 +0100
                                    Re: Migrating Debian installation to a new motherboard mick crane <mick.crane@gmail.com> - 2018-11-03 03:00 +0100
                                      Re: Migrating Debian installation to a new motherboard Michael Stone <mstone@debian.org> - 2018-11-03 12:50 +0100
                                        Re: Migrating Debian installation to a new motherboard Curt <curty@free.fr> - 2018-11-03 18:30 +0100
                                          Re: Migrating Debian installation to a new motherboard Michael Stone <mstone@debian.org> - 2018-11-03 19:10 +0100
                              Re: Migrating Debian installation to a new motherboard Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2018-11-03 05:10 +0100
                      Re: Migrating Debian installation to a new motherboard Michael Stone <mstone@debian.org> - 2018-11-01 19:00 +0100
    Re: Migrating Debian installation to a new motherboard Patrick Bartek <nemommxiv@gmail.com> - 2018-10-19 18:50 +0200
    Re: Migrating Debian installation to a new motherboard songbird <songbird@anthive.com> - 2018-10-20 00:50 +0200

Page 2 of 3 — ← Prev page 1 [2] 3  Next page →

#202003 — Re: [SOLVED] Re: Migrating Debian installation to a new motherboard

On Fri 02 Nov 2018 at 07:05:16 (-0400), Michael Stone wrote:
> On Thu, Nov 01, 2018 at 10:12:36PM -0500, David Wright wrote:
> > BTW in a network set up like my own, the place where the MAC would be
> > relevant is in the DHCP server (here, the router) because that is how
> > the IP number is assigned. An unassigned MAC will get given an IP
> > address 192.168.1.200+, and it will conect to the Internet, but other
> > machines on the LAN would not recognise it. (Although the router can
> > hand out IP numbers, it doesn't run a nameserver.)
> 
> If you do something strange on your network, the assumption is that
> you're responsible for updating it for new machines. It's not
> something that needs to be in a general guide.

I agree with that sentiment. But what is strange about my setup?
Perhaps you can help me find a less idiosyncratic way.

Condition #1: All devices at home must be addressable by name.
Condition #2: Several devices cannot have a static IP address assigned.
For example, this PC is 192.168.1.17 at home. Currently it is 172.20.5.105;
last night it was 10.0.27.15.

So at home, all the IP addresses are assigned by the router using the
devices' MACs. The computers use /etc/hosts to look up other devices.
The non-"computers" use the router's IP address for their configuration.

What would you change?

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#202008 — Re: [SOLVED] Re: Migrating Debian installation to a new motherboard

On 11/2/18 6:24 PM, David Wright wrote:
> On Fri 02 Nov 2018 at 07:05:16 (-0400), Michael Stone wrote:
>> On Thu, Nov 01, 2018 at 10:12:36PM -0500, David Wright wrote:
>>> BTW in a network set up like my own, the place where the MAC would be
>>> relevant is in the DHCP server (here, the router) because that is how
>>> the IP number is assigned. An unassigned MAC will get given an IP
>>> address 192.168.1.200+, and it will conect to the Internet, but other
>>> machines on the LAN would not recognise it. (Although the router can
>>> hand out IP numbers, it doesn't run a nameserver.)
>>
>> If you do something strange on your network, the assumption is that
>> you're responsible for updating it for new machines. It's not
>> something that needs to be in a general guide.
> 
> I agree with that sentiment. But what is strange about my setup?
> Perhaps you can help me find a less idiosyncratic way.
> 
> Condition #1: All devices at home must be addressable by name.
> Condition #2: Several devices cannot have a static IP address assigned.
> For example, this PC is 192.168.1.17 at home. Currently it is 172.20.5.105;
> last night it was 10.0.27.15.
> 
> So at home, all the IP addresses are assigned by the router using the
> devices' MACs. The computers use /etc/hosts to look up other devices.
> The non-"computers" use the router's IP address for their configuration.
> 
> What would you change?

Buy or build a router with a caching name server that integrates with 
the DHCP server.  Configure the LAN devices to use DHCP.  Set DHCP fixed 
leases on the router for devices that require a static IP.


David

[toc] | [prev] | [next] | [standalone]

#202010 — Re: [SOLVED] Re: Migrating Debian installation to a new motherboard

On Fri 02 Nov 2018 at 20:11:03 (-0700), David Christensen wrote:
> On 11/2/18 6:24 PM, David Wright wrote:
> > On Fri 02 Nov 2018 at 07:05:16 (-0400), Michael Stone wrote:
> > > On Thu, Nov 01, 2018 at 10:12:36PM -0500, David Wright wrote:
> > > > BTW in a network set up like my own, the place where the MAC would be
> > > > relevant is in the DHCP server (here, the router) because that is how
> > > > the IP number is assigned. An unassigned MAC will get given an IP
> > > > address 192.168.1.200+, and it will conect to the Internet, but other
> > > > machines on the LAN would not recognise it. (Although the router can
> > > > hand out IP numbers, it doesn't run a nameserver.)
> > > 
> > > If you do something strange on your network, the assumption is that
> > > you're responsible for updating it for new machines. It's not
> > > something that needs to be in a general guide.
> > 
> > I agree with that sentiment. But what is strange about my setup?
> > Perhaps you can help me find a less idiosyncratic way.
> > 
> > Condition #1: All devices at home must be addressable by name.
> > Condition #2: Several devices cannot have a static IP address assigned.
> > For example, this PC is 192.168.1.17 at home. Currently it is 172.20.5.105;
> > last night it was 10.0.27.15.
> > 
> > So at home, all the IP addresses are assigned by the router using the
> > devices' MACs. The computers use /etc/hosts to look up other devices.
> > The non-"computers" use the router's IP address for their configuration.
> > 
> > What would you change?
> 
> Buy or build a router with a caching name server that integrates with
> the DHCP server.  Configure the LAN devices to use DHCP.  Set DHCP
> fixed leases on the router for devices that require a static IP.

You misunderstood my question. I'm meant to have done something
"strange" with my network and wanted to know how to "rectify" the
situation, not how to throw cash at it.

BTW all the devices are currently configured using DHCP; that's what
I meant by "assigned by the router".

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#202012 — Re: [SOLVED] Re: Migrating Debian installation to a new motherboard

On 11/2/18 8:49 PM, David Wright wrote:
> On Fri 02 Nov 2018 at 20:11:03 (-0700), David Christensen wrote:
>> On 11/2/18 6:24 PM, David Wright wrote:
>>> On Fri 02 Nov 2018 at 07:05:16 (-0400), Michael Stone wrote:
>>>> On Thu, Nov 01, 2018 at 10:12:36PM -0500, David Wright wrote:
>>>>> BTW in a network set up like my own, the place where the MAC would be
>>>>> relevant is in the DHCP server (here, the router) because that is how
>>>>> the IP number is assigned. An unassigned MAC will get given an IP
>>>>> address 192.168.1.200+, and it will conect to the Internet, but other
>>>>> machines on the LAN would not recognise it. (Although the router can
>>>>> hand out IP numbers, it doesn't run a nameserver.)
>>>>
>>>> If you do something strange on your network, the assumption is that
>>>> you're responsible for updating it for new machines. It's not
>>>> something that needs to be in a general guide.
>>>
>>> I agree with that sentiment. But what is strange about my setup?
>>> Perhaps you can help me find a less idiosyncratic way.
>>>
>>> Condition #1: All devices at home must be addressable by name.
>>> Condition #2: Several devices cannot have a static IP address assigned.
>>> For example, this PC is 192.168.1.17 at home. Currently it is 172.20.5.105;
>>> last night it was 10.0.27.15.
>>>
>>> So at home, all the IP addresses are assigned by the router using the
>>> devices' MACs. The computers use /etc/hosts to look up other devices.
>>> The non-"computers" use the router's IP address for their configuration.
>>>
>>> What would you change?
>>
>> Buy or build a router with a caching name server that integrates with
>> the DHCP server.  Configure the LAN devices to use DHCP.  Set DHCP
>> fixed leases on the router for devices that require a static IP.
> 
> You misunderstood my question. I'm meant to have done something
> "strange" with my network and wanted to know how to "rectify" the
> situation, not how to throw cash at it.
> 
> BTW all the devices are currently configured using DHCP; that's what
> I meant by "assigned by the router".

What is strange is that your router does not have a caching name server 
that integrates with the DHCP server.  This is a common and useful 
feature.  Not having it forces work-around's like putting LAN host IP's 
into the /etc/hosts files of every other LAN host, which is a PITA to 
maintain.  Alternatively, implement your own integrated DHCP server and 
caching DNS server.


Low-cost solutions include:

1.  Router appliance -- re-flashing the firmware with a FOSS firmware 
distribution like DD-WRT.

2.  Home-brew router using a PC -- installing a second NIC and a Linux 
or BSD router distribution like IPCop or pfSense.


I tried the former on an older Netgear device and it worked.  But when I 
later tried to flash an upgrade, I bricked it.


I ran home-brew PC routers for years.  This approach gives you the most 
control, and pfSense rocks.  But, I burned up a lot of energy, made a 
lot of noise, and generated a lot of heat.  Unfortunately, ITX PC's with 
dual NIC's are too expensive.


So, I researched commercial products, asked around on Linux and BSD 
lists, and bought Ubiquiti Networks UniFi stuff:

     https://www.ubnt.com/unifi-routing/usg/

     https://www.ubnt.com/unifi/unifi-ap-ac-lite/


I run the UniFi SDN Controller server on Debian:

     https://www.ubnt.com/download/unifi/


What do you mean by "The non-"computers" use the router's IP address for 
their configuration"?


David

[toc] | [prev] | [next] | [standalone]

#202101 — Re: [SOLVED] Re: Migrating Debian installation to a new motherboard

On Fri 02 Nov 2018 at 23:09:02 (-0700), David Christensen wrote:
> On 11/2/18 8:49 PM, David Wright wrote:
> > On Fri 02 Nov 2018 at 20:11:03 (-0700), David Christensen wrote:
> > > On 11/2/18 6:24 PM, David Wright wrote:
> > > > On Fri 02 Nov 2018 at 07:05:16 (-0400), Michael Stone wrote:
> > > > > On Thu, Nov 01, 2018 at 10:12:36PM -0500, David Wright wrote:
> > > > > > BTW in a network set up like my own, the place where the MAC would be
> > > > > > relevant is in the DHCP server (here, the router) because that is how
> > > > > > the IP number is assigned. An unassigned MAC will get given an IP
> > > > > > address 192.168.1.200+, and it will conect to the Internet, but other
> > > > > > machines on the LAN would not recognise it. (Although the router can
> > > > > > hand out IP numbers, it doesn't run a nameserver.)
> > > > > 
> > > > > If you do something strange on your network, the assumption is that
> > > > > you're responsible for updating it for new machines. It's not
> > > > > something that needs to be in a general guide.
> > > > 
> > > > I agree with that sentiment. But what is strange about my setup?
> > > > Perhaps you can help me find a less idiosyncratic way.
> > > > 
> > > > Condition #1: All devices at home must be addressable by name.
> > > > Condition #2: Several devices cannot have a static IP address assigned.
> > > > For example, this PC is 192.168.1.17 at home. Currently it is 172.20.5.105;
> > > > last night it was 10.0.27.15.
> > > > 
> > > > So at home, all the IP addresses are assigned by the router using the
> > > > devices' MACs. The computers use /etc/hosts to look up other devices.
> > > > The non-"computers" use the router's IP address for their configuration.
> > > > 
> > > > What would you change?
> > > 
> > > Buy or build a router with a caching name server that integrates with
> > > the DHCP server.  Configure the LAN devices to use DHCP.  Set DHCP
> > > fixed leases on the router for devices that require a static IP.
> > 
> > You misunderstood my question. I'm meant to have done something
> > "strange" with my network and wanted to know how to "rectify" the
> > situation, not how to throw cash at it.
> > 
> > BTW all the devices are currently configured using DHCP; that's what
> > I meant by "assigned by the router".
> 
> What is strange is that your router does not have a caching name
> server that integrates with the DHCP server.

Eh? None of the consumer-grade routers that I've run have had any DNS
server, but they have all had a DHCP service.

> This is a common and
> useful feature.

… which you pay for with a more expensive device.

> Not having it forces work-around's like putting LAN
> host IP's into the /etc/hosts files of every other LAN host, which is
> a PITA to maintain.

It might be for you. Propogating it from my master copy is trivial
(with the right scripts), and updating it is hardly onerous when there
are fewer than two changes per year over the last five years.

> Alternatively, implement your own integrated DHCP
> server and caching DNS server.
> 
> Low-cost solutions include:
> 
> 1.  Router appliance -- re-flashing the firmware with a FOSS firmware
> distribution like DD-WRT.
> 
> 2.  Home-brew router using a PC -- installing a second NIC and a Linux
> or BSD router distribution like IPCop or pfSense.

So the general opinion held around here is that it's "strange" not to
adopt one of these solutions on a home LAN. Really?

> I tried the former on an older Netgear device and it worked.  But when
> I later tried to flash an upgrade, I bricked it.

Great, just what I want to do. Not.

> I ran home-brew PC routers for years.  This approach gives you the
> most control, and pfSense rocks.  But, I burned up a lot of energy,
> made a lot of noise, and generated a lot of heat.  Unfortunately, ITX
> PC's with dual NIC's are too expensive.

Fine if someone else is paying the electricity and AC bills.

> So, I researched commercial products, asked around on Linux and BSD
> lists, and bought Ubiquiti Networks UniFi stuff:
> 
>     https://www.ubnt.com/unifi-routing/usg/
> 
>     https://www.ubnt.com/unifi/unifi-ap-ac-lite/
> 
> 
> I run the UniFi SDN Controller server on Debian:
> 
>     https://www.ubnt.com/download/unifi/

Most of the eye-watering prices have 3 or 4 figures. Wouldn't it be
"strange" to be running this enterprise-grade kit on a home LAN?

> What do you mean by "The non-"computers" use the router's IP address
> for their configuration"?

The wireless ones need the SSID and PSK but the wired ones are
directly or indirectly connected to the router. However, the printer
(using WiFi) tries to set up some sort of ad hoc networking which
screws things up. IIRC (I'm not at home) I have to point it at the
router's address in some way. But these things are never well
documented; you're either meant to follow instructions on a tiny
display or be using some Windows or Mac software.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#202118 — Re: [SOLVED] Re: Migrating Debian installation to a new motherboard

On 11/4/18 7:25 AM, David Wright wrote:
> On Fri 02 Nov 2018 at 23:09:02 (-0700), David Christensen wrote:
>> ... I researched commercial products, asked around on Linux and
>> BSD lists, and bought Ubiquiti Networks UniFi stuff: ...
> 
> Most of the eye-watering prices have 3 or 4 figures.

Checking prices on amazon.com and ubnt.com:

- Ubiquiti Unifi Security Gateway $119.00

- Ubiquiti Unifi Ap-AC Lite $77.90

- UniFi SDN Controller 5.9.29 for Debian/Ubuntu Linux $Free-as-in-Beer

Total: $196.90


The mini-ITX boxes are still too expensive:

- https://www.amazon.com/dp/B008KB5YCK/ $279.95

- WiFi AP $???

- pfSense 2.4.4 $Free-as-in-Freedom

Total: $279.95 + Access Point


The Netgate SG-1000 microFirewall Security Appliance with pfSense has a 
very aggressive price:

- https://store.netgate.com/SG-1000.aspx $149.00

- WiFi AP $???

- pfSense included $Free-as-in-Freedom

Total: $149.00 + Access Point


> Wouldn't it be "strange" to be running this enterprise-grade kit on a
> home LAN?

As I understand it, UniFi's value proposition is that their "Software 
Defined Network" is better/ faster/ cheaper to configure, operate, and 
maintain for large, multi-site, wired, and wireless network installations.


If you have ever tried to configure multiple routers and AP's in 
multiple LAN's connected by VPN's over the Internet, each via it's own 
web interface, UniFi's proposition becomes very appealing.


Right now, I only have one router and one AP on my LAN.  Even for my 
tiny installation, UniFi is better than my previous high-end consumer/ 
low-end professional Netgear products.  If and when I need to support 
remote LAN's over VPN's, UniFi should only get better.


David

[toc] | [prev] | [next] | [standalone]

#202145 — Re: [SOLVED] Re: Migrating Debian installation to a new motherboard

On Sun 04 Nov 2018 at 16:42:41 (-0800), David Christensen wrote:
> On 11/4/18 7:25 AM, David Wright wrote:
> > On Fri 02 Nov 2018 at 23:09:02 (-0700), David Christensen wrote:
> > > ... I researched commercial products, asked around on Linux and
> > > BSD lists, and bought Ubiquiti Networks UniFi stuff: ...
> > 
> > Most of the eye-watering prices have 3 or 4 figures.
> 
> Checking prices on amazon.com and ubnt.com:
> […]
> Total: $196.90
> […]
> Total: $279.95 + Access Point
> […]
> Total: $149.00 + Access Point

… and my router cost $38.10 at Walmart (May 2018 prices).

> > Wouldn't it be "strange" to be running this enterprise-grade kit on a
> > home LAN?
> 
> As I understand it, UniFi's value proposition is that their "Software
> Defined Network" is better/ faster/ cheaper to configure, operate, and
> maintain for large, multi-site, wired, and wireless network
> installations.

Perhaps I'll be able to call my house multi-site if/when I run a router
in each half. :)

> If you have ever tried to configure multiple routers and AP's in
> multiple LAN's connected by VPN's over the Internet, each via it's own
> web interface, UniFi's proposition becomes very appealing.

Yes, that sounds like enterprise-scale.

> Right now, I only have one router and one AP on my LAN.  Even for my
> tiny installation, UniFi is better than my previous high-end consumer/
> low-end professional Netgear products.  If and when I need to support
> remote LAN's over VPN's, UniFi should only get better.

I think I'll rest assured that there's nothing "strange" about the
setup that I described apart, perhaps, from the amount of money I'm
prepared to spend on it, which is the minimum to provide the
functionality I need, listed earlier.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#202157 — Re: [SOLVED] Re: Migrating Debian installation to a new motherboard

On Sun, 4 Nov 2018 16:42:41 -0800
David Christensen <dpchrist@holgerdanske.com> wrote:

> On 11/4/18 7:25 AM, David Wright wrote:
> > On Fri 02 Nov 2018 at 23:09:02 (-0700), David Christensen wrote:
> >> ... I researched commercial products, asked around on Linux and
> >> BSD lists, and bought Ubiquiti Networks UniFi stuff: ...
> > 
> > Most of the eye-watering prices have 3 or 4 figures.
> 
> Checking prices on amazon.com and ubnt.com:
> 
> - Ubiquiti Unifi Security Gateway $119.00
> 
> - Ubiquiti Unifi Ap-AC Lite $77.90
> 
> - UniFi SDN Controller 5.9.29 for Debian/Ubuntu Linux $Free-as-in-Beer
> 
> Total: $196.90
> 
> 
> The mini-ITX boxes are still too expensive:
> 
> - https://www.amazon.com/dp/B008KB5YCK/ $279.95
> 
> - WiFi AP $???
> 
> - pfSense 2.4.4 $Free-as-in-Freedom
> 
> Total: $279.95 + Access Point
> 
> 
> The Netgate SG-1000 microFirewall Security Appliance with pfSense has a 
> very aggressive price:
> 
> - https://store.netgate.com/SG-1000.aspx $149.00
> 
> - WiFi AP $???
> 
> - pfSense included $Free-as-in-Freedom
> 
> Total: $149.00 + Access Point

Or (depending on one's specific needs, of course), just get something
from one of these threads:

https://forum.openwrt.org/t/best-wireless-ac-router-for-lede/24551
https://forum.openwrt.org/t/whats-your-favourite-cheap-lede-openwrt-device/1362

It helps to enjoy tinkering and DIY, of course ;)

> If you have ever tried to configure multiple routers and AP's in 
> multiple LAN's connected by VPN's over the Internet, each via it's own 
> web interface, UniFi's proposition becomes very appealing.

Using OpenWrt devices, you can use the cli in addition the
(standardized) web interface.

> Right now, I only have one router and one AP on my LAN.  Even for my 
> tiny installation, UniFi is better than my previous high-end consumer/ 
> low-end professional Netgear products.  If and when I need to support 
> remote LAN's over VPN's, UniFi should only get better.

I know that the possibility of bricking devices when flashing alternate
firmware was mentioned earlier in this thread, but if you get devices
with solid OpenWrt support, flashing is quite easy and safe, and it's
amazing what you can do with them once they're running OpenWrt.

Celejar

[toc] | [prev] | [next] | [standalone]

#201983

On 2018-11-01 17:57, Michael Stone wrote:
> On Thu, Nov 01, 2018 at 05:43:56PM +0100, local10 wrote:
>> Under enp3so I see only BROADCAST and MULTICAST, no UP or DOWN. Thanks
> 
> That means it's down. Note that you said enp3so above, that should be
> enp3s0 (zero); which did you put in interfaces? Also, there should be
> either "auto enp3s0" or "allow-hotplug enp3s0". Assuming that's all
> right, try manually running "ifup -v enp3s0".

I have to do a double check with "l" and "1" and "0" and "O", there 
ought to be some way to avoid that.

-- 
Key ID    4BFEBB31

[toc] | [prev] | [next] | [standalone]

#201984

mick crane composed on 2018-11-02 07:22 (UTC):

> I have to do a double check with "l" and "1" and "0" and "O", there 
> ought to be some way to avoid that.

Font selection can make a big difference:

	http://fm.no-ip.com/Auth/Font/fonts-face-samplesM.html
-- 
Evolution as taught in public schools is religion, not science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#201985

On 2018-11-02 07:37, Felix Miata wrote:
> mick crane composed on 2018-11-02 07:22 (UTC):
> 
>> I have to do a double check with "l" and "1" and "0" and "O", there
>> ought to be some way to avoid that.
> 
> Font selection can make a big difference:
> 
> 	http://fm.no-ip.com/Auth/Font/fonts-face-samplesM.html

The 0 with a line through it helps but l still looks like 1.
maybe if l at the end of a filename use L
-- 
Key ID    4BFEBB31

[toc] | [prev] | [next] | [standalone]

#201986

On 2018-11-02, mick crane <mick.crane@gmail.com> wrote:
> On 2018-11-02 07:37, Felix Miata wrote:
>> mick crane composed on 2018-11-02 07:22 (UTC):
>> 
>>> I have to do a double check with "l" and "1" and "0" and "O", there
>>> ought to be some way to avoid that.
>> 
>> Font selection can make a big difference:
>> 
>> 	http://fm.no-ip.com/Auth/Font/fonts-face-samplesM.html
>
> The 0 with a line through it helps but l still looks like 1.
> maybe if l at the end of a filename use L

When I spell my name over the phone to various interlocutors who have
trouble either with my foreign patronym, my foreign accent, or both, I
say "l" as in Louise.

I often wonder if it's uncomfortable for Louise to have an l in her
like that, but whatever. 

The creative possibilities of this system are quite large and allow you
to slyly express any number of notions under seemingly innocent
orthographic cover.

-- 
When you have fever you are heavy and light, you are small and swollen, you
climb endlessly a ladder which turns like a wheel. 
--Jean Rhys, Voyage in the Dark

[toc] | [prev] | [next] | [standalone]

#201989

On Fri, Nov 02, 2018 at 07:58:23AM +0000, mick crane wrote:
>The 0 with a line through it helps but l still looks like 1.

That's still a font selection issue--in the font I'm using it's hard to 
confuse the two. (l has an arc of stem to the bottom right, 1 has 
straight bilateral serifs. l has a straight left serif on the ascender, 
1 has an angled serif.)

[toc] | [prev] | [next] | [standalone]

#202004

On 2018-11-02 11:15, Michael Stone wrote:
> On Fri, Nov 02, 2018 at 07:58:23AM +0000, mick crane wrote:
>> The 0 with a line through it helps but l still looks like 1.
> 
> That's still a font selection issue--in the font I'm using it's hard
> to confuse the two. (l has an arc of stem to the bottom right, 1 has
> straight bilateral serifs. l has a straight left serif on the
> ascender, 1 has an angled serif.)

well I don't know.
what font you use then. ?
what I do is paste into a text editor and compare fonts if think that is 
why not working because I confused my "O"s with my "l"'s
-- 
Key ID    4BFEBB31

[toc] | [prev] | [next] | [standalone]

#202019

On Sat, Nov 03, 2018 at 01:54:32AM +0000, mick crane wrote:
>On 2018-11-02 11:15, Michael Stone wrote:
>>On Fri, Nov 02, 2018 at 07:58:23AM +0000, mick crane wrote:
>>>The 0 with a line through it helps but l still looks like 1.
>>
>>That's still a font selection issue--in the font I'm using it's hard
>>to confuse the two. (l has an arc of stem to the bottom right, 1 has
>>straight bilateral serifs. l has a straight left serif on the
>>ascender, 1 has an angled serif.)
>
>well I don't know.
>what font you use then. ?

Two packages to check out are fonts-hack and fonts-go

[toc] | [prev] | [next] | [standalone]

#202034

On 2018-11-03, Michael Stone <mstone@debian.org> wrote:
> On Sat, Nov 03, 2018 at 01:54:32AM +0000, mick crane wrote:
>>On 2018-11-02 11:15, Michael Stone wrote:
>>>On Fri, Nov 02, 2018 at 07:58:23AM +0000, mick crane wrote:
>>>>The 0 with a line through it helps but l still looks like 1.
>>>
>>>That's still a font selection issue--in the font I'm using it's hard
>>>to confuse the two. (l has an arc of stem to the bottom right, 1 has
>>>straight bilateral serifs. l has a straight left serif on the
>>>ascender, 1 has an angled serif.)
>>
>>well I don't know.
>>what font you use then. ?
>
> Two packages to check out are fonts-hack and fonts-go
>
>

Actually the fonts-hack package doesn't exist here.

I do find, however:

fonts-hack-otf - Typeface designed for source code, OpenType fonts
fonts-hack-ttf - Typeface designed for source code, TrueType fonts
fonts-hack-web - Typeface designed for source code, Web fonts

fonts-go is good to go, though.

I'm personally using andale in an xterm and have no problems
distinguishing between the l as in Louise and the 1 as in wonderful.

(I must've installed the Microsoft ttf core fonts quite a while back,
because my memory of that event is vague. I was unaware of the existence
of fonts-hack* until a moment ago.)

-- 
When you have fever you are heavy and light, you are small and swollen, you
climb endlessly a ladder which turns like a wheel. 
--Jean Rhys, Voyage in the Dark

[toc] | [prev] | [next] | [standalone]

#202041

On Sat, Nov 03, 2018 at 05:24:29PM +0000, Curt wrote:
>Actually the fonts-hack package doesn't exist here.
>
>I do find, however:
>
>fonts-hack-otf - Typeface designed for source code, OpenType fonts
>fonts-hack-ttf - Typeface designed for source code, TrueType fonts
>fonts-hack-web - Typeface designed for source code, Web fonts

Sorry, I forgot it was still like that in stretch. Go with 
fonts-hack-ttf

[toc] | [prev] | [next] | [standalone]

#202011

mick crane <mick.crane@gmail.com> writes:

> On 2018-11-01 17:57, Michael Stone wrote:
>> On Thu, Nov 01, 2018 at 05:43:56PM +0100, local10 wrote:
>>> Under enp3so I see only BROADCAST and MULTICAST, no UP or DOWN. Thanks
>>
>> That means it's down. Note that you said enp3so above, that should be
>> enp3s0 (zero); which did you put in interfaces? Also, there should be
>> either "auto enp3s0" or "allow-hotplug enp3s0". Assuming that's all
>> right, try manually running "ifup -v enp3s0".
>
> I have to do a double check with "l" and "1" and "0" and "O", there
> ought to be some way to avoid that.

We live in a world in which our parents' typewriters had no "1" key,
since it looked just like "l".  We need to adapt to that world, and
check.

[toc] | [prev] | [next] | [standalone]

#201972

On Thu, Nov 01, 2018 at 05:12:35PM +0100, local10 wrote:
> http://debian.2.n7.nabble.com/
>Migrating-Debian-installation-to-a-new-motherboard-td4403474.html ) mentioned
>that the MAC address needs to be changed to reflect the new NIC MAC address on
>the new mb.

Ignore that.

[toc] | [prev] | [next] | [standalone]

#201449

On Thu, 18 Oct 2018 23:36:47 +0200 (CEST)
local10 <local10@tutanota.com> wrote:

> Hi,
> 
> Am looking for an easy way to move my Debian PC to a new motherboard,
> that is without reinstalling all the packages and config settings.
> All the hardware with the exception of the motherboard will remain
> the same, I have a spare hard drive, the same model as my working HD,
> which I can use as a setup area if needed. I did a similar migration
> with success some years back and used the "Shockingly easy server
> upgrade" writeup from Debian Planet as guide, which was available at
> http://www.debianplanet.org/node.php?id=875
> <http://www.debianplanet.org/node.php?id=875> but it's no longer
> there and I can't find it.
> 
> Any ideas? Thanks

I've done this several times even going from a 32-bit MB/OS to a 64-bit
one.  Initially all I did was install the old hard drive in the new MB
and boot. System never failed to boot.  Although, I did at times have to
install a different driver or two.

Since you'll be going from a MBR BIOS to a UEFI-type MB which also
supports MBR, I'd turn off Secure Boot, Fastboot (Debian doesn't support
them) and enable Legacy support.  I assume Buster was installed as MBR
boot on the old MB.

Worse that can happen is it doesn't work, and you have search for
another solution.


B

[toc] | [prev] | [next] | [standalone]

Page 2 of 3 — ← Prev page 1 [2] 3  Next page →

Back to top | Article view | linux.debian.user

csiph-web