Prev: Upgrading Kernel For First Time.
Next: ATI xorg - Slackware 12.2/Slamd64
From: Joe on 27 Jan 2010 23:58
(null) wrote on 01/26/10 21:11:

>
> But on port 80, it waits about 3 seconds, then says "No route to host".

You have port forwarding set up on port 80, forwarding to an unknown host.
Check your firewall (iptables) setup.

-Joe

--- news://freenews.netfront.net/ - complaints: news(a)netfront.net ---
From: jkaidor on 30 Jan 2010 12:48
In article <4B61196A.5000004(a)mailinator.com>, Joe <joe(a)mailinator.com> wrote:
>(null) wrote on 01/26/10 21:11:
>
>>
>> But on port 80, it waits about 3 seconds, then says "No route to host".
>
>You have port forwarding set up on port 80, forwarding to an unknown host.
>Check your firewall (iptables) setup.

*** That was it! Thanks, Joe & Henrik. I had imported an rc.firewall from
my remote site, where I had done a good deal of work to organize it, using
functions - had also changed it to adhere to the slackware standard command
line parameters ( start, stop , restart ).

**** OOPS. The remote site DOES use port forwarding. ***

As usual, it was my own fault. Shot myself in the foot.

I've been thinking of recoding my firewall script in Perl. Could
streamline it quite a bit. Probably shoot myself in the foot pretty good
doing that :).

- Jerry Kaidor
--
Jerry Kaidor
From: Grant on 30 Jan 2010 15:08
On 30 Jan 2010 17:48:29 GMT, jkaidor(a)sonic.net ((null)) wrote:

....
> **** OOPS. The remote site DOES use port forwarding. ***
>
> As usual, it was my own fault. Shot myself in the foot.

Finally solved :)
>
> I've been thinking of recoding my firewall script in Perl.

I can't see why one would write a firewall script in perl.

Bash (or your preferred shell) is smart enough to read parameter
files for drop block lists and so on. I've not felt the need
to go beyond bash (with perhaps gawk helpers) for rc.firewall.

Where's the win in converting a firewall script to perl?

Grant.
--
http://bugs.id.au/
From: jkaidor on 30 Jan 2010 23:44
In article <hv39m5lktkriet830jr0fl8g9ld5gebulr(a)4ax.com>,
Grant <g_r_a_n_t_(a)bugs.id.au> wrote:

>> I've been thinking of recoding my firewall script in Perl.
>
>I can't see why one would write a firewall script in perl.
>
>Bash (or your preferred shell) is smart enough to read parameter
>
>Where's the win in converting a firewall script to perl?
>
*** It's a personal win. I've been doing a lot of Perl for the past few
years, so I'm quite comfortable in it. I'm sure I might think differently
if I'd coded my past 100K lines in Bash, sed & AWK. I find my current
script to be very repetitive and error-prone, and would like to make it
a bit more elegant.

One advantage of Perl is that there are libraries for pretty much
anything you might want to do. For example, if I wanted to keep the
firewall config in an SQL database and access it via CGI, I could do that
easily. Not that I would do such a thing - it would demand an awful lot of
stuff be working before you got your firewall. There's a reason why
iptables is in /sbin :).

- Jerry Kaidor
--
Jerry Kaidor
First  |  Prev  | 
Pages: 1 2
Prev: Upgrading Kernel For First Time.
Next: ATI xorg - Slackware 12.2/Slamd64