search for: bw10

Displaying 8 results from an estimated 8 matches for "bw10".

Did you mean: b10
2019 Jun 24
0
Reverse DNS
...--------------------------------------- Jun 24 01:36:24 server5-ad named[1007]: samba_dlz: cancelling transaction on zone LIN.group Jun 24 01:36:24 server5-ad named[1007]: samba_dlz: starting transaction on zone LIN.group Jun 24 01:36:24 server5-ad named[1007]: samba_dlz: allowing update of signer=BW10\$\@LIN.GROUP name=bw10.LIN.group tcpaddr=192.168.14.150 type=AAAA key=1068-ms-7.1-80306.78bac884-9620-11e9-62 a7-9a9237443f23/160/0 Jun 24 01:36:24 server5-ad named[1007]: samba_dlz: allowing update of signer=BW10\$\@LIN.GROUP name=bw10.LIN.group tcpaddr=192.168.14.150 type=A key=10...
2013 Apr 15
1
Imputation with SOM using kohonen package
...ng the SOM technique as a comparison to some other methods). I don't know if providing some or all data is useful, please let me know if you think it is. # get the data bw <- read.csv("bw.csv") # some missing values in data bwm <- data.frame(na.approx(bw, na.rm=FALSE, rule=2)) bw10 <- bwm[, 1:10] bw10.sc <- scale(bw10) bw.som <- som(data=bw10.sc, grid=somgrid(25,20,'hexagonal')) # playing with diff grid sizes # the different plots of the som at this point show some interesting features to me, but are quite difficult to interpret. # there's much work nee...
2019 Jun 25
2
Reverse DNS
...----- > > Jun 24 01:36:24 server5-ad named[1007]: samba_dlz: cancelling > transaction on zone LIN.group Jun 24 01:36:24 server5-ad > named[1007]: samba_dlz: starting transaction on zone > LIN.group Jun 24 01:36:24 server5-ad named[1007]: samba_dlz: > allowing update of signer=BW10\$\@LIN.GROUP > name=bw10.LIN.group tcpaddr=192.168.14.150 type=AAAA > > key=1068-ms-7.1-80306.78bac884-9620-11e9-62 > a7-9a9237443f23/160/0 > Jun 24 01:36:24 server5-ad named[1007]: samba_dlz: allowing > update of signer=BW10\$\@LIN.GROUP name=bw10.LIN.group &g...
2019 Jun 19
4
Reverse DNS
Hi, We have some issue with the reverse DNS in Samba AD. We're running Bind9_DLZ on Ubuntu 18.04. The DHCP server(Ubuntu 16.04) is different to the AD server and not in the same AD domain. The DHCP scope points to the Samba AD server as the DNS server When a machine with DHCP assigned address tries to update the DNS record, it is able to update the forward zone but not the reverse zone. The
2019 Jun 26
0
Reverse DNS
...------- > > Jun 24 01:36:24 server5-ad named[1007]: samba_dlz: cancelling > transaction on zone LIN.group Jun 24 01:36:24 server5-ad > named[1007]: samba_dlz: starting transaction on zone LIN.group Jun 24 > 01:36:24 server5-ad named[1007]: samba_dlz: > allowing update of signer=BW10\$\@LIN.GROUP name=bw10.LIN.group > tcpaddr=192.168.14.150 type=AAAA > > key=1068-ms-7.1-80306.78bac884-9620-11e9-62 > a7-9a9237443f23/160/0 > Jun 24 01:36:24 server5-ad named[1007]: samba_dlz: allowing update of > signer=BW10\$\@LIN.GROUP name=bw10.LIN.group >...
2019 Jun 27
4
Reverse DNS
Hai Praveen, > -----Oorspronkelijk bericht----- > Van: Praveen Ghimire [mailto:PGhimire at sundata.com.au] > Verzonden: donderdag 27 juni 2019 13:46 > Aan: samba at lists.samba.org > CC: 'L.P.H. van Belle' > Onderwerp: RE: [Samba] Reverse DNS > > Hi Guys, > > Thank you for your emails. Here is the info > > /etc/apparmor.d/local/usr.sbin.dhcp >
2019 Jul 04
0
Reverse DNS
...running the scripts > In the Windows machine, ticked the Use this connection's DNS > suffix in DNS registration under the Advanced DNS settings(IPV4) > Results > Both forward and reverse works > > Jul 4 06:16:03 server5 named[90]: samba_dlz: allowing update > of signer=BW10\$\@lin.GROUP name=150.14.168.192.in-addr.arpa > tcpaddr=192.168.14.150 type=PTR > key=1264-ms-7.4-aaefc.307cfafe-9e22-11e9-65a7-9a9237443f23/160/0 > Jul 4 06:16:03 server5 named[90]: samba_dlz: allowing update > of signer=BW10\$\@lin.GROUP name=150.14.168.192.in-addr.arpa > tcpa...
2004 Jun 10
6
Shaping incoming traffic on the other interface
Hi, I have a typical configuration for my firewall/gateway box: single network card, with a pppoe connection to the DSL modem. I''m already successfully shaping the uplink (how come that the wondershaper.htb doesn''t use the ceil parameter? It should implement bandwidth borrowing!) but i found the ingress policy a little bit rough. I''d like to keep the traffic categories