Re: Questions about VRF function in /etc/network/interfaces
Hi. On Sat, Dec 29, 2018 at 01:31:02PM +0800, Simon Jones wrote: > Hi all, > > This is my OS: > > > # uname -a > > Linux dut211 4.9.0-7-amd64 #1 SMP Debian 4.9.110-3+deb9u2 (2015-12-19) > > x86_64 GNU/Linux That's not a kernel 4.3, for starters. And it's outdated, consider upgrading. Does not affect your problem though. > Now I have to rewrite /etc/network/interfaces to implement this function, > but I got errors, so I want to know if there is demo about how to define > VRF interface and implement VRF function in /etc/network/interfaces. > > As I follow your man file, I don't know how to do, and gots errors. Usual debugging of interfaces(5) involves 'ifup -v' and 'ifdown -v'. > This is my try on this feature, rewrite /etc/network/interfaces like this > > iface eth0 inet static > > address 172.18.8.211 > > netmask 255.255.255.0 > > ## management network policy routing rules > > # management port up rules > > up ip -4 link add mgmtvrf type vrf table 10 > > up ip -4 link set dev mgmtvrf up > > up ip -4 link set dev eth0 master mgmtvrf > > up ip -4 route add default via 172.18.8.1 dev eth0 table 10 > > up ip -4 route add 172.18.8.0/24 dev eth0 table 10 > > up ip -4 rule add from 172.18.8.211/32 table 10 > > post-up sysctl -w net.ipv4.tcp_l3mdev_accept=1 > > # management port down rules > > down ip -4 route delete default via 172.18.8.1 dev eth0 table 10 > > down ip -4 route delete 172.18.8.0/24 dev eth0 table 10 > > down ip -4 rule delete from 172.18.8.211/32 table 10 > > down ip -4 link set dev eth0 nomaster '-4' is redundant here (you either modify L2 entities or it can be guessed from the context), you might remove it as well. > This is errors I got > > Dec 29 02:38:48 dut211 ifup[8690]: RTNETLINK answers: File exists This. Everything else in your log is useless. A simple test shows that: $ ifup -v eth0 ifup: configuring interface eth0=eth0 (inet) /bin/run-parts --exit-on-error --verbose /etc/network/if-pre-up.d /bin/ip addr add 172.18.8.211/255.255.255.0 broadcast 172.18.8.255 dev eth0 label eth0 /bin/ip link set dev eth0 up ip -4 link add mgmtvrf type vrf table 10 ip -4 link set dev mgmtvrf up ip -4 link set dev eth0 master mgmtvrf ip -4 route add default via 172.18.8.1 dev eth0 table 10 ip -4 route add 172.18.8.0/24 dev eth0 table 10 RTNETLINK answers: File exists ifup: failed to bring up eth0 So, it's all good until you try to add an additional route to 172.18.8.0/24, because this route is there already: $ ip ro l table 10 broadcast 172.18.8.0 dev eth0 proto kernel scope link src 172.18.8.211 172.18.8.0/24 dev eth0 proto kernel scope link src 172.18.8.211 local 172.18.8.211 dev eth0 proto kernel scope host src 172.18.8.211 broadcast 172.18.8.255 dev eth0 proto kernel scope link src 172.18.8.211 And you've got your 'down' rules wrong, you should delete your custom 'mgmtvrf' interface: # ifdown eth0 # ip a l dev mgmtvrf 5: mgmtvrf: mtu 65536 qdisc noqueue state UP group default qlen 1000 link/ether 4a:dc:f1:71:c7:00 brd ff:ff:ff:ff:ff:ff And, of course, there's a leftover kernel knob: # /sbin/sysctl net.ipv4.tcp_l3mdev_accept net.ipv4.tcp_l3mdev_accept = 1 Summing all this up: iface eth0 inet static address 172.18.8.211 netmask 255.255.255.0 ## management network policy routing rules # management port up rules up ip link add mgmtvrf type vrf table 10 up ip link set dev mgmtvrf up up ip link set dev eth0 master mgmtvrf up ip route add default via 172.18.8.1 dev eth0 table 10 up ip rule add from 172.18.8.211/32 table 10 post-up sysctl -qw net.ipv4.tcp_l3mdev_accept=1 # management port down rules down ip -4 route delete default via 172.18.8.1 dev eth0 table 10 down ip -4 route delete 172.18.8.0/24 dev eth0 table 10 down ip -4 rule delete from 172.18.8.211/32 table 10 down ip -4 link set dev eth0 nomaster down ip -4 link del mgmtvrf post-down sysctl -qw net.ipv4.tcp_l3mdev_accept=0 Reco
Questions about VRF function in /etc/network/interfaces
Hi all, I'm working on SONiC project management vrf function under debian with kernel 4.3. This is my OS: > # uname -a > Linux dut211 4.9.0-7-amd64 #1 SMP Debian 4.9.110-3+deb9u2 (2015-12-19) > x86_64 GNU/Linux This is SONiC project management vrf function: > https://www.youtube.com/watch?v=uAHmZKEdqDE&feature=youtu.be Now I have to rewrite /etc/network/interfaces to implement this function, but I got errors, so I want to know if there is demo about how to define VRF interface and implement VRF function in /etc/network/interfaces. As I follow your man file, I don't know how to do, and gots errors. This is my try on this feature, rewrite /etc/network/interfaces like this iface eth0 inet static > address 172.18.8.211 > netmask 255.255.255.0 > ## management network policy routing rules > # management port up rules > up ip -4 link add mgmtvrf type vrf table 10 > up ip -4 link set dev mgmtvrf up > up ip -4 link set dev eth0 master mgmtvrf > up ip -4 route add default via 172.18.8.1 dev eth0 table 10 > up ip -4 route add 172.18.8.0/24 dev eth0 table 10 > up ip -4 rule add from 172.18.8.211/32 table 10 > post-up sysctl -w net.ipv4.tcp_l3mdev_accept=1 > # management port down rules > down ip -4 route delete default via 172.18.8.1 dev eth0 table 10 > down ip -4 route delete 172.18.8.0/24 dev eth0 table 10 > down ip -4 rule delete from 172.18.8.211/32 table 10 > down ip -4 link set dev eth0 nomaster This is errors I got Dec 29 02:38:48 dut211 ifup[8690]: RTNETLINK answers: File exists > Dec 29 02:38:48 dut211 ifup[8690]: ifup: failed to bring up eth0 > Dec 29 02:38:48 dut211 systemd[1]: networking.service: Main process > exited, code=exited, status=1/FAILURE > Dec 29 02:38:48 dut211 systemd[1]: Failed to start Raise network > interfaces. > -- Subject: Unit networking.service has failed > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- Unit networking.service has failed. > -- > -- The result is failed. > Dec 29 02:38:48 dut211 systemd[1]: networking.service: Unit entered failed > state. > Dec 29 02:38:48 dut211 systemd[1]: networking.service: Failed with result > 'exit-code’. Thank you. Simon Jones
Re: Thank you for your insight.
Thank you for the response, though I feel you don't address my question. Happily though, I spoke with an acquaintance and it was determined that the subservience to the license (i.e. agreeing to be bound by the GPL2) could not be offered as consideration as its restrictions were not the licensee's to offer at the time of acceptance of the license. The licensee had no rights to offer as part of the contract, as the contract had not yet given them any rights to give up. The terms put forth by the GPL2 are only restrictions that are part of the license. Furthermore, as stated above, it should seem quite self referential - I can't offer my acceptance of a license as consideration, because it is what I am trying to accept. As I am sure you are aware, under US law there is no contract if both sides have not provided consideration. This leaves us in the strange place of gratis licenses being suggestions. Cheers, R0b0t1 On Fri, Dec 28, 2018 at 12:47 PM wrote: > > Thank you for your insight. > > It is a shame that there were no responses. They ignored your post, then > kept baying at me: "no this is wrong" "you're not a lawyer" "I will not > lower myself to refute you with arguments!". > > As for non-monetary consideration to support an additional no-revocation > term: > Many of the old linux-kernel (programmer)rights-holders have received > nothing, and have made no such promise. > Many of the contributors (who did not transfer their rights) have > received nothing. > > There is nothing to uphold the contention that they have forfeited their > default right to rescind license to their property. > They never made such a promise, they were never paid for such a promise, > they never contracted for such, etc. > > They wrote code, licensed it gratuitously, > and now an attempt is being made to both control their speech, their > action, and to basically convert their property. > > Most of the entities who have been licensed the works have neither paid > anything to the various rights-holders, > nor have they ever contacted nor been contacted by the various > rights-holders, etc. >
Re: In Testing: gkrellm <-> digikam (libsensors5 <-> libsensors4)
On Fri, 28 Dec 2018 18:16:18 +0100 Jürgen Köhler wrote: > I have a little "problem" in testing with gkrellm last updated since: > a conflict between gkrellm and digikam Not sure how far testing is behind unstable, but there has been a serious problem in the sensors area of unstable for a couple of weeks. I haven't been able to resolve it manually, but presumably it will be fixed soon, for some value of 'soon'. Qt5 has just got into the same sort of muddle, but orders of magnitude larger... -- Joe
Re: intermittent name resolution failures
* kamaraju kusumanchi: > On Fri, Dec 28, 2018 at 3:51 AM wrote: >> >> Whenever your DNS fails try a "traceroute 8.8.8.8". Compare its results >> to what you get when you do it at times where your DNS works. Perhaps >> this sheds some light on it. > > That is tough to capture because the problem is intermittent. When I > retry it seems to come back and vice versa. Instead I ran the > traceroute command 10 times and stored the output in trial_1.txt, > trial_2.txt, ... trial_10.txt in > http://kamaraju.xyz/tmp/network_issues/ > > Command used: > $ for i in `seq 1 10`; do traceroute 8.8.8.8 > trial_$i.txt; done This is more useful than the dig +trace output (which is not representative at all because +trace > I see a lot of differences between trial_6.txt and trial_4.txt. Does > that mean anything or is this variation expected? The first hop should be the same in all cases and reachable (no stars). It looks like the network is down intermittently. What kind of network connection is this? Do you have physical access to the machine.
In Testing: gkrellm <-> digikam (libsensors5 <-> libsensors4)
I have a little "problem" in testing with gkrellm last updated since: a conflict between gkrellm and digikam gkrellm gkrellm : Hängt ab von: libsensors4 (>= 1:3.0.0) soll aber nicht installiert werden root@jk:/home/juergen1# apt-get -s install libsensors4 Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt: cups-pk-helper digikam-data enblend enfuse ffmpegthumbs gdal-data gir1.2-packagekitglib-1.0 gir1.2-secret-1 hplip-data hugin hugin-data h ugin-tools kipi-plugins-common libaec0 libarmadillo9 libarpack2 libastro1 libcharls1 libepsilon1 libfreexl1 libfyba0 libgdal20 libgdcm2.8 libgeos-3.7.1 libgeos-c1v5 libgeotiff2 libhdf4-0-alt libhdf5-103 libieee1284-3 libimage- exiftool-perl libkf5mediawiki5 libkf5sane-data libkmlbase1 libkmlconvenience1 libkmldom1 libkmlengine1 libkmlregionator1 libkmlxsd1 libmarblewidget-qt5-28 libnetcdf13 libogdi3.2 libopencv-core3.2 libopencv-highgui3.2 libopencv-imgcodecs3.2 libopencv-imgproc3.2 libopencv-ml3.2 libopencv-objdetect3.2 libopencv-videoio3.2 libpano13-3 libpano13-bin libposix-strptime-perl libproj13 libqhull7 libqtav1 libqtavwidgets1 libsane-common libshp2 libsnmp-base libsocket++1 libspatialite7 libsuperlu5 libsz2 libuchardet0 liburiparser1 libvigraimpex6 marble-data marble-plugins marble-qt-data minidlna opencv-data proj-bin python3- cups python3-cupshelpers python3-pexpect python3-pil python3-ptyprocess python3-renderpm python3-reportlab python3-reportlab-accel python3-smbc system-config- printer system-config-printer-common system-config-printer-udev Verwenden Sie »apt autoremove«, um sie zu entfernen. Vorgeschlagene Pakete: lm-sensors Die folgenden Pakete werden ENTFERNT: digikam digikam-private-libs hplip kipi-plugins libhpmud0 libkf5sane5 libsane libsane-hpaio libsensors-config libsensors5 libsnmp30 printer- driver-hpcups sane-utils Die folgenden NEUEN Pakete werden installiert: libsensors4 0 aktualisiert, 1 neu installiert, 13 zu entfernen und 0 nicht aktualisiert. Remv digikam [4:5.9.0-1+b1] Remv kipi-plugins [4:5.9.0-1+b1] Remv digikam-private-libs [4:5.9.0-1+b1] Remv hplip [3.18.12+dfsg0-2] Remv printer-driver-hpcups [3.18.12+dfsg0-2] Remv libsane-hpaio [3.18.12+dfsg0-2] Remv libhpmud0 [3.18.12+dfsg0-2] Remv libkf5sane5 [17.08.3-1] Remv sane-utils [1.0.27-3.1] Remv libsane [1.0.27-3.1] Remv libsnmp30 [5.7.3+dfsg-4+b2] Remv libsensors5 [1:3.5.0-3] Remv libsensors-config [1:3.5.0-3] Inst libsensors4 (1:3.4.0-4 Debian:testing [amd64]) Conf libsensors4 (1:3.4.0-4 Debian:testing [amd64])
Re: Wireless driver
On 28.12.2018 12:32, john doe wrote: > On 12/27/2018 12:24 PM, Alexander V. Makartsev wrote: >> On 27.12.2018 14:05, john doe wrote: >>> Hi, >>> >>> I'm trying to get (1) to work on Debian Stretch. >>> >>> >From what I understand, only "qca9982" v1 is supported on Debian, >>> however, (3) supports qca9882 v2. >>> That brings me to some questions: >>> >>> - Am I on the right track by trying to build the firmware using >>> backports from (3)? >>> - Can I build the firmware in an VM an move that firmware to that >>> wireless box? >>> >>> In other words, what should I do to get qca9882 v2 to work on Debian >>> Stretch? >>> >>> Any help is appriciated. >>> >>> >>> 1) https://www.compex.com.sg/product/wle600vx/ >>> 2) https://packages.debian.org/stretch/firmware-atheros >>> 3) https://wireless.wiki.kernel.org/en/users/drivers/ath10k >>> >> ||According to specifications from Compex, WLE600VX utilizes >> Qualcomm-Atheros QCA*98*82 chip. >> I think it is a good idea to try packages from "stretch-backports" first >> [1] [2], because it looks like WLE600VX was produced a few years ago and >> should have already have support in linux kernel. >> So I highly doubt this NIC model requires latest Qualcomm firmware >> update, that was pushed into kernel.org source repository 9 days ago. >> >> [1] $ rmadison -s stable,stretch-backports firmware-atheros >> firmware-atheros | 20161130-4 | stable/non-free | all >> firmware-atheros | 20180825+dfsg-1~bpo9+1 | stretch-backports/non-free | all >> > Thank you, the last time I tryed didn't have much luck. > If I understand correctly, (1) does list the qca9882 v1 but not qca9882 v2? > > 1) https://packages.debian.org/stretch-backports/firmware-atheros > I think "qca9882 v2" doesn't exist. What made you think there are different versions of qca9882 chipsets? Support for qca9882 chipset was added to kernel 2 years ago and gets updated when new firmware version is available. [1] This page from kernel.org wiki lists your NIC as supported [2], which means firmware file is available in repository. At this moment "firmware-atheros" package from "stretch/non-free" repo contains firmware for qca9882 chipset, version 10.2.4.70.54 (ath10k/QCA988X/hw2.0/firmware-5.bin) which should provide support for WLE600VX NIC. Try to get some information from kernel logs to see if ath10k module loads at all. # dmesg | grep ath10k This guide should be helpful to debug more [3], especially these commands should output more debug information into kernel logs: # modprobe -r ath10k_core # modprobe ath10k_core debug_mask=0x0432 [1] https://github.com/kvalo/ath10k-firmware/tree/master/QCA988X/hw2.0 [2] https://wireless.wiki.kernel.org/en/users/drivers/ath10k [3] https://wireless.wiki.kernel.org/en/users/drivers/ath10k/debug -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
Re: Wireless driver
On 12/28/2018 8:32 AM, john doe wrote: > On 12/27/2018 12:24 PM, Alexander V. Makartsev wrote: >> On 27.12.2018 14:05, john doe wrote: >>> Hi, >>> >>> I'm trying to get (1) to work on Debian Stretch. >>> >>> >From what I understand, only "qca9982" v1 is supported on Debian, >>> however, (3) supports qca9882 v2. >>> That brings me to some questions: >>> >>> - Am I on the right track by trying to build the firmware using >>> backports from (3)? >>> - Can I build the firmware in an VM an move that firmware to that >>> wireless box? >>> >>> In other words, what should I do to get qca9882 v2 to work on Debian >>> Stretch? >>> >>> Any help is appriciated. >>> >>> >>> 1) https://www.compex.com.sg/product/wle600vx/ >>> 2) https://packages.debian.org/stretch/firmware-atheros >>> 3) https://wireless.wiki.kernel.org/en/users/drivers/ath10k >>> >> ||According to specifications from Compex, WLE600VX utilizes >> Qualcomm-Atheros QCA*98*82 chip. >> I think it is a good idea to try packages from "stretch-backports" first >> [1] [2], because it looks like WLE600VX was produced a few years ago and >> should have already have support in linux kernel. >> So I highly doubt this NIC model requires latest Qualcomm firmware >> update, that was pushed into kernel.org source repository 9 days ago. >> >> [1] $ rmadison -s stable,stretch-backports firmware-atheros >> firmware-atheros | 20161130-4 | stable/non-free | all >> firmware-atheros | 20180825+dfsg-1~bpo9+1 | stretch-backports/non-free | all >> > > Thank you, the last time I tryed didn't have much luck. > If I understand correctly, (1) does list the qca9882 v1 but not qca9882 v2? > > 1) https://packages.debian.org/stretch-backports/firmware-atheros > Ok -- I'm currently testing the fw from (1). In the log I get: $ journalctl -x -o cat | awk '/ath10k/ && /[Ee]rror/' ath10k_pci :04:00.0: Direct firmware load for ath10k/pre-cal-pci-:04:00.0.bin failed with error -2 ath10k_pci :04:00.0: Direct firmware load for ath10k/cal-pci-:04:00.0.bin failed with error -2 ath10k_pci :04:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2 Can anyone tell me what the first two firmwares are for and where I can find them? Should I care about the missing board-2.bin? Thanks for any help. 1) https://github.com/kvalo/ath10k-firmware -- John Doe
Re: intermittent name resolution failures
On Fri, Dec 28, 2018 at 3:51 AM wrote: > > Whenever your DNS fails try a "traceroute 8.8.8.8". Compare its results > to what you get when you do it at times where your DNS works. Perhaps > this sheds some light on it. That is tough to capture because the problem is intermittent. When I retry it seems to come back and vice versa. Instead I ran the traceroute command 10 times and stored the output in trial_1.txt, trial_2.txt, ... trial_10.txt in http://kamaraju.xyz/tmp/network_issues/ Command used: $ for i in `seq 1 10`; do traceroute 8.8.8.8 > trial_$i.txt; done I see a lot of differences between trial_6.txt and trial_4.txt. Does that mean anything or is this variation expected? $ cat trial_6.txt traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * 6 * be3295.ccr31.jfk05.atlas.cogentco.com (154.54.80.2) 2.131 ms be3294.ccr31.jfk05.atlas.cogentco.com (154.54.47.218) 2.078 ms 7 level3.dfw03.atlas.cogentco.com (154.54.12.18) 1.905 ms 1.906 ms 2.038 ms 8 if-ae-12-2.tcore1.n75-new-york.as6453.net (66.110.96.5) 2.274 ms 2.271 ms if-ae-12-4.tcore1.n75-new-york.as6453.net (66.110.96.59) 2.257 ms 9 72.14.195.232 (72.14.195.232) 3.073 ms 3.074 ms * 10 * * * 11 * * * 12 * 108.170.235.183 (108.170.235.183) 2.605 ms 108.170.238.203 (108.170.238.203) 2.794 ms 13 google-public-dns-a.google.com (8.8.8.8) 2.182 ms 2.084 ms 2.044 ms $ cat trial_4.txt traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets 1 38.76.11.1 (38.76.11.1) 0.416 ms 0.359 ms 0.412 ms 2 gi0-2-0-6.rcr51.ewr04.atlas.cogentco.com (38.122.117.97) 1.213 ms 1.197 ms 1.208 ms 3 be3657.rcr21.ewr03.atlas.cogentco.com (154.24.33.169) 1.620 ms 1.514 ms 1.584 ms 4 be2601.rcr24.jfk01.atlas.cogentco.com (154.54.40.49) 2.044 ms * * 5 * * * 6 * be3294.ccr31.jfk05.atlas.cogentco.com (154.54.47.218) 2.205 ms be3295.ccr31.jfk05.atlas.cogentco.com (154.54.80.2) 2.085 ms 7 level3.dfw03.atlas.cogentco.com (154.54.12.18) 1.674 ms 1.657 ms 1.745 ms 8 if-ae-12-2.tcore1.n75-new-york.as6453.net (66.110.96.5) 2.147 ms 2.232 ms if-ae-12-4.tcore1.n75-new-york.as6453.net (66.110.96.59) 2.181 ms 9 72.14.195.232 (72.14.195.232) 2.772 ms 2.766 ms 2.756 ms 10 * * * 11 * * 72.14.234.64 (72.14.234.64) 4.559 ms 12 209.85.243.193 (209.85.243.193) 2.346 ms 108.170.235.181 (108.170.235.181) 2.933 ms 74.125.37.97 (74.125.37.97) 2.650 ms 13 google-public-dns-a.google.com (8.8.8.8) 2.204 ms 2.200 ms 2.231 ms thanks raju -- Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
Re: File ownership problem using removeable media
On Fri, Dec 28, 2018 at 09:05:54AM -0600, Richard Owlett wrote:
[...]
> It demonstrates the problem of Linux's jargon[1].
Linux's jargon has no problems ;-)
> That file has 32 entries. Only 2 are relate to my problem ["richard"
> & "root"].
How would you know? Perhaps the other 30 users are busy keeping
your system running smoothly?
>Who is "owner" {more jargon} of specific files &/or
> directories. What is needed the concept of something similar to
> Intellectual Property.
No. More similar to access rights.
> I started trying to restate my problem unambiguously.
> While looking for some local concrete examples I think I thought of
> another line of attack on my problem. My homework assignment for to
> day is "Investigate further" ;/
How 'bout you take advice seriously and just do an "ls -l" on one of
those files you think you would like to have access to and post the
results. Then we can continue to debug from there on. Would that be
a proposal?
Cheers
-- tomás
signature.asc
Description: Digital signature
Re: File ownership problem using removeable media
On 12/27/2018 07:34 AM, to...@tuxteam.de wrote:
On Thu, Dec 27, 2018 at 06:48:51AM -0600, Richard Owlett wrote:
On 12/25/2018 11:22 AM, to...@tuxteam.de wrote:
On Tue, Dec 25, 2018 at 10:06:04AM -0600, Richard Owlett wrote:
[...]
Linux intrinsically assumes one machine has multiple users.
...and it is right in its assumption.
I will admit its assumption is typically valid.
It is *technically* valid: besides "your" user there's at least
"root", "daemon"; typically there's "bin", "man", often"www-data"
and more: lots of little gnomes catering to your well-being behind
the curtains. Have a look at /etc/passwd and behold...
It demonstrates the problem of Linux's jargon[1].
That file has 32 entries. Only 2 are relate to my problem ["richard" &
"root"]. Who is "owner" {more jargon} of specific files &/or
directories. What is needed the concept of something similar to
Intellectual Property.
I started trying to restate my problem unambiguously.
While looking for some local concrete examples I think I thought of
another line of attack on my problem. My homework assignment for to day
is "Investigate further" ;/
[snip]
[1] https://literarydevices.net/jargon/
Re: help regarding timer
On 2018-12-28, Manikandan Kandili Sivaraj wrote: > > hi, > > I am new to Kali Linux. Could you kindly assist me how to install timer on > Kali Linux. Seems you have to install it (via the 'make.sh' script provided), and then enable it (via the 'gnome-tweak-tool': Shell Extensions/Timer Extension). > I downloaded from Github using the following command. > git clone https://github.com/olebowle/gnome-shell-timer.git > But not aware how to run it from there onwards. Thank you. > > Regards, > Manikandan K S >
Re: File ownership problem using removeable media
On Sat, Dec 29, 2018 at 12:13:23AM +1100, David wrote:
> The command
> awk -F: '{print $1}' /etc/passwd
> will display all the known users on your machine.
A better (more general) one would be: getent passwd | awk -F: '{print $1}'
/etc/passwd will be complete for many systems, but not for all systems,
because some machines are part of a network that uses NIS or LDAP or
similar remote authentication sources.
Re: File ownership problem using removeable media
On Thu, 27 Dec 2018 at 23:49, Richard Owlett wrote:
>
> {I am the ONLY user on any of the machines.}
Have you checked?
The command
awk -F: '{print $1}' /etc/passwd
will display all the known users on your machine.
The commands 'ps aux' or top or htop
will show active users in the USER column.
Re: intermittent name resolution failures
On Fri, Dec 28, 2018 at 11:57:35AM +0100, Pascal Hambourg wrote: > Le 28/12/2018 à 09:51, to...@tuxteam.de a écrit : > >On Thu, Dec 27, 2018 at 11:41:48PM -0500, kamaraju kusumanchi wrote: > >>How to debug intermittent name resolution failures on a Debian Stretch > >>machine? > > > >I take your DNS server is 8.8.8.8 > > And 8.8.4.4, as can be seen in /etc/resolv.conf. [...] Right. > Or there is a more specific routing problem between the machine and > the DNS servers. Yes, that would be next. Traceroute might shed light on this, too. Cheers -- t signature.asc Description: Digital signature
Re: intermittent name resolution failures
Le 28/12/2018 à 09:51, to...@tuxteam.de a écrit : On Thu, Dec 27, 2018 at 11:41:48PM -0500, kamaraju kusumanchi wrote: How to debug intermittent name resolution failures on a Debian Stretch machine? I take your DNS server is 8.8.8.8 And 8.8.4.4, as can be seen in /etc/resolv.conf. My top two would be that either 8.8.8.8 is down And also 8.8.4.4. Unlikely. or that your Internet connection is down. Or there is a more specific routing problem between the machine and the DNS servers.
OpenIAM or FreeIPA
Hi, What is the best OpenIAM or FreeIPA ? Thank's -- *Ilyass kaouam* *Ingénieur System OpenSource* *Mastère européen Manager de Projets Informatiques*
Re: help regarding timer
On Fri, Dec 28, 2018 at 02:16:33PM +0530, Manikandan Kandili Sivaraj wrote: > Kindly send me the appropriate email address. Thank you. Manikandan, this is not a service desk. This is a mailing list run by volunteers. Please consider that you are sending your mails to over 3000 people. A short web search yields this page for Kali community support: https://www.kali.org/community/ They don't seem to have mailing lists, but IRC channels and fora. HTH -- tomás signature.asc Description: Digital signature
Re: help regarding timer
Kindly send me the appropriate email address. Thank you. Sent from my iPhone > On 28-Dec-2018, at 10:15 AM, kamaraju kusumanchi > wrote: > > On Thu, Dec 27, 2018 at 10:18 PM Manikandan Kandili Sivaraj > wrote: >> >> hi, >> >> I am new to Kali Linux. Could you kindly assist me how to install timer on >> Kali Linux. > > Wrong mailing list. This is for Debian users. > > raju
Re: intermittent name resolution failures
On Thu, Dec 27, 2018 at 11:41:48PM -0500, kamaraju kusumanchi wrote: > How to debug intermittent name resolution failures on a Debian Stretch > machine? [...] > ;; Received 525 bytes from 8.8.8.8#53(8.8.8.8) in 11 ms I take your DNS server is 8.8.8.8 (kids, do we have to hand off every bit of our lives to The Goog? But I disgress). My top two would be that either 8.8.8.8 is down (hee, hee ;-) or that your Internet connection is down. I'd guess number two is the case. So I'd guess that it's not only your DNS resolution failing. Whenever your DNS fails try a "traceroute 8.8.8.8". Compare its results to what you get when you do it at times where your DNS works. Perhaps this sheds some light on it. Cheers -- tomás signature.asc Description: Digital signature
Re: help regarding timer
On Fri, Dec 28, 2018 at 03:00:44AM +, Manikandan Kandili Sivaraj wrote: > hi, > > I am new to Kali Linux. Could you kindly assist me how to install timer on > Kali Linux. > > I downloaded from Github using the following command. > git clone https://github.com/olebowle/gnome-shell-timer.git > But not aware how to run it from there onwards. Thank you. Actually, there are instrutions in the README. You are installing from source, thus, quoting the README: Direct from source [...] use the provided make.sh script du (un)install the extension Enable the extension using gnome-tweak-tool Press Alt + F2, and r in command to restart gnome-shell What did you try? Where did it fail? Cheers -- tomás signature.asc Description: Digital signature
