firewall blocks ppp0?

firewall blocks ppp0?

[Haines Brown]

I'm setting up a copy of RedHat 8.0 on a machine that is intended as a
standalone machine with DSL access to Internet.

I have eth0 up and running, and did the adsl-setup with my usual valid
information. The problem comes trying to make ppp0 active. It tries,
but cycles between active and inactive.

When I run adsl-start with debugging, it tells me that I'm set up for
demand-connection. I definitely have eth0 set to be permanently
up. Does this alert refer instead to ppp0? If so, perhaps this is what
I'd expect. Is that right?

I'm also told: ipchains: Protocol not available

That sounds to me as if my firewall (which I set to be "high"
protection), may be blocking the ppp protocol. Does this seem to be
the case?

I went to pursue this, and ran ipchains -L, but got the error message
that this command is incompabible with my kernel.

What to do?

Haines Brown
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: firewall blocks ppp0?

[Haines Brown]

Chuck,

>  I use Roaring Penguin PPPOE. http://www.roaringpenguin.com/pppoe/ I
> selected permanent connection, but I am unsure if this applies to
> eth# or ppp#. :-| 'adsl-setup' and 'adsl-start' are script names
> with my application (Roaring Penguin).  I am assuming that your
> using the same or similar.
> 
>  How do you know "I definitely have eth0 set to be permanently up" ?
>  Actually, I'm betting that it is ppp# that is set to demand or
>  permanent.

Yes, I also use the roaring penguin, My eth0 is made active during
boot, for I can run ifconfig and see that it is up as soon as I've
finished booting. The ppp0, on the other hand, is not up until
adsl-start is run. That is, ppp0 is on demand, while eth0 is
permanent. That's my impression, anyway. pppd is a daemon which I
assume is meant normally to be on demand.

Actually, when I run redhat-configuration-network, I see not only
eth0, but also ppp0 (trying to be active). That's not right. ppp0
should not appear (or at least it does not show up under RH7.3 as I
speak to you). I may have some kind of problem in that pppd is trying
to start ppp, rather than my starting pppoe by means of adsl-start

>  It seems that your dsl connection (PPPOE?) application is setting
> up IPCHAINS, but your kernel is using IPTABLES.

That may be, but then a good percentage of folks who get RedHat 8.0
must reconfigure and recompile their kernel, which I doubt.

> - configure IPTABLES to replace your dsl-connection application's
> attempt to use IPCHAINS.

This was my inclination, for I gather IPTables are better. I've got a
copy of Bastille, which should make my life a lot easier, not only
spotting the source of any difficulty, but setting up a secure set of
rules.

Haines
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Who is running Red Hat 8.0 and Roaring Penguin?

[Chuck Gelm]

 Please address your linux-newbie messages to
linux-newbie@vger.kernel.org
 and not to 
linux-newbie@hartford-hwp.com
 and not to
nc8q@gelm.net without linux-newbie@vger.kernel.org

 as I cannot 'reply' to linux-newbie@vger.kernel.org
 without adding that address manually &
 I see no reason to reply to you alone.

 If you cannot do this, I'll edit to suit. ;-)

Haines Brown wrote:
> 
> Chuck,
> 
> >  I use Roaring Penguin PPPOE. http://www.roaringpenguin.com/pppoe/ I
> > selected permanent connection, but I am unsure if this applies to
> > eth# or ppp#. :-| 'adsl-setup' and 'adsl-start' are script names
> > with my application (Roaring Penguin).  I am assuming that your
> > using the same or similar.
> >
> >  How do you know "I definitely have eth0 set to be permanently up" ?
> >  Actually, I'm betting that it is ppp# that is set to demand or
> >  permanent.
> 
> Yes, I also use the roaring penguin, My eth0 is made active during
> boot, for I can run ifconfig and see that it is up as soon as I've
> finished booting. 

 Yes, AFAIK, the eth# device that PPPOE is going to use should be up.
However, it should not have an IP address.

>  The ppp0, on the other hand, is not up until
> adsl-start is run. That is, ppp0 is on demand, while eth0 is
> permanent. That's my impression, anyway. pppd is a daemon which I
> assume is meant normally to be on demand.

 This is your choice for ppp#: demand or permanent.
For a DSL connection, I recommend permanent, especially if you are
having problems with demand.

> Actually, when I run redhat-configuration-network, I see not only
> eth0, but also ppp0 (trying to be active). That's not right. ppp0
> should not appear (or at least it does not show up under RH7.3 as I
> speak to you). I may have some kind of problem in that pppd is trying
> to start ppp, rather than my starting pppoe by means of adsl-start

Seems reasonable.

> >  It seems that your dsl connection (PPPOE?) application is setting
> > up IPCHAINS, but your kernel is using IPTABLES.
> 
> That may be, but then a good percentage of folks who get RedHat 8.0
> must reconfigure and recompile their kernel, which I doubt.

Who is running Red Hat 8.0 and Roaring Penguin?

 I run Roaring Penguin v3.3 and it created IPCHAINS.
I run kernel 2.2.19 as it uses IPCHAINS by default.
IIRC, kernel 2.4.x uses IPTABLES by default.

So, perhaps your Roaring Penguin installation created an
IPCHAINS ruleset and your kernel is using IPTABLES.

Again:

- Create an IPTABLES ruleset for your current kernel.
  Roaring Penguin did not do this. (?)

- Rebuild your current kernel to use IPCHAINS.
  The IPCHAINS ruleset you choose when you configured Roaring Penguin.

HTH, Chuck

> > - configure IPTABLES to replace your dsl-connection application's
> > attempt to use IPCHAINS.
> 
> This was my inclination, for I gather IPTables are better. I've got a
> copy of Bastille, which should make my life a lot easier, not only
> spotting the source of any difficulty, but setting up a secure set of
> rules.
> 
> Haines
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: firewall blocks ppp0?

[Ray Olszewski]

Haines -- My attempt to reply to your initial message bounced due to the 
error in your To: line that someone else already pointed out (but that I 
didn't notice when replying, only when I found the bounce this morning) -- 
you really need to fix this.

As I read both this and your earlier posting, you have three independent 
configuration issues, namely --

1. ppp0  "cycles between active and inactive". If you are using RP-PPPoE in 
"on demand" mode, this may be normal. The interface gets dropped (either by 
your end or by the ISP) when there is no traffic, and it gets restored (by 
your end) when there is new traffic. If more is going on here, you will 
need to describe the problem in more detail to get help. (BTW, while pppd 
is a daemon, it can be configured in different ways -- "on demand" is one, 
and "permanent", that is, restore the connection whenever it goes down due 
to action from the other end, is another. When I had the misfortune to use 
a PPPoE connection a couple of years back, my router, using a prepackaged 
LEAF image that ran RP-PPPoE, was set for "permanent", and it worked nicely 
here with SBC's DSL service.)

2. "ipchains -L" does not work ("got the error message that this command is 
incompabible with my kernel."). Odd, since you also report that in a 
different context, the ipchains commands returns an error message ("I'm 
also told: ipchains: Protocol not available"), and ipchains has to run to 
be able to return this message.  The inconsistency here is the first thing 
to address. Please run (as root) "ipchains -nvL" and if you get an error 
message, quote the EXACT, COMPLETE message, and the EXACT command you 
enter, in your followup to us. Also identify your kernel ("uname -a" will 
serve). And finally, tell us the context in which some ipchains command IS 
running.

3. You think your firewall might be interfering with the ppp protocol. The 
way you state it, this is unlikely, since with ipchains-based firewalls, 
"protocol" refers only to layer 4 (transport layer - TCP, UDP, ICMP, 
mainly), not  layer 2 (link layer - Ethernet, ppp). The ipchains error 
message you quote is almost surely just an error in a -A or -I command 
(specifically, its -p argument) to ipchains. But to be sure, please provide 
context -- where are you "told" this (in a log file? in the dmesg buffer? 
on a console?) and what precedes and follows it there?

But your firewall and your PPPoE connection may be interfering with each 
other in a different way. If ppp0 stops and restarts, its IP address 
probably changes. Most firewalls (especially ones set to "high" protection, 
as you say yours is) block all external-interface traffic not to your 
external IP address. If your external (ppp0) IP address changes, the 
ipchains rulesets have to be cleared and restored to reflect the new IP 
address. RP-PPPoE has a way to do this, but whether it works with your 
firewall package ... well, who can guess? What firewall package are you 
using? Did you provide for RP-PPPoE to restart the firewall whenever it 
comes up?

One last thought ... what does it mean when you say "My eth0 is made active 
during boot, for I can run ifconfig and see that it is up as soon as I've 
finished booting"? The term "active" has no specific meaning, but if you 
can see the interface with "ifconfig" (rather than with "ifconfig -a"), 
that implies that it has a IP address assigned to it. In my (admittedly 
limited) experience, an eth* interface being used for PPPoE does NOT get an 
IP address assigned to it; at the network layer, your external connection 
is over ppp0, not eth0. If you are assigning an IP address to this 
interface, that might be part of your problem. Hard to say without more 
information, such as the complete output of "ifconfig -a" and "netstat -nr" 
(one way to display your routing table).

At 01:01 PM 11/24/02 -0500, Haines Brown wrote:
>Chuck,
>
> >  I use Roaring Penguin PPPOE. http://www.roaringpenguin.com/pppoe/ I
> > selected permanent connection, but I am unsure if this applies to
> > eth# or ppp#. :-| 'adsl-setup' and 'adsl-start' are script names
> > with my application (Roaring Penguin).  I am assuming that your
> > using the same or similar.
> >
> >  How do you know "I definitely have eth0 set to be permanently up" ?
> >  Actually, I'm betting that it is ppp# that is set to demand or
> >  permanent.
>
>Yes, I also use the roaring penguin, My eth0 is made active during
>boot, for I can run ifconfig and see that it is up as soon as I've
>finished booting. The ppp0, on the other hand, is not up until
>adsl-start is run. That is, ppp0 is on demand, while eth0 is
>permanent. That's my impression, anyway. pppd is a daemon which I
>assume is meant normally to be on demand.
>
>Actually, when I run redhat-configuration-network, I see not only
>eth0, but also ppp0 (trying to be active). That's not right. ppp0
>should not appear (or at least it does not show up under RH7.3 as I
>speak to you). I may have some kind of problem in that pppd is trying
>to start ppp, rather than my starting pppoe by means of adsl-start
>
> >  It seems that your dsl connection (PPPOE?) application is setting
> > up IPCHAINS, but your kernel is using IPTABLES.
>
>That may be, but then a good percentage of folks who get RedHat 8.0
>must reconfigure and recompile their kernel, which I doubt.
>
> > - configure IPTABLES to replace your dsl-connection application's
> > attempt to use IPCHAINS.
>
>This was my inclination, for I gather IPTables are better. I've got a
>copy of Bastille, which should make my life a lot easier, not only
>spotting the source of any difficulty, but setting up a secure set of
>rules.




--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski					-- Han Solo
Palo Alto, California, USA			  ray@comarre.com
-------------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Who is running Red Hat 8.0 and Roaring Penguin?

[Haines Brown]

Chuck,

> Date: Sun, 24 Nov 2002 13:55:11 -0500
> From: Chuck Gelm <nc8q@gelm.net>
> X-Accept-Language: en
> CC: linux-newbie@hartford-hwp.com
> 
>  Please address your linux-newbie messages to
> linux-newbie@vger.kernel.org and not to
> linux-newbie@hartford-hwp.com and not to nc8q@gelm.net without
> linux-newbie@vger.kernel.org
> 
>  as I cannot 'reply' to linux-newbie@vger.kernel.org without adding
>  that address manually & I see no reason to reply to you alone.
> 
>  If you cannot do this, I'll edit to suit. ;-)

Chuck. I quite understand. Somehow a CC: linux-newbie@vger.kernel.org
got in there, and so when I replied, it was reproduced. The header of
this message looks clean, and so it's a kind of test. It goes to you,
and a CC: for the list and back to me.
 
>  Yes, AFAIK, the eth# device that PPPOE is going to use should be
> up.  However, it should not have an IP address.

Yes, the eth0 is up and running. The problem was that the
configuration utility gave me the choice of a static address or DHCP,
and I was unable to enter " ". I can get back to the files themselves,
but right now on the machine I'm using, I have a permanent address for
my machine (192.168.0.1) that is simply ignored when I set up a DSL
connection.

> > Actually, when I run redhat-configuration-network, I see not only
> > eth0, but also ppp0

I simply killed that unwanted ppp0, and it goes better.

> Who is running Red Hat 8.0 and Roaring Penguin?

15% of all linux users? ;-)

With eth0 up and running, and having defined the inteface property in
network configuration, I then proceed to configure Roaring Penguin.

Before I do I run adsl-status and am told, naturally, that there's no
/etc/ppp/pppoe.conf file. I then proceed to configure Roaring Penguin
(I'm comfortable with that), and at the end save the
configuration. However, no /etc/ppp/pppoe.conf file shows up.

Then I start adsl and get: ipchains: protocol not available. My first
reaction was that iptables were blocking ppp, but now I don't think
so. Nevertheless, when I run

      ipchains -L ...  REJECT tcp anysource anydest tcp
      flags:SYN,RSG,AC...

However, I can read the error above to mean that ipchains is telling
me there's no ppp protocol running. That, with the absense of a
configuraion file, suggests that Roaring Penguin failed to configure
pppoe. I did all this as root, but I'll have to check permissions,
etc. to make sure the configuration file can be created. Also, I can
try importing my old config file, which should be the same.

Haines
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Who is running Red Hat 8.0 and Roaring Penguin?

[Chuck Gelm]

:-)


Haines Brown wrote:
> 
> Chuck,
> 
> > Date: Sun, 24 Nov 2002 13:55:11 -0500
> > From: Chuck Gelm <nc8q@gelm.net>
> > X-Accept-Language: en
> > CC: linux-newbie@hartford-hwp.com
> >
> >  Please address your linux-newbie messages to
> > linux-newbie@vger.kernel.org and not to
> > linux-newbie@hartford-hwp.com and not to nc8q@gelm.net without
> > linux-newbie@vger.kernel.org
> >
> >  as I cannot 'reply' to linux-newbie@vger.kernel.org without adding
> >  that address manually & I see no reason to reply to you alone.
> >
> >  If you cannot do this, I'll edit to suit. ;-)
> 
> Chuck. I quite understand. Somehow a CC: linux-newbie@vger.kernel.org
> got in there, and so when I replied, it was reproduced. The header of
> this message looks clean, and so it's a kind of test. It goes to you,
> and a CC: for the list and back to me.
> 
> >  Yes, AFAIK, the eth# device that PPPOE is going to use should be
> > up.  However, it should not have an IP address.
> 
> Yes, the eth0 is up and running. The problem was that the
> configuration utility gave me the choice of a static address or DHCP,
> and I was unable to enter " ". I can get back to the files themselves,
> but right now on the machine I'm using, I have a permanent address for
> my machine (192.168.0.1) that is simply ignored when I set up a DSL
> connection.

 To remove the IPADDRESS from eth0, do
ifconfig eth0 down
ifconfig eth0 0.0.0.0 up

> > > Actually, when I run redhat-configuration-network, I see not only
> > > eth0, but also ppp0
> 
> I simply killed that unwanted ppp0, and it goes better.
> 
> > Who is running Red Hat 8.0 and Roaring Penguin?
> 
> 15% of all linux users? ;-)

Naw, not how many or percentile, but who, specifically,
can help us with a replica of your system.  ;-)

> With eth0 up and running, and having defined the inteface property in
> network configuration, I then proceed to configure Roaring Penguin.
> 
> Before I do I run adsl-status and am told, naturally, that there's no
> /etc/ppp/pppoe.conf file. I then proceed to configure Roaring Penguin
> (I'm comfortable with that), and at the end save the
> configuration. However, no /etc/ppp/pppoe.conf file shows up.

locate pppoe.conf
 on my system reports:
/etc/ppp/pppoe.conf
/usr/local/rp-pppoe-3.5/configs/pppoe.conf

 I think that 'adsl-setup' should have created a
'pppoe.conf' file.  Where it was placed, I'm not sure.


> Then I start adsl and get: ipchains: protocol not available. My first
> reaction was that iptables were blocking ppp, but now I don't think
> so. 

>       I think that IPTABLES is blocking IPCHAINS.

- I think that the default Red Hat 8.0 kernel uses
   IPTABLES and not IPCHAINS.  
- I think that rp-pppoe_v3.x uses IPCHAINS and not IPTABLES.

- I think that when (if?) adsl-setup creates an IPCHAINS ruleset
   it is useless to your kernel as your kernel is expecting
   an IPTABLES ruleset.  :-|

>     Nevertheless, when I run
> 
>       ipchains -L ...  REJECT tcp anysource anydest tcp
>       flags:SYN,RSG,AC...
> 
> However, I can read the error above to mean that ipchains is telling
> me there's no ppp protocol running. That, with the absense of a
> configuraion file, suggests that Roaring Penguin failed to configure
> pppoe. I did all this as root, but I'll have to check permissions,
> etc. to make sure the configuration file can be created. Also, I can
> try importing my old config file, which should be the same.
> 
> Haines

 Give Ray what he asked for. 
  "uname -a", "ifconfig -a", & "netstat -nr".  
 I've edited some IP addresses.  Here are mine:

Linux firewall 2.2.19.firewall #8 Wed Aug 28 18:23:22 EDT 2002 i486
unknown

Chain input (policy ACCEPT):
target     prot opt     source                destination          
ports
DENY       udp  ----l-  anywhere             anywhere              any
->   0:1023
DENY       tcp  ----l-  anywhere             anywhere              any
->   0:1023
DENY       tcp  -y--l-  anywhere             anywhere              any
->   any
DENY       icmp ----l-  anywhere             anywhere             
echo-request
Chain forward (policy DENY):
target     prot opt     source                destination          
ports
MASQ       all  ------  anywhere             anywhere              n/a
Chain output (policy ACCEPT):

Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface
000.72.131.1    0.0.0.0         255.255.255.255 UH        0 0          0
ppp0
192.168.0.0     0.0.0.0         255.255.255.0   U         0 0          0
eth0
127.0.0.0       0.0.0.0         255.0.0.0       U         0 0          0
lo
0.0.0.0         000.72.131.1    0.0.0.0         UG        0 0          0
ppp0

 And here is my pppoe.conf for your perusal:

ETH='eth1'
USER='this_is@edited.net'
DEMAND=no
DNSTYPE=NOCHANGE
PEERDNS=no
DNS1=
DNS2= 000.000.000.000 ;-)
DEFAULTROUTE=yes
CONNECT_TIMEOUT=30
CONNECT_POLL=2
ACNAME=
SERVICENAME=
PING="."
CF_BASE=`basename $CONFIG`
PIDFILE="/var/run/$CF_BASE-adsl.pid"
SYNCHRONOUS=no
CLAMPMSS=1412
LCP_INTERVAL=20
LCP_FAILURE=3
PPPOE_TIMEOUT=80
FIREWALL=MASQUERADE	; <---- see /etc/ppp/firewall-standalone
LINUX_PLUGIN=
PPPOE_EXTRA=""
PPPD_EXTRA=""

HTH, Chuck
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: firewall blocks ppp0?

[Haines Brown]

Ray,

I've cleaned up some difficulties due to my floundering about (a
strangely gummed up configuration), and while the situyation seems a
bit simpler now, it still remains obscure to me. One exemple of my
confusion is that if I run adsl-status when adsl is down, it tells me
it can't find /etc/ppp/pppoe.conf, but that file no longer holds pppoe
configuration information under RH 8.0.

The simplest way to describe the present situation is to provide a bit
of the debug log:

> ...
> sent [LCP EchoRep id=0x0 magic=0xb81d9109]
> rcvd [IPCP ConfReq id=0x6c <addr 64.252.160.1>]
> sent [IPCP ConfAck id=0x6c <addr 64.252.160.1>]
> rcvd [IPCP ConfNak id=0x1 <addr 64.252.164.224>]
> sent [IPCP ConfReq id=0x2 <addr 64.252.164.224>]
> rcvd [IPCP ConfAck id=0x2 <addr 64.252.164.224>]
> local  IP address 64.252.164.224
> remote IP address 64.252.160.1
> Script /etc/ppp/ip-up started (pid 4916)
> rcvd [LCP EchoReq id=0x0 magic=0x3ddca2a6]
> sent [LCP EchoRep id=0x0 magic=0xb81d9109]
> Script /etc/ppp/ip-up finished (pid 4916), status = 0x0
> Script /usr/sbin/pppoe 
>       -p 
>	-I eth0 
>	-T 20 
>	-U  
>	-m 1412    
>	-D 0-0 
>	finished (pid 4906), status = 0x1
> Modem hangup
> Script /etc/ppp/ip-down started (pid 4950)
> Connection terminated.
> Connect time 0.4 minutes.
> Sent 30 bytes, received 58 bytes.
> Waiting for 1 child processes...
> script /etc/ppp/ip-down, pid 4950
> Script /etc/ppp/ip-down finished (pid 4950), status = 0x0

What this looks like to me is that I've actually shook hands with my
DSL provider and gotten back an IP address. The script ip-up seems to
have done its job succecssfully (exit code 0). Then the command pppoe
-p is issued to write the pppoe process ID to the file
/var/run/pppoe-adsl.pid.pppoe.

It finishes with status 0x1. I know about exit code 0 or 1, but have
no idea what 0x1 implies. Did the process complete satisfactorily or
not?  In any case, I get a hangup at that point. Apparently timing out
after a series of: "ipchains: Protocol not available" statements.

I don't understand why a successful connection results in a
hangup. The -T timeout option of 20 seconds seems about the time it takes for
my connection to die. I gather that timeout can cause trouble if
there's no traffic. The solution is to use lcp-echo-internal option
for pppd. The pppoe timeout should be about four times the LCP echo
interval. Any idea where one implements the LCP echo option?

The -m clamp value of 1412 for TCP max segment size is appropriate for
a LAN behind a gateway. Since I'm not in that situation, the option
could be omitted, I guess.

The -D option specifies the file in which to dump debug informaitno. I
gather this really slows down the process, and so wonder if it might
be causeing a timeout.

Is it possible that the dump slows things down too much, and the
Protocol not available statements just is the result of waiting for
pppoe to got going?

What I'm running now on my old system is 
  ...
  PPPOE_TIMEOUT=20
  LCP_FAILURE=3
  LCP_INTERVAL=20
  CLAMPMSS=1412
  CONNECT_POLL=6
  CONNECT_TIMEOUT=60

I don't think I have the new system configured much differently.

I'm profoundly ignorant about all these things, but something is
triggering a shutdown.

>   As I read both this and your earlier posting, you have three
>   independent configuration issues, namely --
>
>   1. ppp0 "cycles between active and inactive". If you are using
>   RP-PPPoE in "on demand" mode, this may be normal.

Yes. I set up pppoe to be run when I ask it to run, and I've concluded
the irregularity may be normal as the connection is established.

>   2. "ipchains -L" does not work ("got the error message that this
>   command is incompabible with my kernel."). Odd,

Yes, but my getting rid of a flakey configuration seems to have
stopped that behavior.

>   But your firewall and your PPPoE connection may be interfering
>   with each other in a different way. If ppp0 stops and restarts,
>   its IP address probably changes. Most firewalls (especially ones
>   set to "high" protection, as you say yours is) block all
>   external-interface traffic not to your external IP address. If
>   your external (ppp0) IP address changes, the ipchains rulesets
>   have to be cleared and restored to reflect the new IP
>   address. RP-PPPoE has a way to do this, but whether it works with
>   your firewall package ... well, who can guess? What firewall
>   package are you using? Did you provide for RP-PPPoE to restart the
>   firewall whenever it comes up?

I can't give good answers here. The firewall package is that which
shipped with RH8.0. While I've since run Bastille, I didn't use it to
mess with IPchains. But what you say may again point to timing as
pppoe tries to readjust to a new ipaddress. As for your last question,
the only configuration parameter in roaring penguin pppoe utility is
to state that I've a stand alone machine. Did you have something else
in mind here?

   One last thought ... what does it mean when you say "My eth0 is
   made active during boot, for I can run ifconfig and see that it is
   up as soon as I've finished booting"? The term "active" has no
   specific meaning,

I originally had diven my machine an IP address (something like
168.192.0.1) because I've had my mahcine on a LAN, but now am just
happy to get it to work as a stand-along workstation. When eth0 had an
address, ifconfig recported it; when I made a DSL connection, the
number changed to whatever my provider provides. I subsequently tried
to cut the IP address, and I believe (not sure) that now ifconfig
shows the eth0 as up, but with noi address until pppoe is started..


Haines Brown
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Who is running Red Hat 8.0 and Roaring Penguin?

[Haines Brown]

    To remove the IPADDRESS from eth0, do
   ifconfig eth0 down
   ifconfig eth0 0.0.0.0 up

Yes, I did get rid of it. 

   > > Who is running Red Hat 8.0 and Roaring Penguin?
   > 
   > 15% of all linux users? ;-)

   Naw, not how many or percentile, but who, specifically,
   can help us with a replica of your system.  ;-)

My feeble attempt at humor.

   > With eth0 up and running, and having defined the inteface property in
   > network configuration, I then proceed to configure Roaring Penguin.
   > 
   > Before I do I run adsl-status and am told, naturally, that there's no
   > /etc/ppp/pppoe.conf file. I then proceed to configure Roaring Penguin
   > (I'm comfortable with that), and at the end save the
   > configuration. However, no /etc/ppp/pppoe.conf file shows up.

   locate pppoe.conf
    on my system reports:
   /etc/ppp/pppoe.conf
   /usr/local/rp-pppoe-3.5/configs/pppoe.conf

    I think that 'adsl-setup' should have created a
   'pppoe.conf' file.  Where it was placed, I'm not sure.

This turned out very interesting. Despite the message I quote, roaring
penguin under RH8.0 no longer stgores its configuration in
/etc/pppoe.conf. I know it stores info becasue when I rerun adsl-setup
I see it, but there's now no pppoe.conf file.

    Give Ray what he asked for. 
     "uname -a", "ifconfig -a", & "netstat -nr".  

I will when I can. switching hard disks when there's a bunch strung on
three different scsi channels is a pain.  So I have to leap in and out
fairly quickly. I'll get the info and pass it along asap.

    I've edited some IP addresses.  Here are mine:

Thanks. Info appreciated. I'll compare at this end as soon as I can.

And here is my pppoe.conf for your perusal:

   DNS1=
   DNS2= 000.000.000.000 ;-)

What's this? I have some onfiburation in
/etc/sysconfig/network-scripts/ifcfg.conf. It is somewwhats like your
own. But you have a much bigger ppp0e timeout value, and I may try
that because I'm begginng to seuspec a timing problem.

Haines 
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: firewall blocks ppp0?

[Ray Olszewski]

OK. Just as a reminder ... I don't run Red Hat here, and I don't currently 
run PPPoE on my Debian-based router. So I can't help with specifics at the 
level of what config file the RH-8.0 version or RP-PPPoE uses.

Having said that, I think you yourself have spotted the problem. A severely 
edited version of your report, below, focuses on it.

At 03:57 PM 11/25/02 -0500, Haines Brown wrote:
[...]
> > Script /usr/sbin/pppoe
> >       -p
> >       -I eth0
> >       -T 20
> >       -U
> >       -m 1412
> >       -D 0-0
> >       finished (pid 4906), status = 0x1

The problem you have here is with the -T setting. It tells pppoe to exit if 
there is no link-layer (ppp) traffic for 20 seconds.  As you go on to 
comment ...

>I don't understand why a successful connection results in a
>hangup. The -T timeout option of 20 seconds seems about the time it takes for
>my connection to die. I gather that timeout can cause trouble if
>there's no traffic. The solution is to use lcp-echo-internal option
>for pppd. The pppoe timeout should be about four times the LCP echo
>interval. Any idea where one implements the LCP echo option?

This is a pppd option ("lcp-echo-interval", not "lcp-echo-internal", BTW). 
Put it wherever the RH-8.0 implementation of pppd stores its settings (on 
my Debian system, this would be in /etc/ppp/options, but YMMV ... check 
*your* version of the pppd man page for this info).
[...]


--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski					-- Han Solo
Palo Alto, California, USA			  ray@comarre.com
-------------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: firewall blocks ppp0?

[Chuck Gelm]

Haines Brown wrote:
<big snip> 
 
> I originally had diven my machine an IP address (something like
> 168.192.0.1) because I've had my mahcine on a LAN, but now am just
> happy to get it to work as a stand-along workstation. When eth0 had an
> address, ifconfig recported it; when I made a DSL connection, the
> number changed to whatever my provider provides. I subsequently tried
> to cut the IP address, and I believe (not sure) that now ifconfig
> shows the eth0 as up, but with noi address until pppoe is started.

 eth0 never gets an IP address in my situation.
 Are you 'forcing' an IP address on via 'ip-up' or something?
 RP-PPPOE assigns an IP address to ppp0, not eth0.

 After 'normal' install of rp-pppoe-3.5  ;-) 
 Run:     I put adsl-start in my /etc/rd.d/rc.local script.
 I edited no files (other than rc.local) to get RP-PPPOE to work.
:-|
 This how it works for me.  Perhaps your is different. But....
Again I mention that the eth# device that attaches to the DSL modem
does not have an IP address.  Ala:

This is my LAN NIC:
eth0 Link encap:Ethernet  HWaddr 00:20:AF:10:63:D3  
     inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
     UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
     RX packets:10581519 errors:14 dropped:0 overruns:14 frame:14
     TX packets:11506381 errors:0 dropped:0 overruns:0 carrier:0
     collisions:1837 txqueuelen:100 
     RX bytes:2017650304 (1924.1 Mb)  TX bytes:3952593210 (3769.4 Mb)
     Interrupt:5 Base address:0x300 

This is my DSL NIC:
eth1 Link encap:Ethernet  HWaddr 00:20:AF:19:F4:58  
     UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
     RX packets:2260684 errors:4 dropped:0 overruns:4 frame:4
     TX packets:1435674 errors:0 dropped:0 overruns:0 carrier:3
     collisions:8 txqueuelen:100 
     RX bytes:3069518901 (2927.3 Mb)  TX bytes:115487500 (110.1 Mb)
     Interrupt:10 Base address:0x200 

It is my ppp# device that gets an IP address from my DSL-ISP provider:
ppp0 Link encap:Point-to-Point Protocol  
     inet addr:123.456.789.210  P-t-P:123.456.789.1 
Mask:255.255.255.255
     UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
     RX packets:2253580 errors:0 dropped:0 overruns:0 frame:0
     TX packets:1429007 errors:0 dropped:0 overruns:0 carrier:0
     collisions:0 txqueuelen:10 
     RX bytes:3465872234 (3305.3 Mb)  TX bytes:118613004 (113.1 Mb)

HTH, Chuck

> Haines Brown
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Help with Roaring Penguin & Red Hat 8.0?

[Chuck Gelm]

Haines Brown wrote:
<big snip>
> Thanks. Info appreciated. I'll compare at this end as soon as I can.
> 
> And here is my pppoe.conf for your perusal:
> 
>    DNS1=
>    DNS2= 000.000.000.000 ;-)
> 
> What's this? I have some onfiburation in
> /etc/sysconfig/network-scripts/ifcfg.conf. It is somewwhats like your
> own. But you have a much bigger ppp0e timeout value, and I may try
> that because I'm begginng to seuspec a timing problem.

 rp-pppoe may recognize that your system is a different distribution
than mine and places configuration files in different places as
appropriate.  I showed you how I looked for pppoe.conf, but you
didn't show us how you searched for 'pppoe.conf'.  I'm worried
that you only looked in a specific directory. :-|  Maybe your
distribution doesn't even use a file named 'pppoe.conf'! :-|

 Other than adding "adsl-start" to my 'rc.local',
I edited no other files.  The 'install' procedure and
'adsl-setup' is all I did. :-|

 I see that it is difficult for you to view settings whereas
you need to reboot a busy system.  My system ("firewall") is
an old 80486dx33 that I bought a year or so ago for 5 USD. :-)

 I'm still holding on to these concepts:

- RP-PPPOE creates an IPCHAINS ruleset & Red Hat 8.0 uses IPTABLES.
  i.e. You never end up with 'valid' instructions to the kernel
  about handling packets with your DSL modem.

- eth0 should not have an IP address.
  ppp0 gets the IP address.
  Notice that my eth1 device does appear in my 'netstat -nr' report,
  and that my ppp0 device does.

HTH, Chuck
> 
> Haines
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Help with Roaring Penguin & Red Hat 8.0?

[Haines Brown]

Well, made some progress, but not quite there yet.

I find that adsl-configure does not write the configuration file as it
should in /etc/ppp/pppoe.conf. I had to get the default sample and
reconstruct it by hand.

Not only does adsl-configure not write a configuration file, but
adsl-stop does not work either. That is, using the new configuration
file, I run adsl-start, and then when I check with ifconfig, I see
that I indeed now have ppp0 running, and it has been given an IP
address by my DSL provider.

Unfortunately, though, that's as far as I get. For example, when I try
to ping something, ping just hangs. adsl-status tells me the link is
down, even though ppp0 has a valid IP address.

Then when I run adsl-stop, it has no effect! The ppp0 process won't
die! The only way I can get rid of it is to run ifconfig down
ppp0. That does remove the entry in the table that comes up when I run
ifconfig.

However, it does not really remove the process from memory. So, if I
run adsl-start again, it creates ppp1, even though ifconfig does not
list ppp0. If I do it gain, I get ppp2, etc. Each time I run
adsl-start, it creates a new thread that is numbered in sequence, but
adsl-stop does not kill the thread. Each of these pppN processes has
its own assigned IP address.
 
>  I'm still holding on to these concepts:
> 
> - RP-PPPOE creates an IPCHAINS ruleset & Red Hat 8.0 uses IPTABLES.
> i.e. You never end up with 'valid' instructions to the kernel about
> handling packets with your DSL modem.

This terrifies me, knowing absolutely nothing of ip
tables. Furthermore, it strikes me as very odd that RH 8.0 would ship
with an application (rp is part of the distribution of RH 8.0) that is
incompatible with the shipped kernel. Mistakes can occur, of course,
but wouldn't we have heard about it by now?

Is there any way I can verify that iptables is in fact blocking
packets sent by pppoe, or that roaring penguin depends on ipchains? I
gather that ipchains and iptables can co-exist, so how do I verify
that the specific rules are in conflict?

> - eth0 should not have an IP address.  ppp0 gets the IP address.
> Notice that my eth1 device does appear in my 'netstat -nr' report,
> and that my ppp0 device does.

eth0 has the address 168.192.0.1 on my present machine because at one
time eto0 was the intrface for a LAN. That it comes up with that
address one my this machine, even though it is stand-alone, does not
seem to prevent DSL from working. In any case, on the new machine I'm
trying to get to work, the eth0 now comes up with no address.

Haines
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Help with Roaring Penguin & Red Hat 8.0?

[Chuck Gelm]

Haines Brown wrote:
> 
> Well, made some progress, but not quite there yet.
<snip>
> Unfortunately, though, that's as far as I get. For example, when I try
> to ping something, ping just hangs. adsl-status tells me the link is
          ^^^^^^^^^  ^^^^^^^^^^^^^^^
What are you trying to ping, an IP address or a domain name?
This could be a routing problem.

> down, even though ppp0 has a valid IP address.
<snip>
> eth0 has the address 168.192.0.1 on my present machine because at one
> time eto0 was the intrface for a LAN. That it comes up with that
> address one my this machine, even though it is stand-alone, 
> does not seem to prevent DSL from working. In any case, on the new 
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
What does work?

> machine I'm trying to get to work, the eth0 now comes up with no
> address.

 What version of rp-pppoe are you trying to run?

Chuck

> Haines
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Help with Roaring Penguin & Red Hat 8.0?

[Ray Olszewski]

Haines --

While I cannot help you diagnose at the level of peculiarities in the 
interaction between RP-PPPoE and other parts of RH-8.0, I might be able to 
offer some suggestions based on "rounding up the usual suspects" for your 
configuration. If you'd like this, please post (from a time when ppp0 is up 
and configured) the complete, unedited output of the following commands:

         ifconfig -a
                 (to check the status of ALL interfaces)
         netstat -nr
                 (to check if you have a problem with your routing table)
         ipchains -nvL
         iptables -nvL
                 (one of those two will error out, but perhaps the other 
will succeed)
         ping a.b.c.d
                 (replace a.b.c.d with your default gateway, as reported by 
netstat -nr)
         ping e.f.g.h
                 (replace e.f.g.h with the IP address of ppp0)
                 (in these last 2 cases, if ping "just hangs", tell us what 
it reports when you
                 SIGINT (^C) out of it)

Now a couple of specifics, below.

At 04:50 PM 11/26/02 -0500, Haines Brown wrote:
[...]
> >  I'm still holding on to these concepts:
> >
> > - RP-PPPOE creates an IPCHAINS ruleset & Red Hat 8.0 uses IPTABLES.
> > i.e. You never end up with 'valid' instructions to the kernel about
> > handling packets with your DSL modem.
>
>This terrifies me, knowing absolutely nothing of ip
>tables. Furthermore, it strikes me as very odd that RH 8.0 would ship
>with an application (rp is part of the distribution of RH 8.0) that is
>incompatible with the shipped kernel. Mistakes can occur, of course,
>but wouldn't we have heard about it by now?

My memory of RP-PPPoE is that it is extremely easy to misconfigure it; the 
app is very tempramental. If you are not doing a "by the book" 
configuration of it (RH seems to want you to use an X-based app called 
"Internet Druid", whatever that is), you might be running into some 
sufficiently uncommon problem that it doesn't get talked about. Or there 
may not be very many RH 8.0 users running RP-PPPoE (your humorously-offered 
15% estimate seems extraordinarily high to me).

>Is there any way I can verify that iptables is in fact blocking
>packets sent by pppoe, or that roaring penguin depends on ipchains? I
>gather that ipchains and iptables can co-exist, so how do I verify
>that the specific rules are in conflict?

First, the PPPoE part of RP does NOT depends on either ipchains or 
iptables. RP-PPPoE seems to have an associated firewall that uses ipchains. 
But since you are running a standalone system, not a router, you should be 
able to connect just fine (for test purposes, anyway) with no firewall 
rulesets (either ipchains or iptables) installed.

Second, the way to find out what rules are blocking packets is to list your 
rules. The "iptables -nvL" command does this for iptables; if it does not 
work, then there is no other way to check.

Third, ipchains and iptables CANNOT "co-exist". 2.2.x kernels use ipchains; 
2.4.x kernels use iptables. Period. What *might* be the case is that RH 
supplies some userspace program that lets you configure an iptables kernel 
using ipchains syntax (but if they do, it is not a backward-compatibility 
app I am acquainted with ... Debian seems to have nothing like it). There 
was such an app that handled the similar change in firewalling code between 
2.0.x kernels (ipfwadm) and 2.2.x kernels (ipchains).



--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski					-- Han Solo
Palo Alto, California, USA			  ray@comarre.com
-------------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Help with Roaring Penguin & Red Hat 8.0?

[Haines Brown]

> > Well, made some progress, but not quite there yet.  <snip> >
> Unfortunately, though, that's as far as I get. For example, when I
> try > to ping something, ping just hangs. adsl-status tells me the
> link is ^^^^^^^^^ ^^^^^^^^^^^^^^^ What are you trying to ping, an IP
> address or a domain name?  This could be a routing problem.

I first tried a common domain name, and when that didn't work, the IP
address of my DNS, which is valid for sure.

> > down, even though ppp0 has a valid IP address.  <snip> > eth0 has
> the address 168.192.0.1 on my present machine because at one > time
> eto0 was the intrface for a LAN. That it comes up with that >
> address one my this machine, even though it is stand-alone, > does
> not seem to prevent DSL from working. In any case, on the new
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ What does work?

Simply having a handshake with the DSL server and obtaining from it an
IP address. So hardware (and port, I assume) work.
> 
> > machine I'm trying to get to work, the eth0 now comes up with no
> > address.
> 
>  What version of rp-pppoe are you trying to run?

I'll find out when I manage to boot the other HD, but it is the
default roaring penguin packaged with RH 8.0.

Haines
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Who is running Red Hat 8.0 and Roaring Penguin?

[Haines Brown]

Here's the result of my run today:

========================

a) redhat-config-network. It shows both eth0 (ethernet) and ppp0 (xDSL)
as being inactive.

========================

b) ifconfig shows etho0 up (how do I reconcile with the above?) and with 
no IP address.

========================

c) I bring to bring ppp0 by what I thought was a straightforward way:

# ifconfig ppp0 up
ppp0: unknown interface: No such device

========================

d) While adsl-start has not yet timed out:
 	
# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:03:47:CA:FA:E2
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:24 errors:0 dropped:0 overruns:0 frame:0
          TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:1821 (1.7 Kb)  TX bytes:1131 (1.1 Kb)
          Interrupt:11 Base address:0x9000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:250 errors:0 dropped:0 overruns:0 frame:0
          TX packets:250 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:17268 (16.8 Kb)  TX bytes:17268 (16.8 Kb)

ppp0      Link encap:Point-to-Point Protocol
          inet addr:64.252.166.131  P-t-P:64.252.160.1  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
          RX packets:9 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:577 (577.0 b)  TX bytes:495 (495.0 b)

========================

e) Then adsl-start times out:

# adsl-start
/sbin/adsl-start: line 221: 18532 Terminated $CONNECT "$@" >/dev/null 2>&1

========================

f) I then look at my routing table:

# netstat -nr
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
64.252.160.1    0.0.0.0         255.255.255.255 UH       40 0          0 ppp0
127.0.0.0       0.0.0.0         255.0.0.0       U        40 0          0 lo
0.0.0.0         64.252.160.1    0.0.0.0         UG       40 0          0 ppp0

========================

g) Kernel not using ipchains

# ipchains -nvL
ipchains: Incompatible with this kernel

========================

h) Here is the iptables

# iptables -nvL
Chain INPUT (policy ACCEPT 2 packets, 95 bytes)
 pkts bytes target     prot opt in     out     source               destination
  259 18589 RH-Lokkit-0-50-INPUT  all  --  *      *       0.0.0.0/0
0.0.0.0/0

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain OUTPUT (policy ACCEPT 278 packets, 18866 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain RH-Lokkit-0-50-INPUT (1 references)
 pkts bytes target     prot opt in     out     source               destination
    7  1226 ACCEPT     udp  --  *      *       206.141.193.55       0.0.0.0/0
        udp spt:53 dpts:1025:65535
    0     0 ACCEPT     udp  --  *      *       206.73.20.40         0.0.0.0/0
        udp spt:53 dpts:1025:65535
    0     0 ACCEPT     udp  --  eth0   *       0.0.0.0/0            0.0.0.0/0
        udp spts:67:68 dpts:67:68
    0     0 ACCEPT     udp  --  eth1   *       0.0.0.0/0            0.0.0.0/0
        udp spts:67:68 dpts:67:68
  250 17268 ACCEPT     all  --  lo     *       0.0.0.0/0            0.0.0.0/0

    0     0 REJECT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0
        tcp flags:0x16/0x02 reject-with icmp-port-unreachable
    0     0 REJECT     udp  --  *      *       0.0.0.0/0            0.0.0.0/0
        udp reject-with icmp-port-unreachable

========================

i) I can ping my gateway:

# ping 64.252.160.1
PING 64.252.160.1 (64.252.160.1) from 64.252.166.131 : 56(84) bytes of data.
64 bytes from 64.252.160.1: icmp_seq=1 ttl=64 time=15.6 ms
64 bytes from 64.252.160.1: icmp_seq=2 ttl=64 time=16.5 ms
64 bytes from 64.252.160.1: icmp_seq=3 ttl=64 time=18.3 ms
64 bytes from 64.252.160.1: icmp_seq=4 ttl=64 time=16.8 ms

--- 64.252.160.1 ping statistics ---
4 packets transmitted, 4 received, 0% loss, time 3006ms
rtt min/avg/max/mdev = 15.655/16.837/18.303/0.963 ms

========================

j) I can also ping my ppp0's address

# ping 64.252.166.131
PING 64.252.166.131 (64.252.166.131) from 64.252.166.131 : 56(84) bytes of data.
64 bytes from 64.252.166.131: icmp_seq=1 ttl=64 time=0.038 ms
64 bytes from 64.252.166.131: icmp_seq=2 ttl=64 time=0.027 ms
64 bytes from 64.252.166.131: icmp_seq=3 ttl=64 time=0.029 ms

--- 64.252.166.131 ping statistics ---
3 packets transmitted, 3 received, 0% loss, time 1998ms
rtt min/avg/max/mdev = 0.027/0.031/0.038/0.006 ms

========================

k) But I can't ping my ISP's domain name server:

# ping 206.73.20.40
PING 206.73.20.40 (206.73.20.40) from 64.252.166.131 : 56(84) bytes of data.

--- 206.73.20.40 ping statistics ---
10 packets transmitted, 0 received, 100% loss, time 9012ms

========================

Haines
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Who is running Red Hat 8.0 and Roaring Penguin?]

[Chuck Gelm]

Haines Brown wrote:
 
> Here's the result of my run today:
 
> a) redhat-config-network. It shows both eth0 (ethernet) and ppp0 (xDSL)
> as being inactive.

I think that this is OK.

> b) ifconfig shows etho0 up (how do I reconcile with the above?) and with
> no IP address.

I think that this is OK.

> c) I bring to bring ppp0 by what I thought was a straightforward way:
> 
> # ifconfig ppp0 up
> ppp0: unknown interface: No such device

 I think that 'adsl-start' should be the way to create device ppp0.
 I think that you should not be forcing ppp0 up by hand.

> d) While adsl-start has not yet timed out:
> 
> # ifconfig -a
> eth0      Link encap:Ethernet  HWaddr 00:03:47:CA:FA:E2
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:24 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:1821 (1.7 Kb)  TX bytes:1131 (1.1 Kb)
>           Interrupt:11 Base address:0x9000
> 
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:250 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:250 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:17268 (16.8 Kb)  TX bytes:17268 (16.8 Kb)
> 
> ppp0      Link encap:Point-to-Point Protocol
>           inet addr:64.252.166.131  P-t-P:64.252.160.1  Mask:255.255.255.255
>           UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
>           RX packets:9 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:3
>           RX bytes:577 (577.0 b)  TX bytes:495 (495.0 b)

 This looks good to me.

> e) Then adsl-start times out:
> 
> # adsl-start
> /sbin/adsl-start: line 221: 18532 Terminated $CONNECT "$@" >/dev/null 2>&1

 Umm, is this a 'time-out' or a script execution failure?
 My adsl-start file has only 197 lines.
 A line nearly identical to your appears in my line 152:
"$CONNECT "$@" >/dev/null 2>&1 &"
 Except my line is terminated with a "&".
 This line appears after a comment:
# Start the connection in the background unless we're debugging

> f) I then look at my routing table:
> 
> # netstat -nr
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
> 64.252.160.1    0.0.0.0         255.255.255.255 UH       40 0          0 ppp0
> 127.0.0.0       0.0.0.0         255.0.0.0       U        40 0          0 lo
> 0.0.0.0         64.252.160.1    0.0.0.0         UG       40 0          0 ppp0

 This may be part of a problem.  Notice that your routing table
 has only a ppp0 device (not counting 'lo') and no eth0 device ...

> g) Kernel not using ipchains
> 
> # ipchains -nvL
> ipchains: Incompatible with this kernel

Here is my ipchains -nvL
Chain input (policy ACCEPT: 12771974 packets, 4905163086 bytes):
 pkts bytes target     prot opt    tosa tosx  ifname     mark      
outsize  source                destination           ports
 5336  423K DENY       udp  ----l- 0xFF 0x00 
ppp+                           0.0.0.0/0           
0.0.0.0/0             * ->   0:1023
  744 37331 DENY       tcp  ----l- 0xFF 0x00 
ppp+                           0.0.0.0/0           
0.0.0.0/0             * ->   0:1023
 1149 55368 DENY       tcp  -y--l- 0xFF 0x00 
ppp+                           0.0.0.0/0           
0.0.0.0/0             * ->   *
   53  2489 DENY       icmp ----l- 0xFF 0x00 
ppp+                           0.0.0.0/0           
0.0.0.0/0             8 ->   *
Chain forward (policy DENY: 0 packets, 0 bytes):
 pkts bytes target     prot opt    tosa tosx  ifname     mark      
outsize  source                destination           ports
1376K   85M MASQ       all  ------ 0xFF 0x00 
*                              0.0.0.0/0           
0.0.0.0/0             n/a
Chain output (policy ACCEPT: 12894352 packets, 3893742239 bytes):

 Notice that my IPCHAINS uses ppp+
  (perhaps the + indicates all ppp# devices)
 and does not mention my eth0 nor eth1 devices.
 
 Likewise notice that ppp* is never mentioned in your IPTABLES ruleset,
 only eth0 and eth1 which are 'down'. :-|

 It appears that rp-pppoe has not modified your IPTABLES ruleset.

> h) Here is the iptables
> 
> # iptables -nvL
> Chain INPUT (policy ACCEPT 2 packets, 95 bytes)
>  pkts bytes target     prot opt in     out     source               destination
>   259 18589 RH-Lokkit-0-50-INPUT  all  --  *      *       0.0.0.0/0
> 0.0.0.0/0
> 
> Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
>  pkts bytes target     prot opt in     out     source               destination
> 
> Chain OUTPUT (policy ACCEPT 278 packets, 18866 bytes)
>  pkts bytes target     prot opt in     out     source               destination
> 
> Chain RH-Lokkit-0-50-INPUT (1 references)
>  pkts bytes target     prot opt in     out     source               destination
>     7  1226 ACCEPT     udp  --  *      *       206.141.193.55       0.0.0.0/0
>         udp spt:53 dpts:1025:65535
>     0     0 ACCEPT     udp  --  *      *       206.73.20.40         0.0.0.0/0
>         udp spt:53 dpts:1025:65535
>     0     0 ACCEPT     udp  --  eth0   *       0.0.0.0/0            0.0.0.0/0
>         udp spts:67:68 dpts:67:68
>     0     0 ACCEPT     udp  --  eth1   *       0.0.0.0/0            0.0.0.0/0
>         udp spts:67:68 dpts:67:68
>   250 17268 ACCEPT     all  --  lo     *       0.0.0.0/0            0.0.0.0/0
> 
>     0     0 REJECT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0
>         tcp flags:0x16/0x02 reject-with icmp-port-unreachable
>     0     0 REJECT     udp  --  *      *       0.0.0.0/0            0.0.0.0/0
>         udp reject-with icmp-port-unreachable

> i) I can ping my gateway:
> 
> # ping 64.252.160.1
> PING 64.252.160.1 (64.252.160.1) from 64.252.166.131 : 56(84) bytes of data.
> 64 bytes from 64.252.160.1: icmp_seq=1 ttl=64 time=15.6 ms
> 64 bytes from 64.252.160.1: icmp_seq=2 ttl=64 time=16.5 ms
> 64 bytes from 64.252.160.1: icmp_seq=3 ttl=64 time=18.3 ms
> 64 bytes from 64.252.160.1: icmp_seq=4 ttl=64 time=16.8 ms
> 
> --- 64.252.160.1 ping statistics ---
> 4 packets transmitted, 4 received, 0% loss, time 3006ms
> rtt min/avg/max/mdev = 15.655/16.837/18.303/0.963 ms
> 
> ========================
> 
> j) I can also ping my ppp0's address
> 
> # ping 64.252.166.131
> PING 64.252.166.131 (64.252.166.131) from 64.252.166.131 : 56(84) bytes of data.
> 64 bytes from 64.252.166.131: icmp_seq=1 ttl=64 time=0.038 ms
> 64 bytes from 64.252.166.131: icmp_seq=2 ttl=64 time=0.027 ms
> 64 bytes from 64.252.166.131: icmp_seq=3 ttl=64 time=0.029 ms
> 
> --- 64.252.166.131 ping statistics ---
> 3 packets transmitted, 3 received, 0% loss, time 1998ms
> rtt min/avg/max/mdev = 0.027/0.031/0.038/0.006 ms
> 
> ========================
> 
> k) But I can't ping my ISP's domain name server:
> 
> # ping 206.73.20.40
> PING 206.73.20.40 (206.73.20.40) from 64.252.166.131 : 56(84) bytes of data.
> 
> --- 206.73.20.40 ping statistics ---
> 10 packets transmitted, 0 received, 100% loss, time 9012ms

 I get the same results when I ping 206.73.20.40.
 100% failure.  So:

a. Sorry, I don't know Red Hat's 'redhat-config-network'.
b. You do not want eth# up.
   'ifconfig eth0 down' before running adsl-start.
c. Do not 'bring up' ppp0 yourself.  Let adsl-start do it.
d. '# ifconfig -a' looks perfect
e. I think 'adsl-start' fails rather than 'times out'.
f. Output of 'netstat -nr' looks fine.
g. Yes, kernel 2.4.x does not use IPCHAINS.
h. IPTABLES indicates no knowledge/use of ppp0.  :-(
i. I can ping your gateway too. ;-)
j. Not applicable.
k. I cannot ping your DNS either.

Conclusion:

- rp-pppoe-v? has not been correctly installed and/or configured.
  e.g. Your adsl-start script 'fails'.
  I suggest that if your version is not the 'current' one,
  download and install the current version from Roaring Penguin.
  I think that they have RPMs.  Hopefully a release that creates
  an IPTABLES ruleset is available.

- You do not have a 'working' iptables ruleset because ppp0
  is not mentioned.

HTH, Chuck

> Haines
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Who is running Red Hat 8.0 and Roaring Penguin?

[Chuck Gelm]

I added linux-newbie back into the address field.

Haines Brown wrote:
> 
> Chuck,
> 
> Thanks for your helpful reply. I'll respond to it more fully after
> I've had a chance to visit the RH8.0 machine having the problem.
> 
> I did not include in my report that I originally had a problem getting
> roaring penguin to build a configuration file. Because when I re-ran
> adsl-setup it new my settings (apparently) previously entered, I
> assumed that the configuration was stored elsewhere even though there
> was no longer a /etc/ppp/pppoe.conf file.

 Your previous responses to adsl-setup are stored.
 If adsl-setup never created a configuration file,
 re-running it with the same responses might not create one either.
 :-|
 Was there ever a /etc/ppp/pppoe.conf file?
 
> But I just now visited the roarding penguin site to download a new
> version, and I see that the configuration file remains the same as
> before. So I conclude my rppppoe is broken, did not install properly,
> or there's a permission problem somewhere preventing the creation of
> its configuration file.
> 
> I'll look at the script as you suggest and otherwise snoop around
> roaring penguin.
> 
> Currently, my present (working) system has in its routing table the
> line:
> 
>   192.168.0.0   0.0.0.0   255.255.255.0   U   40   0   0   eth0
> 
> but on my present machine, I gave eth0 a static address because it was
> once part of a LAN. On my other machine, as you point out, there's no
> eth0 line, but what address should it have if it were present on a
> stand-alone machine? 0.0.0.0?
> 
> I think I'll add eth0 to the routing table with that address to see
> what happens. Some of the iptables problems may be resolved once I
> resolve the two problems above. I'll get back to the list after I've
> been able to explored this.

 I think I have said this before, several times before;
the eth# device that connects to the DSL modem should
not have an IP address (when you run adsl-start).

 rp-pppoe will not work if the eth# device already has an IP address.

 ppp0 gets the IP address (from adsl-start).

 The eth# device must be UP and RUNning and have no IP address.

 Suggestion:
 If you have both a DSL modem and a LAN, put another ethernet NIC
in the computer. A few dollars for an old 3c509, NE2000, whatever
card should be do-able.  Then let RedHat have its way with the eth0
device and configure RP-pppoe to use the eth1 device.
;-)
HTH, Chuck

> Haines
> 
>
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Who is running Red Hat 8.0 and Roaring Penguin?

[Haines Brown]

Chuck,

I've revisited my drive with RH 8.0, and while the situation is
different, not sure I've made much progress. After messing around last
time, after booting eth0 was not seen. And so I had to deal with that
first. Here's the result, which should be ok.

  # ifconfig -a

  eth0      Link encap:Ethernet  HWaddr 00:03:47:CA:FA:E2
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:400 (400.0 b)  TX bytes:0 (0.0 b)
          Interrupt:11 Base address:0xb000

  lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:482 errors:0 dropped:0 overruns:0 frame:0
          TX packets:482 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:33284 (32.5 Kb)  TX bytes:33284 (32.5 Kb)

I had been running rp-pppoe 3.4-7, but now upgraded it to 3.5-1. When I
run adsl-setup to create a new configuration, I discovered that this
time a /etc/ppp/pppoe.conf file is created. Clearly the distribution
copy of roarding penguin was broken. When I run adsl-start, I now get
a proper response and no hang:

    # adsl-start
  . Connected!

Now my interfaces are looking good:

  # ifconfig -a
  eth0      Link encap:Ethernet  HWaddr 00:03:47:CA:FA:E2
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:31 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:2490 (2.4 Kb)  TX bytes:2260 (2.2 Kb)
          Interrupt:11 Base address:0xb000

  lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:482 errors:0 dropped:0 overruns:0 frame:0
          TX packets:482 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:33284 (32.5 Kb)  TX bytes:33284 (32.5 Kb)

  ppp0      Link encap:Point-to-Point Protocol
          inet addr:64.252.168.146  P-t-P:64.252.160.1  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
          RX packets:10 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:864 (864.0 b)  TX bytes:1298 (1.2 Kb)

However, I find that my routing table still missing eth0

  # netstat -nr
  Kernel IP routing table
  Destination  Gateway      Genmask         Flags MSS Window  irtt Iface
  64.252.160.1 0.0.0.0      255.255.255.255 UH     40 0       0 ppp0
  127.0.0.0    0.0.0.0      255.0.0.0       U      40 0       0 lo
  0.0.0.0      64.252.160.1 0.0.0.0         UG     40 0       0 ppp0

I check with route:

  # route
  Kernel IP routing table
  Destination     Gateway         Genmask         Flags ...   Use Iface
  1.160.252.64.sn *               255.255.255.255 UH    ...   0 ppp0
  127.0.0.0       *               255.0.0.0       U     ...   0 lo
  default         1.160.252.64.sn 0.0.0.0         UG    ...   0 ppp0

So I try to add it:

  # route add eth0
  SIOCADDRT: No such device

I try to ping my gateway as reported by netstat above: 

  # ping 64.252.160.1

That is successful, but trying to ping the ppp0 address failed:

  # ping 1.160.252.64

And other pings failed.

Haines
  


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Who is running Red Hat 8.0 and Roaring Penguin?

[Chuck Gelm]

Hi, Haines:

 That ppp0 IP address in your route looks odd.
1.160.252.64.sn 
            ^^^   ?
 Perhaps it is a truncated FQDN.  More...

Haines Brown wrote:
> 
> Chuck,
> 
> I've revisited my drive with RH 8.0, and while the situation is
> different, not sure I've made much progress. After messing around last
> time, after booting eth0 was not seen. And so I had to deal with that
> first. Here's the result, which should be ok.
> 
>   # ifconfig -a
> 
>   eth0      Link encap:Ethernet  HWaddr 00:03:47:CA:FA:E2
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:6 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:400 (400.0 b)  TX bytes:0 (0.0 b)
>           Interrupt:11 Base address:0xb000
> 
>   lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:482 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:482 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:33284 (32.5 Kb)  TX bytes:33284 (32.5 Kb)
> 
> I had been running rp-pppoe 3.4-7, but now upgraded it to 3.5-1. When I
> run adsl-setup to create a new configuration, I discovered that this
> time a /etc/ppp/pppoe.conf file is created. Clearly the distribution
> copy of roarding penguin was broken. When I run adsl-start, I now get
> a proper response and no hang:
> 
>     # adsl-start
>   . Connected!
> 
> Now my interfaces are looking good:
> 
>   # ifconfig -a
>   eth0      Link encap:Ethernet  HWaddr 00:03:47:CA:FA:E2
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:31 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:2490 (2.4 Kb)  TX bytes:2260 (2.2 Kb)
>           Interrupt:11 Base address:0xb000
> 
>   lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:482 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:482 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:33284 (32.5 Kb)  TX bytes:33284 (32.5 Kb)
> 
>   ppp0      Link encap:Point-to-Point Protocol
>           inet addr:64.252.168.146  P-t-P:64.252.160.1  Mask:255.255.255.255
>           UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
>           RX packets:10 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:3
>           RX bytes:864 (864.0 b)  TX bytes:1298 (1.2 Kb)
> 
> However, I find that my routing table still missing eth0
> 
>   # netstat -nr
>   Kernel IP routing table
>   Destination  Gateway      Genmask         Flags MSS Window  irtt Iface
>   64.252.160.1 0.0.0.0      255.255.255.255 UH     40 0       0 ppp0
>   127.0.0.0    0.0.0.0      255.0.0.0       U      40 0       0 lo
>   0.0.0.0      64.252.160.1 0.0.0.0         UG     40 0       0 ppp0
> 
> I check with route:
> 
>   # route
>   Kernel IP routing table
>   Destination     Gateway         Genmask         Flags ...   Use Iface
>   1.160.252.64.sn *               255.255.255.255 UH    ...   0 ppp0
>   127.0.0.0       *               255.0.0.0       U     ...   0 lo
>   default         1.160.252.64.sn 0.0.0.0         UG    ...   0 ppp0
                    ^^^^^^^^^^^^^^^

 This may be a truncated fully qualified domain name (FQDN)
 and may not be ping-able.  Check with
# route -n
 instead.  I wonder what your (route -n) was before and after
adsl-start.

 Actually, I think that 'netstat -nr' is identical to 'route -n'.

> So I try to add it:
> 
>   # route add eth0
>   SIOCADDRT: No such device
> 
> I try to ping my gateway as reported by netstat above:
> 
>   # ping 64.252.160.1

 This is an external IP address.  This is great! :-)

> That is successful, but trying to ping the ppp0 address failed:
> 
>   # ping 1.160.252.64

 This is not the ppp0 address, 64.252.168.146 was.

> And other pings failed.

 ;-) What other pings?  Your other mention of an unpingable
 address was unpingable by others too.  :-|

 I can ping 'aol.com' and 'yahoo.com'.  Can you?
 This will test your DNS server.

 As per your report, everything looks fine...
 except your choice of IP addresses to ping.

HTH, Chuck

> Haines
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Who is running Red Hat 8.0 and Roaring Penguin?

[Ray Olszewski]

Haines -- You are not here reporting any problem with your configuration. 
Everything you list below is as it should be with PPPoE. In particular, 
your routing table does not list eth0 because you have (and need have) no 
routes that use it; it isn't even a configured interface (that is, no IP 
address). It just operates at the link level, where it provides an Ethernet 
link that encapsulates a ppp link (a different link-level protocol). The 
ppp link carries your network-layer (IP) traffic.

The next test is to try using the connection to the Internet that exists. 
As I already said, if you need an IP address that you know responds to 
pings, please feel free to use mine (which I listed in a prior message, or 
you can check the Received: headers here). Or just try doing whatever it is 
you actually do on this computer and see if it works.

The ping you specifically report trying that fails, namely

           # ping 1.160.252.64

no doubt fails because it is not your ppp0 address, which is (according to 
ifconfig) 64.252.168.146 . The address that fails is your gateway address 
in reverse order; I can't guess where you might have picked that up from.

Just to be completely clear on this, I **can** ping both your gateway 
address and your ppp0 address (but not the bogus address you report as your 
gateway in the ping test), suggesting that you are connected (though the 
second success may be a trick, depending on how the ISP implements ppp at 
its end). Here are my results:

autovcr@kuryakin:~$ ping 1.160.252.64
PING 1.160.252.64 (1.160.252.64): 56 data bytes

--- 1.160.252.64 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
autovcr@kuryakin:~$ ping 64.252.160.1
PING 64.252.160.1 (64.252.160.1): 56 data bytes
64 bytes from 64.252.160.1: icmp_seq=0 ttl=47 time=98.9 ms
64 bytes from 64.252.160.1: icmp_seq=1 ttl=47 time=97.5 ms

--- 64.252.160.1 ping statistics ---
3 packets transmitted, 2 packets received, 33% packet loss
round-trip min/avg/max = 97.5/98.2/98.9 ms
autovcr@kuryakin:~$ ping 64.252.168.146
PING 64.252.168.146 (64.252.168.146): 56 data bytes
64 bytes from 64.252.168.146: icmp_seq=0 ttl=110 time=118.9 ms
64 bytes from 64.252.168.146: icmp_seq=1 ttl=110 time=135.3 ms
64 bytes from 64.252.168.146: icmp_seq=2 ttl=110 time=119.7 ms

--- 64.252.168.146 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 118.9/124.6/135.3 ms
autovcr@kuryakin:~$

You say "And other pings failed", but that's too vague to troubleshoot (and 
your getting your own gateway address wrong gives me some cause for 
skepticism regarding parts of your report that I cannot check). Tell us 
what you tried to ping and EXACTLY how the pings failed (pings fail in many 
distinct ways, and the differences are informative).

The main problem you *may* still have is with DNS. Since the ISP DNS server 
address you are using does not respond to pings (and cannot be reached 
using traceroute), you *may* be trying to use the wrong address. So you 
first want to try doing things that use actual IP addresses, not FQNs. If 
actual addresses work but not FQNs, your options are

         1. Get the correct IP addresses for your ISP's nameserves in 
/etc/resolv.conf
         2. Run BIND (or an equivalent) yourself and bypass the ISP's 
nameservers (your ISP *might* block this, but it is rare for them to do so).

At 05:23 PM 11/29/02 -0500, Haines Brown wrote:
>Chuck,
>
>I've revisited my drive with RH 8.0, and while the situation is
>different, not sure I've made much progress. After messing around last
>time, after booting eth0 was not seen. And so I had to deal with that
>first. Here's the result, which should be ok.
>
>   # ifconfig -a
>
>   eth0      Link encap:Ethernet  HWaddr 00:03:47:CA:FA:E2
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:6 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:400 (400.0 b)  TX bytes:0 (0.0 b)
>           Interrupt:11 Base address:0xb000
>
>   lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:482 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:482 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:33284 (32.5 Kb)  TX bytes:33284 (32.5 Kb)
>
>I had been running rp-pppoe 3.4-7, but now upgraded it to 3.5-1. When I
>run adsl-setup to create a new configuration, I discovered that this
>time a /etc/ppp/pppoe.conf file is created. Clearly the distribution
>copy of roarding penguin was broken. When I run adsl-start, I now get
>a proper response and no hang:
>
>     # adsl-start
>   . Connected!
>
>Now my interfaces are looking good:
>
>   # ifconfig -a
>   eth0      Link encap:Ethernet  HWaddr 00:03:47:CA:FA:E2
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:31 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:2490 (2.4 Kb)  TX bytes:2260 (2.2 Kb)
>           Interrupt:11 Base address:0xb000
>
>   lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:482 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:482 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:33284 (32.5 Kb)  TX bytes:33284 (32.5 Kb)
>
>   ppp0      Link encap:Point-to-Point Protocol
>           inet addr:64.252.168.146  P-t-P:64.252.160.1  Mask:255.255.255.255
>           UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
>           RX packets:10 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:3
>           RX bytes:864 (864.0 b)  TX bytes:1298 (1.2 Kb)
>
>However, I find that my routing table still missing eth0
>
>   # netstat -nr
>   Kernel IP routing table
>   Destination  Gateway      Genmask         Flags MSS Window  irtt Iface
>   64.252.160.1 0.0.0.0      255.255.255.255 UH     40 0       0 ppp0
>   127.0.0.0    0.0.0.0      255.0.0.0       U      40 0       0 lo
>   0.0.0.0      64.252.160.1 0.0.0.0         UG     40 0       0 ppp0
>
>I check with route:
>
>   # route
>   Kernel IP routing table
>   Destination     Gateway         Genmask         Flags ...   Use Iface
>   1.160.252.64.sn *               255.255.255.255 UH    ...   0 ppp0
>   127.0.0.0       *               255.0.0.0       U     ...   0 lo
>   default         1.160.252.64.sn 0.0.0.0         UG    ...   0 ppp0
>
>So I try to add it:
>
>   # route add eth0
>   SIOCADDRT: No such device
>
>I try to ping my gateway as reported by netstat above:
>
>   # ping 64.252.160.1
>
>That is successful, but trying to ping the ppp0 address failed:
>
>   # ping 1.160.252.64
>
>And other pings failed.
>
>Haines


--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski					-- Han Solo
Palo Alto, California, USA			  ray@comarre.com
-------------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs