so I set it up as follows:
* Speedstream runs "pppoe on the modem" mode, giving an address of 192.18.0.1 on it's LAN port (can't change this - I tried)
* Router is setup as "I don't need a password to connect" and has a LAN ip of 192.168.1.1
this way, I can browse to both through firefox for configuration, and the speedstream handles it's own shit... nothing else seems to work
god this took forever to figure out... changing the topic now...fookin SBC
]]>oh dear god... I was looking around in the documentation for the speedstream and crap like that... I don't seem to recall ever switching the username/password on it from the master "sbcyahoo@whatever" account...
muahahah...
muahahaha....
Hey, by the way, keep an eye on your IDE activity light while you're connected. SBC is pretty good, but when I was on an old comcast cable intranet, they were probing something on my system at 30 sec intervals. suckers...
]]>However, I have my info in my router, which is using pppoe in bridge mode through the modem... so I don't even know if the modem is logging on....
]]>OT: Think it would hurt anything to remove the fan connector from the processor on an 866P3 - the heatsink is pretty large, but the fan is irritating sounding and I don't feel like paying $20 for a good fan for a shitty machine
You can drop it's noise quite a bit by using an adjustable rheostat and using the 5/12 connections to power it. That's an old OC'er trick. With your older P3 rig, I doubt the mobo has a fan speed detector, limiting you from posting. If it does, it won't work since it needs a ground at 0V. Basically, you'll be running your fan at a slower speed.
Check the OC forums. I'm sure they dot links to do it.
Oh, by the way Phrakture, I remember my old P3 800. I had it with just a heatsink for a while, but it ran too hot for my tastes. I got away with a bare naked PII-400 all the time, but I've been too afraid since then.
[edit]By the way, here's some info for a 7V fan. Just do a google on "7V" fan and you'll get the results I was talking about earlier. Basically,
" You use the yellow 12v wire as the power connector to the fan and use the red 5v connector as the fan ground. The fan sees the potential difference between the 12v and the 5v so is run at 7 volts. Fans can be run at 5v but some will fail to start and air flow is low."[/edit]
]]>if their DNS servers are just crappy... I'll run bind on my fileserver...
OT: Think it would hurt anything to remove the fan connector from the processor on an 866P3 - the heatsink is pretty large, but the fan is irritating sounding and I don't feel like paying $20 for a good fan for a shitty machine
]]>[...]I'll call SBC if all else fails (I hate talking to those people....)
I grew a beard talking to those guys one day. After so many runarounds with 'em, I finally got to speak to some Regional Manager out there in California, and he gave me a free year's contract.
I'll check back later if I can think of something else. I'm sure it's something simple, like a router configuration option or something. I would think it's your gateway settings giving you these problems. You could try:
route -n
to see how you're getting outside your subdomain, and maybe add another one.
]]>anyone else using the chicago SBC servers for dns...or anyone near here want to attempt using them, just to see if it's me or them?
Primary DNS 206.141.192.60
Secondary DNS 206.141.196.13
I'll call SBC if all else fails (I hate talking to those people....)
I've tried everything skoal and cactus suggested (even the deleted posts... I kept them up while I was disconnected from the internet, so I know I tried it all....)
]]>however, I have just been using bbs.archlinux.org - my issue was manifesting as almost a DNS lookup error, but once it had successfully looked something up, and (I'm assuming) cached it, it worked fine... so the forums work great... I'll try closing the browser and retrying just to see if it's still working fine - I figure I'll track it down tomorrow, as it's getting late now...
]]>It's been a while since I used that Cisco wireless card I had, but I remember having to "cat /proc/net/wireless(?)" (somewhere in there) to get a bunch of good information not given by just "iwconfig". The way I troubleshooted was displaying the "/proc" stuff in one term, play with "iwconfig" settings in another term, "committ" changes, then check the strength, node, and other info from the "/proc" interface as it updated.
I ran the Windows driver also, copied over all the info, and used it to manually set some stuff in the "/proc" interface directly, which "iwconfig" didn't recognize with it's "extensions". I got pretty good results (on par with Windows driver) when I did that.
* I never used ndiswrapper and am not familiar with it. I solely used "iwconfig". You probably already know most of that anyway, but for me, the "/proc" interface was my friend...
One thing I vividly remember from the "/proc" interface, was seeing in "real" time how my signal strength was varying as I adjusted it in the other term.
]]>Then I would try tranferring a large file from a known location using tcp (ie http). Something big enought to take a while. Like maybe an iso or something..
then when it is done, do a netstat -ts and see what it says..
]]>