- NZNOG - lists.nznog.org

Firewalling on Cisco router?
by PhoneNet 14 Aug '01

14 Aug '01

Can anyone give some suggestions on the best way to firewall a system using a Cisco router.... a friend on another list I'm on has been charged with moving a system .... some of the misfortunes he has been faced with so far are (Don't Laugh): 1.They had no list of thier machine names, 2. No IP addresses, 3. moved token ring to ethernet. 4. They had hubs, but no patch cables.... They get the Cisco router today and are moving tomorrow. Initally they will just use a very restrictive set of Cisco filters and NAT. It has bee nsuggested he use either Checkpoint or Cisco Pix, both standalone machines. Any comments? Ian Cousins PhoneNet --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Max 6000 R2 Settings
by Craig Whitmore 13 Aug '01

13 Aug '01

If anyone is kind enough to be running a Max6000 with R2, could you please send me a copy of the Settings for the E1's so they will work with R2 :-) I set up the first 4000's at IHUG on PRI's years and years ago, about I don't know the "right" settings to R2's :-( Also. if anyone has a suggestion on most stable firmware for the 6000? 7.2? 8.1? 9.0? It would be great. Sig Mode=NEW ZEALAND Switch Type=CAS Framing Mode=G.703 etc etc etc Thanks Craig Whitmore Orcon Internet http://www.orcon.net.nz

4 5

Orcon Internet Updated Prefix List
by root 13 Aug '01

13 Aug '01

For those people who are Peering with Orcon Internet Please Note the Updated Prefix Lists. (210.54.56.0/21 is added from previous prefix-lists) ip prefix-list ORCON-networks description Orcon Internet <noc(a)orcon.net.nz> ip prefix-list ORCON-networks permit 202.14.20.0/22 le 24 ip prefix-list ORCON-networks permit 202.27.76.0/23 le 24 ip prefix-list ORCON-networks permit 202.27.140.0/22 le 24 ip prefix-list ORCON-networks permit 202.27.188.128/25 ip prefix-list ORCON-networks permit 210.27.250.0/24 ip prefix-list ORCON-networks permit 210.54.13.0/24 ip prefix-list ORCON-networks permit 210.54.142.0/23 le 24 ip prefix-list ORCON-networks permit 210.54.148.0/23 le 24 ip prefix-list ORCON-networks permit 210.55.8.0/24 ip prefix-list ORCON-networks permit 210.55.12.0/22 le 24 ip prefix-list ORCON-networks permit 210.55.18.0/24 ip prefix-list ORCON-networks permit 210.55.199.0/24 ip prefix-list ORCON-networks permit 210.54.56.0/21 Thanks Craig Whitmore Orcon Internet http://www.orcon.net.nz --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

Re: CLEAR Net Tempest
by Mark Foster 13 Aug '01

13 Aug '01

Well youre talking about mathematical stuff which I let go over my head years ago. :P Fair enough; I defer to those with higher skills than myself. I spose nows not a good time to mention im job hunting? :P Anyone need a Senior Helpdesk or Junior NOC type person? ... *shrug* :) Mark. At 09:55 14/08/2001 +1200, Matthew G Brown wrote: >All loss can be calculated . ( Within reason ) > >The exact frequency of the ISM band channel is avai on manafacture WWW sites. > >Cable Loss - http://www.timesmicrowave.com ( If your a LMR person ) >Connector Loss - http://www.tessco.com or http://www.timesmicrowave.com >* NB: I use Shuners conenctors over Times anyday >Insertion Loss - See Antenna manafacture > >Free Space Loss (isotropic):FSL (isotropic) = 20Log10(Frequency in MHz) + >20Log10 (Distance in Miles) + 36.6 > >Then you can check your operating margin, I run with 10db+ anything less and >you asking to get your head run over by a bare naked lady > >SOM = RX Signal Level - RX Sensitivity > >RX Signal Level = TX Power - TX Cable Loss + TX Antenna Gain - FSL + RX >Antenna Gain - RX Cable Loss > *Snip* --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Max 6000 won't Assign ip from second ip pool
by John Lynch 12 Aug '01

12 Aug '01

Hi I was wondering if any one out there has ever got the Ascend-Assign-IP-Pool radius attribute to work with a max 6000. I have just set up ip pool 2 on the max and am now trying to get an ip assigned from this new pool for a test user. I am using the radiusd-cistron 1.6.1-0.1 debian linux package for radius auth, the TAOS on the max is 9.0.0. I can login just fine but the win95 pc I am dialing in with is still assigned and ip address from pool 1. here is the debug info from radius : radrecv: Request from host ca1bd0fc code=1, id=233, length=123 User-Name = "testlynch" Password = "l\012\307\203\375\367\204\272\317\313\236\275\205f{\201" NAS-IP-Address = 202.27.208.252 NAS-Port-Id = 20202 NAS-Port-Type = Async Service-Type = Framed-User Framed-Protocol = PPP Called-Station-Id = "3700055" Acct-Session-Id = "343972952" Vendor-Specific = "V529:T197:L6::T0:L0:]\300" Vendor-Specific = "V529:T255:L6::T0:L0:\305\353" users: Matched testlynch at 51 auth: Local Sending Ack of id 233 to ca1bd0fc (nas maxbox) Service-Type = Framed-User Framed-Protocol = PPP Framed-Address = 255.255.255.254 Framed-Netmask = 255.255.255.255 Ascend-Assign-IP-Pool = 2 Ascend-Maximum-Channels = 1 Ascend-Idle-Limit = 1200 Login OK: [testlynch] (from nas maxbox/S20202) Here is the debug info from the maxbox (not the same session as above but you get the picture) : authenticating <9:testlynch> with PAP RADIF 1:49:20> _radiusRequest: id 202, user name <9:testlynch> RADIF: not sending NULL State-Attribute for VSA RADIF: not sending NULL State-Attribute for VSA RADIF: _radiusReq: socket 6 len 123 ipaddr 202.27.208.65 port 65534->1812 RADIF:_radiusReq: id 202 <9:testlynch>, starting timer (10 sec) _receivedResponse :1, addrPoolAcked : 0 RADIF: _radCallback: buf=b0aaee80 from 202.27.208.65 1812 RADIF: _radCallback, authcode = 2, id 202 RADIF: _radCallback: id 202, killing timer RADIF: Authentication Ack RADIF: vendor 0 attr 6, len 6, 00 00 00 02 RADIF: vendor 0 attr 7, len 6, 00 00 00 01 RADIF: callMgmtType set to 2. RADIF: vendor 0 attr 8, len 6, ff ff ff fe RADIF: vendor 0 attr 9, len 6, ff ff ff ff RADIF: vendor 0 attr 218, len 6, 00 00 00 02 RADIF: vendor 0 attr 235, len 6, 00 00 00 01 RADIF: vendor 0 attr 244, len 6, 00 00 04 b0 Disposing of tunnel info object b0ab8a80. RADIF:_freeInfoClassSess RADIF: radius type Acct ID = 93 RADIF:sending to 202.27.208.242 1813 _receivedResponse :1, addrPoolAcked : 0 RADIF: _radCallback: buf=b0aab400 from 202.27.208.242 1813 RADIF: _radProcAcctRsp: user:<9:testlynch>, ID=93 RADIF:_freeInfoClassSess RADIF: _radCallback: processed acct server type=0 RADIF: radius type Auth ID = 203 any help would be much appreciated. John Lynch System Administrator (string and tape specialist) Wise Net --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 1

CLEAR Net Tempest
by Neil 12 Aug '01

12 Aug '01

Hi All, Has anyone else had any problems with Clear's 802.11 wireless internet service (http://www.clear.net.nz/services/tempest.html) as a source of interference? They have just done a rollout in Rotorua and totally stoped 3 separate wireless networks that had been running together nicely for the past year or two. Clear have told me that Rotorua is the only place that this has happened in and are being very slow to do anything about it so if this has happened to you could you let me know. Neil Fincham Integral LTD.

2 1

NZNOG List Change Now Effective
by Donald Neal 12 Aug '01

12 Aug '01

NZNOG People, Postings for the NZNOG list should now be accepted only from addresses subscribed to one of the following lists: nznog - this list nznog-digest - the digest version of this list nznog-postonly - a list which exists only to allow addresses subscribed to it to post to the nznog list. Messages will not normally be sent to addresses subscibed to nznog-postonly. To subscribe new addresses to one or more of these lists, send email to majordomo(a)list.waikato.ac.nz where each line of the body of the message has the form subscribe <list name> to subscribe the address from which that message is being sent, or subscribe <list name> <address> to subscribe a different address. More than one subscription request may be sent in the same message. Donald Neal List Administrator --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Re: CLEAR Net Tempest
by Neil 12 Aug '01

12 Aug '01

Hi all, Sorry about the Spam, I have the displeasure of being on the end of one of these links (the mail client did not get the signoff from the smtp server so it tried again). Neil Fincham Integral LTD ----- Original Message ----- From: Olderon To: Neil Sent: Monday, August 13, 2001 4:47 PM Subject: Re: CLEAR Net Tempest is there something wrong with your mail? youve sent that same email 4times. 4:23 4:28 4:29 4:36 ----- Original Message ----- From: Neil To: nznog(a)list.waikato.ac.nz Sent: Monday, August 13, 2001 4:18 PM Subject: CLEAR Net Tempest Hi All, Has anyone else had any problems with Clear's 802.11 wireless internet service (http://www.clear.net.nz/services/tempest.html) as a source of interference? They have just done a rollout in Rotorua and totally stoped 3 separate wireless networks that had been running together nicely for the past year or two. Clear have told me that Rotorua is the only place that this has happened in and are being very slow to do anything about it so if this has happened to you could you let me know. Neil Fincham Integral LTD.

1 0

CLEAR Net Tempest
by Neil 12 Aug '01

12 Aug '01

Hi All, Has anyone else had any problems with Clear's 802.11 wireless internet service (http://www.clear.net.nz/services/tempest.html) as a source of interference? They have just done a rollout in Rotorua and totally stoped 3 separate wireless networks that had been running together nicely for the past year or two. Clear have told me that Rotorua is the only place that this has happened in and are being very slow to do anything about it so if this has happened to you could you let me know. Neil Fincham Integral LTD.

1 0

CLEAR Net Tempest
by Neil 12 Aug '01

12 Aug '01

Hi All, Has anyone else had any problems with Clear's 802.11 wireless internet service (http://www.clear.net.nz/services/tempest.html) as a source of interference? They have just done a rollout in Rotorua and totally stoped 3 separate wireless networks that had been running together nicely for the past year or two. Clear have told me that Rotorua is the only place that this has happened in and are being very slow to do anything about it so if this has happened to you could you let me know. Neil Fincham Integral LTD.

1 0