GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
PLEASE NOTE: All LQ Rules apply to the General forum. Flame wars, personal attacks, hostility, insults and behavior of that nature will not be tolerated. Differing opinions are one of the things that make this site great, but to benefit from differing opinions the discourse must happen respectfully and thoughtfully... without insult and personal attack. Members who are unable or unwilling to participate in General under those parameters will not be permitted to do so. If you see behavior of this nature please report it.
I have the Home Portal 2wire 1000sw and I seem to have just figured it out (But not yet)
It seems to take in the DSL through the IP specified by SBC. Now I have yet to figure out if its PPPoE or DHCP and I dont know the differnce. It then spits out a DHCP internal IP which my Linksys router picks up on.
I get SBC DSL with the speadstream 5100 modem. I have also the Linksys BEFSR41 router, and when I first booted into Linux Mandrake, I had no problems at all, no configuring whatsoever. Recognized my LAN in a snap.
* Notice to SBC DSL Users *
If you use DSL and have a 2wire Homeportal 1000sw/hw - 1800hw - These are both routers and PPPoE is taken care of by the internal client. Routers have internal PPPoE software and do not require PPPoE client software such as Enternet 300 or Roaring Penguin to be loaded on the computer.
The 2wire's all use 172.16.0.x addressing via DHCP for their LAN side. The WAN side is given the IP from SBC when it logs into the network. 2Wire's also have a built-in firewall. Its not very hard to configure. You can browse into a 2wire configuration by browsing to 172.16.0.1 - You will need your system password in order to make changes to its config, you set this password up when you installed the modem. Do not confuse this password with your SBC user id password. SBC Tier1 support cannot reset the 2wire system password, you must speak with a 2wire representative to be able to reset the password. If you need your system password reset just call 1-877-SBC-DSL5 and request to speak with 2Wire for a system password reset if you forgot it.
Also the new SpeedStream 5100b also has built in client software which means if you have DHCP set on your Linux box then you will be able to get an IP from the DSL modem and browse. The new ss5100b is different in that its PPPoE client software obtains an IP then forwards it to your nic via DHCP. If you are not logged into the internet, ie your internet light is off, then the IP you should see sent to your nic is 192.168.1.64 with a gateway ip of 192.168.0.1 and a subnet of 255.255.255.0. You should be able to browse into the modems config using any browser. The modems config page gives you everything you need to know about your connection. If you are unable to browse into the modem then check you tcp/ip configuration settings. Also if the modem is in bridge mode you will not receive an IP from the modem and the only way to get to its config is to manually put in the above ip settings so that you are on the same network as the modem. In bridge mode the 5100b modems client software has been turned off to allow PPPoE traffic to pass through. If the 5100b is set to bridge mode you will see PPPonComputer set in the advanced settings in the web configuration. Once this is reenabled you can set your nic back to DHCP and you should have the same IP. Once you are logged in with a 5100b and the internet light is solid the ip you should see on your nic should be a dsl ip. If you perform a traceroute to your pc from the internet you will see a timeout right before your PC's hop. This is the 5100b performing IP forwarding and is done transparently.
SBC does not support Linux configuration so don't try and get anybody to help you figure out whats wrong with your connection with anything other than a Windows or Mac OS platform. The whole spiel about testing your modem with it connected directly to one computer without the router is done to eliminate any other issues that may possibly arise with your routers configuration since it is a third party appliance. Most people will get by without having to call SBC if they just read their DSL modem or router manual. Powercycle or test the connection using another computer with all the required software needed to connect. If you are not sure if your router is logging into the PPPoE read the log file. Every router has one and you will see errors generated in them if there is something wrong with the connection. Most people do not read their manuals and end up overlooking the fact that they have all the info needed to troubleshoot their connection in their Routers log files.
Modems that SBC supports that require PPPoE clients are:
Speedstream Models (ss) - ss3060, ss4060, ss5260, ss5360, ss5100a(does not have an internet light) & Westell Wirespeed B90 (there are more modems out there but you should get the picture)
Other DSL providers all use PPPoE for the connection between the end user and the co/rt - I don't know of any that don't.
All modems have status lights, Use Them, They Mean Something!! With the Speedstreams if you have a solid green dsl light then you have SYNC (dsl signal to your house and the Central office or Remote Terminal). The 2wire with a solid orange broadband link light means that you have SYNC but you are not logged in to the SBC network with you SBC User ID. When Broadband Link is green that means your 2wire is connected to the internet. A quick search on Google should find you anything you need to know about any particular DSL modem model. Every modem has a SYNC light and an ethernet light or some other way to tell wether it is getting signal. Always test your connection by pinging a website by name and by ip to be sure you can browse. As always Read the Manual.
Hope this helps you guys out, and enlightens many...
Don't worry about pppd, pppoe, etc. This is all handled by the 2Wire router. The only thing that you need to do is get an IP address for your network card from the 2Wire router.
Basically, it seems that getting the HomePortal modem working is only a problem in dualboot scenarios. I've seen quite a few posts here and elsewhere where Linux distros just recognized it and it worked out of the box.
But if you follow 2Wire's instructions, the first time it assigns an IP address via DHCP to your network card will be under Windows or Mac. At that point you will be screwed when you try to get a connection under Linux. Once the HomePortal DHCP has assigned an IP address to a card, it will not try to assign to an address again to the same card. Under SuSe, this results in a "No DHCP" error during bootup. One cure for this is to goto
This clears the router's cache of assigned IP addresses/network card addresses. Now boot into Linux and the network card will receive an IP address via DHCP. Configure both the default gateway and DNS server to 172.16.0.1 and presto you have internet. Note that your computer will need to have different hostnames under windows and linux.
Unfortunately, this was not truly viable for me because I have a LinkSys wireless access point on my network and I have not found a way to get it to request a new DHCP lease except for reinstalling the software under Windows. However, my computer came with a network card (Tulip DecChip aka *wincard*) preinstalled and then SBC sent me another network card (mine was a RealTek aka *lincard*) with the HomePortal. So I put the RealTek card into my computer. I did not plug the network cables back in. I booted into Windows and disabled *lincard*. I booted into SuSe and disabled *wincard*. Now plug in the cables. When you boot into linux *lincard* will get an IP address via DHCP and *wincard* will not try. When you boot into windows *wincard* will get an IP address via DHCP and *lincard* will not try. Internet will work fine in both OS.
There are probably ways to get the same effect by futzing around with the DHCP client name but I'm not a networking guru so this was simpler for me.
This is a repost from another forum. My situation is
I've been spending a heck of a lot of time rebooting
back and forth from red hat linux 9 and windows
attempting to resolve this.
My modem is speedstream 5100, not 5100b,
but the Broadcom 4401 ethernet card is not being detected,
and is not an ethernet card that is a default
installation on this distribution. So, all the
lights are functioning as it does on windows
when a connection is established with the
exception of the activity light(there are
5 LEDs on the Speedstream 5100).
Any thoughts or ideas are more than welcome:
Thanks. Still a no go, though, and I wouldn't be surprised
if it turns out to be something obvious...
After installing RPM package,
rpm -ivh bcm4400-3.0.7-1.src.rpm
...then changing directory as,
...then attempting to build object file,
rmpbuild -bb SPECS/bcm4400.spec, error outs as,
+ umask 022
+ cd /usr/src/redhat/BUILD
+ CD BCM4400-3.0.7
+ export LANG
+ make bcm4400.o
Makefile:18: *** Linux kernel source
tree not found Stop.
error: Bad exit status from /var/tmp
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.7053 (%build)
Line 18 of the makefile is:
$(error Linux kernel source tree not found)
...attempted assigning LINUX variable
to /usr/src/redhat instead of /usr/src/linux
in the makefile, which did not build the
object file. Any thoughts?
ive got sbc dsl, the 2wire etc. no prob setting it up, cept having to deal with 2 routers is kinda a pain sometimes,(the 2wire i got routes)
funny story - i got the modem sitting by the linux box, my other computers are wireless, so when i talk on the phone to them i say, yea ive got winders xp, blah blah. guy comes and needs to chk it, gets on the computer with linux and goes uh.......whats this?
no major isp in the us supports anything other than winders, excluding server and nt typically, most also do not support software other than ie/outlook and oe. sbc doesnt, charter doesnt and comcast,and bellsouth dont eitheri know for sure....
I have a Home-portal 1000HW, and I tried what Sherwood said, but it didn't work, I even tried completely disabling the firewall and the resetting it again, and it still didn't work. Are there other resets that might help it work, but wont mess up my connection ?
Also, I don't understand Deneteus's post ... can someone please clarify what the solution he is suggesting is in plain English (without technical jargon) ? Please ?
Ok, well I'm trying to make the modem work for Linspire, and I'm dual-booting with Win XP. The modem works on XP, but not on Linspire. All the lights are green on both XP and Linspire, and Linspire does detect my ethernet card, but I cant access the internet on Linspire no matter what I try. So, Deneteus said something about bridging ... if I put the modem in bridging mode do you think I can get it to work, and somehow by-pass the problem mentioned by Sherwood ? Or are there other solutions ? The modem did NOT come with a manual, so I cant get help from there. Or should I just get rid of XP ? I'll only get rid of it if the modem is guarranteed to work on Linspire, not dual-booting.
Last edited by H_TeXMeX_H; 10-04-2005 at 10:40 AM.
A modem/router such as a netgear dg834 is the way to go.. just get any combo modem/router that does the handshaking, password sending, pppoe, DNS, etc. and gives you four hot ethernet ports. You turn it on, wait 15 seconds and you have access. Make sure it's a NAT router that does rudimentary firewalling (can be set to drop unsolicited packets).
Going this route, I've had no problems with SBC at all.. I doubt they noticed or care. For a while I had used their speedstream modem with Roaring Penguin pppoe. But then I wanted an internet connection that did not depend on my computer being fired up (mainly because my then-fiance' moved in with her windows machine). I should have bought the router in the first place, because the trouble of setting up SBC's cheap-ass modem in linux was more to me than the cost of the NAT router, which was no trouble to set up at all. If you have no money to buy one of these, I recommend you take the path of least resistance and just panhandle the $60 or so that they cost.
Furthermore, having a small, low-wattage appliance in your house that any guest (running any OS) can plug into and have instant broadband.. well, that's just nice. All this setup and dual booting business.. piss on it. "Does SBC support Linux?" Get a router that makes the OS irrelevant.
I use a Zoom adsl modem/router going into three other switches throughout the house with sbcglobal and it works fine on all OS's. The bad thing is that I have to have a windows box as the master computer for power outages. When there is a power outage, I need to reboot the router then turn the windows box on to reset the modem. It can be a hassle hanging onto a hard drive for a modem but it is easier than learning how the thing really works.
Yeah, I guess I should get a new modem, I never liked 2wire in the first place, their routers kinda suck ... but it was free. Moral: Nothing good is free. (except linux, oh and only some distros) Ok, I'll look into getting a new modem, or in the meantime I can just get rid of Windows. (The modem is supposed to work fine when not dual-booting ... so that may be the only option)