A year ago SBC Yahoo! upgraded their DSL service. I had to redo my Linux partitions, and since then I have been unable to connect to the Internet with SUSE Linux. I called SBC and all I got was an Indian guy who said, "We don't support Linux," and hung up. I contacted SUSE and got no response. Then I was using SUSE 9.1 Pro, but I have since tried it with both SUSE 9.0 Home and 9.3 Pro. I entered the same info I had always entered before. Nothing worked. Prior to the upgrade, both 9.0 and 9.1 worked. I installed SUSE 9.1 Pro on my brother's computer, and it also would not connect to the Internet. I just downloaded SUSE 10 Pro and installed it twice. Both times it would not connect to the Internet with SBC Yahoo. I have successfully connected to SBC Yahoo! with Mandrake, Puppy Linux, Debian, StartCom, Red Hat, Fedora, Slax, Linspire, Kanotix, Knoppix, LiveBSD, Ubuntu, Beatrix, and any one of nearly 40 distros, usually almost effortlessly--sometomes with no effort at all. I've always thought SUSE was a great distro. I don't want to dump it for Fedora or Debian (not that there's anything wrong with those--I never had ANYTHING go wrong with StartCom), because I'm used to it. I've used it for three years. But if I can't make it connect to the Internet, then I'll have to. Can anyone help, since SUSE hasn't responded?

Ninurta

I run SuSE with SBC yahoo DSL - no problems.

What do and show you?

Actually, a description of your setup would be most helpful. Are you going directly though a DSL modem or are you behind a router firewall? Are you running PPPoE and/or a firewall on the SuSE machine?

Im running 9.3 on this computer with SBC DSL just fine. I've also run it as a gateway running PPPoE with no issues either.

I am going directly through a DSL modem. There is no router or hardware

firewall. It is an Efficient Networks SpeedStream 5100. I am running

PPPoE and there is a standard SUSE firewall running in Linux, set up

for a default single-user PC--I also cannot connect to SUSE for

updates. The Ethernet card is a Realtek RTL8139 Family PCI Fast

Ethernet Adapter, configured with DHCP. There is also an NVIDIA nForce

MCP Networking Adapter on the motherboard; since I'm not using a

router, I cannot use more than one ethernet card at a time. SBC says

the nForce adapter is not working, but SUSE automatically configures it

with DHCP. Kinternet is configured to run on boot-up, but doesn't. The

motherboard is an ASUS A7266-VM with an Athlon XP 1800 and 512MB RAM,

80GB hard drive (the SUSE partition is 17GB with a 972MBb swap). There

is no setup with the primary and secondary DNS, since SBC wouldn't give

me that information. I did get it from Windows, but it still didn't

work.

Entering /sbin/ifconfig cat/etc.resolv.conf at a terminal, I get:

sage:
ifconfig [-a] [-i] [-v] [-s] <interface> [[<AF>] <address>]


[add <address>[/<prefixlen>]]
[del <address>[/<prefixlen>]]


[[-]broadcast [<address>]] [[-]pointopoint [<address>]]
[netmask

<address>] [dstaddr <address>] [tunnel <address>]
[outfill <NN>]

[keepalive <NN>]
[hw <HW> <address>] [metric <NN>] [mtu <NN>]


[[-]trailers] [[-]arp] [[-]allmulti]
[multicast] [[-]promisc]


[mem_start <NN>] [io_addr <NN>] [irq <NN>] [media <type>]


[txqueuelen <NN>]
[[-]dynamic]
[up|down] ...

<HW>=Hardware

Type.
List of possible hardware types:
loop (Local Loopback) slip

(Serial Line IP) cslip (VJ Serial Line IP)
slip6 (6-bit Serial Line

IP) cslip6 (VJ 6-bit Serial Line IP) adaptive (Adaptive Serial Line

IP)
strip (Metricom Starmode IP) ether (Ethernet) tr (16/4 Mbps

Token Ring)
tr (16/4 Mbps Token Ring (New)) ax25 (AMPR AX.25)

netrom (AMPR NET/ROM)
tunnel (IPIP Tunnel) ppp (Point-to-Point

Protocol) arcnet (ARCnet)
dlci (Frame Relay DLCI) frad (Frame Relay

Access Device) sit (IPv6-in-IPv4)
fddi (Fiber Distributed Data

Interface) hippi (HIPPI) irda (IrLAP)
x25 (generic X.25)


<AF>=Address family. Default: inet
List of possible address

families:
unix (UNIX Domain) inet (DARPA Internet) inet6 (IPv6)


ax25 (AMPR AX.25) netrom (AMPR NET/ROM) ipx (Novell IPX)
ddp

(Appletalk DDP) x25 (CCITT X.25)

Those are two different commands. Check my post again. You will need to enter them separately.

The simplest thing is to make sure your interfaces come up at boot time and make sure you put in the full username (user@sbcglobal.net) in the PPPoE login. Can you confirm this?

Can you ping around anything? Ping 206.141.192.60. Try accessing everything again after typing "rcSuSEfirewall stop".

Just a few suggestions to try.

Here are the results of /sbin/ifcongfig:

eth0 Link encap:Ethernet HWaddr 00:E0:18:BB:8B:2B
inet6 addr: fe80::2e0:18ff:febb:8b2b/64 Scope:Link
UP BROADCAST NOTRAILERS MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:10 Base address:0xe000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:28 errors:0 dropped:0 overruns:0 frame:0
TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1840 (1.7 Kb) TX bytes:1840 (1.7 Kb)

I ran cat/etc/resolv.conf several times. It did not return anything.

The simplest thing is to make sure your interfaces come up at boot time and make sure you put in the full username (user@sbcglobal.net) in the PPPoE login. Can you confirm this?

Kinternet did not come up at boot, but I checked the configuration and the full username, including @sbcglobal.net, was correct.

Pinging 141.192.60 returned the message "Network not found."

rcSuSEfirewall stop returned the message "Command rcSuSEfirewall not found."

FYI, the 2 commands are are having issues with are actually:

rcSuSEfirewall2 stop
**and**
cat /etc/resolve.conf

It looks as though you are missing IP addresses for eth0 (unless you actually use IPv6) and you also don't have a ppp0 interface for PPPoE. The eth0 will become the ppp0 interface once you setup PPPoE.

There is no IP bound to your NIC. As ghight mentioned, you have some additional settings to take care of.

FWIW, I believe my SBC yahoo DSL works a little differently than both of yours. In my case, the modem also happens to be a NAT device and a DHCP server (for private network), and it runs PPPoE. Nice and easy.

You appear to have missed the second sentence in my original post. "I called SBC and all I got was an Indian guy who said, "We don't support Linux," and hung up." I specifically asked the Indian guy for my primary and secondary DNS, which he refused to give. I can't change the settings because SBC refuses to give me the correct information to change them with. I tried getting it from Windows, but nothing worked. PPPoE is set up, and YAST says Kinternet is set to run on boot. Comman rcSUSEfirewal2 stop is not found. cat etc/resolv.conf still returns nothing. The SBC software performance in Windows is often pretty flaky too. I believe the problem is that SUSE is not detecting the DSL modem, but that doesn't explain why some 45 other distros all connect just fine--even without any configuration! I must say, that those Linux versions that do connect run great. I've had this problem for a year, with three different versions of SUSE: I can't put information into the settings that I can't get anywhere. That's what I've been saying all along. I have to have the information before I can put it in, and SBC won't give it to me, because they don't support Linux.

I caught it the first time. When tech support asks me what I'm running, I don't tell them Linux. I say, "I need the nameserver info please." Saying "We don't support Linux" is obviously a copout.

Anyway, you don't need nameserver info to obtain an IP address. Nameservers have only one purpose - name resolution.

Claro que si. It would have been helpful to have known that earlier.

Go to the network address setup in yast. Click the button "Host Name and Server". Make sure you enter sbcglobal.net in the domain. Suse defaults to something like "site". I couldn't connect to sbc until I made this change.

Good luck.

I did think of one more thing. I called SBC Support about a connection problem in Windows and they told me the NVIDIA nForce ethernet card on my motherboard wasn't working, so they had me connect the DSL modem to the Realtek card instead (and of course, without a router, I can only use one ethernet card at a time). So I disconnected the Realtek card and reconnected the NVIDIA card, and started Windows. Suddenly my internet connection was working twice as well. So I fired up Suse. It didn't appear that Kinternet was running, but I figured, what the heck, and opened Firefox. It immediately went to Novell. I tried Yahoo: it worked. My other posts were written in Firefox in Windows XP. I"m now writing this from Firefox running inside SUSE Linux. So it now appears that there was nothing wrong with my Linux internet configuration. What happened was that SBC Yahoo wrongly told me that my NVIDIA card wasn't working, and the Realtek card isn't working with SUSE. So the problem is really with the Realtek card. And that's TWO STRIKES against SBC Yahoo.

Thanks a lot.

Glad it's working, but I'm just going to pass along something that will help you next time you write in. Again, it's a helpful hint and not a gripe, but please make sure of your typing. It would be helpful to use tab completion to make sure you get the correct command.

Several of the commands we had you look at were mistyped several times which give us very little info to go by.

Again, glad you are up and running.

Hint 2: If you aren't familiar with rcSuSEfirewall2 in Suse, please take a few minutes to learn it if you aren't going to use a third party router firewall.

I went through this a year ago and figured our to connect by looking at the Mac configuration directions. The connection worked but the registration web site required MS IE6 or it wouldn't register me with the SBC servers. I went with Comcast. It had similar problems but no PPPoe configuration problems. They claim they don't support Linux either -- such idiots. Crossover office or wine can install IE6 and run it. That or borrowing a laptop with MS can also get you started. You never need MS again unless you run into more idiots like FEMA that only allows disaster registration with IE.