If you have AT&T DSL and cannot connect it is because they control the operating systems that can connect with the firmware of their own modems. I know this for a fact. See my posts in the connection section. They turned me on for a test, then turned me off and now they want money to turn me back on. XP is no problem. That they give you. Perhaps they have some sort of deal with Microsoft, who knows?>:(
jdcart15 wrote:
>
> If you have AT&T DSL and cannot connect it is because they control the
> operating systems that can connect with the firmware of their own
> modems. I know this for a fact. See my posts in the connection
> section. They turned me on for a test, then turned me off and now they
> want money to turn me back on. XP is no problem. That they give you.
> Perhaps they have some sort of deal with Microsoft, who knows?>:(
>
>
I am not familiar with at&t since I am not a northern american resident but
from germany. But are you sure you do not missinterpret what probably
happened.
You say somehow they enabled a feature for you which makes your linux system
connect and then it disappeared.
Can it simply be that your modem was/is configured to update its firmware
regularly via the web connection it establishes and that such an update
simply overwrote your firmware setting so that you are now back where you
were before?
In germany such settings are not uncommon in routers from the internet
provider (and can sometimes lead to trouble also, if something goes wrong).
What kind of hardware do you have (the modem/router)?
Maybe it is easy to fix for someone familiar with it.
–
openSUSE 11.3 64 bit | Intel Core2 Quad Q8300@2.50GHz | KDE 4.5 | GeForce
9600 GT | 4GB Ram
openSUSE 11.3 64 bit | Intel Core2 Duo T9300@2.50GHz | KDE 4.5 | Quadro FX
3600M | 4GB Ram
I’ve never heard of firmware for a modem that can lock out a specific operating system.
Go to Yast and turn off the firewall temporarily. Can you connect??
No connection with firewall turned off. My modem is a 2WIRE which was purchased from AT&T.
You say that XP runs okay. Are you running a laptop or desktop. What brand and model?
Did you try shutting down the modem, disconnecting all wires, waiting for 1 minute.
Then reconnecting and powering up?
Yes, I have done all of that. Both xp machines have never had a problem, in either ethernet or wireless mode. The linux machine is a dual boot with win 98 second ed. Is there anyway the Win 98 2nd edition in a different partition could be causing a problem?
I built both xp machines. the Linux is an older IBM Aptiva. It was slow yesterday when working, but it worked perfectly. Win 98 also worked perfectly both ethernet and wireless. But now win 98 cannot connect either.
So I wonder how this modem would know what OS is running? Does the Linux setup get an IP address and such. Does the problem just block Firefox perhaps? You can install the User Agent that allows FireFox to report it is Internet Explorer for instance.
https://addons.mozilla.org/en-US/firefox/addon/59/
Thank You,
You are confused.
I have been using AT&T as my ISP since 2001.
Oops, I’ll take that back. I was using Ameritech in 2001. They merged into SBC somewhere around 2002, and I have been using SBC ever since. A while back, SBC bought out AT&T, and then started using the AT&T name. However, it is still the same company that was SBC back in 2002.
I have been using various versions of unix for that whole period - slackware, solaris 7, solaris 8, opensuse. I have never had a problem.
AT&T will tell you that they do not support linux. But that only means that if you have problems that are related to your OS, they won’t help you fix it.
I’m not sure what other posts of yours I should look at. Hmm, I see you are having problems with a driver. And it is true that AT&T won’t help you resolve driver problems with linux. You will get better support here on that problem.
Another place you can consider is the AT&T Midwest forum on dslreports.com. You will find people there who have a long experience dealing with your ISP.
I appreciate all of your responses, because it is changing my way of thinking. I am now thinking that Mr. Helm from Germany is probably right. This system that is running Linux is so slow that it is not reconfiguring fast enough. It probably reconfigured for the win 98 partition because that was the last system I was running when everything was working good. Perhaps if I give it some time it will reconfigure to Linux. I think my solution will be to build a new machine for me to run my Linux on. I used the old machine because I wanted to try it out. I know my drivers in Linux are ok, because, as I have said, yesterday everything was perfect. No errors in any system. Thanks for perhaps putting my thinking on the right track, especially to Mr. Helm.
Every OS (and every router as well) has a TCP/IP fingerprint. Not the modem, but the ISP knows what OS you - more precisely the computer directly connected to the modem - is running. You can find out too if you use the command: **nmap -O ** with root privileges, followed by a hostname in your lan or anywhere in the Internet. It will tell you what OS it is running or, if it cannot guess, it will display it’s TCP/IP fingerprint.
Every OS (and every router as well) has a TCP/IP fingerprint. Not the modem, but the ISP knows what OS you - more precisely the computer directly connected to the modem - is running. You can find out too if you use the command: **nmap -O ** with root privileges, followed by a hostname in your lan or anywhere in the Internet. It will tell you what OS it is running or, if it cannot guess, it will display it’s TCP/IP fingerprint.
And that is it, your OS is always given away and nothing you can do about it then?
Thank You,
Well, people from the outside world scanning your IP will see the fingerprint of your router, not the one of the computers behind. The operation called “scrubbing” is intended to complicate TCP/IP fingerprinting and port scanning. I know very little about iptables and Linux firewall, as I use OpenBSD and pf for my firewalls. But I would assume that iptables offers a similar protection.
TCP/IP stack fingerprinting - Wikipedia, the free encyclopedia
That sounds like a hardware problem. NIC gone bad?
jdcart15 wrote:
>
> No connection with firewall turned off. My modem is a 2WIRE which was
> purchased from AT&T.
Qwest also used 2WIRE for a while. After the 4th one died a premature death
they switched back to ActionTec. Never had a problem (while the modem
worked) with Linux (openSUSE 10.xx and 11.xx) so it’s not likely to be an OS
issue with the modem unless you are setting up the DSL parameters from the
computer. I think AT&T, Verison, and Qwest all use different mode settings.
It got to the point I made a list of all the settings after fighting the
issue a few times. Now, if I could just find the list…
–
Will Honea
-
No way.
-
Assuming your nic is eth0 (but double check with ifconfig -a
) and is connected to your modem, get root and send a dhcp request :
su -l
/sbin/dhclient eth0
what happens? -
If it doesn’t work retry after rebooting in runlevel 3 (console mode) - I don’t entirely trust KDE and whatever network applet might be running there.
I concur in general to the others. The modems used for DSL are not specific to any ISP, while they may favor one over the other from time to time, with the right settings it’s likely all will work. What the ISP needs starts with the MAC address of the DSL modem. This should be printed on the device and is unique. No two devices are ever supposed to have the same MAC address. In 35 years I have only come across such once and the offending device was factory recalled. Like all hardware, they can work one moment and for no apparent reason fail/go-defective the next. As for your ISP telling you they turned off and on your Linux access, it is more likely, they just routed you from a general public controller card to a preferred client one for a test. This I had happen with a troublesome ADSL line. I couldn’t connect for weeks, checked the clarity of my line (signal to noise ratio) and the line was 3/120 instead of 10/2 so I was getting 60 times more noise than normal and less than 1/3 of valid signal. They switched me to a new card and I got 10/1 immediately but a day later it was back to 3/120 and no joy.
Long story short, the ISP used every trick in their arsenol to convince me that the problem was on my end, and even said things like we only work with windows machines, MACs Linux and UNIX need special hardware and special ISP’s so if you want to surf the Internet go back to windows.
test your nic, and make sure it can talk to the dsl device as noted in last post. If that in fact works, then it’s the settings of the dsl which can be controlled from the isp end, or it’s the settings of your linux/windows OS’s.
I had a problem with the initial setup of my at&t service, but that was only because their registration site refused to load in anything other than IE. Since then, no problems.
On 2010-10-09 17:36, russlar wrote:
>
> I had a problem with the initial setup of my at&t service, but that was
> only because their registration site refused to load in anything other
> than IE. Since then, no problems.
Which is funny, as they invented unix.
By the way, can’t you people use a router instead of a modem? That way, configuration is internal to
the device from the ISP, nothing in the computers affect it, no drivers. Just plain local network
and a gateway.
I have no idea what AT&T offers, I live thousands of miles away. Big water in the middle, you know 
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
There are times when a combined router/switch/modem wont satisfy. Like many internet voip phone units do not play nice when the modem and router are together. In order to use voip without lockouts I had to feed internet modem to switch and 1 switch connect to router and pc’s and another switch connect to voip modem to phones. using just a Internet modem with 4 port router built in, the pc’s worked if no voip phone call, but when a voip call arrived pc’s would lose connect and trying to re-establish connect killed the voip call. Sometimes you need to do as you must to live happy.