- NZNOG - lists.nznog.org

IPV6, Cisco
by Philip D'Ath 27 Feb '05

27 Feb '05

After much torment this weekend I have managed to get IPv6 running nicely on a low end Cisco DSL router (Cisco 837). If anyone wants an IPv6 connection at home (and a /48 block of real world IPv6 address space) to experiment with, say yourself some grief and start with this. http://www.ifm.net.nz/cookbooks/ipv6configwizard.html Now if we can just get a critical mass of users we might be able to tempt an ISP to offer native connections ... and actually use Joe's IPv6 F root server.

1 0

RE: [nznog] IPv6, NAT-PT
by Philip D'Ath 26 Feb '05

26 Feb '05

I'm talking about using NAT-PT to allow a native ipv6 network to talk to an ipv4 network. Without some kind of protocol translation (aka PT) ipv6 can't talk to ipv4. The reason this has to be done is because you can't buy an ipv6 connection to an ISP in NZ yet. -----Original Message----- From: Cameron Kerr [mailto:cameron(a)humbledown.org] Sent: Saturday, 26 February 2005 2:27 p.m. To: Philip D'Ath Cc: nznog Subject: Re: [nznog] IPv6, NAT-PT On 26/02/2005, at 1:25 PM, Philip D'Ath wrote: > I'm trying to get NAT-PT support working on a Cisco DSL router to > support native ipv6 clients behind it. I've done a lot of searching, > and can't find the answers to what I'm doing wrong. I have two > problems. Why are you using NAT with IPv6? There is very little reason pros for using IPv6 with NAT, and many cons. Afterall, NAT is just a hack for IPv4 to prevent address exhaustion. IIRC, ISPs are not to give out single IP addresses, but rather /64 allocations. Anyone care to correct me on this? -- Cameron Kerr Telecommunications Teaching Fellow & SysAdmin ckerr(a)cs.otago.ac.nz

7 15

Paradise bouncing emails?
by PhoneNet 25 Feb '05

25 Feb '05

Anyone else getting complaints from customers re email destined for Paradise accounts being bounced? Ian

3 2

RE: [nznog] IPv6, NAT-PT
by Philip D'Ath 25 Feb '05

25 Feb '05

I'm not wishing to get access to ipv6 content at this stage (but will of course eventually want to do this). I'm wanting to start using ipv6 internally. Once we are using it, I'll probably start some of our clients using it later this year. Once enough people are using it hopefully some ISP will start offering native ipv6 connections, because they will have a business case to do so. Hence, the desire to use NAT-PT, otherwise I'll be stuck running dual stacks. -----Original Message----- From: Joe Abley [mailto:jabley(a)isc.org] Sent: Saturday, 26 February 2005 4:57 p.m. To: Philip D'Ath Cc: nznog; Cameron Kerr Subject: Re: [nznog] IPv6, NAT-PT On 25 Feb 2005, at 20:39, Philip D'Ath wrote: > I'm talking about using NAT-PT to allow a native ipv6 network to talk > to an ipv4 network. Without some kind of protocol translation (aka > PT) > ipv6 can't talk to ipv4. The reason this has to be done is because > you can't buy an ipv6 connection to an ISP in NZ yet. Most people running v6 are only using their v6 access to reach content served over v6. Most of the mechanisms suggested to allow a v6-only host to access v4 content remain undeployed. If you want to reach v6 content, the easiest thing to do is find an ISP who can give you v6 transit. In the absense of local carriers with dual-stack edge routers (i.e. in the case of most of the planet) the way you do this is terminate a tunnel somewhere. Joe

1 0

IPv6, NAT-PT
by Philip D'Ath 25 Feb '05

25 Feb '05

I'm trying to get NAT-PT support working on a Cisco DSL router to support native ipv6 clients behind it. I've done a lot of searching, and can't find the answers to what I'm doing wrong. I have two problems. First, I can't get them to grab additional parameters from DHCP. I'm using: ipv6 dhcp pool dhcppool dns-server ::210.55.12.1 - I know the above is not likely to answer AAAA requests, but I plan to use DNS-ALG domain-name local.arpa Interface Ethernet0 ipv6 enable ipv6 nd other-config-flag ipv6 dhcp server dhcppool The second problem is I can't NAT-PT to work at all. It doesn't even attempt to do translations. Snippits I'm using are: Interface Dialer0 description ipv4 Interface connecting to Internet ipv6 nat Interface Ethernet0 description ipv6 Interface connection to local lan (aka LINK-LOCAL) ipv6 address 3FFE:AAAA:BBBB:1::9/64 - An address copied from an example, hope to use LINK-LOCAL addresses later ipv6 enable ipv6 nat ipv6 nat translation udp-timeout 600 ipv6 nat v6v4 source list pt-list1 interface Dialer0 overload ipv6 nat prefix 3FFE:B00:1::/96 ipv6 access-list pt-list1 permit ipv6 3FFE:AAAA:BBBB:1::/64 any

3 2

Notification of NZRR Database changes
by NZRR Database Notifications 24 Feb '05

24 Feb '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: [CityLink #1958] Routing updates for WIX Route Servers (fwd) - Date: Fri, 25 Feb 2005 17:41:59 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0502251727510.24165(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS18119 descr: advertised to AS9439 by LinuxNet - AS18119 members: 192.107.113.0/24^24-29, 202.7.4.80/29, 202.21.136.0/23^23-29, 202.36.44.0/24^24-29, 202.37.136.0/24^24-29, 202.49.249.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: lincoln(a)linuxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050222 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS18119 descr: advertised to AS9439 by LinuxNet - AS18119 members: 192.107.113.0/24^24-29, 202.7.4.80/29, 202.7.6.32/28^28-29, 202.21.136.0/23^23-29, 202.36.44.0/24^24-29, 202.37.136.0/24^24-29, 202.49.249.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: lincoln(a)linuxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050225 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 24 Feb '05

24 Feb '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: [CityLink #1951] Routing updates for APE Route Servers (fwd) - Date: Fri, 25 Feb 2005 16:57:10 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0502251654230.24165(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 198.32.66.0/24, 199.212.90.0/23, 199.212.92.0/23^23-24, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.240.0/23, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.41.136.0/22, 202.41.140.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20030407 changed: rpsl-admin(a)nzix.net 20040629 changed: rpsl-admin(a)nzix.net 20040831 changed: rpsl-admin(a)nzix.net 20040930 changed: rpsl-admin(a)nzix.net 20050224 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 138.235.0.0/16^16-29, 192.107.113.0/24^24-29, 192.173.16.0/21^21-29, 198.32.66.0/24^24-29, 199.212.90.0/23^23-29, 199.212.92.0/23^23-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.12.248.0/21^21-29, 202.14.100.0/24^24-29, 202.21.130.0/24^24-29, 202.21.136.0/23^23-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.32.0/24^24-29, 202.36.36.0/22^22-29, 202.36.44.0/24^24-29, 202.36.45.0/24^24-29, 202.36.76.0/23^23-29, 202.37.136.0/24^24-29, 202.37.140.0/22^22-29, 202.37.144.0/21^21-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.200.0/22^22-29, 202.37.224.0/21^21-29, 202.37.232.0/24^24-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.41.136.0/22^22-29, 202.41.140.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 202.50.246.0/24^24-29, 202.55.96.0/20^20-29, 202.74.224.0/21^21-29, 202.182.192.0/19^19-29, 205.233.128.0/21^21-29, 205.233.136.0/23^23-29, 205.233.243.0/24^24-29, 210.185.0.0/18^18-29, 210.48.0.0/17^17-29, 210.54.136.0/22^22-29, 210.54.140.0/24^24-29, 210.54.160.0/19^19-29, 210.55.182.0/23^23-29, 210.55.24.0/22^22-29, 210.55.253.0/24^24-29, 210.56.32.0/20^20-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050225 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 198.32.66.0/24, 199.212.90.0/23, 199.212.92.0/23^23-24, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.240.0/23, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.41.136.0/22, 202.41.140.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20030407 changed: rpsl-admin(a)nzix.net 20040629 changed: rpsl-admin(a)nzix.net 20040831 changed: rpsl-admin(a)nzix.net 20040930 changed: rpsl-admin(a)nzix.net 20050224 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 138.235.0.0/16^16-29, 192.107.113.0/24^24-29, 192.173.16.0/21^21-29, 198.32.66.0/24^24-29, 199.212.90.0/23^23-29, 199.212.92.0/23^23-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.12.248.0/21^21-29, 202.14.100.0/24^24-29, 202.21.130.0/24^24-29, 202.21.136.0/23^23-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.32.0/24^24-29, 202.36.36.0/22^22-29, 202.36.44.0/24^24-29, 202.36.45.0/24^24-29, 202.36.76.0/23^23-29, 202.37.136.0/24^24-29, 202.37.140.0/22^22-29, 202.37.144.0/21^21-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.200.0/22^22-29, 202.37.224.0/21^21-29, 202.37.232.0/24^24-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.41.136.0/22^22-29, 202.41.140.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 202.50.246.0/24^24-29, 202.55.96.0/20^20-29, 202.74.224.0/21^21-29, 202.182.192.0/19^19-29, 205.233.128.0/21^21-29, 205.233.136.0/23^23-29, 205.233.243.0/24^24-29, 210.185.0.0/18^18-29, 210.48.0.0/17^17-29, 210.54.136.0/22^22-29, 210.54.140.0/24^24-29, 210.54.160.0/19^19-29, 210.55.182.0/23^23-29, 210.55.24.0/22^22-29, 210.55.253.0/24^24-29, 210.56.32.0/20^20-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050225 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 24 Feb '05

24 Feb '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Fri, 25 Feb 2005 11:03:24 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0502251102510.23787(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS23754 descr: advertised to AS9560 by Citylink - AS23754 members: 198.48.0.0/22^22-24, 202.8.44.0/22^22-24, 202.7.5.0/24, 202.7.7.0/24, 203.118.144.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23754 descr: advertised to AS9560 by Citylink - AS23754 members: 198.48.0.0/22^22-24, 202.8.44.0/22^22-24, 202.7.5.0/24, 202.7.6.0/24, 203.118.144.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR

1 0

Email hammering from mta20X-rme.xtra.co.nz
by Simon Buchanan 24 Feb '05

24 Feb '05

Hi there, im wondering if anyone could point me in the rite direction here. Starting last night we have been hammered by xtra's mail servers from the email address haggis(a)guard.co.nz... Has any body on the list had simlar problems... How can i follow this up? Suggestions please :) Regards, Simon

3 2

RE: [nznog] (OT) Fax spam (Anti-spam legislation update)
by Regan Murphy 24 Feb '05

24 Feb '05

>You will need: > >* An older fax machine that scans the document slowly as it sends it >* A vivid marker >* Some sellotape This is the age of technology. Surely a few lines of code, a modem and some fax protocols could achieve the same result. Maybe you could even redirect your email spam junk folders to your fax spammer to give it a nice twist. ;) -- Regan

2 1