hi guys i am install linux on my system and i have airtel 256 KBPs night top up with pppoe connection. and its work very well in my windows 2003 enterprise as well as linux. 
Finally Work Airtel Bb In Linux
- Thread starter lakhan_chouhan
- Start date
QUOTE(Airtel 65KBPS @ Dec 16 2006, 11:35 AM) [snapback]71027[/snapback]
hi guys i am install linux on my system and i have airtel 256 KBPs night top up with pppoe connection. and its work very well in my windows 2003 enterprise as well as linux.[/b]
Hi, could someone please mention the steps to configure airtel broadband in linux. I am getting an error while activating the connection. It waits for a long time(4 or 5 minutes) and then gives the following error.
/sbin/adsl-start: line 216: 3480 Terminated $CONNECT "$@" >/dev/null 2>&1
I am using Fedora Code 6. The network card is recognized, the kernel module r1000 is loaded fine. The network card is RealTek RTL8111/8168B PCI Express Gigabit Ethernet controller.
thanks
Bingo
hi guys i am install linux on my system and i have airtel 256 KBPs night top up with pppoe connection. and its work very well in my windows 2003 enterprise as well as linux.
[/b]Hi, could someone please mention the steps to configure airtel broadband in linux. I am getting an error while activating the connection. It waits for a long time(4 or 5 minutes) and then gives the following error.
/sbin/adsl-start: line 216: 3480 Terminated $CONNECT "$@" >/dev/null 2>&1
I am using Fedora Code 6. The network card is recognized, the kernel module r1000 is loaded fine. The network card is RealTek RTL8111/8168B PCI Express Gigabit Ethernet controller.
thanks
Bingo
This test i am done with fedora core 6.
1. Your lan card Recognized fedora core 6 (you are mention so you done this step.)
2. go to your network properties and check all coonection is active if not then press active.
3. create new xdsl connection with necessary info like username, password etc.
4. done all three step then go to terminal and type adsl-start for start your connection and type ping any webstite for checking the connectivity.
5. for stop connection adsl-stop.
6. enjoy surfing
Note: I am use Lan Interface not USB.
I'm done my adsl setup in 60 seconds with fedora core 6.
1. Your lan card Recognized fedora core 6 (you are mention so you done this step.)
2. go to your network properties and check all coonection is active if not then press active.
3. create new xdsl connection with necessary info like username, password etc.
4. done all three step then go to terminal and type adsl-start for start your connection and type ping any webstite for checking the connectivity.
5. for stop connection adsl-stop.
6. enjoy surfing
Note: I am use Lan Interface not USB.
I'm done my adsl setup in 60 seconds with fedora core 6.
hi i recently installed suse linux 10.1 version. i'm not able to ping ADSL modem. i'm getting destination host unreachable.can any one tell. r u able to ping. any configuration in modem..?my sys ip: 192.168.1.2ADSL : 192.168.1.1Modem : ADSL2+ Modem ( beetel 220 bx ) modeland my eth card is configured. ( same setup is working in windows XP OS )please solve my issue.thanksdemigod.
Make sure the subnet masks in the router page and in your network configuration page of the OS are the same
QUOTE(dips0502 @ Apr 1 2007, 02:15 AM) [snapback]85632[/snapback]
Make sure the subnet masks in the router page and in your network configuration page of the OS are the same[/b]
ya both are same please see this http://img231.imageshack.us/my.php?image=lansetupky6.jpg
when i was using Redhat 9 also i faced the same problem. so do i need to do any thing with the modem settings ?
FYI i'm using " Beetel 220Bx ADSL2+ Modem "
the outputs:
eth0 Link encap:Ethernet HWaddr 00:14:85:CE:F0:1D
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::214:85ff:fece:f01d/64 Scope:Link
UP BROADCAST RUNNING 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:177 Base address:0xc000
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:155 errors:0 dropped:0 overruns:0 frame:0
TX packets:155 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:12908 (12.6 Kb) TX bytes:12908 (12.6 Kb)
------------------------------------------------------------------------------------
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 0 0 0 eth0
loopback * 255.0.0.0 U 0 0 0 lo
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
Make sure the subnet masks in the router page and in your network configuration page of the OS are the same[/b]
ya both are same please see this http://img231.imageshack.us/my.php?image=lansetupky6.jpg
when i was using Redhat 9 also i faced the same problem. so do i need to do any thing with the modem settings ?
FYI i'm using " Beetel 220Bx ADSL2+ Modem "
the outputs:
eth0 Link encap:Ethernet HWaddr 00:14:85:CE:F0:1D
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::214:85ff:fece:f01d/64 Scope:Link
UP BROADCAST RUNNING 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:177 Base address:0xc000
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:155 errors:0 dropped:0 overruns:0 frame:0
TX packets:155 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:12908 (12.6 Kb) TX bytes:12908 (12.6 Kb)
------------------------------------------------------------------------------------
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 0 0 0 eth0
loopback * 255.0.0.0 U 0 0 0 lo
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0