shyam batra wrote:
>
> # cat /etc/resolv.conf shows
>
> nameserver218.248.240.79
> nameserver218.248.240.135
>
> and on run ping 202.54.1.18 nothing happens and on killing it ping
> statistics are 29 packets transmitted, 0 packet received, 100 % packet
> loss.
>
> pppo info shows
>
> connection establisher.
>
> duration 2.0.... min
>
> send 60 ... received 3
>
> speed 0 byte
>
>
> Please help i need to have a working connection with linux
>
>
> Thanks
>
> Dr. Shyam Batra
>
>
>
> */Ripunjay Bararia /* wrote:
>
> drshyambatra wrote:
> >
> >
> > Hi!
> > I am using Mepis Linux 6.0.
> >
> > Unable to connect to the net using BSNL broadband.
> >
> > Modem purchased UTStarcom/ut-300RU
> >
> > Downloaded rp-pppoe-3.5.tar.gz from bsnl website and installed the
> > gui based client via shell with following settings as described on
> > bsnl site.
> >
> > Ethernet Interface: eth0
> > User name: amit
> > Activate-on-demand: No
> > DNS: Do not adjust / server (tried both)
> > Firewalling: MASQUERADE( tried with firewall off)
> >
> > Adsl start connects to the net but when i try to connect to any
> > website i get the following message
> >
> > Server not found
> >
> > Firefox can't find the server at www.mepis.org.
> >
> > * Check the address for typing errors such as
> > ww.example.com instead of
> > www.example.com
> >
> > * If you are unable to load any pages, check your computer's network
> > connection.
> >
> > * If your computer or network is protected by a firewall or
> > proxy, make sure
> > that Firefox is permitted to access the Web.
> >
> > Tried other site but getting the same message.
> >
> > asdsl status, ifconfig and running mozilla from shell as root show
> > following message
> > adsl-status: Link is up and running on interface ppp0
> > ppp0 Link encap:Point-to-Point Protocol
> > inet addr:59.95.169.174 P-t-P:59.95.160.1 Mask:255.255.255.255
> > UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
> > RX packets:39 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:3
> > RX bytes:7890 (7.7 KiB) TX bytes:30 (30.0 b)
> >
> >
> ===================================================================================
> >
> > ifconfig eth0
> > eth0 Link encap:Ethernet HWaddr 00:50:FC:6F:EA:2D
> > inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:2693 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:1016 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:1000
> > RX bytes:247544 (241.7 KiB) TX bytes:102137 (99.7 KiB)
> > Interrupt:185 Base address:0x6000
> >
> ====================================================================================
> -- SNIP --
> >
> > Please advice on any other distro which will work properly with bsnl
> > broadband and which modem should i get.
> >
> > The above mentioned modem is working properly in windows xp.
> >
> > Thanks
> >
> > Dr.Shyam Batra.
> >
> >
>
>
>
> Hi,
>
> Seems that your system is not able to resolv hostnames,
> try pinging an ip address...
>
> # ping 202.54.1.18
>
> this will ping a VSNL IP address, if you can get replies then you
> need
> to check your
>
> /etc/resolv.conf file...
>
> should look something like this
>
> # cat /etc/resolv.conf
> nameserver 208.67.220.220
> nameserver 208.67.222.222
>
>
>
> regards
> Ripunjay Bararia
>
>
> ------------------------------------------------------------------------
>
> Visit Your Group
>
>
> Yahoo! Mail
>
> Stay in Touch
>
>
> Stay connected
>
> and manage your life
>
> Y! Answers
>
> Ask, Answer, Find
>
>
>
> A new way to get &
>
> share information.
>
> Yahoo! Toolbar
>
> Get it Free!
>
>
> easy 1-click access
>
> to your groups.
>
> .
>
>



Hi,

can you ping your gateway...???

please attach the output for

# route -n

and if you can ping your gateway
then can you also send the output for a traceroute

# traceroute 202.54.1.18

Your phy. connectivity seems to be working, but there seems to be some
other problem in the middle

you can also try to stop your firewall by issuing the following command:

/etc/init.d/iptables stop

once you have done that issue the command

# iptables -L

you should get an output matching the below...

>>>>
Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
<<<<<


regards
Ripunjay Bararia