Amit Shah writes:
> I have tried the configuration mentioned at 
> http://blogs.sun.com/popuri/entry/configuring_pppoe_on_bsnl_networks

I don't think that's authoritative, and it does have some mistakes,
but it's a reasonable start.

> but it didn't work.I am still unable to connect to internet on Solaris.
> Additionaly ,while installing (In solaris install options)I haven't done any 
> configuration like DNS and I mentioned Solaris not connected to 
> network.(where as my system is connected to internet through router and it is 
> working fine on Windows XP)
> The file below edited as follows .I have just kept USERNAME and PASSWORD as 
> it is for this posting.On my machine I have added appropriate values for 
> USERNAME and PASSWORD.

When reporting a problem, *please* include log messages and any debug
information you can think of.  It's crucial to know exactly what's
going wrong if we're going to fix it.

> #/etc/ppp/peers/vsnl
> 
> connect "/usr/bin/chat -f /etc/ppp/myisp-chat"  # dial into ISP.

Remove the line above.  It's incorrect and does nothing here.

> sppptun
> plugin pppoe.so
> connect "/usr/lib/inet/pppoec rtls0"

Do you have "rtls0" in your /etc/ppp/pppoe.if file?

What does "/usr/sbin/sppptun query" (running as root) say?

What happens when you run the following command?

        # pppd debug call vsnl

What output is produced?  After starting pppd, do you have an "sppp0"
interface in the "/usr/sbin/ifconfig -a" output?

If pppd doesn't work, then what do you see if you run this command?

        # /usr/lib/inet/pppoec -i rtls0

> #/usr/sbin/sppptun plumb pppoe rtls0
> #/usr/sbin/sppptun plumb pppoed rtls0

Note that if you have "rtls0" in your /etc/ppp/pppoe.if file at boot
time, you should not need to run those commands by hand.

-- 
James Carlson, Solaris Networking              <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677
_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to