You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@knox.apache.org by Rajat Goel <ra...@guavus.com> on 2018/07/27 14:24:10 UTC

IPv6 support

Hello,

Can Knox work on IPv6 interface? Specifically, I want to have Client/User to Knox communication on IPv6 network but my backend services say Ambari/WebHDFS runs on IPv4 network so I want Knox to Service communication on IPv4 network. Will this work with Knox ?

Thanks & Regards,
Rajat

Re: IPv6 support

Posted by larry mccay <lm...@apache.org>.
Well, it seems that you can certainly specify IPv6 using curl for a call to
webhdfs as the following output shows:

new-host-6:knox-1.1.0 lmccay$ curl -ivk6u guest:guest-password
https://localhost:8443/gateway/sandbox/webhdfs/v1/tmp?op=LISTSTATUS
*   *Trying ::1*...
* TCP_NODELAY set
** Connected to localhost (::1) port 8443 (#0)*
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection:
ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server did not agree to a protocol
* Server certificate:
*  subject: C=US; ST=Test; L=Test; O=Hadoop; OU=Test; CN=localhost
*  start date: Jul 26 02:14:01 2018 GMT
*  expire date: Jul 26 02:14:01 2019 GMT
*  issuer: C=US; ST=Test; L=Test; O=Hadoop; OU=Test; CN=localhost
*  SSL certificate verify result: self signed certificate (18), continuing
anyway.
* Server auth using Basic with user 'guest'
> GET /gateway/sandbox/webhdfs/v1/tmp?op=LISTSTATUS HTTP/1.1
> Host: localhost:8443
> Authorization: Basic Z3Vlc3Q6Z3Vlc3QtcGFzc3dvcmQ=
> User-Agent: curl/7.54.0
> Accept: */*
>
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Date: Fri, 27 Jul 2018 15:30:19 GMT
Date: Fri, 27 Jul 2018 15:30:19 GMT
< Set-Cookie:
JSESSIONID=k4qsr435jctv1sx4bf6r7yo0k;Path=/gateway/sandbox;Secure;HttpOnly
Set-Cookie:
JSESSIONID=k4qsr435jctv1sx4bf6r7yo0k;Path=/gateway/sandbox;Secure;HttpOnly
< Expires: Thu, 01 Jan 1970 00:00:00 GMT
Expires: Thu, 01 Jan 1970 00:00:00 GMT
< Set-Cookie: rememberMe=deleteMe; Path=/gateway/sandbox; Max-Age=0;
Expires=Thu, 26-Jul-2018 15:30:19 GMT
Set-Cookie: rememberMe=deleteMe; Path=/gateway/sandbox; Max-Age=0;
Expires=Thu, 26-Jul-2018 15:30:19 GMT
< Server: nginx/1.15.0
Server: nginx/1.15.0
< Date: Fri, 27 Jul 2018 15:30:20 GMT
Date: Fri, 27 Jul 2018 15:30:20 GMT
< Content-Type: application/json; charset=UTF-8
Content-Type: application/json; charset=UTF-8
< Cache-Control: no-cache
Cache-Control: no-cache
< Expires: Fri, 27 Jul 2018 15:30:19 GMT
Expires: Fri, 27 Jul 2018 15:30:19 GMT
< Pragma: no-cache
Pragma: no-cache
< Expires: Fri, 27 Jul 2018 15:30:19 GMT
Expires: Fri, 27 Jul 2018 15:30:19 GMT
< Pragma: no-cache
Pragma: no-cache
< X-FRAME-OPTIONS: SAMEORIGIN
X-FRAME-OPTIONS: SAMEORIGIN
< Content-Length: 1003
Content-Length: 1003

<
* Connection #0 to host localhost left intact
{"FileStatuses":{"FileStatus":[{"accessTime":0,"blockSize":0,"childrenNum":0,"fileId":17212,"group":"hadoop","length":0,"modificationTime":1529337971112,"owner":"druid","pathSuffix":"druid-indexing","permission":"775","replication":0,"storagePolicy":0,"type":"DIRECTORY"},{"accessTime":0,"blockSize":0,"childrenNum":1,"fileId":16393,"group":"hdfs","length":0,"modificationTime":1529333529967,"owner":"hdfs","pathSuffix":"entity-file-history","permission":"755","replication":0,"storagePolicy":0,"type":"DIRECTORY"},{"accessTime":0,"blockSize":0,"childrenNum":2,"fileId":16537,"group":"hdfs","length":0,"modificationTime":1529334778446,"owner":"ambari-qa","pathSuffix":"hive","permission":"733","replication":0,"storagePolicy":0,"type":"DIRECTORY"},{"accessTime":1532571397860,"blockSize":134217728,"childrenNum":0,"fileId":144616,"group":"hdfs","length":96969,"modificationTime":1532571397885,"owner":"sam","pathSuffix":"sample.log","permission":"755","replication":1,"storagePolicy":0,"type":"FILE"}]}}


Hope that is helpful.

On Fri, Jul 27, 2018 at 10:24 AM, Rajat Goel <ra...@guavus.com> wrote:

> Hello,
>
>
>
> Can Knox work on IPv6 interface? Specifically, I want to have Client/User
> to Knox communication on IPv6 network but my backend services say
> Ambari/WebHDFS runs on IPv4 network so I want Knox to Service communication
> on IPv4 network. Will this work with Knox ?
>
>
>
> Thanks & Regards,
>
> Rajat
>