search for: fe6f

....11) systems with KAME IPSec implementation. I tried to establish the connection, but it has some problems which are explained below. |----------------->| host1-[mohan]| |host2-[ram] |<-----------------| host1 IPv6 address : fe80::2b0:d0ff:fe6f:dfa0 host2 IPv6 address : fe80::2b0:d0ff:fe48:7ce7 The 'ipsec.conf' file at Host1 and Host2 are attached along with this email.(you can refer them) IPsec is started with the following commands at both systems:(ipsec SA & SPD are set according to ipsec.conf files at both sides) ******...

...stems using IPv6 addresses.The connetcion is host-to-host between two FreeBSD( RELEASE 4.11) systems with KAME IPSec implementation. |----------------->| host1-[mohan]| |host2-[ram] |<-----------------| host1 IPv6 address : fe80::2b0:d0ff:fe6f:dfa0 host2 IPv6 address : fe80::2b0:d0ff:fe48:7ce7 The 'ipsec.conf' file at Host1 and Host2 are attached along with this email.(you can refer them) IPsec is started with the following commands at both systems: *******at Host1******* mohan# /usr/local/etc/rc.d/setkey.sh start Starting VPN...

...you get? Store your friends 'n family snaps for FREE with Yahoo! Photos http://in.photos.yahoo.com -------------- next part -------------- ########The 'ipsec.conf' file at Host2 ######### # flush configs flush ; spdflush ; # add a SAD entry add fe80::2b0:d0ff:fe48:7ce7 fe80::2b0:d0ff:fe6f:dfa0 esp 0xFEAD -m transport -E 3des-cbc "ipv6readylogo3descbcout1" -A hmac-sha1 "ipv6readylogsha1out1"; add fe80::2b0:d0ff:fe6f:dfa0 fe80::2b0:d0ff:fe48:7ce7 esp 0xFEED -m transport -E 3des-cbc "ipv6readylogo3descbcin01" -A hmac-sha1 "ipv6readylogsha1in01";...

I noticed that samba is listening on IPv6, so I became curious and wondered if I could actually use it, and so far, it looks like it isn't usable. Running nbtstat -A fe80::216:3eff:fe6f:1f3a on Windows returns the stupid message that the address must be in the a.b.c.d format. I then tried using nbtlookup from linux: nmblookup -S -U '[fe80::216:3eff:fe6f:1f3a]' \* 10.1.1.232 *<00> Looking up status of 10.1.1.232 DEVSERV2 <00> - B <ACT...

...bsystem.txt The idea of it sounds interesting, but I would really like to know if they have approached anyone regarding having it included in openssh proper. Thanks. -- MandrakeSoft Security; http://www.mandrakesecure.net/ "lynx - source http://linsec.ca/vdanen.asc | gpg --import" {FE6F2AFD: 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD} -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 186 bytes Desc: not available Url : http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/2002101...

...] On Behalf Of Phil Susi via samba Sent: 11 April 2017 13:54 To: samba at lists.samba.org Subject: [Samba] IPv6? I noticed that samba is listening on IPv6, so I became curious and wondered if I could actually use it, and so far, it looks like it isn't usable. Running nbtstat -A fe80::216:3eff:fe6f:1f3a on Windows returns the stupid message that the address must be in the a.b.c.d format. I then tried using nbtlookup from linux: nmblookup -S -U '[fe80::216:3eff:fe6f:1f3a]' \* 10.1.1.232 *<00> Looking up status of 10.1.1.232 DEVSERV2 <00> - B <ACT...

...vserver.local systemd[1]: Started The Apache HTTP Server. it's running. I have checked network status: # ifconfig eno16777728: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.222.133 netmask 255.255.255.0 broadcast 192.168.222.255 inet6 fe80::20c:29ff:fe6f:2b72 prefixlen 64 scopeid 0x20<link> ether 00:0c:29:6f:2b:72 txqueuelen 1000 (Ethernet) RX packets 152628 bytes 225455749 (215.0 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 54931 bytes 3355746 (3.2 MiB) TX errors 0 dropped 0 overr...

...en with the right password can't get in (sshd logs "PAM: Authentication Failure). Can the same not be done with the "without-password" option? Thanks. -- OpenSLS - Secure Linux Server: http://opensls.org/ "lynx -source http://linsec.ca/vdanen.asc | gpg --import" {FE6F2AFD : 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD} -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part Url : http://lists.mindrot.org/pipermail/openssh-unix-d...

Greetings all. I usually don't get involved in the mailing lists unless it is of a major importance. Here is a new problem that came up with the 3.3.p1 version, which I already reported to the Mandrake Developers on their RPM build. Basically, it boils down to this. In the Priv Seperation Mode or not, the public Key Authentication is throughly broken on all 3 versions of Keys,

Hello, I have recently compiled and installed release 3.8.1p1. This was done on a Solaris 8 system using LDAP as its naming service. The new release, however, will not let me log in (as a regular user). I repeatedly get "Permission denied, please try again" messages. The root user, though, can log in okay. The same thing happened with the 3.7.1p2 release. The 3.6.1p1 release

...if there are no plans, does anyone have any ideas how I could implement something like this? Thanks very much in advance. -- MandrakeSoft Security; http://www.mandrakesecure.net/ Online Security Resource Book; http://linsec.ca/ "lynx -source http://linsec.ca/vdanen.asc | gpg --import" {FE6F2AFD : 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD} -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 186 bytes Desc: not available Url : http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20030...

...confusing because 192.168.3.2 is the ip addres of the Mint computer running ssh to SERVER. WORKSTATION has an ip address of 192.168.3.3 10) nmblookup -d 2 '*' responds with rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) added interface eth0 ip=fe80::211:11ff:fe6f:8df0%eth0 bcast=fe80::ffff:ffff:ffff:ffff%eth0 netmask=ffff:ffff:ffff:ffff:: added interface eth0 ip=192.168.3.210 bcast=192.168.3.255 netmask=255.255.255.0 querying * on 192.168.3.255 Got a positive name query response from 192.168.3.2 ( 192.168.3.2 ) 192.168.3.2 *<00> Again, this is confusi...