Linux PPP protocol development
 help / color / mirror / Atom feed
From: James Carlson <carlsonj@workingcode.com>
To: linux-ppp@vger.kernel.org
Subject: Re: pppoe config connects, but can't ping *past* gateway. something wrong with my routes?
Date: Sat, 15 Nov 2008 14:35:49 +0000	[thread overview]
Message-ID: <18718.56901.462737.559729@gargle.gargle.HOWL> (raw)
In-Reply-To: <7259d7020811141843i44d31119u999b70ccd717c61e@mail.gmail.com>

JC Janos writes:
> /etc/ppp/ip-up.local
> 	echo /sbin/ip route list | awk '/^default / { print $3 }' > /etc/default-route
> 	/sbin/route del default
> 	/sbin/route add default netmask 255.255.255.248 gw x.x.x.150
[...]
> and to my gateway,
> 
> 	ping -c 1 99.164.169.50
> 		PING 99.164.169.50 (99.164.169.50) 56(84) bytes of data.
> 		64 bytes from 99.164.169.50: icmp_seq=1 ttl%5 time\x11.9 ms

It looks like your routes are misconfigured.  Your default route in
this case should point to the other end of this link -- 99.164.169.50
as you've shown -- and not to one of your own local addresses.  By
using a local address, you've basically told the kernel to drop all
your packets, and it's just doing what you've asked it to do.

As another poster suggested, you should use the "defaultroute" option
instead of this ip-up hackery.  If you really do need all of this
complex manual configuration in the ip-up script, then consider using
the $IPREMOTE environment variable or $5 in /etc/ppp/ip-up.  (I'm not
sure how Linux handles the command line arguments for that script, but
pppd itself passes the remote address as $5 when it invokes
/etc/ppp/ip-up.)

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

      parent reply	other threads:[~2008-11-15 14:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-15  2:43 pppoe config connects, but can't ping *past* gateway. something wrong with my routes? JC Janos
2008-11-15  7:30 ` Gilles Espinasse
2008-11-15 14:35 ` James Carlson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=18718.56901.462737.559729@gargle.gargle.HOWL \
    --to=carlsonj@workingcode.com \
    --cc=linux-ppp@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox