it still does not work trying to access the ip.
it says unknown host

looks like it is trying to connect but, it does not.

Also with Firewall switched off ?

Is that the best subnet you have chosen to use... 255.255.224.0? Would 255.255.255.0 work better? You seem to know what you're on about so no offence meant if you are correct. I'm just going off the way my XP and SuSE 9.1 are configured to work with my Router.

That said, if you can ping the router and it's resolving names, I can't understand why it not browsing for you. Can you pick up email?

Looking at the beginning of the post, you say you have a Router so you shouldn't need to fill out the DSL settings, just give the NIC an IP address, a Default Gateway and at least one DNS address. As you say, the DSL asks for a userID and Password, this should be inside the Router (i'm sure you know this, sorry), so perhaps you need to get rid of the DSL settings incase they are taking presedence over the NIC from the browser. Maybe ping looks to the NIC first and that's why they are resolving...?

Just some thoughts. I'm really new to Linux but have dabbled in Networking. - Hope you get it sorted.

yes the firewall is turned off.
my ISP gave me the 255.255.224.0 address.
I will go try 255.255.255.0

If I can not get this working maybe it is the network card is not right for this distro? I used it with red hat 9.0 a few months ago and it connected fine.

I got the drivers for the network card but, I do not know how to install them. forgive me for I am a newbie in need.

I don't want to cause you unnecessary work mate. Like I said, I'm just comparing your setup to mine. Obviously if you DO change the subnet mask, you'll have to make sure it's the same on the router too. And if you change it on the router, you'll have to make sure the XP machine is the same or that will probably stop working.

What is your routers subnet mask set to out of interest...?

By the way, I am a probably a newer newbie than you mate. Only got Linux properly installed on my PC yesterday!!!!!

Hi,


Can anyone help. I have a conexant hsf internal modem; and this is the connection log.
suse 9.0 2.4.21 installed.



SuSE Meta pppd (smpppd-ifcfg), Version 1.06 on linux.
Status is: disconnected
trying to connect to smpppd
connect to smpppd
Status is: disconnected
Status is: connecting
pppd[0]: Plugin passwordfd.so loaded.
pppd[0]: --> WvDial: Internet dialer version 1.42
pppd[0]: --> Initializing modem.
pppd[0]: --> Sending: ATZ
pppd[0]: ATZ
pppd[0]: OK
pppd[0]: --> Sending: AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
pppd[0]: AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
pppd[0]: OK
pppd[0]: --> Sending: ATM1
pppd[0]: ATM1
pppd[0]: OK
pppd[0]: --> Modem initialized.
pppd[0]: --> Sending: ATDT6989701
pppd[0]: --> Waiting for carrier.
pppd[0]: ATDT6989701
pppd[0]: CONNECT 115200
pppd[0]: --> Carrier detected. Chatmode finished.
pppd[0]: Serial connection established.
pppd[0]: Using interface ppp0
pppd[0]: Connect: ppp0 <--> /dev/ttyS0
pppd[0]: Remote message: Authentication failure
pppd[0]: PAP authentication failed
Authentication error. Maybe bad account or password.
pppd[0]: Connection terminated.
pppd[0]: Hangup (SIGHUP)
Status is: disconnected
pppd[0] died: Authentication error (exit code 19)

Burzenlite,

please open a new thread. Your problem is not related to the original posting.
Thanx.

As you can see in the log: Connection terminated due to an authentification problem.
Check your username and password.

Hallo EazyMoney,

can you please als try following. It might be that there is a problem wit IP V 6 (default turned on in SuSE 9.1)

Take a look on your /etc/modprobe.conf

Look there for
alias net-pf-10 ipv6

Add below this line
install ipv6 /bin/true

So it should look like:

alias net-pf-10 ipv6
install ipv6 /bin/true


Reboot and test again.

You might have this problem

Oversimplified Example:
1) PC contacts -> DHCP Sees & Registers Client -> Client IP -> Linux OS -> Linux Holds IP
2) Reboot
3) Login to Windows
4) PC contacts -> DHCP Doesn't realize you;ve rebooted -> No IP supplied -> Windows Gets Confused.

In-Depth Example:
What happens here is that the SuSe has an option that is called something like "Unregister IP on shutdown". Whatever it is called (which I'll look up soon), is that the DHCP will hold your computer IP registered for an IP until it expires. In order to know if your IP is in use or not, the PC will tell the DHCP that the computer has shutdown. Normally, this wouldn't matter if you did or not, because the Windows would try to grab the previous IP. However, the DHCP doesn't know the computer has turned off and switch OS's, because the Linux did not let it know, and the Windows tries to get the same assigned IP. In general it will fail and get confused. (I accidentally took down a T1 network with this problem..)

Without going into more details I will look up that option and let you know what it is.

I DO NOT RUN SUSE (in technical aspects..) I RUN SUN JAVA DESKTOP, which is uses the SuSe 9.1 as its core and then mods it from there...
What this means is that I may not be able to give you the exact info you need but it SHOULD be something similar to this.

Step 1) "xterm -e yast2" or from a shell, or terminal, "yast2"
Step 2)you do remember your root password?
Step 3) Select System Tab then select Editor (/etc/sysconfig) {System->Editor for /etc/sysconfig}
Note) If you'll notice, you can go to /etc/sysconfig and do this manually, but that can be unsafe if you are not familiar with this.
Step 4) find DHCLIENT_RELEASE_BEFORE_QUIT, which should be located under Network->Dhcp.
Step 5) Make sure that the value is set to YES (or true, if choices are boolean)
Step 6) SAVE
Step 7) reboot to be sure.
Step 9) While this will probably fix your problem, I had previously touched the fact that the IP has been leased. So, you may have to wait for it to tweak it if this is the case. Nevertheless, since you did this on your Linux machine and rebooted, it should unregister that IP, so there should be no problem.

WARNING:
If you came across this problem and began statically changing/forcing IP addresses to get around the problem you can crash the network as it thinks you have XXX machineds all running and in use and nobody will be able to get a valid IP and connect.

as a note from before, I said .bashrc & .bash_profile, but those were files located in /home/username/ which was my mistake. BUT i was on target.

Inside the etc, in the bashrc file, you can find where the aliases are added.

More specifically, in my Linux, It is located in /etc/bash.bashrc/

HOWEVER, .bashrc found in the /home/username directory will allow for user-specific (& user-only) aliases. The aliases configured in the /etc/ bash file is global, while the .bashrc is local to the user.

This IS the solution i belive your looking for.


TO MODIFY
You must modify this file as root.
In general, you shoukd not touch anything that is already there, for now.

My recommendation is scroll to the bottom of the page and add the following line: Then on a line below add aliases of your choice in this format:

alias =aliascommand

for example, try: When you loginto a shell it will then run that an make that file open with vim.

Some allow for seperate local files and i would further recommend that
(ie: create "/etc/bash.bashrc.local" and insert all the stuff you wish, instead of adding to "/etc/bash.bashrc") But this may not work...depending on your shell and some other stuff.