The SaskTel default IP address is not in the 192.168 address range. I have tested this with a SaskTel router and it didn't work. Also, the SaskTel units are encrypted by default.
Even substituting the correct address does not help. I can't get this exploit to work with a SaskTel unit. Some of them get to SaskTel's MDC console, for which the password is not publicly available. I'm sure it could be exploited if that became known.
I work for SaskTel, a smallish telco in Canada, but still an ILEC in Sasktchewan. Here's how our network works:
Our landline switches have access points for third party long distance switches interconnecting with ours. This allows for long distance competition.
Our landline switches also have access points for third party telephone company switches, for example Shaw has telephone service in my city. Rogers and SaskTel mobility also provice local service.
Although we don't have any, third party unbundled loop CLECs are allowed to lease space in our COs to directly provice traditional copper based services like phone or DSL from their own equipment.
Our IP core network allows for multiple backhauls onto the internet, so you can lease DSL ports from SaskTel and use your own internet connection for the backhaul. If you're a SaskTel DSL customer you get SaskTel's default backhaul.
I feel this provides for a fairly open access network. Competitors can hook into just about any area of our network. We have more than enough bandwidth to our DSLAMs to handle 10 meg connections to every port. The only "competitors" that I feel are completely useless are the rebilling kind, the ones who will charge you for our service, which we provide the whole way, just front line tech support is provided by the rebiller.
Independent ISPs can circumvent the issue by colocating their own DSLAMs in Bell's COs. At that point, Bell can't interfere, because the ISPs get (and are paying for) access to the raw, dumb copper. Of course, Bell doesn't care about throttling at that point, because Bell's network isn't used for backhauling (although it can be, but you're buying LAN extensions then).
If Bell's infrastructure is like SaskTel's, that wouldn't work. Here in Saskatoon if you only locate DSLAMs in the CO you'd only be able to reach 20% of your potential customers unless you were willing to take a performance hit due to distance. SaskTel's DSLAMs are mostly in curbside cabinets (FTTN) that server 200-300 customers at most. There really isn't much room for competition, unfortunately. That's why I believe that independant ISPs should be able to hook up to SaskTel's (and Bell's) wholesale network. Of course a charge should exist because the big companies do maintain the outside plant infrastructure.
What is really too bad is the distance limits of DSL. If DSL could be made to work farther away from a CO without curbside cabinets competitors could colocate a DSLAM in a Bell CO.
Since there are a lot of cabinets out there on the street it's infeasible to colocate.
I've never developed with XNA, but I have done it with.Net. You're right, it shouldn't be a big deal for those. I also can't imagine that many commercial games are developed using XNA.
If the game is C++ and they don't make any assumptions about architecture it also shouldn't be a problem. It will be a problem if they assume a pointer is 32 bits or if they use a shift operation. There are a lot of data structure issues that can pop up when you go from big endian (PowerPC) to little endian(Intel).
What we really need is for game devs to see that some games (in particular those on 360) can be ported with little effort to PC for the most part. In terms of the 360, there is no reason why all games for 360 cant be played on the PC.
Except, you know, that pesky CPU architecture. The 360 is a PowerPC, and the PC is an x86.
I work for a smallish Canadian telco. We offer DSL, IPTV, and telephone all over copper. Our infrastructure is all FTTN, and you can pull 10mbps at 600m easy. If you're on our service, 20mbps is possible if you have HDTV. There's one of two things going on here. Verizon is trying to screw you, or there's something wrong with your line.
If it's the former Verizon won't help you. If it's the latter, a tech should be able to fix it. If you're only 550m from the CO you might not have an access cabinet in between you and the CO, but there should be many pairs into the pedestal near your house. A tech should be able to just do a pair change and fix it. The other thing that could happen is a port change in the CO. Both of these are quick, as long as the CO is manned. We have about 25 in this city, and only 1 is manned full time.
How does one install new software on BSD? (do you compile everything from source?)
I upgraded from 6.2 to 7.0-PRERELEASE by doing the following:
It's a convolouted process, but I wanted to follow FreeBSD 7 development. It's easier when you do it from a binary CD. Basically you restart from the CD and upgrade and it's automated.
Start by updating my system source: $ sed -e 's/RELENG_6/RELENG_7/'/usr/share/examples/cvsup/stable-supfile >/root/7-supfile $ csup -h cvsup6.freebsd.org/root/7-supfile
Now the source is updated. So we build:
$ cd/usr/src $ make buildworld buildkernel
Now the system is built from source, ready to go into my temporary directory. Back up/etc and other config files:
$ mergemaster -p
Now my/etc is backed up ready to merge later. Install new kernel
$ make installkernel $ reboot
Now I start up in single user mode. Install new system just build from source.
$ mount -a $ cd/usr/src $ make installworld
The binaries are all installed. Merge new/etc files with old ones:
$ mergemaster
Now the machine is up to date.
As for installing packages, you have several choices. I prefer to build from source, but you can use packages. Packages are usually a little behind the ports tree. So for example, to install KDE the way I would do it:
$ cd/usr/ports/x11/kde3 $ make install
And several hours later you have KDE 3, Xorg, and a host of other apps that aren't included with the base install that KDE3 needs.
Installing from CD is easy, but it's all text based so don't be shocked. I recommend installing the "X-Developer" package and the ports tree. That should include all the base system and developer tools.
Actually, the Governor-General appoints the PM. Traditionally the leader of the party with the most seats in Parliament, or the leader of a coalition of two or more parties representing the majority of the members of Parliament. True though, is that the PM doesn't have to be a sitting member, but nearly always is either a member of the Commons or of the Senate.
GNU Make, but they also provide BSD Make. BSD make is called "bsdmake", and GNU Make is called "gnumake" with a symbolic link to "make"
[meshach:~] dan% uname -a Darwin meshach 9.1.0 Darwin Kernel Version 9.1.0: Wed Oct 31 17:48:21 PDT 2007; root:xnu-1228.0.2~1/RELEASE_PPC Power Macintosh [meshach:~] dan% ls -l `which make` lrwxr-xr-x 1 root wheel 7 9 Dec 15:08/usr/bin/make@ -> gnumake [meshach:~] dan%
If everyone made a phone call at the sametime the phone network couldent handle it because they oversell the service to produce cheaper rates but I have NEVER had a problem making a phonecall because my service provider has carefully planned things out to make sure this dosent happen.
I work for a phone company. Last year there was a huge snow storm, and when work got out, at about 2 in the afternoon (Everyone was let out early to "beat traffic") the trunk groups between the land line switches and the cellular switch plugged up. I couldn't get a hold of my wife on a landline when she was going home so I went and grabbed a cell phone to call her. There's only one cell switch so there were no capacity issues there.
Needless to say, after that the trunk groups are a lot bigger now then they were then.
I believe that Vista Business will do all that, you just lose the Windows Media Centre tools. Personally I have Vista Ultimate, and the POSIX C compiler is broken for 64 bit, unless they've fixed that since I installed it.
I recall reading that MTS Allstream was going in with Quebecor and Vodaphone to build a national GSM network. MTS's home network is CDMA, but that doesn't mean that its former AT&T Canada (Allstream) branch can't build a GSM network nation-wide.
I work for SaskTel and that was a "Industry Update" we received in our email.
I'd like to see a powerpc port, and I'd be willing to work on it if I understood the platform a little better. I'll wait for Apple to release Java 6, I guess.
Slashdot Mirror
My SaskTel router's firmware version is 5.29.111.5. Looks a bit more recent.
The SaskTel default IP address is not in the 192.168 address range. I have tested this with a SaskTel router and it didn't work. Also, the SaskTel units are encrypted by default.
Even substituting the correct address does not help. I can't get this exploit to work with a SaskTel unit. Some of them get to SaskTel's MDC console, for which the password is not publicly available. I'm sure it could be exploited if that became known.
I feel this provides for a fairly open access network. Competitors can hook into just about any area of our network. We have more than enough bandwidth to our DSLAMs to handle 10 meg connections to every port. The only "competitors" that I feel are completely useless are the rebilling kind, the ones who will charge you for our service, which we provide the whole way, just front line tech support is provided by the rebiller.
Independent ISPs can circumvent the issue by colocating their own DSLAMs in Bell's COs. At that point, Bell can't interfere, because the ISPs get (and are paying for) access to the raw, dumb copper. Of course, Bell doesn't care about throttling at that point, because Bell's network isn't used for backhauling (although it can be, but you're buying LAN extensions then).
If Bell's infrastructure is like SaskTel's, that wouldn't work. Here in Saskatoon if you only locate DSLAMs in the CO you'd only be able to reach 20% of your potential customers unless you were willing to take a performance hit due to distance. SaskTel's DSLAMs are mostly in curbside cabinets (FTTN) that server 200-300 customers at most. There really isn't much room for competition, unfortunately. That's why I believe that independant ISPs should be able to hook up to SaskTel's (and Bell's) wholesale network. Of course a charge should exist because the big companies do maintain the outside plant infrastructure.
Basically it's that copper or fibre infrastructure is very expensive. As far as I know there is no law preventing others from building, just expense.
What is really too bad is the distance limits of DSL. If DSL could be made to work farther away from a CO without curbside cabinets competitors could colocate a DSLAM in a Bell CO.
Since there are a lot of cabinets out there on the street it's infeasible to colocate.
I work for SaskTel, a crown corporation. We offer among other things DSL, IPTV, and telephone services.
I've never developed with XNA, but I have done it with .Net. You're right, it shouldn't be a big deal for those. I also can't imagine that many commercial games are developed using XNA.
If the game is C++ and they don't make any assumptions about architecture it also shouldn't be a problem. It will be a problem if they assume a pointer is 32 bits or if they use a shift operation. There are a lot of data structure issues that can pop up when you go from big endian (PowerPC) to little endian(Intel).
What we really need is for game devs to see that some games (in particular those on 360) can be ported with little effort to PC for the most part. In terms of the 360, there is no reason why all games for 360 cant be played on the PC.
Except, you know, that pesky CPU architecture. The 360 is a PowerPC, and the PC is an x86.
It's a regional ILEC, so you probably can't get service from us. SaskTel
I work for a smallish Canadian telco. We offer DSL, IPTV, and telephone all over copper. Our infrastructure is all FTTN, and you can pull 10mbps at 600m easy. If you're on our service, 20mbps is possible if you have HDTV. There's one of two things going on here. Verizon is trying to screw you, or there's something wrong with your line.
If it's the former Verizon won't help you. If it's the latter, a tech should be able to fix it. If you're only 550m from the CO you might not have an access cabinet in between you and the CO, but there should be many pairs into the pedestal near your house. A tech should be able to just do a pair change and fix it. The other thing that could happen is a port change in the CO. Both of these are quick, as long as the CO is manned. We have about 25 in this city, and only 1 is manned full time.
The main repository of FreeBSD packages is at ftp://ftp.freebsd.org/pub/FreeBSD/packages.
I turned out to be mistaken about this. The real address is: ftp.freebsd.org/pub/FreeBSD/ports/ARCH/packages-VERSION.
For example: ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-7.0-release
How does one install new software on BSD? (do you compile everything from source?)
/usr/share/examples/cvsup/stable-supfile > /root/7-supfile /root/7-supfile
/usr/src
/etc and other config files:
/etc is backed up ready to merge later. Install new kernel
/usr/src
/etc files with old ones:
/usr/ports/x11/kde3
I upgraded from 6.2 to 7.0-PRERELEASE by doing the following:
It's a convolouted process, but I wanted to follow FreeBSD 7 development. It's easier when you do it from a binary CD. Basically you restart from the CD and upgrade and it's automated.
Start by updating my system source:
$ sed -e 's/RELENG_6/RELENG_7/'
$ csup -h cvsup6.freebsd.org
Now the source is updated. So we build:
$ cd
$ make buildworld buildkernel
Now the system is built from source, ready to go into my temporary directory. Back up
$ mergemaster -p
Now my
$ make installkernel
$ reboot
Now I start up in single user mode. Install new system just build from source.
$ mount -a
$ cd
$ make installworld
The binaries are all installed. Merge new
$ mergemaster
Now the machine is up to date.
As for installing packages, you have several choices. I prefer to build from source, but you can use packages. Packages are usually a little behind the ports tree. So for example, to install KDE the way I would do it:
$ cd
$ make install
And several hours later you have KDE 3, Xorg, and a host of other apps that aren't included with the base install that KDE3 needs.
Take a look here for more info about FreeBSD's package management. The main repository of FreeBSD packages is at ftp://ftp.freebsd.org/pub/FreeBSD/packages.
Installing from CD is easy, but it's all text based so don't be shocked. I recommend installing the "X-Developer" package and the ports tree. That should include all the base system and developer tools.
Actually, the Governor-General appoints the PM. Traditionally the leader of the party with the most seats in Parliament, or the leader of a coalition of two or more parties representing the majority of the members of Parliament. True though, is that the PM doesn't have to be a sitting member, but nearly always is either a member of the Commons or of the Senate.
GNU Make, but they also provide BSD Make. BSD make is called "bsdmake", and GNU Make is called "gnumake" with a symbolic link to "make"
/usr/bin/make@ -> gnumake
[meshach:~] dan% uname -a
Darwin meshach 9.1.0 Darwin Kernel Version 9.1.0: Wed Oct 31 17:48:21 PDT 2007; root:xnu-1228.0.2~1/RELEASE_PPC Power Macintosh
[meshach:~] dan% ls -l `which make`
lrwxr-xr-x 1 root wheel 7 9 Dec 15:08
[meshach:~] dan%
If everyone made a phone call at the sametime the phone network couldent handle it because they oversell the service to produce cheaper rates but I have NEVER had a problem making a phonecall because my service provider has carefully planned things out to make sure this dosent happen.
I work for a phone company. Last year there was a huge snow storm, and when work got out, at about 2 in the afternoon (Everyone was let out early to "beat traffic") the trunk groups between the land line switches and the cellular switch plugged up. I couldn't get a hold of my wife on a landline when she was going home so I went and grabbed a cell phone to call her. There's only one cell switch so there were no capacity issues there.
Needless to say, after that the trunk groups are a lot bigger now then they were then.
I believe that Vista Business will do all that, you just lose the Windows Media Centre tools. Personally I have Vista Ultimate, and the POSIX C compiler is broken for 64 bit, unless they've fixed that since I installed it.
Many politicians are like this. They get power and stop listening to the little guy. You see it with Liberals, you see it with Tories, it's pervasive.
Mind you, my MP has always been a dink. I also never voted for him, and I know people who made shirts that say "Fuck Vellacott" on them.
Well, I believe it was the Three Dead Trolls in a Baggie who said that when he died he took it all with him, he even took the gin.
And you can verify it's really him because his user id is so low.
No, no, no! We need to pummel him with Tim Bits!
I doubt hating our government officials is a uniquely American phenomenon either.
;)
Well, I'm Canadian, and I hate your government officials, too.
I recall reading that MTS Allstream was going in with Quebecor and Vodaphone to build a national GSM network. MTS's home network is CDMA, but that doesn't mean that its former AT&T Canada (Allstream) branch can't build a GSM network nation-wide.
I work for SaskTel and that was a "Industry Update" we received in our email.
I'd like to see a powerpc port, and I'd be willing to work on it if I understood the platform a little better. I'll wait for Apple to release Java 6, I guess.
No no. It's 600 Canadian Dollars.