Ipv6 on hpux


 
Thread Tools Search this Thread
Operating Systems HP-UX Ipv6 on hpux
# 1  
Old 04-14-2016
Ipv6 on hpux

my problem: i want to change from ipv4 to ipv6 on my home network.
On hpux i can assign only address non routable as fe80::1 fe80::3 etc to my lan0
Editing netconf-ipv6 i can assing a routable ipv6 address like
Code:
fd55:282f:3b98::/48

or
Code:
2001:470:26:307:89a0:aba1:f98b:eb3e

but only to alias interface like lan0:1,lan0:2
If i try to ping from other node fed80::1 is pingable,but ssh cannot reach it as host(using
etc/hosts) and fd55:282f:3b98::/48 is not pingable at all.
How to assign a correct ipv6 address to lan0?
Thanks
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Solaris

Solaris 10 IPv6

Hello Dears , please I need your support I have Oracle Solaris 10 X86 server please if you can advise how can I add IP v6 on my server and if IPv6 was disabled how can i enable it also how can i add two IP (v4 and v6) on the same interface or I have to add another interface . Thanks in... (1 Reply)
Discussion started by: ttashman
1 Replies

2. IP Networking

IPv6 Problems

I am trying to setup an IPv6 network. I modified the interfaces file: /etc/network/interfaces # The loopback network interface auto lo iface lo inet loopback iface etho0 inet static address 2620:7:a000::1 netmask 64 gateway ::ffff:c0a8:101 ... (0 Replies)
Discussion started by: Meow613
0 Replies

3. UNIX for Dummies Questions & Answers

Assigning ipv6 to bonding interface - getting old as well as changed ipv6 in ifconfig output

Hi, I have created a bonding bond1 interface with 6 Eth , mode=4. Recently i have changed my old ipv6 to new one and tried to restart as well as reload network service. Post which i can see old as well as changed ipv6 in ifconfig command output. Below are few files and command output for your... (1 Reply)
Discussion started by: omkar.jadhav
1 Replies

4. HP-UX

pwage-hpux-T for Trusted HPUX servers

I'm sharing this in case anybody needs it. Modified from the original solaris pwage script. This modified hpux script will check /etc/password file on hpux trusted systems search /tcb and grep the required u_succhg field. Calculate days to expiry and notify users via email. original solaris... (2 Replies)
Discussion started by: sparcguy
2 Replies

5. SuSE

Linux and IPv6

Hi gurus, In a few month, we must enable IPv6 on our Linux Server! Should we reinstall the Linux machine to enable IPv6 or could we just make some change in configuration's files? Could Linux run simultaneous IPv4 and IPv6? Thanks in advance for our help our ideas? Best regards, nm (3 Replies)
Discussion started by: hiddenshadow
3 Replies

6. Shell Programming and Scripting

Need Script to Use CPUs on a HPUX server to simulate Workload Manager on HPUX.

I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas? (2 Replies)
Discussion started by: cpolikowsky
2 Replies

7. AIX

IPv6 on AIX

Hi Every1, I want to configure IPv6 on AIX and want to communicate between IPv4 machine IP and IPv6 machine. Is it possible? (2 Replies)
Discussion started by: Shrek
2 Replies

8. IP Networking

IPv6 testbed

Hello guyz.. did some of u have implement or making a testbed for IPv6? if yes, can u attached the procedures and standard guidelines because i really need for my proposal.. thanx.. (2 Replies)
Discussion started by: unknown2205
2 Replies
Login or Register to Ask a Question
ALL-KNOWING-DNS(1p)					User Contributed Perl Documentation				       ALL-KNOWING-DNS(1p)

NAME
all-knowing-dns - Tiny DNS server for IPv6 Reverse DNS SYNOPSIS
all-knowing-dns [--configfile <path>] [--querylog] DESCRIPTION
AllKnowingDNS provides reverse DNS for IPv6 networks which use SLAAC (autoconf), e.g. for a /64 network. The problem with IPv6 reverse DNS and traditional nameservers is that the nameserver requires you to provide a zone file. Assuming you want to provide RDNS for a /64 network, you have 2**64 = 18446744073709551616 different usable IP addresses (a little less if you are using SLAAC). Providing a zone file for that, even in a very terse notation, would consume a huge amount of disk space and could not possibly be held in the memory of the computers we have nowadays. AllKnowingDNS instead generates PTR and AAAA records on the fly. You only configure which network you want to serve and what your entries should look like. OPTIONS
--configfile=path Use path instead of /etc/all-knowing-dns.conf as configuration file. --querylog Enable logging every query to stdout (for debugging). CONFIGURATION FILE (/etc/all-knowing-dns.conf) The configuration file is wonderfully simple: # Configuration file for AllKnowingDNS v1.3 listen 79.140.39.197 listen 2001:4d88:100e:1::3 # RaumZeitLabor network 2001:4d88:100e:ccc0::/64 resolves to ipv6-%DIGITS%.nutzer.raumzeitlabor.de with upstream 2001:4d88:100e:1::2 # Chaostreff network 2001:4d88:100e:cd1::/64 resolves to ipv6-%DIGITS%.treff.noname-ev.de This example contains all configuration directives. Let's go over them one by one: listen address Listens on the given address (IPv4 and IPv6 is supported) on port 53. network network Specifies that queries for PTR records within the given network should be answered (any query for an unconfigured network will be answered with NXDOMAIN). You need to specify at least the resolves to directive afterwards. resolves to address Specifies the address to which PTR records should resolve. The address needs to contain %DIGITS% exactly once. When answering AAAA queries, %DIGITS% will be parsed and converted back to an IPv6 address. Example: network 2001:4d88:100e:ccc0::/64 resolves to ipv6-%DIGITS%.nutzer.raumzeitlabor.de Example query: The PTR query 2001:4d88:100e:ccc0:216:eaff:fecb:826 will resolve to ipv6-0216eafffecb0826.nutzer.raumzeitlabor.de with upstream address Before answering a PTR query for this network, AllKnowingDNS will ask the DNS server at address first, appending .upstream to the query. Example: network 2001:4d88:100e:ccc0::/64 resolves to ipv6-%DIGITS%.nutzer.raumzeitlabor.de with upstream 2001:4d88:100e:1::2 Example query: The PTR query 2001:4d88:100e:ccc0:219:dbff:fe43:2ec5 will make AllKnowingDNS ask for 5.c.e.2.3.4.e.f.f.f.b.d.9.1.2.0.0.c.c.c.e.0.0.1. 8.8.d.4.1.0.0.2.ip6.arpa.upstream. at 2001:4d88:100e:1::2 and relay the answer, if any. DELEGATING ZONES
This section shows you how to delegate a zone in BIND9 or any DNS server with a compatible zone file syntax. To use AllKnowingDNS, you need to delegate the appropriate .ip6.arpa zone for your network and one regular domain. REVERSE DELEGATION (.ip6.arpa) $ORIGIN . $TTL 604800 ; 1 week e.0.0.1.8.8.d.4.1.0.0.2.ip6.arpa IN SOA infra.in.zekjur.net. hostmaster.zekjur.net. ( 20 ; serial 604800 ; refresh (1 week) 86400 ; retry (1 day) 2419200 ; expire (4 weeks) 604800 ; minimum (1 week) ) NS libri.sur5r.net. NS infra.in.zekjur.net. ; net for RaumZeitLabor 0.c.c.c.e.0.0.1.8.8.d.4.1.0.0.2.ip6.arpa. IN NS ipv6-rdns.zekjur.net. FORWARD DELEGATION (.nutzer.raumzeitlabor.de) $TTL 6h raumzeitlabor.de IN SOA ns1.jpru.de. hostmaster.jpru.de. ( 2012030701 3h 30m 7d 1d ) IN NS ns1.jpru.de. IN NS ns2.jpru.de. IN A 195.49.138.121 IN MX 10 rzl.uugrn.org. IN MX 20 up.uugrn.org. IN MX 50 mail.uugrn.org. IN MX 100 rzl.uugrn.org. nutzer.raumzeitlabor.de. IN NS ipv6-rdns.zekjur.net. VERSION
Version 1.3 AUTHOR
Michael Stapelberg, "<michael at stapelberg.de>" LICENSE AND COPYRIGHT
Copyright 2012 Michael Stapelberg. This program is free software; you can redistribute it and/or modify it under the terms of the BSD license. perl v5.14.2 2012-03-28 ALL-KNOWING-DNS(1p)