Linux Newbie help
 help / color / mirror / Atom feed
From: Chuck Gelm <nc8q@gelm.net>
To: Linux Newbie <linux-newbie@vger.kernel.org>
Subject: Re: firewall blocks ppp0?
Date: Sun, 24 Nov 2002 12:02:57 -0500	[thread overview]
Message-ID: <3DE10641.5A70C2DF@gelm.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1978 bytes --]

How/why did your message arrive as

From:    Haines Brown <brownh@hartford-hwp.com>  Sat 6:55 PM
Subject: firewall blocks ppp0?
     To: linux-newbie@hartford-hwp.com
                     ^^^^^^^^^^^^^^^^^
                      ???????????????

This does not allow a 'reply all'    :-(

Dear Haines Brown:

 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.

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

You can:

- reconfigure (make config) your kernel to use IPCHAINS.

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

HTH, Chuck

Haines Brown wrote:
> 
> 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

[-- Attachment #2: nsmail8M.TMP --]
[-- Type: message/delivery-status, Size: 384 bytes --]

[-- Attachment #3: nsmailIN.TMP --]
[-- Type: message/rfc822, Size: 2641 bytes --]

From: Chuck Gelm <nc8q@gelm.net>
To: Haines Brown <brownh@hartford-hwp.com>
Cc: linux-newbie@hartford-hwp.com
Subject: Re: firewall blocks ppp0?
Date: Sun, 24 Nov 2002 11:48:58 -0500
Message-ID: <3DE102FA.85D8F85D@gelm.net>

Dear Haines Brown:

 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.

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

You can:

- reconfigure (make config) your kernel to use IPCHAINS.

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

HTH, Chuck

Haines Brown wrote:
> 
> 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


             reply	other threads:[~2002-11-24 17:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-24 17:02 Chuck Gelm [this message]
2002-11-24 18:14 ` firewall blocks ppp0? Haines Brown
  -- strict thread matches above, loose matches on Subject: below --
2002-11-23 23:55 Haines Brown
     [not found] ` <3DE102FA.85D8F85D@gelm.net>
2002-11-24 18:01   ` Haines Brown
2002-11-24 18:58     ` Ray Olszewski
2002-11-25 20:57       ` Haines Brown
2002-11-25 22:44         ` Ray Olszewski
2002-11-26  0:30         ` Chuck Gelm

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=3DE10641.5A70C2DF@gelm.net \
    --to=nc8q@gelm.net \
    --cc=linux-newbie@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