search for: rapsberri

Displaying 11 results from an estimated 11 matches for "rapsberri".

Did you mean: rapsberry
2015 Jan 03
2
Samba4 Kerberos kinit does not resolve kdc hostname
Hi, /etc/resolv.conf looks exactly like this: domain family.rapsberry.local search family.rapsberry.local nameserver 192.168.178.222 So to answer your question: yes the only Nameserver the raspberry has is itself. Greetings Am 2015-01-03 um 7:40 PM schrieb Rowland Penny: > On 03/01/15 16:31, Robert Hartmann wrote: >> Hi, >> >> i am really depressed at this moment. I set
2015 Jan 03
1
Samba4 Kerberos kinit does not resolve kdc hostname
Hi, thank you so! much. Turning off avahi daemon was the solution! rapsberry instead of raspberry is a typo during porivision actually. Thank you again :) I will write an entry on my blog to make sure that does not happen again. One last time for google bots. IF you receive kinit: Cannot contact any KDC for realm while getting initial credentials make sure you don't run avahi However
2015 Jan 03
2
Samba4 Kerberos kinit does not resolve kdc hostname
Hi, i am really depressed at this moment. I set up an domain controller using samba4 and an raspberry pi. I can join the domain and everything works BUT kerberos has some strange problems resolving my raspberry hostname. First of all some information: Raspberry pi is DHCP Server and DNS-Server (BIND9). First of all the configurations: Code: /usr/local/samba/etc/smb.conf # Global
2015 Jan 03
0
Samba4 Kerberos kinit does not resolve kdc hostname
On 03/01/15 18:45, Robert Hartmann wrote: > > Hi, > > /etc/resolv.conf looks exactly like this: > > domain family.rapsberry.local > search family.rapsberry.local > nameserver 192.168.178.222 > > So to answer your question: yes the only Nameserver the raspberry has > is itself. > Hi, firstly, you might as well remove the 'domain' line, it will be
2015 Jan 03
0
Samba4 Kerberos kinit does not resolve kdc hostname
On 03/01/15 16:31, Robert Hartmann wrote: > Hi, > > i am really depressed at this moment. I set up an domain controller > using samba4 and an raspberry pi. > > I can join the domain and everything works BUT kerberos has some > strange problems resolving my raspberry hostname. > > First of all some information: > > Raspberry pi is DHCP Server and DNS-Server
2018 Feb 27
2
Work around for power recycling after shutdown.return - TSSHARA UPS - nutdrv_qx driver - megatec protocol
Hi, I had an issue where after returning the power from a shutdown.return the ups would do another shutdown.return during the boot, and kept this forever. After some investigation I found the problem is a bug on the ups - TSSHARA model, driver nutdrv_qx: every time I shutdown with return, and reconnect the usb after the power is back it would start another shudown.return cycle. When I used my
2019 Apr 23
2
Tinc and firewall
Hello, Early this year I got help here to setup tinc tunnels between users and a company LAN. Now I would like to try something different for a home usage and I have a question regarding security. The setup would look like as follows: - My home LAN has a classical topology where my ISP router is doing NAT and is blocking all incoming connection. I'm planning to enable port forwarding on the
2020 Jul 16
1
R 4.0 for ARM processors
2 years ago at one Meetup in Paris, Marc Girondot, professor at University Paris-Saclay, presented his cluster built with 12 Odroid (equivalent to Rapsberry Pi). The stack was almost the same size than your picture as there was no fan and a narrower distance between each PCB card. There were many more cables. For a total cost of less than 1000 ? and an electrical consumption reduced by a
2018 Feb 28
2
Work around for power recycling after shutdown.return - TSSHARA UPS - nutdrv_qx driver - megatec protocol
Answers bellow. 2018-02-28 1:41 GMT-03:00 Daniele Pezzini <hyouko at gmail.com>: > 2018-02-27 14:51 GMT+01:00 Jairo Rotava <jairo.rotava at gmail.com>: > > Hi, > > > > I had an issue where after returning the power from a shutdown.return the > > ups would do another shutdown.return during the boot, and kept this > forever. > > After some
2018 Feb 28
0
Work around for power recycling after shutdown.return - TSSHARA UPS - nutdrv_qx driver - megatec protocol
2018-02-27 14:51 GMT+01:00 Jairo Rotava <jairo.rotava at gmail.com>: > Hi, > > I had an issue where after returning the power from a shutdown.return the > ups would do another shutdown.return during the boot, and kept this forever. > After some investigation I found the problem is a bug on the ups - TSSHARA > model, driver nutdrv_qx: every time I shutdown with return, and
2018 Feb 28
0
Work around for power recycling after shutdown.return - TSSHARA UPS - nutdrv_qx driver - megatec protocol
Hello, I think that on this file nutdrv_qx_megatec.c the definition for shutdown.stayoff may be wrong. In the file the definition is "S%sR0000\r"m while on the megatec protocol description ( http://networkupstools.org/protocols/megatec.html) the command is just "S%s\r". When I changed it my system was abe to at least stay off, and stopped making an instant power recycling.