Re: New ISP Conclusions
> Just some conclusions to follow up my earlier post: > Is your date set correctly? Rob
Re: New ISP Conclusions
On 2/01/2009, at 8:23 AM, Bernard Frankpitt wrote: I was surprised to find the the ISP situation has changed drastically in the last three years. There are now essentially 4 ISPs in New Zealand: Telecom, Telstra, Vodaphone and Slingshot: Orcon (a large ISP that is now indirectly government-owned) and Xnet/ WorldXchange (a budget ISP) are pretty big in terms of subscriber numbers too. They sit in the chain at the same level that Vodafone and Slingshot/Callplus do, in that they sell DSL over Telecom's DSLAMs predominantly, but have either started deploying their own DSLAMs in some exchanges or plan to do so. There's also ten or so smaller ISPs around the place, some of which are predominantly regional. Basically all of them, with the exception of some wireless ISPs (of which Woosh is the most well known, but probably not for the right reasons), sell DSL services. There's also a few business ISPs around, and many of the above residential ISPs also have business services. -jasper
Re: New ISP Conclusions
On Fri, Jan 2, 2009 at 8:23 AM, Bernard Frankpitt wrote: > In the end I went for the cable modem option: It is the option offered by > my Telstra, and I already have a cable connected to my house. > ... > When you go to a broadband connection, the ISP controls both sides of the > link since they provide you with a stand-alone modem that usually connects > to you computer via a TCP/IP link over Ethernet. That is a much easier set > of protocols to design to. In addition, it is easy to put a firewall router > between the modem and your machines to give you additional security. Just be aware that with Telstra, by default you get a real external IP address bound directly to your computer; if you are not running a pretty aggressive firewall you will now be processing all attack traffic directly on your machine. Of course, the majority of this will be stuff that subverts Windows machines, but some if it will be valid attacks against other services too. Attaching a Windows computer directly to Telstra's service is severely negligent. :-) The Telecom ADSL solution, where there is a NAT layer between you and the Internet run on a separate piece of hardware, is actually nicer from that perspective. I strongly recommend a separate machine of some description between you and the Telstra connection. Just what that is, depends on what you want to do with your new connection ... -jim
New ISP Conclusions
Just some conclusions to follow up my earlier post: First: Thanks for all the replies and discussion. In the end I went for the cable modem option: It is the option offered by my Telstra, and I already have a cable connected to my house. Second: I was surprised to find the the ISP situation has changed drastically in the last three years. There are now essentially 4 ISPs in New Zealand: Telecom, Telstra, Vodaphone and Slingshot: Paradise and Clearnet are just brands for Telstra clear. Telstra has completely integrated the operation of these companies with its own TelstraClear service. While the old Paradise and Clearnet domain names still exist, all new users get TelstraClear accounts. IHug is now Vodaphone. I am sure there are still some small ISPs around, but it seems like the top end is well and truely shaken out. Third: As regards PPP over modem, I downloaded the relevant RFC's and looked pretty carefully at the PPP problem I was having. The problem I was having was in the LCP setup layer. It seems that Slingshot's state machine and the pppd state machine go out of sync when the Slingshot peer tries to renegotiate the LCP layer. The pppd peer ( the only side that I can see in detail ) looks to follow the RFC specification, but the whole thing is so complicated that I cannot conclude that the Slingshot peer is at fault. It may well be that the right combination of options to pppd will overcome this problem, but it is really a sticking plaster solution. The underlying issue is that PPP is a complicated protocol that involves extensive negotiation of parameters between the two peers at several protocol layers. While I am sure that whoever writes the ISP's peers could do better with their testing, I doubt if it is possible to come up with a test suite that guarantees the implementation is compliant with standard under all circumstances. I doubt that PPP over modem connections to any ISP will ever be truely Linux friendly in a set and forget sense. When you go to a broadband connection, the ISP controls both sides of the link since they provide you with a stand-alone modem that usually connects to you computer via a TCP/IP link over Ethernet. That is a much easier set of protocols to design to. In addition, it is easy to put a firewall router between the modem and your machines to give you additional security. Bernie Frankpitt
Re: OT: Christchurch bus info
Eliot Blennerhassett wrote: Recalling that there was some bemoaning of the lack of linux support for bus information in chch, I stumbled across this just now: http://arcgis.ecan.govt.nz/Beta/Metro/wheresmybus.aspx (From here http://ecangisbeta.wordpress.com/) Looking good Happy New Year to all *nix users
OT: Christchurch bus info
Recalling that there was some bemoaning of the lack of linux support for bus information in chch, I stumbled across this just now: http://arcgis.ecan.govt.nz/Beta/Metro/wheresmybus.aspx (From here http://ecangisbeta.wordpress.com/)
