- wlug - list.wlug.org.nz

RE: [wlug] iptables question
by Lindsay Druett 26 Apr '04

26 Apr '04

Well, that address space wasn't featured on the Auckland Peering Exchange, Mmm... > -----Original Message----- > From: pdm1-forwarding > Sent: Tuesday, 27 April 2004 11:43 > To: Waikato Linux Users Group > Subject: Re: [wlug] iptables question > > > Lindsay Druett wrote: > > What ? All of it ? > > > > But someone mentioned that there are bits of it over in Japan. > > Someone else mentioned that it was all over the show. > > That would have been a more recent assignment, I don't think APNIC > > even see Telecom as a big enough player to assign a full /8 block. > > > > They got assigned 222.152/16. I have one of these addresses > on my home DSL > and I can't get to various portions of the internet, can be > quite annoying. > > Philip Murray > Systems Engineer - Open2view.com > webmaster(a)open2view.com > > _______________________________________________ > wlug mailing list | wlug(a)list.waikato.ac.nz > Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug > >

1 0

RE: [wlug] iptables question
by Lindsay Druett 26 Apr '04

26 Apr '04

Of course they are, which means getting a /24 block might be a bit easier, and that they stand a chance for a /16 block. > -----Original Message----- > From: Drew Broadley [mailto:drew(a)corrupt.co.nz] > Sent: Tuesday, 27 April 2004 11:44 > To: 'Waikato Linux Users Group' > Subject: RE: [wlug] iptables question > > > > I don't think APNIC even see Telecom as a big enough player > to assign > a > > full /8 block. > > Last I saw they were a medium membership holder. > > Surely they would "care" about that sized customer ? > > - Drew > > _______________________________________________ > wlug mailing list | wlug(a)list.waikato.ac.nz > Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug > >

1 0

RE: [wlug] iptables question
by Lindsay Druett 26 Apr '04

26 Apr '04

What ? All of it ? But someone mentioned that there are bits of it over in Japan. Someone else mentioned that it was all over the show. That would have been a more recent assignment, I don't think APNIC even see Telecom as a big enough player to assign a full /8 block. Anyway, not my problem... > -----Original Message----- > From: Drew Broadley [mailto:drew(a)corrupt.co.nz] > Sent: Tuesday, 27 April 2004 11:13 > To: 'Waikato Linux Users Group' > Subject: RE: [wlug] iptables question > > > > Dunno... Who has that one ? > > Who knows, everything under my administrative control was in > > there, so I'm happy with it... > > Xtra's Flatrate 256k Netblock. > > > _______________________________________________ > wlug mailing list | wlug(a)list.waikato.ac.nz > Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug > >

3 3

RE: [wlug] iptables question
by Lindsay Druett 26 Apr '04

26 Apr '04

Dunno... Who has that one ? Who knows, everything under my administrative control was in there, so I'm happy with it... > -----Original Message----- > From: Drew Broadley [mailto:drew(a)corrupt.co.nz] > Sent: Tuesday, 27 April 2004 09:50 > To: 'Waikato Linux Users Group' > Subject: RE: [wlug] iptables question > > > > Here you go... > > Auckland Peering Exchnage's peering list would be a good start... > > > > <prefix-list> > > Where is 222/8 ? :) > > - Drew > > _______________________________________________ > wlug mailing list | wlug(a)list.waikato.ac.nz > Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug > >

4 3

RE: [wlug] iptables question
by Lindsay Druett 26 Apr '04

26 Apr '04

Yeah, so if you decided to go down the path that Bruce suggested which was to allow only source addresses from within New Zealand networks to do normal port 80 web traffic, then the first place I would look is the BGP prefix lists on the New Zealand's primary peering point, and worry about the rest later if that becomes a problem. As I said, this is a good start... > -----Original Message----- > From: Richard Stevenson [mailto:richard(a)endace.com] > Sent: Tuesday, 27 April 2004 10:09 > To: Waikato Linux Users Group > Subject: RE: [wlug] iptables question > > > On Tue, 27 Apr 2004, Lindsay Druett wrote: > > > Dunno... Who has that one ? > > 222/8 is spread all over APNIC space... KDDI (in Japan) has > 222.0.0.0/12, > if I calculate my bits correctly. > > Cheers > > R > > > Who knows, everything under my administrative control was > in there, so > > I'm happy with it... > > > > > -----Original Message----- > > > From: Drew Broadley [mailto:drew(a)corrupt.co.nz] > > > Sent: Tuesday, 27 April 2004 09:50 > > > To: 'Waikato Linux Users Group' > > > Subject: RE: [wlug] iptables question > > > > > > > > > > Here you go... > > > > Auckland Peering Exchnage's peering list would be a > good start... > > > > > > > > <prefix-list> > > > > > > Where is 222/8 ? :) > > -- > Richard Stevenson > _______________________________________________ > wlug mailing list | wlug(a)list.waikato.ac.nz > Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug > >

1 0

food for installfest thought
by Gavin Denby 26 Apr '04

26 Apr '04

Ok its really nothing to do with the installfest, But here is an interesting article comparing a mandrake and win2k install on a system. All the rules and issues are there, but its a fair view on the install processes of 2 OS's Its a fun read, we all know it of course, but for those that are not forced to do Windows installs, it exposes some of the problems with installing Windows onto a machine. If you have time its worth looking at . Have a nice day. (and no I don't use either of these versions, so I can't discuss the findings.)

1 1

RE: [wlug] iptables question
by Lindsay Druett 26 Apr '04

26 Apr '04

> -----Original Message----- > From: zcat [mailto:zcat(a)wired.net.nz] > Sent: Tuesday, 27 April 2004 08:01 > To: Waikato Linux Users Group > Subject: Re: [wlug] iptables question > > > DrWho? wrote: > > > My idea was to use a callback too hook port 80 and use a > perl script > > to reverse lookup the ip address and look for .nz at the > end and pass > > fail there after. > > PAINFUL!! > > If you wanted it hidden you'd have do blackhole the port by default, > sniff for attempted connections, look up the address, change > firewalling > on the fly.. and you're opening yourself up for a huge self-DoS if > someone spoofs millions of random SYN packets at you. > > I believe there's a list of IP ranges that are allocated within New > Zealand. configure your box to accept those and blackhole everything > else. End of problem. > > Here you go... Auckland Peering Exchnage's peering list would be a good start... ip prefix-list pl100 permit 129.223.96.0/19 le 24 ip prefix-list pl100 permit 130.123.0.0/16 le 24 ip prefix-list pl100 permit 130.195.0.0/16 le 24 ip prefix-list pl100 permit 130.216.0.0/15 le 24 ip prefix-list pl100 permit 131.203.0.0/16 le 24 ip prefix-list pl100 permit 134.128.160.0/22 le 24 ip prefix-list pl100 permit 138.211.0.0/16 le 24 ip prefix-list pl100 permit 138.235.0.0/16 le 24 ip prefix-list pl100 permit 143.96.0.0/16 le 24 ip prefix-list pl100 permit 144.130.192.0/24 ip prefix-list pl100 permit 151.135.0.0/16 le 24 ip prefix-list pl100 permit 152.158.213.0/24 ip prefix-list pl100 permit 152.158.254.0/23 ge 24 le 24 ip prefix-list pl100 permit 153.111.0.0/16 le 24 ip prefix-list pl100 permit 156.59.0.0/16 le 24 ip prefix-list pl100 permit 156.62.0.0/16 le 24 ip prefix-list pl100 permit 161.65.0.0/16 le 24 ip prefix-list pl100 permit 163.7.0.0/16 le 24 ip prefix-list pl100 permit 165.84.0.0/16 le 24 ip prefix-list pl100 permit 165.205.0.0/16 le 24 ip prefix-list pl100 permit 166.65.0.0/16 le 24 ip prefix-list pl100 permit 166.83.0.0/16 le 24 ip prefix-list pl100 permit 170.9.56.0/21 le 24 ip prefix-list pl100 permit 192.5.5.0/24 ip prefix-list pl100 permit 192.54.130.0/24 ip prefix-list pl100 permit 192.88.190.0/24 ip prefix-list pl100 permit 192.94.169.0/24 ip prefix-list pl100 permit 192.100.53.0/24 ip prefix-list pl100 permit 192.105.10.0/24 ip prefix-list pl100 permit 192.107.113.0/24 ip prefix-list pl100 permit 192.107.171.0/24 ip prefix-list pl100 permit 192.107.172.0/24 ip prefix-list pl100 permit 192.122.171.0/24 ip prefix-list pl100 permit 192.122.180.0/24 ip prefix-list pl100 permit 192.146.150.0/24 ip prefix-list pl100 permit 192.148.221.0/24 ip prefix-list pl100 permit 192.150.219.0/24 ip prefix-list pl100 permit 192.156.225.0/24 ip prefix-list pl100 permit 192.173.16.0/21 le 24 ip prefix-list pl100 permit 192.188.185.0/24 ip prefix-list pl100 permit 192.190.108.0/24 ip prefix-list pl100 permit 192.195.12.0/23 le 24 ip prefix-list pl100 permit 192.195.14.0/24 ip prefix-list pl100 permit 192.195.219.0/24 ip prefix-list pl100 permit 192.203.154.0/24 ip prefix-list pl100 permit 192.203.216.0/24 ip prefix-list pl100 permit 192.207.143.0/24 ip prefix-list pl100 permit 192.245.36.0/24 ip prefix-list pl100 permit 198.32.66.0/24 ip prefix-list pl100 permit 198.48.0.0/22 ip prefix-list pl100 permit 199.190.182.0/24 ip prefix-list pl100 permit 199.212.93.0/24 ip prefix-list pl100 permit 202.0.10.0/24 ip prefix-list pl100 permit 202.0.32.0/19 le 24 ip prefix-list pl100 permit 202.0.84.0/24 ip prefix-list pl100 permit 202.0.151.0/24 ip prefix-list pl100 permit 202.2.8.0/21 le 24 ip prefix-list pl100 permit 202.2.96.0/19 le 24 ip prefix-list pl100 permit 202.6.5.0/24 ip prefix-list pl100 permit 202.6.75.0/24 ip prefix-list pl100 permit 202.6.84.0/24 ip prefix-list pl100 permit 202.7.4.0/24 ip prefix-list pl100 permit 202.7.32.0/24 ip prefix-list pl100 permit 202.7.34.0/23 le 24 ip prefix-list pl100 permit 202.7.38.0/24 ip prefix-list pl100 permit 202.8.13.0/24 ip prefix-list pl100 permit 202.8.44.0/22 le 24 ip prefix-list pl100 permit 202.10.80.0/20 le 24 ip prefix-list pl100 permit 202.12.0.0/24 ip prefix-list pl100 permit 202.12.70.0/24 ip prefix-list pl100 permit 202.12.105.0/24 ip prefix-list pl100 permit 202.14.0.0/18 le 24 ip prefix-list pl100 permit 202.14.82.0/24 ip prefix-list pl100 permit 202.14.99.0/24 ip prefix-list pl100 permit 202.14.100.0/24 ip prefix-list pl100 permit 202.14.102.0/24 ip prefix-list pl100 permit 202.14.141.0/24 ip prefix-list pl100 permit 202.14.142.0/24 ip prefix-list pl100 permit 202.14.216.0/23 le 24 ip prefix-list pl100 permit 202.14.252.0/23 le 24 ip prefix-list pl100 permit 202.20.0.0/21 le 24 ip prefix-list pl100 permit 202.20.64.0/23 le 24 ip prefix-list pl100 permit 202.20.92.0/23 le 24 ip prefix-list pl100 permit 202.20.102.0/24 ip prefix-list pl100 permit 202.21.16.0/20 le 24 ip prefix-list pl100 permit 202.21.130.0/24 ip prefix-list pl100 permit 202.21.136.0/23 le 24 ip prefix-list pl100 permit 202.21.157.0/24 ip prefix-list pl100 permit 202.22.16.0/20 le 24 ip prefix-list pl100 permit 202.27.34.0/24 ip prefix-list pl100 permit 202.27.40.0/21 le 24 ip prefix-list pl100 permit 202.27.48.0/21 le 24 ip prefix-list pl100 permit 202.27.56.0/22 le 24 ip prefix-list pl100 permit 202.27.64.0/23 le 24 ip prefix-list pl100 permit 202.27.68.0/24 ip prefix-list pl100 permit 202.27.76.0/24 ip prefix-list pl100 permit 202.27.78.0/23 le 24 ip prefix-list pl100 permit 202.27.81.0/24 ip prefix-list pl100 permit 202.27.83.0/24 ip prefix-list pl100 permit 202.27.85.0/24 ip prefix-list pl100 permit 202.27.88.0/23 le 24 ip prefix-list pl100 permit 202.27.92.0/22 le 24 ip prefix-list pl100 permit 202.27.99.0/24 ip prefix-list pl100 permit 202.27.100.0/22 le 24 ip prefix-list pl100 permit 202.27.110.0/24 ip prefix-list pl100 permit 202.27.140.0/22 le 24 ip prefix-list pl100 permit 202.27.186.0/23 le 24 ip prefix-list pl100 permit 202.27.188.128/25 ip prefix-list pl100 permit 202.27.192.0/21 le 24 ip prefix-list pl100 permit 202.27.200.0/22 le 24 ip prefix-list pl100 permit 202.27.204.0/24 ip prefix-list pl100 permit 202.27.206.0/24 ip prefix-list pl100 permit 202.27.208.0/21 ge 24 le 24 ip prefix-list pl100 permit 202.27.210.0/23 ip prefix-list pl100 permit 202.27.212.0/22 le 23 ip prefix-list pl100 permit 202.27.216.0/22 le 24 ip prefix-list pl100 permit 202.27.222.0/24 ip prefix-list pl100 permit 202.27.234.0/24 ip prefix-list pl100 permit 202.27.236.0/24 ip prefix-list pl100 permit 202.27.247.0/24 ip prefix-list pl100 permit 202.27.250.0/23 le 24 ip prefix-list pl100 permit 202.36.16.0/21 le 24 ip prefix-list pl100 permit 202.36.24.0/22 le 24 ip prefix-list pl100 permit 202.36.33.0/24 ip prefix-list pl100 permit 202.36.34.0/23 le 24 ip prefix-list pl100 permit 202.36.36.0/22 le 24 ip prefix-list pl100 permit 202.36.43.0/24 ip prefix-list pl100 permit 202.36.44.0/23 le 24 ip prefix-list pl100 permit 202.36.46.0/24 ip prefix-list pl100 permit 202.36.60.0/24 ip prefix-list pl100 permit 202.36.70.0/24 ip prefix-list pl100 permit 202.36.75.0/24 ip prefix-list pl100 permit 202.36.76.0/23 le 24 ip prefix-list pl100 permit 202.36.80.0/24 ip prefix-list pl100 permit 202.36.94.0/23 le 24 ip prefix-list pl100 permit 202.36.114.0/24 ip prefix-list pl100 permit 202.36.121.0/24 ip prefix-list pl100 permit 202.36.122.0/23 le 24 ip prefix-list pl100 permit 202.36.137.0/24 ip prefix-list pl100 permit 202.36.141.0/24 ip prefix-list pl100 permit 202.36.147.0/24 ip prefix-list pl100 permit 202.36.148.0/24 ip prefix-list pl100 permit 202.36.154.0/24 ip prefix-list pl100 permit 202.36.162.0/23 le 24 ip prefix-list pl100 permit 202.36.164.0/22 le 24 ip prefix-list pl100 permit 202.36.173.0/24 ip prefix-list pl100 permit 202.36.174.0/24 ip prefix-list pl100 permit 202.36.183.0/24 ip prefix-list pl100 permit 202.36.195.0/24 ip prefix-list pl100 permit 202.36.198.0/23 le 24 ip prefix-list pl100 permit 202.36.202.0/24 ip prefix-list pl100 permit 202.36.204.0/23 le 24 ip prefix-list pl100 permit 202.36.219.0/24 ip prefix-list pl100 permit 202.36.224.0/22 le 24 ip prefix-list pl100 permit 202.36.229.0/24 ip prefix-list pl100 permit 202.36.230.0/23 le 24 ip prefix-list pl100 permit 202.36.232.0/24 ip prefix-list pl100 permit 202.36.235.0/24 ip prefix-list pl100 permit 202.36.244.0/23 le 24 ip prefix-list pl100 permit 202.36.251.0/24 ip prefix-list pl100 permit 202.36.252.0/24 ip prefix-list pl100 permit 202.36.255.0/24 ip prefix-list pl100 permit 202.37.0.0/20 le 24 ip prefix-list pl100 permit 202.37.19.0/24 ip prefix-list pl100 permit 202.37.23.0/24 ip prefix-list pl100 permit 202.37.27.0/24 ip prefix-list pl100 permit 202.37.28.0/24 ip prefix-list pl100 permit 202.37.32.0/21 le 24 ip prefix-list pl100 permit 202.37.52.0/23 le 24 ip prefix-list pl100 permit 202.37.54.0/24 ip prefix-list pl100 permit 202.37.57.0/24 ip prefix-list pl100 permit 202.37.60.0/22 le 24 ip prefix-list pl100 permit 202.37.64.0/23 le 24 ip prefix-list pl100 permit 202.37.68.0/24 ip prefix-list pl100 permit 202.37.70.0/23 le 24 ip prefix-list pl100 permit 202.37.72.0/24 ip prefix-list pl100 permit 202.37.74.0/23 le 24 ip prefix-list pl100 permit 202.37.76.0/22 ge 24 le 24 ip prefix-list pl100 permit 202.37.78.0/23 ip prefix-list pl100 permit 202.37.80.0/22 le 24 ip prefix-list pl100 permit 202.37.85.0/24 ip prefix-list pl100 permit 202.37.86.0/23 le 24 ip prefix-list pl100 permit 202.37.88.0/24 ip prefix-list pl100 permit 202.37.90.0/23 le 24 ip prefix-list pl100 permit 202.37.93.0/24 ip prefix-list pl100 permit 202.37.101.0/24 ip prefix-list pl100 permit 202.37.106.0/23 le 24 ip prefix-list pl100 permit 202.37.112.0/24 ip prefix-list pl100 permit 202.37.114.0/24 ip prefix-list pl100 permit 202.37.117.0/24 ip prefix-list pl100 permit 202.37.118.0/24 ip prefix-list pl100 permit 202.37.120.0/24 ip prefix-list pl100 permit 202.37.124.0/23 le 24 ip prefix-list pl100 permit 202.37.127.0/24 ip prefix-list pl100 permit 202.37.129.0/24 ip prefix-list pl100 permit 202.37.132.0/24 ip prefix-list pl100 permit 202.37.135.0/24 ip prefix-list pl100 permit 202.37.137.0/24 ip prefix-list pl100 permit 202.37.138.0/23 le 24 ip prefix-list pl100 permit 202.37.140.0/22 le 24 ip prefix-list pl100 permit 202.37.144.0/21 le 24 ip prefix-list pl100 permit 202.37.160.0/24 ip prefix-list pl100 permit 202.37.163.0/24 ip prefix-list pl100 permit 202.37.167.0/24 ip prefix-list pl100 permit 202.37.168.0/24 ip prefix-list pl100 permit 202.37.171.0/24 ip prefix-list pl100 permit 202.37.173.0/24 ip prefix-list pl100 permit 202.37.176.0/24 ip prefix-list pl100 permit 202.37.181.0/24 ip prefix-list pl100 permit 202.37.184.0/22 ge 24 le 24 ip prefix-list pl100 permit 202.37.184.0/23 ip prefix-list pl100 permit 202.37.192.0/23 le 24 ip prefix-list pl100 permit 202.37.194.0/24 ip prefix-list pl100 permit 202.37.197.0/24 ip prefix-list pl100 permit 202.37.200.0/22 le 24 ip prefix-list pl100 permit 202.37.218.0/23 le 24 ip prefix-list pl100 permit 202.37.220.0/24 ip prefix-list pl100 permit 202.37.222.0/24 ip prefix-list pl100 permit 202.37.224.0/21 le 24 ip prefix-list pl100 permit 202.37.234.0/24 ip prefix-list pl100 permit 202.37.240.0/23 le 24 ip prefix-list pl100 permit 202.37.248.0/22 le 24 ip prefix-list pl100 permit 202.37.252.0/24 ip prefix-list pl100 permit 202.37.254.0/24 ip prefix-list pl100 permit 202.39.129.0/24 ip prefix-list pl100 permit 202.41.136.0/22 le 24 ip prefix-list pl100 permit 202.41.140.0/24 ip prefix-list pl100 permit 202.45.254.0/24 ip prefix-list pl100 permit 202.46.160.0/19 le 24 ip prefix-list pl100 permit 202.49.0.0/21 le 24 ip prefix-list pl100 permit 202.49.16.0/20 le 24 ip prefix-list pl100 permit 202.49.33.0/24 ip prefix-list pl100 permit 202.49.34.0/23 le 24 ip prefix-list pl100 permit 202.49.46.0/23 le 24 ip prefix-list pl100 permit 202.49.48.0/24 ip prefix-list pl100 permit 202.49.58.0/24 ip prefix-list pl100 permit 202.49.62.0/23 le 24 ip prefix-list pl100 permit 202.49.64.0/21 le 24 ip prefix-list pl100 permit 202.49.72.0/22 le 24 ip prefix-list pl100 permit 202.49.78.0/24 ip prefix-list pl100 permit 202.49.80.0/22 ge 23 le 24 ip prefix-list pl100 permit 202.49.84.0/24 ip prefix-list pl100 permit 202.49.88.0/21 ge 23 le 24 ip prefix-list pl100 permit 202.49.92.0/22 ip prefix-list pl100 permit 202.49.96.0/21 le 24 ip prefix-list pl100 permit 202.49.104.0/24 ip prefix-list pl100 permit 202.49.106.0/24 ip prefix-list pl100 permit 202.49.135.0/24 ip prefix-list pl100 permit 202.49.136.0/23 le 24 ip prefix-list pl100 permit 202.49.140.0/23 le 24 ip prefix-list pl100 permit 202.49.144.0/24 ip prefix-list pl100 permit 202.49.148.0/23 le 24 ip prefix-list pl100 permit 202.49.152.0/21 le 24 ip prefix-list pl100 permit 202.49.164.0/23 le 24 ip prefix-list pl100 permit 202.49.168.0/24 ip prefix-list pl100 permit 202.49.172.0/22 le 24 ip prefix-list pl100 permit 202.49.176.0/23 le 24 ip prefix-list pl100 permit 202.49.178.0/24 ip prefix-list pl100 permit 202.49.180.0/23 le 24 ip prefix-list pl100 permit 202.49.183.0/24 ip prefix-list pl100 permit 202.49.186.0/24 ip prefix-list pl100 permit 202.49.189.0/24 ip prefix-list pl100 permit 202.49.198.0/23 le 24 ip prefix-list pl100 permit 202.49.200.0/22 le 24 ip prefix-list pl100 permit 202.49.206.0/24 ip prefix-list pl100 permit 202.49.208.0/22 le 24 ip prefix-list pl100 permit 202.49.212.0/23 le 24 ip prefix-list pl100 permit 202.49.214.0/24 ip prefix-list pl100 permit 202.49.224.0/20 le 24 ip prefix-list pl100 permit 202.49.240.0/21 ge 22 le 24 ip prefix-list pl100 permit 202.49.250.0/24 ip prefix-list pl100 permit 202.49.252.0/22 le 24 ip prefix-list pl100 permit 202.50.0.0/24 ip prefix-list pl100 permit 202.50.16.0/20 le 24 ip prefix-list pl100 permit 202.50.49.0/24 ip prefix-list pl100 permit 202.50.52.0/22 le 24 ip prefix-list pl100 permit 202.50.57.0/24 ip prefix-list pl100 permit 202.50.60.0/22 le 24 ip prefix-list pl100 permit 202.50.64.0/21 le 24 ip prefix-list pl100 permit 202.50.72.0/23 le 24 ip prefix-list pl100 permit 202.50.84.0/24 ip prefix-list pl100 permit 202.50.95.0/24 ip prefix-list pl100 permit 202.50.102.0/23 ge 24 le 24 ip prefix-list pl100 permit 202.50.104.0/22 le 24 ip prefix-list pl100 permit 202.50.109.0/24 ip prefix-list pl100 permit 202.50.110.0/23 le 24 ip prefix-list pl100 permit 202.50.112.0/24 ip prefix-list pl100 permit 202.50.117.0/24 ip prefix-list pl100 permit 202.50.124.0/22 le 24 ip prefix-list pl100 permit 202.50.129.0/24 ip prefix-list pl100 permit 202.50.137.0/24 ip prefix-list pl100 permit 202.50.139.0/24 ip prefix-list pl100 permit 202.50.143.0/24 ip prefix-list pl100 permit 202.50.164.0/23 le 24 ip prefix-list pl100 permit 202.50.167.0/24 ip prefix-list pl100 permit 202.50.170.0/24 ip prefix-list pl100 permit 202.50.176.0/23 ge 24 le 24 ip prefix-list pl100 permit 202.50.176.0/24 ge 25 le 29 ip prefix-list pl100 permit 202.50.188.0/22 le 24 ip prefix-list pl100 permit 202.50.192.0/19 le 24 ip prefix-list pl100 permit 202.50.240.0/24 ip prefix-list pl100 permit 202.50.244.0/24 ip prefix-list pl100 permit 202.50.252.0/24 ip prefix-list pl100 permit 202.50.255.0/24 ip prefix-list pl100 permit 202.53.176.0/20 le 24 ip prefix-list pl100 permit 202.62.116.0/23 le 29 ip prefix-list pl100 permit 202.65.32.0/19 le 24 ip prefix-list pl100 permit 202.68.94.0/23 le 27 ip prefix-list pl100 permit 202.73.192.0/20 le 24 ip prefix-list pl100 permit 202.74.192.0/20 le 24 ip prefix-list pl100 permit 202.78.128.0/19 le 24 ip prefix-list pl100 permit 202.83.32.0/19 le 24 ip prefix-list pl100 permit 202.86.96.0/21 le 24 ip prefix-list pl100 permit 202.89.32.0/19 le 24 ip prefix-list pl100 permit 202.89.128.0/19 le 24 ip prefix-list pl100 permit 202.124.96.0/20 le 24 ip prefix-list pl100 permit 202.127.8.0/22 le 29 ip prefix-list pl100 permit 202.135.20.0/24 ip prefix-list pl100 permit 202.135.38.0/24 ip prefix-list pl100 permit 202.135.48.0/24 ip prefix-list pl100 permit 202.135.62.0/24 ip prefix-list pl100 permit 202.135.64.0/24 ip prefix-list pl100 permit 202.135.85.0/24 ip prefix-list pl100 permit 202.135.86.0/24 ip prefix-list pl100 permit 202.135.112.0/24 ip prefix-list pl100 permit 202.135.115.0/24 ip prefix-list pl100 permit 202.135.116.0/24 ip prefix-list pl100 permit 202.135.142.0/24 ip prefix-list pl100 permit 202.135.182.0/24 ip prefix-list pl100 permit 202.135.190.0/24 ip prefix-list pl100 permit 202.135.192.0/24 ip prefix-list pl100 permit 202.135.231.0/24 ip prefix-list pl100 permit 202.147.35.128/25 ip prefix-list pl100 permit 202.154.128.0/19 le 24 ip prefix-list pl100 permit 202.175.128.0/20 le 24 ip prefix-list pl100 permit 202.180.64.0/18 le 24 ip prefix-list pl100 permit 202.182.192.0/20 le 24 ip prefix-list pl100 permit 203.21.24.0/21 le 24 ip prefix-list pl100 permit 203.26.179.0/24 ip prefix-list pl100 permit 203.79.64.0/18 le 24 ip prefix-list pl100 permit 203.96.0.0/18 le 24 ip prefix-list pl100 permit 203.96.119.0/24 ip prefix-list pl100 permit 203.96.120.0/23 le 24 ip prefix-list pl100 permit 203.96.123.0/24 ip prefix-list pl100 permit 203.96.126.0/24 ip prefix-list pl100 permit 203.96.128.0/19 le 24 ip prefix-list pl100 permit 203.96.192.0/19 le 24 ip prefix-list pl100 permit 203.97.0.0/16 le 24 ip prefix-list pl100 permit 203.97.44.0/24 ge 25 le 29 ip prefix-list pl100 permit 203.97.66.0/24 ge 25 le 29 ip prefix-list pl100 permit 203.98.0.0/18 le 24 ip prefix-list pl100 permit 203.99.0.0/19 le 24 ip prefix-list pl100 permit 203.99.64.0/21 le 24 ip prefix-list pl100 permit 203.109.128.0/17 le 24 ip prefix-list pl100 permit 203.110.0.0/18 le 24 ip prefix-list pl100 permit 203.114.128.0/19 le 24 ip prefix-list pl100 permit 203.118.128.0/18 le 24 ip prefix-list pl100 permit 203.144.32.0/20 le 24 ip prefix-list pl100 permit 203.152.96.0/19 le 24 ip prefix-list pl100 permit 203.161.39.0/24 ip prefix-list pl100 permit 203.163.68.0/24 ip prefix-list pl100 permit 203.163.70.0/23 ge 24 le 24 ip prefix-list pl100 permit 203.163.86.0/24 ip prefix-list pl100 permit 203.163.98.0/24 ip prefix-list pl100 permit 203.167.128.0/17 le 24 ip prefix-list pl100 permit 203.173.128.0/17 le 24 ip prefix-list pl100 permit 210.48.0.0/17 le 24 ip prefix-list pl100 permit 210.54.0.0/22 le 24 ip prefix-list pl100 permit 210.54.12.0/23 le 24 ip prefix-list pl100 permit 210.54.32.0/21 le 24 ip prefix-list pl100 permit 210.54.56.0/21 le 24 ip prefix-list pl100 permit 210.54.128.0/21 le 24 ip prefix-list pl100 permit 210.54.142.0/23 le 24 ip prefix-list pl100 permit 210.54.148.0/22 le 24 ip prefix-list pl100 permit 210.54.152.0/21 le 24 ip prefix-list pl100 permit 210.54.211.0/24 ip prefix-list pl100 permit 210.54.252.0/24 ip prefix-list pl100 permit 210.55.0.0/25 ip prefix-list pl100 permit 210.55.1.0/25 ip prefix-list pl100 permit 210.55.4.0/23 le 24 ip prefix-list pl100 permit 210.55.7.0/24 ip prefix-list pl100 permit 210.55.8.0/24 ip prefix-list pl100 permit 210.55.10.0/24 ip prefix-list pl100 permit 210.55.12.0/22 le 24 ip prefix-list pl100 permit 210.55.16.0/21 le 24 ip prefix-list pl100 permit 210.55.28.0/22 le 24 ip prefix-list pl100 permit 210.55.72.0/21 le 24 ip prefix-list pl100 permit 210.55.100.0/22 le 24 ip prefix-list pl100 permit 210.55.104.0/22 le 24 ip prefix-list pl100 permit 210.55.108.0/24 ip prefix-list pl100 permit 210.55.110.0/23 le 24 ip prefix-list pl100 permit 210.55.155.0/24 ip prefix-list pl100 permit 210.55.157.0/24 ip prefix-list pl100 permit 210.55.158.0/24 ip prefix-list pl100 permit 210.55.169.0/24 ip prefix-list pl100 permit 210.55.180.128/26 ip prefix-list pl100 permit 210.55.184.0/22 ge 24 le 24 ip prefix-list pl100 permit 210.55.186.0/23 ip prefix-list pl100 permit 210.55.193.64/27 ip prefix-list pl100 permit 210.55.198.0/23 ge 24 le 24 ip prefix-list pl100 permit 210.55.202.0/23 le 24 ip prefix-list pl100 permit 210.55.212.0/22 ge 23 le 23 ip prefix-list pl100 permit 210.55.214.0/23 ge 24 le 24 ip prefix-list pl100 permit 210.55.227.0/24 ip prefix-list pl100 permit 210.55.228.0/24 ip prefix-list pl100 permit 210.55.230.0/24 ip prefix-list pl100 permit 210.55.248.0/21 le 24 ip prefix-list pl100 permit 210.246.0.0/18 le 24 ip prefix-list pl100 permit 218.101.0.0/17 le 24 ip prefix-list pl100 permit 218.101.56.0/24 ge 25 le 29 ip prefix-list pl100 permit 219.88.103.0/24 ip prefix-list pl100 permit 219.88.128.0/20 le 24 ip prefix-list pl100 permit 219.88.224.0/19 ge 20 le 24 ip prefix-list pl100 deny 0.0.0.0/0 le 32 Yeah go on.... Type type

3 2

Firewall script problem
by Gun Caundle 25 Apr '04

25 Apr '04

I am a newbie trying to create a firewall on RH9. I am using a script from the RH9 bible (p507). I am running a section at a time. What I have so far: # (1) Policies (default) iptables _P INPUT DROP iptables -P OUTPUT DROP iptables -P FORWARD DROP # (2) user-defined chain for ACCEPTED TCP packets iptables -N okay iptables -A okay -p TCP --syn -j ACCEPT iptables -A okay -p TCP -m state ESTABLISHED,RELATED -j ACCEPT iptables -A okay -p TCP -j DROP This line is giving me some grief: 'iptables -A okay -p TCP -m state ESTABLISHED,RELATED -j ACCEPT' Because I get this error when I run it. 'firescript: line 23: ESTABLISHED,RELATED: command not found' The author says this line "allows through packets associated with an ESTABLISHED connection (one that has already had traffic pass through the interface) or a RELATED connection (one that is starting a new connection related to an already-established connection) Are there other commands I could use or another line of script that would do the same job? Any help would be appreciated. Gun Caundle

5 8

WLUG Meeting is tonight
by Meeting Reminder bot 25 Apr '04

25 Apr '04

The WLUG meeting is this evening ---------------------------------------------------------------------- Linux as a Personal Video Recorder ([PVR]). In particular, looking at [MythTV], although I'll investigate the other options if I have time. Date: Monday 26 April 2004%%% Time: 7:00pm onwards - __Please note new time!__ %%% Location: CrawshawSchool%%%

1 0

Fw: [wlug] Firewall script problem
by Craig Box 24 Apr '04

24 Apr '04

(Forwarded from Mark Grimshaw) Hi Gun, It may be something as simple as the 'ACCEPT' being on a different line to the main body of the command and therefore being treated as a command itself which will obviously lead to an error (although that could be word wrap in email clients). Try putting it on the same line. Mark G. On 24 Apr 2004 at 9:21, Gun Caundle wrote: > I am a newbie trying to create a firewall on RH9. I am using a script > from the RH9 bible (p507). I am running a section at a time. What I > have so far: > > # (1) Policies (default) > iptables _P INPUT DROP > iptables -P OUTPUT DROP > iptables -P FORWARD DROP > > > # (2) user-defined chain for ACCEPTED TCP packets > iptables -N okay > iptables -A okay -p TCP --syn -j ACCEPT > iptables -A okay -p TCP -m state ESTABLISHED,RELATED -j ACCEPT > iptables -A okay -p TCP -j DROP > > This line is giving me some grief: > 'iptables -A okay -p TCP -m state ESTABLISHED,RELATED -j ACCEPT' > Because I get this error when I run it. > 'firescript: line 23: ESTABLISHED,RELATED: command not found' > > The author says this line "allows through packets associated with an > ESTABLISHED connection (one that has already had traffic pass through > the interface) or a RELATED connection (one that is starting a new > connection related to an already-established connection) > > Are there other commands I could use or another line of script that > would do the same job? Any help would be appreciated. > > Gun Caundle

1 0

[Administrivia] WLUG Committee Mailing List
by daniel＠meta.net.nz 24 Apr '04

24 Apr '04

One of the points of order raised at the last WLUG Committee meeting regarded the wlug-committee mailing list. For those of you who aren't aware of the current situation, the wlug-committee mailing list is a moderated mailing list available for the commitee members to discuss committee business. As such, only committee members can post. However, in the interests of open policy, and not least because we are a group concerned with open standards and discussions, the wlug-committee mailing list available for read-only access for general paid-up LUG members. However, it is important that anyone who wishes to read the wlug-committee mailing list understands a few points: * You are allowed to read the list, but you are not given write access. This is primarily because you have elected the committee to act on your behalf, and it is up to the committee to make the decisions. If you feel strongly about something you may forward your point to any committee member, who may act upon it. This does not mean they will raise your point immediately, nor does it mean they will forward your email direct to the wlug-committee list. * The list is there for the purpose of committee discussions. As such, the committee needs to be able to have candid discussions. * Once a final decision is made, the committee may inform the rest of the LUG if appropriate. However, until the committee has committed to a decision, you have no permission to act upon it. * If the committee wishes to ask for general input on a point, then it is up to the committee to do so. We have decided to keep the wlug-committee mailing list the way it is for now, despite some recent events which have lead, it seems, a great deal of confusion in external groups to the LUG. Had the above guidelines been understood beforehand, this would not have happened. It is important to us that if you choose to read the wlug-committee mailing list, you adhere to the above guidelines. We don't want to have to close the list to non-committee members completely. Daniel El Presidente :)

2 1

mail clients and archiving
by Glenn Ramsey 22 Apr '04

22 Apr '04

Hi, Does anyone know if any of the popular/stable mail clients have an archiving feature? If not then what is a good way to archive mail? Ideally I'd like something where I can say "archive all mail older than X" or something like that. I am using maildir so I guess I could just use shell commands to find all the old files but a method where I don't have to think too hard or read a zillion different man pages would be better ;-). g -- Glenn Ramsey <glenn(a)componic.co.nz> 07 8627077 http://www.componic.co.nz

3 3

InstallFest Progress
by Matt Brown 22 Apr '04

22 Apr '04

Hi, I wanted to keep everybody up to date on how progress with planning for the InstallFest is going. Keep an eye on www.wlug.org.nz/InstallFest for the latest details. We have confirmed the date (8 May) and venue Crawshaw School. The InstallFest will run from 11am to 4pm. Advertising is well underway but the most effective form of advertising we can get is word of mouth, tell all your friends and then bring them along on the day. Please register first so we know how many people are likely to be there! While we are calling the event an InstallFest we really want it to be much more than that, we want it to be a social event for the lug, even if you already have linux installed and do not plan to install anything on the day feel free to come along. You don't even need to be a paid member of WLUG to participate. What happens on the day will really be determined by who is there, obviously our first priority will be installing Linux for new people who attend, but if time allows and there are interested people there it is feasible that we could also have some other activities based around various applications etc. I've got no idea what form that sort of thing would take, if we would have time, or if people are interested in that sort of thing. The InstallFest is not just for new linux users (although that is the primary focus). One idea that I think would be quite cool if time permitted would be to have a bug finding / squashing or documentation party where pick a peice of software and as a group work towards making this better. The benefit of this is that there are lots of different tasks that can be done, if you're not a programmer you can test and look for bugs, if you are a programmer you can hack around in the code etc. Anyway, I'm starting to ramble and I'm really just throwing out ideas rather than describing existing plans - the point is we want everyone who is involved in the LUG to come and be at the InstallFest, given enough people we could easily have a group doing new installs while other people are doing something else. So consider this a challenge, we've never done an InstallFest before, it's new and interesting, get in and support your LUG by being involved! -- Matt Brown Email: matt(a)mattb.net.nz GSM : 021 611 544

4 4

RE: [wlug] Request for old hardware.
by David Nicholls 22 Apr '04

22 Apr '04

Sorry cant remember, its been a while since I last looked. But it uses scsi and once again is free for the taking for anyone who even just wants to take a peep. Warning: it's a big sod so anyone planning on using a carrybag and motor scooter to transport it, beware... Its heavy and I repeat large! :) Cheers... david -----Original Message----- From: Simon Anderson [mailto:oob(a)wildstar.net] Subject: RE: [wlug] Request for old hardware. Hello David, What type of Sun server do you have ? Regards, SImon. On Thu, 22 Apr 2004, David Nicholls wrote: > I have an old sun server if you want that... Unknown working order at > this stage but it should be working (just minus HDDs). free > > Cheers... > david >

2 1

RE: [wlug] Request for old hardware.
by David Nicholls 21 Apr '04

21 Apr '04

I have an old sun server if you want that... Unknown working order at this stage but it should be working (just minus HDDs). free Cheers... david -----Original Message----- Wondering if anyone out there has any old PCs, they don't require anymore? Preferably greater than 133MHz, that they want taken off their hands. :) Also interested if anyone has any old Sun Sparcstation/IPXs, they don't need anymore. Almost anything considered :D Thanks, Lance. _________________________________________________________________ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail _______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug

3 3

Request for old hardware.
by Lance Fitz-Herbert 21 Apr '04

21 Apr '04

Wondering if anyone out there has any old PCs, they don't require anymore? Preferably greater than 133MHz, that they want taken off their hands. :) Also interested if anyone has any old Sun Sparcstation/IPXs, they don't need anymore. Almost anything considered :D Thanks, Lance. _________________________________________________________________ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail

2 1

Spare RAM.
by Nigel Nguyen 21 Apr '04

21 Apr '04

Hi there, I've just joined the mailing list. Just an email to say hi to everyone. The other thing, I have some spare 128 - PC133 Ram @ home. So if you guys need to speed up the server, then let me know where and to whom I can drop it. With best wishes, Nigel Ng. P.S: I did see the bank account on the internet but who is the bank acc holder as my bank asked for the holder thou. Thanks for respone.

3 2

P200 for free.
by Oliver Jones 21 Apr '04

21 Apr '04

A number of people have expressed interest in the P200. Please note that I am in Taupo. You either have to come get it or pay the $20 in postage it'll probably cost to send it to Hamilton. Regards -- Oliver Jones » Director » oliver.jones(a)deeperdesign.com » +64 (21) 41 2238 Deeper Design Limited » +64 (7) 377 3328 » www.deeperdesign.com

1 0

how to find files with multiple suffixes
by Glenn Ramsey 20 Apr '04

20 Apr '04

How do I find files having either of several extensions? Eg this finds all .c and .h files $find . -name '*.[ch]' but what if I want to find all .cpp and .h files? I guess I need a grouping operator in the pattern but I can't figure out what it is. I've looked in the man page and Google and tried a few things, also tried the -regex switch instead of -name but couldn't get it to work. Eg this doesn't find anything $find . -regex '.*\.(cpp|h)' I suspect the answer is really simple. Any ideas what I'm doing wrong? g -- Glenn Ramsey <glenn(a)componic.co.nz> 07 8627077 http://www.componic.co.nz

3 2

Kiwi VOIP interconnect
by Simon Anderson 20 Apr '04

20 Apr '04

G'day, I read in your Wiki some details on Asterisk, notably from Nathan Ward and Matt Riddell, but my quick search of the last two years' postings to this list didn't turn anything else up, so forgive me if this message is coming to the wrong place. Matt R and I are already in touch with one another, working on an Asterisk<->Asterisk interconnect arrangement. Matt is in Dunedin and I'm in Wellington. I wonder if there is there an Asterisk operator (or a prospective operator) in the Waikato who would like to interconnect? In the spirit of quid pro quo, I will terminate calls in the Wellington free calling area in exchange for my calls being terminated in the Waikato, with a view to setting up a peering arrangement between all willing Asterisk operators in this country as and when the opportunity arises, down the line. Note that I am not proposing a commercial venture of any sort - I'm an enthusiast looking for other enthusiasts who enjoy messing with this technology and might be interested in providing a small scale solution to others out of a sense of altruism. Talk to me about it or request an account here; iax2://guest(a)gateway.anderson.gen.nz Regards, Simon

2 2

RE: [wlug] Pentium 200, free to a good home.
by DrWho? 19 Apr '04

19 Apr '04

It is tempting.. but I all ready have a good collection of old PCs... Sadly the 286 has gone to silicon heaven. At 09:02 20/04/2004, you wrote: >content-class: urn:content-classes:message >Content-Type: multipart/alternative; x-avg-checked=avg-ok-23701A9B; >boundary="----_=_NextPart_001_01C42651.9C081870" > >There you go Dr. Who... > >How can you refuse this ? >You won't need to run Linux on your 286 anymore... >-----Original Message----- >From: Oliver Jones [mailto:oliver(a)deeper.co.nz] >Sent: Monday, 19 April 2004 20:54 >To: Waikato Linux Users Group >Subject: [wlug] Pentium 200, free to a good home. > >Pentium 200, 64MB SIMM RAM, AT Case & Motherboard. Free to a good >home. Take it now or I chuck it. > >Regards >-- >Oliver Jones » Director » ><mailto:oliver.jones(a)deeperdesign.com>oliver.jones(a)deeperdesign.com » +64 >(21) 41 2238 >Deeper Design Limited » +64 (7) 377 3328 » ><http://www.deeperdesign.com>www.deeperdesign.com > >_______________________________________________ >wlug mailing list | wlug(a)list.waikato.ac.nz >Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug

1 0

RE: [wlug] Pentium 200, free to a good home.
by Lindsay Druett 19 Apr '04

19 Apr '04

There you go Dr. Who... How can you refuse this ? You won't need to run Linux on your 286 anymore... -----Original Message----- From: Oliver Jones [mailto:oliver(a)deeper.co.nz] Sent: Monday, 19 April 2004 20:54 To: Waikato Linux Users Group Subject: [wlug] Pentium 200, free to a good home. Pentium 200, 64MB SIMM RAM, AT Case & Motherboard. Free to a good home. Take it now or I chuck it. Regards -- Oliver Jones > Director > <mailto:oliver.jones(a)deeperdesign.com> oliver.jones(a)deeperdesign.com > +64 (21) 41 2238 Deeper Design Limited > +64 (7) 377 3328 > <http://www.deeperdesign.com> www.deeperdesign.com

1 0

Pentium 200, free to a good home.
by Oliver Jones 19 Apr '04

19 Apr '04

Pentium 200, 64MB SIMM RAM, AT Case & Motherboard. Free to a good home. Take it now or I chuck it. Regards -- Oliver Jones » Director » oliver.jones(a)deeperdesign.com » +64 (21) 41 2238 Deeper Design Limited » +64 (7) 377 3328 » www.deeperdesign.com

1 0

3 * EDO 128MB sticks
by Drew Broadley 18 Apr '04

18 Apr '04

Does anyone have 3 for sale ?

1 2

RE: [wlug] Dual Booting for the install-fest [long]
by Lindsay Druett 18 Apr '04

18 Apr '04

FFS Man !!! Which part don't you understand about WLUG not wanting to use Ghost or Partition Magic ? Licensing costs and issues are not the only reason behind this... I personally wouldn't paint myself into a corner backing up peoples computers, there are a lot of issues, what if the back up failed ? What is the content I'm backing up ? What about disposing of the data once finished ? Believe it or not, there are a lot of legal issues there... The other issues (which I thought was very obvious) is that here we are promoting a suite of software ranging from the OS right up to end user applications that is for starters free, open source, an alternative to Microsoft, and we are going to use what? to partition hard drive space, and we are going to use what? to backup the data. Hey if you want to use at home (or whatever) is fine to me, but what you are suggesting here is as appropriate as suggesting that you consume alcohol at church... Personally, Hard Drives are not expensive, people should consider installing a new hard drive in their machine and install the going distro. If they are newbies, things *will* go wrong somewhere along the line, and at least they can reformat the drive and start all over again without losing any sleep. > -----Original Message----- > From: DrWho? [mailto:x_files_(a)ihug.co.nz] > Sent: Sunday, 18 April 2004 19:20 > To: Waikato Linux Users Group > Subject: Re: [wlug] Dual Booting for the install-fest [long] > > > At 17:56 18/04/2004, you wrote: > > > > >>I think the idea of asking Symantic if they would do some sort of > >>sponsorship with Ghost would be a great idea. > > > >Great. Where can I download the source code? > > > You cant, but sometimes you need to spend a bit of money to > get the job > done <grin> and if a commercial pay for it product will do > the job a hell > of allot better than any free product then so be it <grin>. > > Also if symantic would be willing to give away some copies > then take it!! > it will do a good job, better than any oss solutions <grin> > > > > > >_______________________________________________ > >wlug mailing list | wlug(a)list.waikato.ac.nz > >Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug > > > > >

1 0