DebianThis forum is for the discussion of Debian Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
i managed to connect to the internet using internal modem on slackware
we
however incase of debian im able to dial out and the modem is logging onto the ISP but im unable to open any webpage
Do you have any other network interfaces configured on the machine (eg. an ethernet port?). If so, the modem must be set to configure itself (ppp0 usually) to be the default route and gateway on connection, otherwise packets that are for "outside" will go to the ethernet card (eg. eth0). Alternatively you can unconfigure any eth device you don't need (ie. if you have no LAN).
What does "route -n" produce when you're connected?
OK, but I wanted to see the (whole) output of the commands so that I could see whether the routes are perhaps directing non-local packets to another network interface rather than ppp0. Can you post the two commands' output please?
i think ur guess is right when i try to ping an ip it says 192.168.1.2 is unable to ping. 192.168.1.2 is the static ip of the eth card that im using
OK, so that probably tells us it still thinks "you" are 192.168.1.2, so you haven't completely shutdown the eth1 interface - the ping packets are trying to go out via eth1.
This looks odd (and explains the ping problem). The default route is still using the 192.168.1.1 as a gateway, even though ppp0 is up. You need to completely shut down eth1 (maybe) and override the default route with ppp0 - there should be an option somewhere in your dialer to make pppd set the default route when it connects.
Incidentally, you might be able to ping 61.0.6.14 in this state as that should route directly to your ISP host. But only that oneaddress will work until you set the default route!
Quote:
here is the output for slackware as well
root@ankush:~# netstat -r
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
61.0.6.14 * 255.255.255.255 UH 0 0 0 ppp0
loopback * 255.0.0.0 U 0 0 0 lo
default * 0.0.0.0 U 0 0 0 ppp0
This looks more like it. I would expect the gateway for the default route to be shown as 61.0.6.14, but that may be the output of netstat (I'm used to using route -n). The default route is certainly ppp0, which is what you need.
You need to look into getting pppd to set the default route.
Is there a configuration utility in Debian Etch to configure a modem as in Slackware? I remember during setup Slackware asked for the location of the modem and would create the necessary device for this. This does not appear to be the case in Debian, as I have tried to configure wvdial with an ISA hardware modem that is set for COM2. Do I need to run setserial for this, as I believe that this should already be in place? If so, what parameters do I need to configure for setserial? Thanks.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.