dhcp help

[vishesh.l]

hi,
1st of all i cant search the site as the pages dont open,
i cant use google for info,same problem,many pages dont open.
so im bothering the community as a last resort....

i managed to configure my net connection with pppoe
the problem im facing is many websites don't open
popular websites like gmail,msn etc are loading,
i have noticed that sites with long and complex urls in particular cant open...
maybe just a hunch,
the connection is Dhcp
so i really have no clue what to do about it.

is the problem related to my isp not sending me proper dns ?
also can someone breif me about peerdns and synchronousPPP,should they be on or off ?

since my isp requires a service name i use the pppoe-start,pppoe-stop with the following pppoe.conf
..................................................

# Ethernet card connected to DSL modem
ETH='eth0'

USER='blah'
PASSWORD='123456'

DEMAND=no
#DEMAND=300

# DNS type: SERVER=obtain from server; SPECIFY=use DNS1 and DNS2;
# NOCHANGE=do not adjust.
DNSTYPE=SERVER

# Obtain DNS server addresses from the peer (recent versions of pppd only)
# In old config files, this used to be called USEPEERDNS.  Changed to
# PEERDNS for better Red Hat compatibility
PEERDNS=yes

DNS1=
DNS2=202.63.164.18

# Make the PPPoE connection your default route.
DEFAULTROUTE=yes

CONNECT_TIMEOUT=30

CONNECT_POLL=2

ACNAME=IOLNETCOM
SERVICENAME=IOLNETCOM

# Character to echo at each poll.  Use PING="" if you don't want
# anything echoed
PING="."

# File where the pppoe-connect script writes its process-ID.
# Three files are actually used:
#   $PIDFILE       contains PID of pppoe-connect script
#   $PIDFILE.pppoe contains PID of pppoe process
#   $PIDFILE.pppd  contains PID of pppd process
CF_BASE=`basename $CONFIG`
PIDFILE="/var/run/$CF_BASE-pppoe.pid"

# Do you want to use synchronous PPP?  "yes" or "no".  "yes" is much
# easier on CPU usage, but may not work for you.  It is safer to use
# "no", but you may want to experiment with "yes".  "yes" is generally
# safe on Linux machines with the n_hdlc line discipline; unsafe on others.

SYNCHRONOUS=yes

# Do you want to clamp the MSS?  Here's how to decide:
# - If you have only a SINGLE computer connected to the DSL modem, choose
#   "no".
# - If you have a computer acting as a gateway for a LAN, choose "1412".
#   The setting of 1412 is safe for either setup, but uses slightly more
#   CPU power.
#CLAMPMSS=1412
CLAMPMSS=no

# LCP echo interval and failure count.
LCP_INTERVAL=20
LCP_FAILURE=3

# PPPOE_TIMEOUT should be about 4*LCP_INTERVAL
PPPOE_TIMEOUT=80

# Firewalling: One of NONE, STANDALONE or MASQUERADE
FIREWALL=NONE

# Linux kernel-mode plugin for pppd.  If you want to try the kernel-mode
# plugin, use LINUX_PLUGIN=/etc/ppp/plugins/rp-pppoe.so
#LINUX_PLUGIN=

# Any extra arguments to pass to pppoe.  Normally, use a blank string
# like this:
PPPOE_EXTRA=""

# Rumour has it that "Citizen's Communications" with a 3Com
# HomeConnect DSL Modem DualLink requires these extra options:
# PPPOE_EXTRA="-f 3c12:3c13 -S ISP"

# Any extra arguments to pass to pppd.  Normally, use a blank string
# like this:
PPPD_EXTRA=""


########## DON'T CHANGE BELOW UNLESS YOU KNOW WHAT YOU ARE DOING
# If you wish to COMPLETELY overrride the pppd invocation:
# Example:
# OVERRIDE_PPPD_COMMAND="pppd call dsl"

# If you want pppoe-connect to exit when connection drops:
RETRY_ON_FAILURE=yes

any help appreciated,

regards
vishesh

[hazel]

is the problem related to my isp not sending me proper dns ?
also can someone breif me about peerdns and synchronousPPP,should they be on or off ?

You can check whether the peer is sending dns addresses by looking at /var/log/messages. When your connection is accepted, the local and remote IP addresses and two DNS server addresses should appear at the bottom of this file.

If that is so, then USEPEERDNS is appropriate. If not, you will have to find out from your ISP what DNS servers to use and put them in /etc/resolv.conf.

[vishesh.l]

thnx hazel,
the messages file shows
local ip
remote ip
primary dns
secondary dns
addresses,
so i guess thats fine
but below that theres
Jul 31 18:29:41 thoughtbubble-linux pppd[8038]: Protocol-Reject for unsupported protocol 0x2e67
Jul 31 18:29:41 thoughtbubble-linux pppd[8038]: Protocol-Reject for unsupported protocol 0x0
Jul 31 18:29:47 thoughtbubble-linux pppd[8038]: Protocol-Reject for unsupported protocol 0x6f6b
Jul 31 18:29:59 thoughtbubble-linux pppd[8038]: Protocol-Reject for unsupported protocol 0x6572
Jul 31 18:29:59 thoughtbubble-linux pppd[8038]: Protocol-Reject for unsupported protocol 0x3531
Jul 31 18:30:16 thoughtbubble-linux pppd[8038]: Protocol-Reject for unsupported protocol 0x0
Jul 31 18:30:23 thoughtbubble-linux pppd[8038]: Protocol-Reject for unsupported protocol 0x3230
Jul 31 18:30:23 thoughtbubble-linux pppd[8038]: Protocol-Reject for unsupported protocol 0x2057
Jul 31 18:30:41 thoughtbubble-linux pppd[8038]: Protocol-Reject for unsupported protocol 0x0
Jul 31 18:30:41 thoughtbubble-linux pppd[8038]: Protocol-Reject for unsupported protocol 0x0
Jul 31 18:31:11 thoughtbubble-linux pppd[8038]: Protocol-Reject for unsupported protocol 0x3533
Jul 31 18:31:41 thoughtbubble-linux pppd[8038]: Protocol-Reject for unsupported protocol 0x0
Jul 31 18:31:44 thoughtbubble-linux pppd[8038]: Protocol-Reject for unsupported protocol 0x3231
Jul 31 18:31:54 thoughtbubble-linux pppd[8038]: Protocol-Reject for unsupported protocol 0x5f5f

any suggestions?