How to configure firewall to not reply to pings?

Booting, installing, newbie
Post Reply
Message
Author
Guest

How to configure firewall to not reply to pings?

#1 Post by Guest »

Hi all
i installed linux firewall and to test it i used grc site,it passed the stealth test but failed to block pings:
[quote]
Ping Reply: RECEIVED (FAILED)

User avatar
mayakovski
Posts: 124
Joined: Sun 20 Nov 2005, 00:42
Location: Comox, BC, CANADA

#2 Post by mayakovski »

Google "Block Ping"

That should give you lots of ideas.

What Linux Firewall did you install?
Mayakovski
**********************
Puppy Linux | Barking Up The Right Tree

Compaq Armada 1580DMT | P150, 49MB RAM - 3.2 GB HD, Puppy 1.0.6
Compaq Deskpro EN | P3-733, 384 MB RAM - 80GB HD, Puppy 1.0.7

User avatar
gnomen
Posts: 65
Joined: Mon 11 Jul 2005, 11:21
Location: NORWAY

#3 Post by gnomen »

ShieldsUp! does report that my PC responds to pings, however this is not a security hazard -- in fact as explained on the Linux Firewall home site (www.projectfiles.com/firewall/), it is contrary to recommended standards to disable ping acknowledgement -- my ISP pings me, I think to check that I'm still there. But, the Linux Firewall docs state that if you are really paranoid, you can set "RFC_1122_COMPLIANT=no" in /etc/rc.d/rc.firewall to disable ping.
From BarryK developer news

http://www.goosee.com/puppy/news2005.htm

So try setting "RFC_1122_COMPLIANT=no" in /etc/rc.d/rc.firewall
fake it until you make it

User avatar
mayakovski
Posts: 124
Joined: Sun 20 Nov 2005, 00:42
Location: Comox, BC, CANADA

#4 Post by mayakovski »

Ah;

Linux Firewall is part of Puppy, how did I miss that. Must dig deeper.
Mayakovski
**********************
Puppy Linux | Barking Up The Right Tree

Compaq Armada 1580DMT | P150, 49MB RAM - 3.2 GB HD, Puppy 1.0.6
Compaq Deskpro EN | P3-733, 384 MB RAM - 80GB HD, Puppy 1.0.7

Clockman
Posts: 2
Joined: Fri 09 Jun 2006, 09:12

#5 Post by Clockman »

gnomen wrote:
ShieldsUp! does report that my PC responds to pings, however this is not a security hazard -- in fact as explained on the Linux Firewall home site (www.projectfiles.com/firewall/), it is contrary to recommended standards to disable ping acknowledgement -- my ISP pings me, I think to check that I'm still there. But, the Linux Firewall docs state that if you are really paranoid, you can set "RFC_1122_COMPLIANT=no" in /etc/rc.d/rc.firewall to disable ping.
From BarryK developer news

http://www.goosee.com/puppy/news2005.htm

So try setting "RFC_1122_COMPLIANT=no" in /etc/rc.d/rc.firewall

I am also new to Puppy 2 after years of Windozing. I also went to GRC.com and everything is fine except it respond to ping (ICMP) How do you turn this off? I clicked on the link provided above and its dead. I would like to try the command "RFC_1122_COMPLIANT=no" in /etc/rc.d/rc.firewall but I don't really know where to type this. Is there a way to turn this ICMP off in Puppy 2?

Clockman

User avatar
Lobster
Official Crustacean
Posts: 15522
Joined: Wed 04 May 2005, 06:06
Location: Paradox Realm
Contact:

#6 Post by Lobster »

This is the new server
http://www.puppylinux.com/news2005.htm

Is it here?
Puppy Raspup 8.2Final 8)
Puppy Links Page http://www.smokey01.com/bruceb/puppy.html :D

Clockman
Posts: 2
Joined: Fri 09 Jun 2006, 09:12

#7 Post by Clockman »

Lobster wrote:This is the new server
http://www.puppylinux.com/news2005.htm

Is it here?
Hi Lobster :-)

Yes, its there, Thank you. Well, there is a Puppy page there and a guy that mentions the "RFC_1122_COMPLIANT=no" in /etc/rc.d/rc.firewall somewhere on the page but that doesn't help me a bit.

Where do you type that "RFC_1122_COMPLIANT=no" in /etc/rc.d/rc.firewall? Or where is it? In Linux everything is different from Windows, so honestly I can't tell neither head or tail of all this "RFC_1122_COMPLIANT stuff.

That's one thing I noticed from the Linux users, they type a lot of informations, but they don't explain anything, just as if to keep it for gurus like themselves, like for the "initiated only", or they think everybody understand what they're typing as if everyone is in their head. They're not that much enclined to help. At least in Windows, I could provide some help to others and get some when I needed it.

With the Fedora Forum its the same attitude. I'll give it a few days and if I see that Linux is followed by people with a "know better than thou attitude". I'll go back to the MicroSoft products. Simple as that.

I have the dog in hostage. If you don't tell me how to setup this stuff, the puppy's gonna get it.

Clockman

John Doe
Posts: 1681
Joined: Mon 01 Aug 2005, 04:46
Location: Michigan, US

#8 Post by John Doe »


User avatar
jason.b.c
Posts: 755
Joined: Wed 08 Feb 2006, 05:32
Location: Marshfield,MO
Contact:

#9 Post by jason.b.c »

Well i'm not sure how this would be done in linux, But you would need to Block the rule called IP-IN..

Thats how i achieved Full Stealth and passed the test on the GRC ( shields up! ) website.. Ha HA HA

Thats awesome, Freakin awesome..! :D
Puppy is Awesome..!!!!
[url=http://www.puppylinux.com/][img]http://www.browserloadofcoolness.com/sig.png[/img][/url]

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#10 Post by BarryK »

Clockman,
The reason no further explanation was given is that it is dead easy to do, even
for a Windows user.

After you have run the Firewall Wizard (in the Setup menu) and accepted the
defaults, you will have a file rc.firewall, located in directory /etc/rc.d/

Start Rox file manager (icon top-left of screen), navigate to /etc/rc.d, left
click on rc.firewall and choose to "Open in text editor"

Scroll down, or use the search tool, and you will find this line:

Code: Select all

RFC_1122_COMPLIANT="yes"
I'll leave you to figure out the final steps.

You may have to reboot Puppy afterward for it to take effect.
(Though, it is possible to stop and restart the firewall without rebooting)

User avatar
gristmill
Posts: 5
Joined: Sun 12 Nov 2006, 19:12
Location: Sudbury,Ma, USA

Making firewall not respond to ping

#11 Post by gristmill »

Iam using Puppy 2.11

I too was was getting a ping response from ShieldsUp at www. grc.com even though I had set up the firewall with the wizard and chose the default settings. Following the suggestions given by BarryK on this forum, I used Rox file manager to change the RFC_1122_compliant to "no". Now I get no ping response at ShieldsUp and all ports are stealthed.

One thing I really like about Puppy is that I can try making changes knowing that if I make a mistake and break the system I can always delete the pup_save.sfs file on my HD, and reload Puppy from the CD. Puppy gives me the freedom to experiment and learn about Linux.

Long live Puppy :D

Wolf Pup
Posts: 637
Joined: Fri 28 Apr 2006, 01:37

#12 Post by Wolf Pup »

http://lfw.sf.net/

The final version of the linux firewall (puppy has 2.0RC9) has RFC_1122_COMPLIANT="depends" and gives no response to pings.

Post Reply