I guess I could have saved you from this -- the same thing happened to me, sort of. See my condensed version of upgrading from DHCP addressing to permanent addressing below.
Rachel
First, I had SBC DSL w/PPoE, I used a wireless DSL hub (DLINK). For the original install, I had to use a PC with the DSL modem but later I installed the DLink with no problems and I went along my merry way with my DLink wireless network.
Second, I decided to install a firewall, DMZ with Linux Web/DNS server and an 'inside' network. I upgraded my DSL service to permanent IP addressing. This became the nightmare of all time. Before installing all my new fun gear, I decided to make sure I could get the permanent addressing to work first with the Dlink that had been working fine for a year. At the approved time all I did was change the addressing from DHCP (and PPOE) to the permanent addresses they gave me -- after I called as asked for a WAN address (/30) to go with the subnet they gave me (/27). It did not work. I could see requests going out on the DSL modem but no response.
Moral of the story: SBC techs can only think in the box so you must do it their way if you want to prove anything to them. DSL will work with anything -- just don't mention that to them. If you have to work with them, you have to be prepared to set up a PC (with windows) to the DSL modem or you'll never get anything accomplished.
At 09:15 AM 3/27/2003 -0800, Ed Jaeger wrote:
The title sums it up pretty well.
Some years ago we got an IDSL (modified ISDN) setup throught ATG because we were too far from Carson City's only DSLAM by about 2,000 feet. We have an internal LAN running RFC 1918 addresses, with a Linux based firewall/NAT. ATG said, "well, then, all you need is an adapter which connects to the ISDN line on one side and has a 10bT port on the other" - and they gave us that, it's worked for years. Downside: speed is 144Kbps up/down.
Recently, SBC set up a new DSLAM, and we're in range! I call up SBC, and one of their reps actually comes out to visit to set us up They've tested the lines and everything, we're good for at least 384Kbps downstream! Here's how it went:
SBC: DSL is great, blah blah blah.
Me: I know. Here's the phone closet - which pair do you want to use?
SBC: Wow, you've got network cables! Are your computers networked already?
Me: Yep, as I explained. Don't worry about that. I suggest this pair.
SBC: Well, which workstation is going to use the DSL?
Me: All of them.
SBC: <pause> What operating system do you use?
Me: It depends: Win98/NT/2K, MacOS, Linux - depends which computer. Why?
SBC: That's too many operating systems!
Me: Well, the computer connecting to the DSL modem runs Linux.
SBC: DSL is not compatible with any form of Unix.
Me: Sure it is. You use PPPoE - I'll just set the firewall up so it can bring up the PPPoE link, I don't need EnterNet (or whatever it is you use) to set up PPPoE.
SBC: You use DSL for the Internet! (EnterNet, Internet - same thing)
At this point I figured out that, despite what I've heard, SBC can only deal with single workstation Windows connections. So now I'll have to drag some old P133 with Windows 98 on it into the phone closet, tell him that's what we're going to use, and do the self install (requesting an external modem) and nobody's the wiser.
Just wanted to save anyone else the aggravation.
--
Ed Jaeger, President & CFO, Bohlender Graebener Corporation
[EMAIL PROTECTED]
http://www.bgcorp.com
---
"No pessimist ever discovered the secret of the stars, or sailed to an uncharted land, or opened a new doorway for the human spirit."
- Helen Keller
_______________________________________________
RLUG mailing list
[EMAIL PROTECTED]
http://www.rlug.org/mailman/listinfo/rlug
