Click to See Complete Forum and Search --> : PPPoE issues
evangelinux
09-03-2004, 01:12 AM
I'm running SUSE 8.0 Pro on a stand-alone box with a LAN card that generally works when I use it. I have a dial-up modem (which I'm using for this message) & I just received a Westell DSL ethernet/usb combo modem from BellSouth.net. The DSL modem shows all the necessary lights, and BS says their side is up with no service problems in my area. But I have no connection.
I think the issue lies in the routing setup. I setup rp-pppoe and have it configured to start at boot time (runlevels 2, 3, 5). I just set this in my last attempt.
I am using a static IP for eth0 (I find the info on using static/DHCP confusing, and the DSL modem never gave eth0 an IP address. (I'll try this again in a few minutes.) BS says I should be able to type the ip address 192.168.1.254 into the url bar, but I get connection refused (or unable to load the page).
Here's a boot message:
Sep 2 23:06:23 famdcp kernel: Linux Tulip driver version 0.9.15-pre9 (Nov 6, 2001)
Sep 2 23:06:23 famdcp kernel: PCI: Found IRQ 11 for device 00:0d.0
Sep 2 23:06:23 famdcp kernel: PCI: Sharing IRQ 11 with 00:07.2
Sep 2 23:06:23 famdcp kernel: PCI: Sharing IRQ 11 with 00:09.0
Sep 2 23:06:23 famdcp kernel: eth0: ADMtek Comet rev 17 at 0x7000, 00:70:78:01:24:70, IRQ 11.
Sep 2 23:06:23 famdcp kernel: eth0: (1) System Error occured (0)
I'm not sure what the error message is.
Thanks in advance for your help - I'm definitely new to DSL
Don
banzaikai
09-03-2004, 05:34 AM
If I may make a suggestion, one that I've made numerous times in these forums...
Get a router!
If you have a spare $40, you can pick up a simple 4-port wired (Belkin 3-port wireless routers are available up here for the same amount of money).
The advantages:
> The router does all the work, just set your box to "dhcp" and call it a day.
> Adding more computers later is a snap.
> Firewall is typically built-in (simple NAT-type, but it works).
> Print server can be added/included, so you won't have to keep a machine powered up 24/7.
Disadvantages:
> Extra cables (unless it's wireless)
> Runs 24/7, but relatively low power.
> May need to be reset on occasion.
So, buy a router, hook up to computer, log into router, config it to your ADSL settings, set up whatever security things you want, save, then connect router to modem, reboot, and you're up and running.
That said, I'd set your eth0 to dhcp (or to 192.168.1.100 to be on the same subnet mask area), since it looks as if the westell may do some of it's own routing. Check your eth0 settings to set the gateway to 192.168.1.254, and use that for dns unless the DSL guys have another IP to use.
It may be that your eth0 is conflicting with your usb (as MrBen just reminded us). It looks like you have Irqs 3, 5, 7, and 9 available (6 is the floppy and 13 is your math co-processor). Why your usb or lan card didn't map to one of these is uncertain. You may want to get into your BIOS and see if any Irqs have been reserved for legacy devices. If you don't have any of these devices (mostly ISA cards), then set everything to "Auto". While you're in there, see if you can find something labeled "Update ESCD -> Disabled" and change to "Enabled" (it will set itself back to Disabled after rebooting). This ensures that the BIOS re-scans all the cards to assign ports/irq/dma/memory maps. If this doesn't shuffle things around, then you may have to re-arrange some cards to get things re-routed.
from: evangelinux
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
I'm not liking the first IP for eth0. If it's what you set things to, then take my original advice and set it to something in the middle of the subnet addresses, like 192.168.1.100. This may be because the modem uses 192.168.1.0/1 for internal use (like my Linksys router), and has a router/switch that uses the 192.168.1.254 that the ISP said to use. So, split the difference and set your IP to 100.
The second address (gateway) should be the modem itself. Try 192.168.1.254 (and 1.0 or 1.1 if that doesn't work). The rest looks okay.
Of course, all this is pretty much avoided when using the aforementioned router and DHCP. Yes, I'm gonna rub it in 'til it hurts...
I don't like either ppp0 settings, as they both fall outside of the subnet masks listed. If you use the 192.168.99.99, then your subnet mask should be at least 255.255.128.0 to get anything going. Of course, 0.0.0.0 is always a bad sign.
Try using DHCP directly with the modem, and see what it picks up for these values. Then use them for the static settings.
banzai "really... get a router" kai
evangelinux
09-04-2004, 11:40 PM
Just out of curiosity, having a dial-up modem still connected to the PC shouldn't hurt, should it? Since it has - until now - been assigned ppp0, will that cause confusion?
Incidentally, I get several insmod failure messages at boot time. They've never effected me that I know of - their just there. Maybe I'll leave that until I sort this out.
Anyway, let me look under the hood of this thing for a minute. See about this BIOS stuff.
Later,
Don
banzaikai
09-05-2004, 04:25 AM
from: evangelinux
Just out of curiosity, having a dial-up modem still connected to the PC shouldn't hurt, should it? Since it has - until now - been assigned ppp0, will that cause confusion?
I thought it was being setup as pppoe? Yes, if you're reconfiguring your eth0 with your dial-up ppp settings, it may get confused. You can just setup the modem as ppp1, then. On my box, I had no problems, and my dialer is still sitting in my launch panel (just in case).
from: evangelinux
Incidentally, I get several insmod failure messages at boot time. They've never effected me that I know of - their just there. Maybe I'll leave that until I sort this out.
Post them - they may be very important. They should be in your /var/log/boot.log.# file.
from: evangelinux
Anyway, let me look under the hood of this thing for a minute. See about this BIOS stuff.
Looking into the soul of the machine, so to speak :D
banzai "orthodox heathen" kai
evangelinux
09-07-2004, 12:02 PM
Originally posted by banzaikai
I thought it was being setup as pppoe? Yes, if you're reconfiguring your eth0 with your dial-up ppp settings, it may get confused. You can just setup the modem as ppp1, then. On my box, I had no problems, and my dialer is still sitting in my launch panel (just in case).
On my box, Kinternet shows dsl0 and ppp0 as the interfaces. dsl0 is assigned to 'dsl provider', while ppp0 is assigned to my dial-up provider (two separate providers).
Also, I've discovered I have a dhcpcd problem, which could play an important role in the whole scenario.
Post them - they may be very important. They should be in your /var/log/boot.log.# file.
I'll get back to you on this.
Looking into the soul of the machine, so to speak :D
My BIOS assigns everything automagically, though it does offer the opportunity to manually assign stuff. As for the ESCD or whatever, I didn't see a way to change that in my BIOS. It's an Award BIOS running on a P-II 350Mhz box.
Don
mrBen
09-07-2004, 12:39 PM
Sorry - should have asked this earlier - is the modem connected by USB or by ethernet to a NIC in your box?
If it is connected via USB, try installing the CDCEther and usbnet modules. There is a slender possibility that the kernel for your version of SuSE did not include the CDCEther module, which, IIRC, is needed for Ethernet-over-USB.
evangelinux
09-07-2004, 08:01 PM
I should have said I was using the ethernet connection. Guess I took it for granted. My apologies for the confusion.
I'm uploading the text file "tshoot.txt" for you to look at. It contains some info about dhcpcd, etc. It may not be everything you need to see, but if you want, I can provide the output of ifconfig, route, and just about any other report you need. :)
BTW, if nothing else, at least I'll be able to call myself a "systems analyst". :D
Don
mrBen
09-08-2004, 04:42 AM
Try running dhclient instead of dhcpcd.
banzaikai
09-08-2004, 06:17 AM
What exact model of Westell did you get? After doing some Googling, there seems to be a consensus that Westells have more than their share of bugaboos. From what I gather:
As I guessed earlier, set your eth0 to an IP of 192.168.1.100 to be somewhere "in the middle" of the subnet.
Make sure you have link lights on the modem and NIC.
The modem setup is accessed at 192.168.1.254, and needs to be set to "Bridge Mode" for use with a router. This indicates that it has some sort of router capability built-in (which, again, is why I thought that the lower subnet addresses may be used by the modem/gateway).
Some Westell models have specific ROMs which are designed for BellSouth use ONLY - this may be one of them, and may have trouble with Linux boxen.
If you have the ability to hook up a Win box, see if that works, and jot down the settings that ipconfig gives you if it does.
Make sure you add the "@bellsouth.net" to the login for pppoe, or it may not allow you to connect (a DSL-equipped cafe up here had this problem until I realized that all I had to do was add the @ part).
Once I get your model number, I can really dig into the specs and see exactly what this thing can/does do. Or, you can always switch to cable...
banzai "3Mbps" kai
evangelinux
09-08-2004, 08:25 AM
It's a black Westell 1600 - B90-610030-06 to be exact. The only tinker toy it has on it is a little white button (reset, maybe?) between the power and ethernet adapters. Both the NIC & Westell are lit up like a Christmas tree. :) Well, the lights that are supposed to be lit, that is.
The NIC on this box isn't properly configured with Win98 for some reason. I need to check the drivers for it. I had NFS running with this computer (no changes other than a fresh SUSE install) and another box previously. I don't have that setup currently though. Haven't tried.
I need to run out for a while. Big morning ahead of me.
Later,
Don
banzaikai
09-10-2004, 06:05 AM
Don't you just love tech support? I Googled your modem, and got this: http://www.westell.com/pages/support/refer.jsp?BV_SessionID=@@@@0746561128.1094807540@@ @@&BV_EngineID=dadcjiiekdfjbedcfkcfkcfin.0&product=B90-610030-06
Great, huh?
I do have an Efficient (Siemens) 5260 ADSL modem lying here, but no DSL line to test (got cable...). It's about 3 lbs. (1.5Kg) to mail... about $5.55 USPS. What's the church's address?
banzai "anything for science" kai
evangelinux
09-10-2004, 06:17 PM
O.k., I'm back. I've been a buzy little beaver.
The short version: I'm up and running, but on a different box. (A moderator might want to move this to the Success stories forum.)
Here's what I've done:
I had some of the church PC's lying around and networked 2 of them to be sure I had good LAN service. Once I pinged each of them from the other and viewed the test HTML page on both from the other, I knew I was in pretty good shape. Both systems have static IP addresses.
I then replaced the LAN cable on #1 with the Westell and its accompanying cable. I ran the Yast DSL setup dialogue, which brought up a question about using"T-Online". I clicked "No" and got back to the setup screen. I added my BS username, password & DNS servers. I also checked the "Start Firewall" option.
I tried to connect, but failed. I pinged 192.168.1.254 succesfully. So I ran "rcnetwork restart" (SUSE's version of service network restart) and tried again. Success is sweeeeet!
My take on why my box won't connect:
I had thoroughly messed up my LAN while trying to get CUPS working over NFS - the CUPS documentation was pathetic. I had gone barking up the wrong tree and totally fried my LAN.
I eventually got around to re-installing Linux, since that would give me a clean start. I never got back to trying the LAN, though. There have been some issues to crop up that lead me to believe my re-install wasn't so clean, and that, somehow, there is a ghost of the old installation, for lack of better words.
I'm going to try the re-install again, making sure to do a better job of formatting the drive.
evangelinux
09-10-2004, 06:20 PM
Originally posted by banzaikai
Don't you just love tech support? I Googled your modem, and got this: http://www.westell.com/pages/support/refer.jsp?BV_SessionID=@@@@0746561128.1094807540@@ @@&BV_EngineID=dadcjiiekdfjbedcfkcfkcfin.0&product=B90-610030-06
Great, huh?
I do have an Efficient (Siemens) 5260 ADSL modem lying here, but no DSL line to test (got cable...). It's about 3 lbs. (1.5Kg) to mail... about $5.55 USPS. What's the church's address?
banzai "anything for science" kai
If you still want to send the DSL modem, we'll still accept it. Never know when it might come in handy. If it's better than the Westell, we'd sure put it to use. It's up to you.
The address:
6123 McIntyre Ridge Drive
Charlotte, NC 28216
banzaikai
09-11-2004, 05:52 AM
At the very least, it'll confirm whether it's the Westell, Bell South, or Linux at fault. Thus:
If it works, the Westell is bad.
If it blinks okay like the Westell, but doesn't work, then Linux is at fault.
If it errors out, then Bell South is at fault.
Let's see Marilyn Vos Savant pick at that logic... :D
banzai "couldn't hurt..." kai
evangelinux
09-24-2004, 05:06 PM
Just want to say thanks. I received the modem in yesterday's mail.
I'll give it a whirl to see if there's any diff between it & the Westell. I haven't actually had any problems with the Westell so far - now that it's running on a different box. I think the real issue was the NIC not working properly. Wish I could test it to determine whether it's bad or just getting assigned to a conflicting IRQ.
If I recall, it was assigned an shared IRQ with the USB system. Given that USB DSL Modems are known not to work well with Linux, I would almost lay down money that says that was the issue. It shouldn't affect it, but probably did.
Thanks again for all your help and the modem.
Don
banzaikai
09-25-2004, 07:33 AM
Shucks...
You may be right about the irqs, but Linux does know how to share (my eth0 and usb are shared, and I don't get so much as a hiccup). I'm thinking it's something to do with how the Westells work. At least you can try the modem to see if it works (again, I use cable here, so the DSL was just gathering dust).
If I can fix the power connection, I have a one-port router (Linksys BEFSR11 - just attach a hub/switch for extra ports) I'm not using...
banzai "reuse/recycle" kai
evangelinux
09-25-2004, 07:33 PM
Funny you should mention that. I've got two hubs, but thinking about a switch. My environment's isn't so critical, but I'm curious as to whether a switch is really a better deal than a hub? I've been told that's true - hubs drop UDP packets if I recall. I just didn't experience problems when I had NFS running - though that was a brief run.
I know Linux can be set up as a router, but have again been told that hardware routers are ultimately better solutions. If you can get that router working, we'd surely accept it. That would help us with connecting the whole LAN to the Net.
banzaikai
09-26-2004, 07:47 AM
Yup, switches are much better, but hubs do fine in a pinch. The lowdown:
HUB:
Just a simpler way of connecting, where all terminations and crossovers are taken care of. When more than a few computers are attached, things get busy, and all those requests are sent at the same time (collision). This is dealt with by telling the NIC to reschedule a random interval before resending the packet.
SWITCH:
A smarter hub, it has everything that the hub has, but also has some "smarts" that helps it avoid collisions and process things faster. It can "switch" between machines to allow connecting while telling the others to wait (different from a collision, but the system doesn't have the dropped packets as much).
ROUTER:
Really smart, in that it can actually pick and put packets (route) exactly to who requested or is waiting for reply. Typical home routers have basic functions, but the big boys running the backbones (we've got a couple of Cisco 2600s where I work - awesome!) have configuration features that'll make your forehead bleed just thinking about them all. IIRC, there was a series of guides put out by "RouterGod", where they parody celebrities (Gary Coleman configures priority queueing). Link: http://www.sabertech.net/routergod/ - scroll down to "Celebrity Interviews".
Anyway, we've had our Linksys wireless router running with three wired computers, one 3-port print server, and two laptops simultaneously, with no apparent slowdown on any one of the computers. Gotta love broadband...
banzai "pick a peck of packets" kai
evangelinux
09-26-2004, 06:52 PM
I did take an MCSE course a couple years back, but we didn't learn much about the hardware. The scholl turned out to be a scam in the end, shutting down in several states - left lots of folks in the lurch. Anyway, I never got to certify, and eventaully began my ministry. Meanwhile I turned to SUSE for our ministry's OS.
I had used Red Hat & Mandrake up to the time of my class, and got sold on SUSE when the MCSE instructor started tinkering with it on breaks. I've used Linux more as a desktop, so when people ask if it's ready, or tell me it's not, I'm dumbfounded.
Now I'm starting to solidify my admin skills. It's mostly a matter of using the things you read in the books. I have the knowledge, just not the experience. Now I have the opportunity to get that too.
Our ministry has something like 19 computers, of which 9 or 10 actually work. I'm working on networking these together in a pure GNU/Linux network. They may wind up with Morphix, rather than SUSE. We'll see.
blackbelt_jones
09-26-2004, 10:02 PM
if you can't afford a router, you might want to try a newer version of SuSE. I just got a DSL connection and I'm finding that most of the new distros are extemely DSL friendly-- although with some ignorant companies you may need Windows or a MAC to get the account started.
The latest version of Fedora and Red Hat Enterprise Linux (I tried Centos, an RHEL clone) both automatically configured my DSL connection upon installation using DCHP, without me doing a single thing. I just booted-- and I was online! :cool: So did Kanotix (a new Debian-based distro, which I love) when I booted it as a live CD-- although when I installed it to the hard drive, it required a simple set up (username and password). So far the distros that I have had no problem with are those mentioned above, and Knoppix. (i'm using a Westell Modem.)
Of course, you don't want to buy a new set of SuSE disks without knowing whether it's going to work... so here's a stroke of good luck. It just so happens that I'm downloading the one disk personal version of SuSE 9.1 at this very moment! I'll have the CD in approximately 27 minutes and 49 seconds, according to the download manager, so in about an hour I ought to be able to tell you something that may be helpful.
Indeed, if you have any friends with a broadband connection, you might want to get a copy of the one-disk personal SuSE, or the Live CD. I have a copy of SuSE 9 pro, and if it works on the connection, I might try installing the packages. I don't know if I could get YAST to work, but I could probably install some of the individual rpms at the command line. Anything if it'll save a few bucks!
Right now it's exactly ten o clock. Watch this space for more developments.
blackbelt_jones
09-26-2004, 11:08 PM
:(
Alas, SusE 9.1 did not succeed in configuring my DSL connection. So there it is.
blackbelt_jones
09-27-2004, 12:45 AM
Another distro that does seem to work automatically with my DSL connection is Debian Sarge. I just installed it via the Debian Installer disk. Now, THIS is cool!
evangelinux
09-27-2004, 06:59 AM
I'm very surprised the SUSE 9.1 didn't configure for you. All you do in SUSE 8.0 is start Yast, go to DSL, enter the info, and you're golden! Haven't tried 9.1 yet.
I'm just tinkering with Morphix - and love it so far. Haven't had time to try the DSL with it yet.
Don
blackbelt_jones
09-27-2004, 08:07 PM
No doubt I've been spoiled by these fancy-pants distros that autoconfigure on boot. When it didn't happen, I had no idea what to do. Thanks for the feedback; I'll be sure to try it again.
Have fun with Morphix! The best part about broadband for me is the ability to download nearly every flavor of Linux at will. Last night I tried the new Debian installer-disk, and finally got Debian working on all cylanders with Sarge. I've been trying to accomplish that for a long, long, time! I used to try to install Woody, and I could never get the sound card configured with the old 2.20 kernel. Tried to compile a new kernel, but that didn't work. There were things I could have done, alas, but I didn't know about them at the time. WELL NOW I GOT MY DEBIAN, I GOT MY SOUNDCARD, AND I GOT A 2.6.8.1 kernel. Persistence pays off. Good thing, too, cause when it comes to learning this stuff, persistence is my only advantage.
One great thing about the installer disk is that with a network install you are automatically tied with apt-get to something like 14 thousand compressed software packages, ready to be installed at any time. For me, this may turn out to be the ultimate Linux system.
PastorAsh
12-05-2004, 06:14 AM
I have experienced the same problem in Suse 9.1, but with more than just PPPoE settings. For some reason I also have to go into YAST every time I boot up to change my keyboard settings. It seems that certain settings are saved by YAST, and others are not. Any ideas what could cause this? It has gotten to a point where tonight when I went to change the keyboard settings YAST pops up the window for the settings, but then immediately closes it without changing them. I'm getting used to using different keys for my characters, but it's still a little concerning - not to mention frustrating to type.
evangelinux
12-06-2004, 12:24 AM
Well, I've just migrated from SUSE 8.0 to SUSE 9.2, which has given me no issues. I would like to ask if you have run Yast On-Line Update lately. It could help solve the problem. I have seen some similar keyboard issues on the SUSE e-mail lists - but mostly pertaining to British users. If I were you, I would:
[list=1]
Run YOU - update your system
Check Yast documentation
Post this message in a new thread
[/list=1]
Posting in a new thread will ensure that more people can see the problem - as it is now, it is buried in an unrelated thread - someone with the solution to your problem won't be looking here for keyboard issues.
I've not had any keyboard issues before myself, so am not quite sure how to help you. You should also view /var/log/messages (can be done from within Yast) to see how SUSE is setting up your keyboard - or whether there might be errors at boot-time.
Peace,
DCP
justlinux.com
Copyright 2007 Jupitermedia Corporation All Rights Reserved.