Hi list, Please enlighten me if you have any experience with using the Tata Indicom USB Modem under the Plug 2 Surf scheme. I have recently taken their subscription and facing problems using it with Kubuntu 7.10 It works fine in windoze, but fails to get any data transfer in Linux. I tried connecting using wvdial and also using KPPP.
The following is a copy of what i get at the terminal on running wvdialconf:
$ sudo wvdialconf /etc/wvdial.conf Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. Modem Port Scan<*1>: S1 S2 S3 WvModem<*1>: Cannot get information for serial port. ttyACM0<*1>: ATQ0 V1 E1 -- OK ttyACM0<*1>: ATQ0 V1 E1 Z -- OK ttyACM0<*1>: ATQ0 V1 E1 S0=0 -- OK ttyACM0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK ttyACM0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK ttyACM0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK ttyACM0<*1>: Modem Identifier: ATI -- ERROR ttyACM0<*1>: Speed 4800: AT -- OK ttyACM0<*1>: Speed 9600: AT -- OK ttyACM0<*1>: Speed 19200: AT -- OK ttyACM0<*1>: Speed 38400: AT -- OK ttyACM0<*1>: Speed 57600: AT -- OK ttyACM0<*1>: Speed 115200: AT -- OK ttyACM0<*1>: Speed 230400: AT -- OK ttyACM0<*1>: Speed 460800: AT -- OK ttyACM0<*1>: Max speed is 460800; that should be safe. ttyACM0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
Found an USB modem on /dev/ttyACM0. Modem configuration written to /etc/wvdial.conf. ttyACM0<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
//////// It appears that it successfully detected a USB modem and created a wvdial.conf file accordingly.
But on trying to dial using "sudo wvdial", i get the following on the terminal:
kamal@kMax:~$ sudo wvdial WvDial<*1>: WvDial: Internet dialer version 1.56 WvModem<*1>: Cannot get information for serial port. WvDial<*1>: Initializing modem. WvDial<*1>: Sending: ATZ WvDial Modem<*1>: ATZ WvDial Modem<*1>: OK WvDial<*1>: Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 WvDial Modem<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 WvDial Modem<*1>: OK WvDial<*1>: Modem initialized. WvDial<*1>: Sending: ATDT#777 WvDial<*1>: Waiting for carrier. WvDial Modem<*1>: ATDT#777 WvDial Modem<*1>: CONNECT WvDial<*1>: Carrier detected. Waiting for prompt. WvDial<Err>: Connected, but carrier signal lost! Retrying... WvDial<*1>: Sending: ATDT#777 WvDial<*1>: Waiting for carrier. WvDial Modem<*1>: ATDT#777 WvDial Modem<*1>: CONNECT WvDial<*1>: Carrier detected. Waiting for prompt.
... and so on and so forth.. it keeps repeating connection attempts and gives the same error "WvDial<Err>: Connected, but carrier signal lost! Retrying..."
I have used wvdial for MTNL Garuda's USB modem on the same installation and it was working fine back then. Also, there was an existent wvdial.conf file with those old settings for MTNL Garuda connection until i executed "wvdialconf" again for the tata indicom USB modem. [* wvdial gave the same problem even with Ubuntu 7.04 installed on the same machine.]
While when i tried connecting with KPPP on Kubuntu 7.10, it did succeed in connecting, that is, it showed me that its connected and the USB modem's indicator too indicated a connection. But i still could not surf the net (or ping any websites)
Am i missing out something while configuring the connection. Could this be an issue with the DNS? The same modem is working fine for windoze on the same machine.
Any help or your experiences in this regard are greatly appreciated. Thanks.
On Tuesday 01 Jul 2008, km wrote:
Hi list, Please enlighten me if you have any experience with using the Tata Indicom USB Modem under the Plug 2 Surf scheme. I have recently taken their subscription and facing problems using it with Kubuntu 7.10 It works fine in windoze, but fails to get any data transfer in Linux. I tried connecting using wvdial and also using KPPP.
The following is my </etc/wvdial.conf> Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 Modem Type = USB Modem Baud = 460800 New PPPD = yes Modem = /dev/ttyACM0 ISDN = 0 Phone = #777 Username = internet Password = internet Stupid Mode = yes </etc/wvdial.conf>
The last line "stupid more" is important. read the man page for details.
HTH, -- Arun Khan
On Tue, Jul 1, 2008 at 9:40 AM, km km@eficacy.com wrote:
Hi list, Please enlighten me if you have any experience with using the Tata Indicom USB Modem under the Plug 2 Surf scheme. I have recently taken their subscription and facing problems using it with Kubuntu 7.10 It works fine in windoze, but fails to get any data transfer in Linux. I tried connecting using wvdial and also using KPPP.
<snip>
WvDial<*1>: Sending: ATDT#777 WvDial<*1>: Waiting for carrier. WvDial Modem<*1>: ATDT#777 WvDial Modem<*1>: CONNECT WvDial<*1>: Carrier detected. Waiting for prompt.
Put following line in /etc/wvdial.conf Stupid mode = 1
... and so on and so forth.. it keeps repeating connection attempts and gives the same error "WvDial<Err>: Connected, but carrier signal lost! Retrying..."
I have used wvdial for MTNL Garuda's USB modem on the same installation and it was working fine back then. Also, there was an existent wvdial.conf file with those old settings for MTNL Garuda connection until i executed "wvdialconf" again for the tata indicom USB modem. [* wvdial gave the same problem even with Ubuntu 7.04 installed on the same machine.]
While when i tried connecting with KPPP on Kubuntu 7.10, it did succeed in connecting, that is, it showed me that its connected and the USB modem's indicator too indicated a connection. But i still could not surf the net (or ping any websites)
Am i missing out something while configuring the connection. Could this be an issue with the DNS? The same modem is working fine for windoze on the same machine.
check if you can ping them! ping 202.54.15.30 etc.. also if you might have eth0 or other interface on, check the default route # route -n
Regards, Karunakar
Disable the "Carrier Check" option and it should work fine.
Regards, Rahul
km km@eficacy.com 07/01/08 9:40 AM >>>
Hi list, Please enlighten me if you have any experience with using the Tata Indicom USB Modem under the Plug 2 Surf scheme. I have recently taken their subscription and facing problems using it with Kubuntu 7.10 It works fine in windoze, but fails to get any data transfer in Linux. I tried connecting using wvdial and also using KPPP.
The following is a copy of what i get at the terminal on running wvdialconf:
$ sudo wvdialconf /etc/wvdial.conf Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. Modem Port Scan<*1>: S1 S2 S3 WvModem<*1>: Cannot get information for serial port. ttyACM0<*1>: ATQ0 V1 E1 -- OK ttyACM0<*1>: ATQ0 V1 E1 Z -- OK ttyACM0<*1>: ATQ0 V1 E1 S0=0 -- OK ttyACM0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK ttyACM0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK ttyACM0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK ttyACM0<*1>: Modem Identifier: ATI -- ERROR ttyACM0<*1>: Speed 4800: AT -- OK ttyACM0<*1>: Speed 9600: AT -- OK ttyACM0<*1>: Speed 19200: AT -- OK ttyACM0<*1>: Speed 38400: AT -- OK ttyACM0<*1>: Speed 57600: AT -- OK ttyACM0<*1>: Speed 115200: AT -- OK ttyACM0<*1>: Speed 230400: AT -- OK ttyACM0<*1>: Speed 460800: AT -- OK ttyACM0<*1>: Max speed is 460800; that should be safe. ttyACM0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
Found an USB modem on /dev/ttyACM0. Modem configuration written to /etc/wvdial.conf. ttyACM0<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
//////// It appears that it successfully detected a USB modem and created a wvdial.conf file accordingly.
But on trying to dial using "sudo wvdial", i get the following on the terminal:
kamal@kMax:~$ sudo wvdial WvDial<*1>: WvDial: Internet dialer version 1.56 WvModem<*1>: Cannot get information for serial port. WvDial<*1>: Initializing modem. WvDial<*1>: Sending: ATZ WvDial Modem<*1>: ATZ WvDial Modem<*1>: OK WvDial<*1>: Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 WvDial Modem<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 WvDial Modem<*1>: OK WvDial<*1>: Modem initialized. WvDial<*1>: Sending: ATDT#777 WvDial<*1>: Waiting for carrier. WvDial Modem<*1>: ATDT#777 WvDial Modem<*1>: CONNECT WvDial<*1>: Carrier detected. Waiting for prompt. WvDial<Err>: Connected, but carrier signal lost! Retrying... WvDial<*1>: Sending: ATDT#777 WvDial<*1>: Waiting for carrier. WvDial Modem<*1>: ATDT#777 WvDial Modem<*1>: CONNECT WvDial<*1>: Carrier detected. Waiting for prompt.
... and so on and so forth.. it keeps repeating connection attempts and gives the same error "WvDial<Err>: Connected, but carrier signal lost! Retrying..."
I have used wvdial for MTNL Garuda's USB modem on the same installation and it was working fine back then. Also, there was an existent wvdial.conf file with those old settings for MTNL Garuda connection until i executed "wvdialconf" again for the tata indicom USB modem. [* wvdial gave the same problem even with Ubuntu 7.04 installed on the same machine.]
While when i tried connecting with KPPP on Kubuntu 7.10, it did succeed in connecting, that is, it showed me that its connected and the USB modem's indicator too indicated a connection. But i still could not surf the net (or ping any websites)
Am i missing out something while configuring the connection. Could this be an issue with the DNS? The same modem is working fine for windoze on the same machine.
Any help or your experiences in this regard are greatly appreciated. Thanks.
Hello,
On Tue, Jul 1, 2008 at 4:35 AM, G Karunakar indlinux@gmail.com wrote:
On Tue, Jul 1, 2008 at 9:40 AM, km km@eficacy.com wrote:
Hi list, Please enlighten me if you have any experience with using the Tata Indicom USB Modem under the Plug 2 Surf scheme. I have recently taken their subscription and facing problems using it with Kubuntu 7.10 It works fine in windoze, but fails to get any data transfer in Linux. I tried connecting using wvdial and also using KPPP.
<snip>
Put following line in /etc/wvdial.conf Stupid mode = 1
<snip>
Am i missing out something while configuring the connection. Could this be an issue with the DNS? The same modem is working fine for windoze on the same machine.
check if you can ping them! ping 202.54.15.30 etc.. also if you might have eth0 or other interface on, check the default route # route -n
Regards, Karunakar -- http://mm.glug-bom.org/mailman/listinfo/linuxers
Thank you all; that was a great deal of help. I added the "Stupid Mode = yes" line in my /etc/wvdial.conf and that made wvdial to successfully get me connected, however that just took me one block ahead of where i was. It still isnt resolving any URLs. Firefox shows me the "Looking up...." msg for quite a looooooong time and then gives up eventually.
And if i got it right, i guess "disabling Carrier Check" is the same as adding the "stupid mode = yes" string in the conf file or is it something else?
Also, I tried using the OpenDNS service, by using their DNS server IP addresses, but it still changes back to another set of DNS ips the moment i disconnect and redial, may be because we are not assigned any static IPs by Tata Indicom(?)
Please help with this. Thanks a ton in advance.
PS: Please confirm if the list received multiple copies (7) of my mail in the beginning of this thread. I regret any inconvenience to you because of that if the list did receive all those mails shown to me only in my web-mail interface. I had no idea about them when i sent out the mail using Mozilla Thunderbird.
On Tue Jul 01, 2008 at 09:40:50PM +0100, km wrote:
Also, I tried using the OpenDNS service, by using their DNS server IP addresses, but it still changes back to another set of DNS ips the moment i disconnect and redial, may be because we are not assigned any static IPs by Tata Indicom(?)
Does DNS work after using OpenDNS? If yes, then you can add OpenDNS IP's to the required configuration file. I am not sure as to which is that. Maybe you can try the solutions enlisted here - http://forums.opendns.com/comments.php?DiscussionID=235
On Wednesday 02 Jul 2008, Mehul Ved wrote:
On Tue Jul 01, 2008 at 09:40:50PM +0100, km wrote:
Also, I tried using the OpenDNS service, by using their DNS server IP addresses, but it still changes back to another set of DNS ips the moment i disconnect and redial, may be because we are not assigned any static IPs by Tata Indicom(?)
Does DNS work after using OpenDNS? If yes, then you can add OpenDNS IP's to the required configuration file. I am not sure as to which is that. Maybe you can try the solutions enlisted here - http://forums.opendns.com/comments.php?DiscussionID=235
km needs to add the opendns entries *after* the connection is established. It is being overwritten by DNS supplied by ISP but I don't think this is root cause of his problem.
I think km needs to verify his routing table as someone else pointed out earlier. If he has multiple interfaces like eth0 and ppp0, his earlier default route may be interfering even though ppp0 over WLL is established.
km, after the connection is established do a:
# route -n
this will give your routing table entries. If the default route is thru eth0 then you need to delete it (man route).
Alternately, before connecting to Tata, stop your networking (/etc/init.d/<network-script-name>), connect to the ISP, this should give you a workable routing table.
HTH, -- Arun Khan
On Wed Jul 02, 2008 at 09:39:35AM +0530, Arun Khan wrote:
km needs to add the opendns entries *after* the connection is established. It is being overwritten by DNS supplied by ISP but I don't think this is root cause of his problem.
As per that thread, there is an option Auto DNS, setting it off might help, as in the case of one of the people there.Thus, the /etc/resolv.conf file won't be overwritten.
On Wednesday 02 Jul 2008, Mehul Ved wrote:
On Wed Jul 02, 2008 at 09:39:35AM +0530, Arun Khan wrote:
km needs to add the opendns entries *after* the connection is established. It is being overwritten by DNS supplied by ISP but I don't think this is root cause of his problem.
As per that thread, there is an option Auto DNS, setting it off might help, as in the case of one of the people there.Thus, the /etc/resolv.conf file won't be overwritten.
The stock Ubuntu version ignores AutoDNS setting, works in openSUSE though.
-- Arun Khan
On Wednesday 02 Jul 2008, kamal wrote:
Alternately, before connecting to Tata, stop your networking (/etc/init.d/<network-script-name>), connect to the ISP, this should give you a workable routing table.
err.. any sure-shot way to figure out the <network-script-name> if i dont know it? and how do we stop it?
how about "ls /etc/init.d/*net*" ? this should give you the network script name. Execute the file without any arguments and it will show all the options. You will have to do it as "root" user.
Suggest you get familiar with basic Linux sys admin, there are several excellent e-books.
Start here http://www.linuxtopia.org/online_books/linux_for_beginners_index.html
On Wednesday 02 Jul 2008, kamal wrote:
Arun Khan wrote:
On Wednesday 02 Jul 2008, Mehul Ved wrote:
On Wed Jul 02, 2008 at 09:39:35AM +0530, Arun Khan wrote:
km needs to add the opendns entries *after* the connection is established. It is being overwritten by DNS supplied by ISP but I don't think this is root cause of his problem.
As per that thread, there is an option Auto DNS, setting it off might help, as in the case of one of the people there.Thus, the /etc/resolv.conf file won't be overwritten.
The stock Ubuntu version ignores AutoDNS setting, works in openSUSE though.
-- Arun Khan
is there a way it can be worked around in Ubuntu? It worked fine with doze.
I gave you a workaround; you have not reported yet whether it works for you or not.
read my other post, even though there is an option to ignore ISP DNS, the Ubuntu wvdial ignores it in and pops in the DNS servers from the ISP (this has been my experience).
Anyway, given that you have 2 NICs and now a Indicom connection (3 'net connections), you basically have a "def. route" routing problem.
-- Arun Khan
Arun Khan wrote:
On Wednesday 02 Jul 2008, Mehul Ved wrote:
On Tue Jul 01, 2008 at 09:40:50PM +0100, km wrote:
Also, I tried using the OpenDNS service, by using their DNS server IP addresses, but it still changes back to another set of DNS ips the moment i disconnect and redial, may be because we are not assigned any static IPs by Tata Indicom(?)
Does DNS work after using OpenDNS? If yes, then you can add OpenDNS IP's to the required configuration file. I am not sure as to which is that. Maybe you can try the solutions enlisted here - http://forums.opendns.com/comments.php?DiscussionID=235
km needs to add the opendns entries *after* the connection is established. It is being overwritten by DNS supplied by ISP but I don't think this is root cause of his problem.
yes, thats what i had to do in order to use opendns. but as you rightly pointed out, thats not the root issue here. its still not resolving.
I think km needs to verify his routing table as someone else pointed out earlier. If he has multiple interfaces like eth0 and ppp0, his earlier default route may be interfering even though ppp0 over WLL is established.
km, after the connection is established do a:
# route -n
this will give your routing table entries. If the default route is thru eth0 then you need to delete it (man route).
i guess this is what i should give a try, however i have no idea what a routing table is and how it works. but i do have eth0 and eth1 attributed to the 2 NICs jacked in, and used eth0 to access the net for quite sometime before switching to Tata Plug2Surf.
Alternately, before connecting to Tata, stop your networking (/etc/init.d/<network-script-name>), connect to the ISP, this should give you a workable routing table.
err.. any sure-shot way to figure out the <network-script-name> if i dont know it? and how do we stop it?
Thanks a lot for all the help. :)
On Wed, Jul 2, 2008 at 4:19 PM, Arun Khan <> wrote:
Anyway, given that you have 2 NICs and now a Indicom connection (3 'net connections), you basically have a "def. route" routing problem.
I second that. In our excitement to get things working we forget about the existing eth0 that's the default route.
KM, simply run 'sudo route add default ppp0' after your usb modem's ppp0 is up. Once this is confirmed to be the solution, remove or comment the default gateway entry for eth0 in /etc/network/interfaces and reboot your machine.
Yes reboot, not restart networking services.
-- Regards,
Rony. GNU/Linux No Viruses No Spyware Only Freedom.
On Wednesday 02 Jul 2008 19:25, Rony Bill wrote:
On Wed, Jul 2, 2008 at 4:19 PM, Arun Khan <> wrote:
Anyway, given that you have 2 NICs and now a Indicom connection (3 'net connections), you basically have a "def. route" routing problem.
I second that. In our excitement to get things working we forget about the existing eth0 that's the default route.
KM, simply run 'sudo route add default ppp0' after your usb modem's ppp0 is up. Once this is confirmed to be the solution, remove or comment the default gateway entry for eth0 in /etc/network/interfaces and reboot your machine.
Yes reboot, not restart networking services.
route del default gw 192.168.whatever . route add defalut gw <ip of ppp0>
Arun Khan wrote:
On Wednesday 02 Jul 2008, Mehul Ved wrote:
On Wed Jul 02, 2008 at 09:39:35AM +0530, Arun Khan wrote:
km needs to add the opendns entries *after* the connection is established. It is being overwritten by DNS supplied by ISP but I don't think this is root cause of his problem.
As per that thread, there is an option Auto DNS, setting it off might help, as in the case of one of the people there.Thus, the /etc/resolv.conf file won't be overwritten.
The stock Ubuntu version ignores AutoDNS setting, works in openSUSE though.
-- Arun Khan
is there a way it can be worked around in Ubuntu? It worked fine with doze. All i needed to do there was enter the DNS server-ips of opendns mentioned on their website and it worked fine (on the same connection - tata indicom plug2surf).
kamal wrote:
Arun Khan wrote:
On Wednesday 02 Jul 2008, Mehul Ved wrote:
On Wed Jul 02, 2008 at 09:39:35AM +0530, Arun Khan wrote:
km needs to add the opendns entries *after* the connection is established. It is being overwritten by DNS supplied by ISP but I don't think this is root cause of his problem.
As per that thread, there is an option Auto DNS, setting it off might help, as in the case of one of the people there.Thus, the /etc/resolv.conf file won't be overwritten.
The stock Ubuntu version ignores AutoDNS setting, works in openSUSE though.
-- Arun Khan
is there a way it can be worked around in Ubuntu? It worked fine with doze. All i needed to do there was enter the DNS server-ips of opendns mentioned on their website and it worked fine (on the same connection - tata indicom plug2surf).
Could you give us a summary of your network interfaces and how they are connected?
On 7/2/08, jtd jtd@mtnl.net.in wrote:
On Wednesday 02 Jul 2008 19:25, Rony Bill wrote:
On Wed, Jul 2, 2008 at 4:19 PM, Arun Khan <> wrote:
Anyway, given that you have 2 NICs and now a Indicom connection (3 'net connections), you basically have a "def. route" routing problem.
I second that. In our excitement to get things working we forget about the existing eth0 that's the default route.
KM, simply run 'sudo route add default ppp0' after your usb modem's ppp0 is up. Once this is confirmed to be the solution, remove or comment the default gateway entry for eth0 in /etc/network/interfaces and reboot your machine.
Yes reboot, not restart networking services.
route del default gw 192.168.whatever . route add defalut gw <ip of ppp0>
-- Rgds
JTD
Many thanks. I think this is what got me going. However, I am sure I did something wrong with the commands initially and got it all screwed up. :P
AFAIR, after doing a # route del default gw I did not find the /etc/network/interfaces file in place; it just disappeared! (is this expected? could not understand that from the man page on route`.)
However, I had a backup copy (incidentally a much older, cleaner backup :P ) of the interfaces file that i restored. And things seemed workable henceforth.
Although, this seems to be a pretty dirty way of getting around a problem and i am still foxed as to what was a proper systematic approach to solve it. I am reading up on this, and will surely catch up pretty soon.
Apologies for late response. Reasons include trying to figure out things the D-I-Y way, though i wonder how much that worked :P, and of course, work-loads a wee-bit heavier than i could handle. :)
Many thanks again to all who helped. :)
On 7/2/08, Rony gnulinuxist@gmail.com wrote: [...]
Could you give us a summary of your network interfaces and how they are connected?
-- Regards,
Rony.
After everything done and working, route -n gives me the following:
kamal@kMax:~$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 172.23.119.14 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp0
and the contents of interfaces file are as follows; which i guess is really crappy, but still working. any clues on cleaning it up? :P --------- GNU nano 2.0.6 File: /etc/network/interfaces
auto lo iface lo inet loopback address 127.0.0.1 netmask 255.0.0.0
iface dsl-provider inet ppp pre-up /sbin/ifconfig eth0 up # line maintained by pppoeconf provider dsl-provider
auto eth0 iface eth0 inet static address 10.10.80.1 netmask 255.0.0.0 gateway ---------
Address 10.10.80.1 < this is the addr i chose on LAN, which i don't use any more. Is it safe to remove? Also, is it safe to comment out the `provider` line? i am not using that dsl-provider any more.
On Sunday 10 Aug 2008 17:36, km wrote:
route del default gw 192.168.whatever . route add defalut gw <ip of ppp0>
AFAIR, after doing a # route del default gw I did not find the /etc/network/interfaces file in place; it just disappeared! (is this expected? could not understand that from the man page on route`.)
No. route addition / deletion does not affect the interface file or the current ip.
However, I had a backup copy (incidentally a much older, cleaner backup :P ) of the interfaces file that i restored. And things seemed workable henceforth.
Although, this seems to be a pretty dirty way of getting around a problem and i am still foxed as to what was a proper systematic approach to solve it. I am reading up on this, and will surely catch up pretty soon.
usually in pppconfig there is an Advanced - Defaultroute option. you should enable defaultroute. Or simply edit /etc/ppp/peers/<your ppp config-name file> and add a the word defaultroute on a new line.
One can of course do all sorts of things by adding appropriate scripts in /etc/ppp/ip-up.d/ and /etc/ppp/ip-down.d/
On Monday 11 Aug 2008 13:06, kamal wrote:
jtd wrote:
One can of course do all sorts of things by adding appropriate scripts in /etc/ppp/ip-up.d/ and /etc/ppp/ip-down.d/
This is valid for any method that brings up/down ppp
Thanks, thats helpful. Is this also applicable to wvdial as i use that to connect?
the conf files and wvdial options are different. wvdial would not connect with cdma and gprs connections many years ago and used ppp since.
jtd wrote:
On Sunday 10 Aug 2008 17:36, km wrote:
route del default gw 192.168.whatever . route add defalut gw <ip of ppp0>
AFAIR, after doing a # route del default gw I did not find the /etc/network/interfaces file in place; it just disappeared! (is this expected? could not understand that from the man page on route`.)
No. route addition / deletion does not affect the interface file or the current ip.
However, I had a backup copy (incidentally a much older, cleaner backup :P ) of the interfaces file that i restored. And things seemed workable henceforth.
Although, this seems to be a pretty dirty way of getting around a problem and i am still foxed as to what was a proper systematic approach to solve it. I am reading up on this, and will surely catch up pretty soon.
usually in pppconfig there is an Advanced - Defaultroute option. you should enable defaultroute. Or simply edit /etc/ppp/peers/<your ppp config-name file> and add a the word defaultroute on a new line.
One can of course do all sorts of things by adding appropriate scripts in /etc/ppp/ip-up.d/ and /etc/ppp/ip-down.d/
Thanks, thats helpful. Is this also applicable to wvdial as i use that to connect?
km wrote:
After everything done and working, route -n gives me the following:
kamal@kMax:~$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 172.23.119.14 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp0
and the contents of interfaces file are as follows; which i guess is really crappy, but still working. any clues on cleaning it up? :P --------- GNU nano 2.0.6 File: /etc/network/interfaces
auto lo iface lo inet loopback address 127.0.0.1 netmask 255.0.0.0
iface dsl-provider inet ppp pre-up /sbin/ifconfig eth0 up # line maintained by pppoeconf provider dsl-provider
auto eth0 iface eth0 inet static address 10.10.80.1 netmask 255.0.0.0 gateway ---------
Address 10.10.80.1 < this is the addr i chose on LAN, which i don't use any more. Is it safe to remove? Also, is it safe to comment out the `provider` line? i am not using that dsl-provider any more.
You can comment the entries you think are not necessary. If you are no longer using the ethernet, you can simply keep two lines. This is useful for those who use cablenet pppoe where there is no static ip for ethernet and no dhcp server at the other end.
auto eth0 iface eth0 inet manual
If you are not using dsl-provider, you can replace it with the one you are using (pppoe). The name should exist in the /etc/ppp/peers directory. The PPPoE entry is written to the interfaces file only because you pressed enter when you were asked if you want it to start during boot time.
-
Arun Khan -
G Karunakar -
jtd -
kamal -
km
-
Mehul Ved -
Rahulkrishna Gupta -
Rony -
Rony Bill