- wlug - list.wlug.org.nz

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

Re: [wlug] Install fest
by DrWho? 18 Apr '04

18 Apr '04

At 15:49 15/04/2004, you wrote: > > I would think, providing something like Partition Magic is available ( > > which I have and no doubt others ) to do the job it could be offered as > > an option for those who are not competent with doing it themselves or > > installing new hardware. > >Oh? Does the license allow that? >Even so, it's still far more risk/hassle than we need I believe. It can run from a boot disk, no install on target PC needed. > > I have resized MANY NTFS and FAT partitions with PQMAGIC and never had a > > problem, not to say there have not or will not be any problems, but > > there is also the option of ghosting their HDD before the resize. > >To what? Are you providing the disk space? >Remember this is an afternoon workshop. Good question, that is one minor problem with ghost.... perhaps a spare 40G HDD?? Or setup a ghost server on a PC with some disk space and ghost over a network? >-- >Greig McGill > > >_______________________________________________ >wlug mailing list | wlug(a)list.waikato.ac.nz >Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug

12 18

WLUG Meeting is one week away
by Meeting Reminder bot 18 Apr '04

18 Apr '04

The WLUG meeting is one week away ---------------------------------------------------------------------- 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: Probably at CrawshawSchool%%%

1 0

[installfest] Hard Disk Repartitioning
by Matt Brown 18 Apr '04

18 Apr '04

In light of the recent frenzy of discussion regarding hard disk partitioning and the InstallFest I would like to clarify what the official position of the WLUG Committee on this issue is. WLUG (and it's representatives) will not be responsible for repartitioning or backing up hard disks at the InstallFest. All data backup and disk preparation tasks (such as ensuring there is sufficient unpartitioned space) are the responsibility of the owner of the computer and should be completed before attending the InstallFest. The minimum requirements that we have specified for hard disks for the install fest are either a) You are willing to wipe the entire disk (which is at least 5GB in size) and have Linux installed. OR b) There is at least 5GB of UNPARTITIONED space available on the disk. The rationale behind this position can be found on the InstallFest wiki page at http://www.wlug.org.nz/InstallFest along with other information related to hardware requirements. If people have further general comments on Free hard disk partitioning tools that are available for use in Linux then you are most welcome to post them to the list, however I would suggest that any disk partitioning issues related solely to the InstallFest have already been well and truly flogged and any more discussion would be counter productive. Questions or concerns about any aspect of the position stated above can be directed to myself or any other member of the committee. Regards -- Matt Brown Email: matt(a)mattb.net.nz GSM : 021 611 544

1 0

Re: [wlug] Install fest
by Wayne Rooney 17 Apr '04

17 Apr '04

>Also, to Wayne, who decided that because a process "works for him" it's >infallible, and 100% safe for all, I've seen plenty of PM partitioning >problems in my time, and it's the benchmark. I didn't say it was infallible. I said it was designed to fail safe. qtparted resizes NTFS partitions with ntfsresize. Part of "man ntfsresize" says: KNOWN ISSUES No reliability problems are known or has been reported. If you need help please try the ntfsresize FAQ first (see below) and if you dont find your answer then send your question, comment or bug report to <linux-ntfs-dev(a)lists.sourceforge.net>. No subscription is needed but the mailing list is moderated and it can take some time to approve your post. There are some very rarely met limitations at present: filesystems having bad sectors, highly fragmented Master File Table (MFT), relocation of the first MFT extent and resizing in the middle of some metadata in some cases arent supported yet. These cases are detected and resizing is refused, restricted to a safe size or the closest safe size is displayed. --------- I like the words "no reliability problems are known" The fact that you've seen problems with OTHER software doesn't mean that THIS software is no good, does it? If you've had problems with qtparted then do share them so we know what to look out for. >So forgive me if I don't >really want to see the WLUG put its balls on the block guaranteeing the >safety of the user's data. That's why you get them to sign a waiver. Why would you want to guarantee somebodys data? That's asking for trouble. An installfest should be all care and no responsibility. Check out this waiver: http://www.acm.uiuc.edu/sigunix/installfest/waiver.shtml Wayne

7 10

Re: [wlug] Install fest
by Wayne Rooney 17 Apr '04

17 Apr '04

>No backups necessary then? > >Cool, so it can predict a power outage? Wow! :-) Smartarse ;-P Yes, actually, it takes a reading from /dev/crystalball and uses KStars to get an alignment of the planets and only resizes partitions if there are no power outages in the near future. Wayne

2 1

Return to Castle Wolfenstein.
by Oliver Jones 16 Apr '04

16 Apr '04

I'm about to put the Game Return to Castle Wolfenstein on TradeMe. RTCW is a great first person shooter and as a bonus works in Linux as a native app! A rare thing with Loki games now gone. http://www.trademe.co.nz/structure/auction_detail.asp?id=10582307 If you're interested place a bid. I'd get a kick out of seeing another Linux gamer enjoy this game. Regards -- Oliver Jones » Director » oliver.jones(a)deeperdesign.com » +64 (21) 41 2238 Deeper Design Limited » +64 (7) 377 3328 » www.deeperdesign.com

19 61

Re: [wlug] Install fest
by Wayne Rooney 16 Apr '04

16 Apr '04

>You do not need to install it as it will run from a boot disk, or in my >case a boot CD. Read your licence agreement again carefully, Doctor. Then perhaps visit http://www.linuxmafia.com/faq/Filesystems/ntfs.html from which comes the following quote: "Partition Magic is one solution -- except that Linux user groups cannot lawfully keep a copy on hand to use on visitors' machines, even if they're willing to spend the money. Advising them to buy a copy and come back is lawful, but not very appealing." Wayne

3 2

Issues with BIND
by Craig Box 15 Apr '04

15 Apr '04

(Passing on the message from Drew. Note to everyone, messages you send from unsubscribed addresses get dropped! -- Craig) I am having issues with a SINGLE domain "corrupt.co.nz", every other domain is fine! Here's the deal: Bind logs return nothing like they usually would saying there was an error with the domain. I can dig to ALL of my AUTH NS servers, and get the records returned no problemo. I can use XTRA, DTS (and a few others have used their own DNS servers) and get returned results without any SERVFAIL errors. I try to dig anything to the PARADISE NS servers (203.96.152{4,12}) and I get mixed results. I get www.corrupt.co.nz and corrupt.co.nz, but none of my overly important records (home.corrupt.co.nz, mail.corrupt.co.nz) It returns SERVFAIL id:2 whenever I try to request anything other then www.corrupt.co.nz / corrupt.co.nz via PARADISES NS Servers Any ideas? I have contacted soa(a)paradise.net.nz but god knows how long that will take to be processed. - Drew

1 0

RE: [wlug] Prefered Mail Client
by David Nicholls 15 Apr '04

15 Apr '04

> Strip back the FUD; apply the standard "there are security holes in Linux applications > fixed all the time, but Gartner Group rarely complains about them, and if they do, it > gets written off as anti-MS propaganda"... One interesting point I think people offten tend to miss when the Gartner Group or other such company is counting bugs/security warnings/year in linux versus windows codebases is that for linux they never differentiate between the O/S itself and the apps that are included with the distros. They like to lump them all in together to get the most number of bugs possible. My suspicion is, if they only looked at the O/S itself they would have a much harder time finding problems. Cheers... david

1 0

Re: [wlug] Install fest
by Wayne Rooney 15 Apr '04

15 Apr '04

>Resizing is a very risky option; the very LAST thing we want is people >who say "I tried to install Linux once, and lost all my data because if >it.". Especially if we were helping them at the time. No, no, no. Resizing is very easy and safe. Boot computer off Knoppix cd. Open an x-term. Type "sudo su <enter>" Type "qtparted <enter>" Click on the edge of the partition you want to resize and drag it to the new size you want. Click "ok" And you're done. And it handles NTFS partitions. And it fails safe, that is, if something is going to go wrong (which it never has for me) it throws up an error message and quits BEFORE making changes to the hard drive. Try it. You'll like it. Wayne

2 1

Upcoming committee meeting
by Craig Box 15 Apr '04

15 Apr '04

Per the WLUG charter, we'd like to inform you that there is an WLUG committee meeting to be held next Wednesday, 21 April. Tentative Agenda 1. Minutes from previous meeting 2. Treasurer's Report 3. Correspondence 4. Committee Mailing List - effectiveness & policy regarding posting 5. Committee - Purpose, Direction, Relationship to WLUG 6. Resignation, Greig McGill 7. General Business If you want to have an item added to this agenda, please contact me at secretary(a)wlug.org.nz. Craig, Secretary

1 0

installing new kernel from rh9
by Stephen Pearce 14 Apr '04

14 Apr '04

I recently tried to compile and install the 2.6.5 kernel on a rh 9 system (dell i8500) .. it installed ok as a grub boot option but hangs trying to load the directory structure .. I have compiled and installed modules .. what else do I have to do to get the new kernel to boot? Thanks Stephen

1 0

New Users Redux
by Craig Box 14 Apr '04

14 Apr '04

Over the last couple of days, due to some comments regarding the upcoming WLUG installfest [1] and "Software Freedom Day" [2], the issue of WLUG and new Linux users has come up again. While I realise that everything I'm going to say has been said before, hopefully any discussion that comes from this will explain a bit better about how some people feel, or get people inspired to do something about it. A lot of the people involved with the LUG are computing professionals, or higher level University students in computing science. It has been said that these people aren't new users, they don't have to do new things again and to keep them interested, we can't offer installation meetings every other month. It's not to say that these people don't want to help new people - lots of them, myself included, reply to posts here, sit in #wlug on IRC offering help. Yet people still don't think there's enough being done. There's a faction of Linux users that like Linux because they hate Microsoft. (Tip: if you use "M$", you're it!) Most of the aforementioned "clever" group, while they might prefer Linux for various reasons (open standards, open source, etc), don't hate Windows. There is a time and a place for everything. Pushing Linux before its time will just cause people to be aggrevated. As an example, if someone suggests running Linux to a home user, they will inevitably field a whole heap of the same questions over again; word documents, Flash. Questions that there exist easy answers for if people are prepared to look. (As an aside, people who deal with users every day who aren't prepared to learn for themselves, get a bit annoyed with that class of people!) Now, if you leave Linux to the people who find out about it themselves (or push it in a non-confrontational way; say "Linux exists, learn about if you want", and then help people when they have specific problems along the way, I think you end up with less problems. This is the approach that several people are espousing at the moment. Let people find Linux on their own merits - we don't have to replace every Windows machine in the world, and we certainly don't have to do it overnight. Then, if they have problems, we'll help them. That way we're sure that they are prepared to learn for themselves. No-one is paid to be involved with the LUG and some people put a lot of time in, only to be discouraged by the attitude of people who complain to other people, but not the LUG itself (so we have no idea how to change). We would love to see more new user based presentations. The general feeling that the people who have recently been new users should be presenting them. It's not tricky, and if you're worried about fielding questions you don't know the answers to, rest assured there will be someone in the audience who can help, or point to the wrong things. We don't want to alienate the people who have done this all before, because then at the current rate there will be no presentations at all. Not everyone in the LUG is interested in holding an "installfest", for the reasons above - Linux is not ready for everyone and we don't want to have to field questions from people who aren't ready to ask them yet. The people that are interested in helping, are. If you're interested, please shout out. Craig [1] http://www.wlug.org.nz/InstallFest [2] http://www.softwarefreedomday.org/forum/viewtopic.php?forum=2&showtopic=159 for us

2 1

RE: [wlug] Re: problem with FC1 installation
by DrWho? 13 Apr '04

13 Apr '04

Have you created a swap partition? or left enough un-partioned disk space to make one? At 18:11 13/04/2004, you wrote: >no, i selected mini installation it poped up the same message. it never >warn me the disk space before that message. > > -----Original Message----- > From: zcat [mailto:zcat(a)wired.net.nz] > Sent: Tue 13/04/2004 12:11 p.m. > To: Waikato Linux Users Group > Cc: > Subject: Re: [wlug] Re: problem with FC1 installation > > > > Gerwin van de Steeg wrote: > > >There is another possibility, if you selected the complete > install of > >FC1 then you will run out of disk space as it exceeds 5.4 GB > > > > > >Gerwin > > > Doesn't it warn you first? Previous versions of Redhat tell you "you > don't have enough space to install this" before even starting, > I'm sure.. > > > > _______________________________________________ > wlug mailing list | wlug(a)list.waikato.ac.nz > Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug > > >_______________________________________________ >wlug mailing list | wlug(a)list.waikato.ac.nz >Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug

1 0

Welly InstallFest a go go!
by Jamie Baddeley 13 Apr '04

13 Apr '04

Fellow NZ_Luggites, Wellylug (http://www.wellylug.org.nz) is pleased to announce we are undergoing the annual ritual of the InstallFest. This year we have chosen MayDay (1st May) as the day that people can make the choice to add some freedom into their computing. We think MayDay is the ideal time to rescue your computer. Basically this email is to spread the good word. Anyone who needs a penguin injection is welcome to join us at Silicon Systems on the 1st. We're always keen for good volunteers, and I'm sure that the Aucklanders amongst us need a reasonable excuse to get out of the traffic jam ;-) Anyways - spread the word, and keep the heat turned up. Not long to go until we form the Jedi Council ;-) peace. Jamie, on behalf of the WellyLug crew.

2 1

RE: [wlug] Re: problem with FC1 installation
by Bo Wang 13 Apr '04

13 Apr '04

no, i selected mini installation it poped up the same message. it never warn me the disk space before that message. -----Original Message----- From: zcat [mailto:zcat(a)wired.net.nz] Sent: Tue 13/04/2004 12:11 p.m. To: Waikato Linux Users Group Cc: Subject: Re: [wlug] Re: problem with FC1 installation Gerwin van de Steeg wrote: >There is another possibility, if you selected the complete install of >FC1 then you will run out of disk space as it exceeds 5.4 GB > > >Gerwin > Doesn't it warn you first? Previous versions of Redhat tell you "you don't have enough space to install this" before even starting, I'm sure.. _______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug

1 0

Re: problem with FC1 installation
by Gerwin van de Steeg 13 Apr '04

13 Apr '04

There is another possibility, if you selected the complete install of FC1 then you will run out of disk space as it exceeds 5.4 GB Gerwin

2 1

compaq armada 1592
by Stephen Pearce 12 Apr '04

12 Apr '04

Someone unkindly hoisted this on me to get going! It came with win95 on the disk and 2 pcmcia modems .. us botics xejm3336 and a 3com device .. Anyway .. I got the damn thing working under win 95 for internet stuff .. then he went and bought a usb printer for which there was no win95 driver Right I thought .. linux is the thing ...and installed rh9.0 .. wiping out the win 95 partition... well it seems to take all day to try loading open office (64 M of memory) ..to the point of being useless So I fell back to win 98 .. and have spent most of today trying to get this installed .. but the graphics drivers don't work .. the modem isn't properly recognised etc etc!!!! :<((((( Has anyone experience of linux on one of these brutes .. it has to read ms word docs ... do a bit of graphing for illustrations and work on the internet ... Thanks Stephen

5 5

problem with FC1 installation
by Bo Wang 10 Apr '04

10 Apr '04

i have tried several times to install fodera core 1 on my laptop. i have 5G free disk space allocated for FC1 but once it's started copying files onto the disk a error msg pop up says 'a problem occured probably because you don't have enough disk space'. does anyone know what the problem is? regards beau

2 1

Re: [wlug] Renaming Debian platforms
by DrWho? 09 Apr '04

09 Apr '04

Microsoft still offer paid support for NT. Must of the current NT installs I have seen are acting as NAS, DNS and in a few file / print servers. It is installed on Compaq or HP server platforms. At 13:43 6/04/2004, you wrote: > > Once again "updating for the sake of updating" applies, sure there some > > genuine new stuff that offer something that is not just a fresh paint > > job. But can the same be said for the SERVER environment. > > > > Since you mentioned mickysoft, allot of people are still running NT3.5 & > > NT4 on there OLD pentium platforms, as a server, and in same cases as a > > work station, and shock horror mickysoft still support them. > >Oh Really? >http://www.microsoft.com/windows/lifecycle/default.mspx > >And reed the "see note" bit. > >Please stop with the unfounded guesswork. > > > Well, it is true for the end user, but I was talking about servers... > >OK, if you want to take that approach... >Name brand server hardware is supplied by most vendors with an expected >lifetime of 3 years. Maybe 5 tops. After that, you expect a high level >of hardware failures. From that angle alone, I'd not be bothering with >old hardware in a server environment. > >Are you for real, or are you trolling? >If the latter, please stop, or feel free to join #wlug, where we are eager >and waiting to tear you a new one! :) > > >-- >Greig McGill > > >_______________________________________________ >wlug mailing list | wlug(a)list.waikato.ac.nz >Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug

2 1

RE: [wlug] Bite
by Lindsay Druett 08 Apr '04

08 Apr '04

This sounds Cat in the Hat > Linux is linux. It doesn't matter how its branded. It's still > the same > thing. Linux *will* run on an embedded 386 processor, and it > *will* run....

3 2

[Fwd: [wlug-committee] O'Reilly Looking for GNOME Hacks]
by Daniel Lawson 07 Apr '04

07 Apr '04

If anyone has any useful or interesting GNOME 'hacks', please pass them on. If you do email Marsee directly, make sure you mention you're a WLUG member (probably best to spell that out, there's several WLUG's in the world)... Or email a committee member and we'll submit on your behalf. Feel free to discuss this on the mailing list if you want to bounce ideas around. -------- Original Message -------- Subject: [wlug-committee] O'Reilly Looking for GNOME Hacks Date: Wed, 07 Apr 2004 14:47:14 -0700 From: Marsee Henon <marsee(a)oreilly.com> Reply-To: WLUG Committee Mailing List <wlug-committee(a)list.waikato.ac.nz> To: wlug-committee(a)list.waikato.ac.nz Hi Linux UG Leader, We're looking for GNOME hacks for our upcoming book, "Linux Desktop Hacks." We already have half of the book filled with KDE hacks, but no GNOME hacks! Do you know of any GNOME Hackers who could help us out? Please forward this email along. If you have a hack to share, please send 'em our way by having your members email me (marsee(a)oreilly.com) with "GNOME hacks" in the subject line. Don't let KDE hacks take over this book! As thanks for sharing, we'll make sure to get copies of "Linux Desktop Hacks" sent to your group shortly after publication. --Marsee _______________________________________________ wlug-committee mailing list wlug-committee(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/wlug-committee

1 0

RE: [wlug] install fest progress
by Lindsay Druett 07 Apr '04

07 Apr '04

Nah... I can hear Daniel reading us the Dr. Suess book.... "Linux is Linux....." > I can see a distro war brewing over this; I've started > leaning towards > Debian, and a lot of people are recommending Mandrake as a good > first-time distro.. > > > _______________________________________________ > wlug mailing list | wlug(a)list.waikato.ac.nz > Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug > >

1 0

Re: [wlug] install fest progress
by zcat 07 Apr '04

07 Apr '04

Jamie Curtis wrote: >>Do we actually want to go ahead with this? >> >>Because we have today and tommorrow to get things underway or there's no >>point doing it at this time. We can put it off, but if we don't get >>things organised real soon it's going to be me sitting on my ass all day >>at Crawshaw playing frozen-bubble. I'd rather be doing other things. >> >> > >I am able to help out as required, but I really doubt the number of >students we will attract on the last Saturday of the break. Are we doing >this focusing on Students or do we think there will be enough general >community interest to make it worth doing anyway. > > Bugger the students, they don't have much choice about using Linux anyway. Let's aim this at the general public. The date is more than two weeks away. I'm happy to phone around tomorrow, Friday, etc. I'm also happy to design a poster (although it'll suck; I'm no artist). Two weeks is plenty of time to make it happen. Are we doing this or not?

6 12

[Fwd: End of Life for Red Hat Linux 9]
by Matthias Dallmeier 06 Apr '04

06 Apr '04

-- Matthias

17 63

RE: [wlug] Renaming Debian platforms
by Lindsay Druett 06 Apr '04

06 Apr '04

> Once again "updating for the sake of updating" applies, sure > there some > genuine new stuff that offer something that is not just a > fresh paint job. > But can the same be said for the SERVER environment. > > Since you mentioned mickysoft, allot of people are still > running NT3.5 & > NT4 on there OLD pentium platforms, as a server, and in same > cases as a > work station, and shock horror mickysoft still support them. I agree with Craig that perhaps you should start getting used to the fact that they are "Microsoft". Also, Microsoft haven't supported NT3.51 for quite a while, they basically have stopped supporting NT 4.0 December last year, and they are about to stop providing security patches very shortly AFAIK. > > >People buy new PC's because they want something which their > old PC didn't give > >them - the ability to do some new task (like play games, or > support larger > >hard > >drives/more drives/more ram, etc), or some existing task > faster than what they > >had. Or just because their old PC is broken. They throw old > PC's away, or off > >the roof at parties, or deal to them with a sledgehammer. That's life in the technology world, get used to it. People do that with cars too you know. > Well, it is true for the end user, but I was talking about servers... > > And yes, putting a server you paid $8,000+ for 3-4 years ago > in the bin is > a bit stupid, just beacuse the "latest and greatest" OS that > does the same > as what you have all ready got will not run on it.... An $ 8,000 server 3-4 years ago would have at least been a 800-1000 MHz PIII, possibly a Dual processor machine, depending on buying power. In the enterprise world, that is not a big deal at all, the ROI would have been well within 3 years. Normally, servers come with a 3 year warranty/service contract and in the enterprise environment in many instances the cost of having the server down for any length of time can outweigh the cost of the server itself, hence High Availability and Redundancy is a very important consideration. If the machine is out of warranty and/or is not on service contract, then in a lot of incidences, it shouldn't be in production. In other environments where things are not so crucial, I would expect a life of 5-7 years for a server. Quite often in the enterprise environment, 3-4 year old servers are used in test environments where if the server bellies up and/or spits out a hard drive, then so what ? So you'll be pleased to know that 3-4 year servers don't go straight in the bin.

1 0