Re: [Dorset] Monitoring Internet Connectivity.
Hi Patrick On 10/03/2019 01:36, Patrick Wigmore wrote: My experience of RADIUS is limited to being a sometime user of [eduroam][1], which uses it. Thanks for explaining how this could work. If the client can be reliably forced into a particular VLAN or a particular IP address by the access point on the basis of the client's authenticated identity, then it is going to be easy for a router/ firewall to control what the client can access and when. The built in Draytek server allows for setting an IP address and mask and they have a number of help guides which I'll go through. But I'm getting the impression this is a bit OTT for a home network. Cheers Tim -- Next meeting: BEC, Bournemouth, Tuesday, 2019-04-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Cannot open nano in boot a shell
On Sunday, 10 March 2019 17:51:59 GMT Ralph Corderoy wrote: > OK, let's start from scratch. You're at your Pi, not at a desktop. You > find typing `nano' followed by Enter at the shell's prompt gives the > error about the unknown terminal type. > > If you then enter, on one line, `TERM=vt220 nano', and press Enter then > nano should be happy and start up. Exactly. That's what I did and that's what happened. > Here's the left-hand side of the two emails with sdiff(1) showing one > has three more blank lines. > > can recall. | monitor. > > -- -- > > > > Terry Coles Terry Coles Exactly the same here in KMail and in BlueMail -- Terry Coles -- Next meeting: BEC, Bournemouth, Tuesday, 2019-04-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Cannot open nano in boot a shell
Hi Terry, > > I don't understand why `nano' would give that error, and `TERM=vt220 > > nano' would give the same error, yet `TERM=vt220' followed by `nano' > > No. The TERM variable is simply `TERM=vt220'. I don't enter nano > until I type it into the shell. OK, let's start from scratch. You're at your Pi, not at a desktop. You find typing `nano' followed by Enter at the shell's prompt gives the error about the unknown terminal type. If you then enter, on one line, `TERM=vt220 nano', and press Enter then nano should be happy and start up. > > https://www.mail-archive.com/dorset@mailman.lug.org.uk/msg08641.html > > https://www.mail-archive.com/dorset@mailman.lug.org.uk/msg08644.html > > Those two sigs look exactly the same to me in Chromium and in KMail. Here's the left-hand side of the two emails with sdiff(1) showing one has three more blank lines. can recall. | monitor. -- -- Terry Coles Terry Coles > > > -- -- Next meeting: BEC, Bournemouth, Tu Next meeting: BEC, Bournemouth, Tu Check to whom you are replying Check to whom you are replying Meetings, mailing list, IRC, ...Meetings, mailing list, IRC, ... New thread, don't hijack: mailto: New thread, don't hijack: mailto: -- Cheers, Ralph. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-04-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Cannot open nano in boot a shell
On Sunday, 10 March 2019 17:24:05 GMT Ralph Corderoy wrote: > I don't understand why `nano' would give that error, and `TERM=vt220 > nano' would give the same error, yet `TERM=vt220' followed by `nano' No. The TERM variable is simply `TERM=vt220'. I don't enter nano until I type it into the shell. Or is that what you meant. > would work. It suggests your shell isn't applying that environment > variable setting yet is still skipping it to run nano. Or you entered > something else. :-) When I type 'env', I get `TERM=vt220'. > > I haven' changed my sig for about 10 years. > > And yet these two recently emails show it's different in the amount of > space it takes. > > https://www.mail-archive.com/dorset@mailman.lug.org.uk/msg08641.html > https://www.mail-archive.com/dorset@mailman.lug.org.uk/msg08644.html Those two sigs look exactly the same to me in Chromium and in KMail. > This is the bit where you normally blame Thunderbird. :-) Well. I'm using KMail and I can't see what's wrong, so maybe the problem is at your end :-) -- Terry Coles -- Next meeting: BEC, Bournemouth, Tuesday, 2019-04-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Cannot open nano in boot a shell
Hi Terry, > > Side effects from just that line? Or does `nano' on its own > > afterwards work? > > Well I wasn't saying it wasn't working; I was saying that it was :-) I don't understand why `nano' would give that error, and `TERM=vt220 nano' would give the same error, yet `TERM=vt220' followed by `nano' would work. It suggests your shell isn't applying that environment variable setting yet is still skipping it to run nano. Or you entered something else. :-) I can show the expected behaviour with tput(1). $ unset TERM $ tput cols tput: No value for $TERM and no -T specified $ TERM=vt220 tput cols 80 $ > My comment was because you said that the setting would only affect > nano, implying that if applied universally, there might be unwanted > side effects. No, I was implying that other commands that also want to know the terminal would still be in the dark. > I haven' changed my sig for about 10 years. And yet these two recently emails show it's different in the amount of space it takes. https://www.mail-archive.com/dorset@mailman.lug.org.uk/msg08641.html https://www.mail-archive.com/dorset@mailman.lug.org.uk/msg08644.html This is the bit where you normally blame Thunderbird. :-) -- Cheers, Ralph. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-04-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Cannot open nano in boot a shell
On Sunday, 10 March 2019 16:26:41 GMT Ralph Corderoy wrote: > What happened? Did nano give exactly the same error as before? > > error opening terminal: unknown Yes. > I can get that, once I find a machine with nano installed, with > > $ env -u TERM nano > Error opening terminal: unknown. > $ > > where env(1) is unsetting the environment variable. OK. > > but `TERM=vt220' seems to work OK and I haven't seen any unwanted side > > effects yet. > > Side effects from just that line? Or does `nano' on its own afterwards > work? Well I wasn't saying it wasn't working; I was saying that it was :-) My comment was because you said that the setting would only affect nano, implying that if applied universally, there might be unwanted side effects. > That's a big sig, or are you just pleased to see me? :-) I haven' changed my sig for about 10 years. Perhaps it's growing as it gets older :-) -- Terry Coles -- Next meeting: BEC, Bournemouth, Tuesday, 2019-04-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Cannot open nano in boot a shell
Hi Terry, > I couldn't get `TERM=linux nano' or `TERM=vt220 nano' to work on the > Pi What happened? Did nano give exactly the same error as before? error opening terminal: unknown I can get that, once I find a machine with nano installed, with $ env -u TERM nano Error opening terminal: unknown. $ where env(1) is unsetting the environment variable. > but `TERM=vt220' seems to work OK and I haven't seen any unwanted side > effects yet. Side effects from just that line? Or does `nano' on its own afterwards work? > -- > > > > Terry Coles > > > That's a big sig, or are you just pleased to see me? :-) -- Cheers, Ralph. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-04-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Cannot open nano in boot a shell
On Sunday, 10 March 2019 15:18:09 GMT Ralph Corderoy wrote: > In that case, it's probably a Linux VT you're seeing, rather that > looking at a console over a serial line say, and so `TERM=linux nano' > would be more accurate, but the VT220 will probably work as it's quite > the subset. I couldn't get `TERM=linux nano' or `TERM=vt220 nano' to work on the Pi, but `TERM=vt220' seems to work OK and I haven't seen any unwanted side effects yet. -- Terry Coles -- Next meeting: BEC, Bournemouth, Tuesday, 2019-04-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Cannot open nano in boot a shell
Hi Terry, > > What equipment are you using to view the `initial boot shell'? > > That's the odd thing; it's just a plain ol' monitor, the same VGA > Monitor with HDMI Adaptor that I've always used. I also get it with a > 'proper' HDMI monitor. In that case, it's probably a Linux VT you're seeing, rather that looking at a console over a serial line say, and so `TERM=linux nano' would be more accurate, but the VT220 will probably work as it's quite the subset. -- Cheers, Ralph. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-04-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Cannot open nano in boot a shell
On Sunday, 10 March 2019 14:45:43 GMT Ralph Corderoy wrote: > If that's the problem then `TERM=vt220 nano' should work. That sets the > TERM environment variable just in the process that runs nano. I'll have a look at that. > What equipment are you using to view the `initial boot shell'? That's the odd thing; it's just a plain ol' monitor, the same VGA Monitor with HDMI Adaptor that I've always used. I also get it with a 'proper' HDMI monitor. -- Terry Coles -- Next meeting: BEC, Bournemouth, Tuesday, 2019-04-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Micro:Bit
Hi Terry, > I commented that it was a shame that the Government / BBC hadn't > chosen the Raspberry Pi, since it already had a strong community. I think two things counted against the Pi back then. It's price, though I haven't checked on what Pi models were available when the decisions would have been being made, i.e. quite a bit before the micro:bit's release. And the opaqueness of its innards given it's a proprietary GPU that happens to be able to load code for an ARM on the side to run. Broadcom were never keen on opening the private bits up when I used to follow the topic. In comparison, the micro:bit is a lot more standard design for a `dev' board, with two ARMs, a Cortex M0 where your code runs, and a Cortex M0+ that provides the USB access to program the M0. Ditching the video output leaves a simpler system to build from scratch. (I have a micro:bit.) -- Cheers, Ralph. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-04-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Cannot open nano in boot a shell
Hi Terry, > but when I try to open nano in the initial boot shell, I get: > > error opening terminal: unknown This used to be a common issue back when there were a wide variety of terminals, as in the CRTs and keyboards with a RS-232 cable running off to the computer. There's an environment variable TERM that should be set to describe your type of terminal. Programs use this to index a database that describes how to achieve effects, e.g. move the cursor. The database was a text file called /etc/termcap, terminal capabilities, but that got slow as it grew so it's now called terminfo and is a binary file per terminal type under /usr/share/terminfo. If that's the problem then `TERM=vt220 nano' should work. That sets the TERM environment variable just in the process that runs nano. What equipment are you using to view the `initial boot shell'? -- Cheers, Ralph. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-04-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
[Dorset] Cannot open nano in boot a shell
I posted this on the Pi Forums, but haven't had much of a response to date: Earlier this week I downloaded and installed the latest Raspbian image from the Downloads page (2018-11-13-raspbian-stretch-full.img) and installed it onto an SD Card for use in a new project. The target device is a Pi Zero but I used my Pi 3 to perform all the updates before plugging the card into the Zero. As far as my project is concerned, everything is working fine, but when I try to open nano in the initial boot shell, I get: error opening terminal: unknown If I open a shell and type nano within the desktop, everything works. What is going on here? I've always used nano on earlier projects and had no issues as far as I can recall. -- Terry Coles -- Next meeting: BEC, Bournemouth, Tuesday, 2019-04-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Micro:Bit
On Sunday, 10 March 2019 13:51:19 GMT Keith Edmunds wrote: > So, er, what's the question? As Peter said, it came up during the LUG Meeting and I commented that it was a shame that the Government / BBC hadn't chosen the Raspberry Pi, since it already had a strong community. After a fairly robust discussion it was asserted that: a) I was anti Microsoft (which might have been true at the time, but less so now). b) I had no evidence that there was no Community behind the Micro:Bit and that was why the take-up was poor. c) I had no evidence that the take-up was poor. (Paul and I have long been adversaries on all things Microsoft :) ) Peter's response tends to support the lack Community and take-up, but I'd love to be proved wrong. -- Terry Coles -- Next meeting: BEC, Bournemouth, Tuesday, 2019-04-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Micro:Bit
So, er, what's the question? -- Linux Tips: https://www.tiger-computing.co.uk/category/techtips/ -- Next meeting: BEC, Bournemouth, Tuesday, 2019-04-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
[Dorset] Micro:Bit
We were wondering about this last Tuesday. I asked around and one of my neighbours who has three children of various ages, the oldest told me that some of her year used it last year in year 7 at the local middle school. I don't see any reference to it on the school web site. Peter M. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-04-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Linux bridging software for MTDfV
Hi Tim, > No, I drew a complete blank I detoured through reading up on OAuth2, etc., but this looks to do what you want... I think https://metacpan.org/pod/WebService::HMRC::VAT#SYNOPSIS shows the use of that Perl library, once `MY-ACCESS-TOKEN' is obtained. The same author provides a suite of HMRC libraries, including https://metacpan.org/pod/WebService::HMRC::Authenticate#SYNOPSIS to get tokens, that were originally developed for https://ledgersmb.org/. HMRC provide a sandbox to run code against for testing. HMRC provide quite a lot of documentation for using the API. https://developer.service.hmrc.gov.uk/guides/vat-mtd-end-to-end-service-guide/ It uses OAuth2 that means the user is bumped onto HMRC to prove their identity. Normally, HMRC would then redirect the browser back to the `Carry on' page on the website whence they came, but there's alternatives that include displaying the token so the user can copy it somewhere else, e.g. to the command line. The House of Commons Treasury Committee have tackled the provision of free software for MTD, including VAT: physical page 10 of https://publications.parliament.uk/pa/cm201617/cmselect/cmtreasy/1135/1135.pdf and starting on physical page 31 of https://publications.parliament.uk/pa/cm201617/cmselect/cmtreasy/927/927.pdf -- Cheers, Ralph. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-04-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Monitoring Internet Connectivity.
Hi Patrick, > > So RADIUS knows how to Authenticate. It then Authorises > > I have made the old mistake of conflating Authentication and > Authorisation. I think I initially got them the wrong way around at least once when typing. It's a bad idea in software to have identifiers that are similar at the start because the fingers too easily slip into typing the wrong one whilst the brain's moved on to thinking about what's next. I think standards and protocols can also make the same mistake, increasing the cognitive overhead in remembering all the terms as they're learnt. I expect `Triple A' here had too much appeal to describe Corroborating the claimed identity, Permitting the user's actions, and Tallying their usage. :-) -- Cheers, Ralph. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-04-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Monitoring Internet Connectivity.
On Sun, 10 Mar 2019 09:57:56 +, Ralph Corderoy wrote: > So RADIUS knows how to Authenticate. It then Authorises I have made the old mistake of conflating Authentication and Authorisation. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-04-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Monitoring Internet Connectivity.
Hi Tim, Patrick wrote: > My understanding is that RADIUS is a protocol for services that > provide authentication for one or more different network access > mechanisms. So, on its own, RADIUS is not really a solution at all, > just part of a solution. Yes, I think there's three parties. The laptop, the access point, and the RADIUS server software. RADIUS could be running on the access point's hardware, but doesn't have to be. The AP is configured to defer to RADIUS on whether the laptop is allowed. This can be using a username/password, or a certificate generated earlier by RADIUS solely for the laptop and then copied onto it. So RADIUS knows how to Authenticate. It then Authorises, and that's where logic can come into it, e.g. only from 9-5 weekdays. It's up to the AP to implement the restrictions using what RADIUS tells it. I don't know the level of understanding between the AP and RADIUS, e.g. RADIUS might keep updating the AP with new Authorisations over time. After that, RADIUS can keep track of Accounting, again with the AP's involvement as it's the AP that sees the traffic, not RADIUS. That allows buying 60 minutes of Wi-fi, etc. > > Yes, that's a possibility, as the Draytek has multiple SSIDs with > > scheduling. But fairly quickly the unscheduled SSID passwords will > > be compromised. > > If the compromise is by means of extracting credentials from other > devices, then I suppose the same risk could apply to a solution using > RADIUS. Yes, though ISTM some systems prevent easy copying of the certificate, e.g. Android. https://www.ed.ac.uk/information-services/computing/desktop-personal/wifi-networking/configure-device/eduroam-android -- Cheers, Ralph. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-04-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Monitoring Internet Connectivity.
Hi Tim H, > Think you will find it now called IPFire, think they have a free and > paid for version including hardware devices as well. Thanks, I hadn't heard of them. Seems it's a fork of IPCop from long ago, just as IPCop was a Smothwall fork. IPFire are still going, but marked the demise of IPCop. https://blog.ipfire.org/post/goodbye-ipcop -- Cheers, Ralph. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-04-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
