Firestarter / SheildsUp

Message

muskrat · #1 Post by **muskrat** » 2006-01-03 04:51

I installed firestarter, but I see something strange when I boot.

The boot squence trys to load firestarter 4 different times, on the fourth it succeeds.

The frist two times are on run level two I believe, and in squence, once after the other. It fails but then proceeds to other items, later it trys again and fails, going on to other items in squence. Finally just before it truns everything over and goes into X, it tries again and this time Firestarter successfully starts.

It does it the same every time I boot.

My question is should I remover Firestarter from those other run levels or is there another problem?

Now on to the second item in my title.

I use a telephone DSL with a cat 5 modem. Also running Firestarter. When I go to ShieldsUp, I get three ports showing open (red). They are port21-FTP, port80-HTTP, and port23-Telnet.

But when I run netstat -l this is my report,

Code: Select all

debbox:/boot# netstat -l
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 *:auth                  *:*                     LISTEN
tcp        0      0 *:ssh                   *:*                     LISTEN
tcp        0      0 *:ipp                   *:*                     LISTEN
udp        0      0 *:bootpc                *:*
udp        0      0 *:ipp                   *:*

I then run /etc/init.d/ssh stop, it stopped
but auth, and ipp returned with errors.

Rerun ShieldsUp, and the results are the same.

I checked my installed programs with dpkg, and the only telnet I have installed is a client, there is no FTP or HTTP servers installed on this box. How come I'm showing open ports on FTP, HTTP, Telnet when I have no services listening on those ports? Could it be my modem retruning those open port results?

Can anyone trun on the lights for me, I'm in the dark on this one.

Penguin Skinner · #2 Post by **Penguin Skinner** » 2006-01-03 21:46

Hi, Muskrat.

Re: the Firestarter question, I'm assuming you're using DHCP ... if so, this is normal behavior. What's happening is the init script is trying to start the firewall before a DHCP lease is obtained.

If you have bootlogging enabled, you can see that there's little harm done, and probably no significant slowing of the boot process:

Code: Select all

Mon Jan  2 23:35:24 2006: Running 0dns-down to make sure resolv.conf is ok...done.
Mon Jan  2 23:35:24 2006: Setting up networking...done.
Mon Jan  2 23:35:24 2006: Configuring network interfaces...Internet Software Consortium DHCP Client 2.0pl5
Mon Jan  2 23:35:24 2006: Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
Mon Jan  2 23:35:24 2006: All rights reserved.
Mon Jan  2 23:35:24 2006:
Mon Jan  2 23:35:24 2006: Please contribute if you find this software useful.
Mon Jan  2 23:35:24 2006: For info, please visit http://www.isc.org/dhcp-contrib.html
Mon Jan  2 23:35:24 2006:
Mon Jan  2 23:35:26 2006: Starting the Firestarter firewall: failed.
Mon Jan  2 23:35:26 2006: Listening on LPF/eth0/00:11:11:b7:94:07
Mon Jan  2 23:35:26 2006: Sending on   LPF/eth0/00:11:11:b7:94:07
Mon Jan  2 23:35:26 2006: Sending on   Socket/fallback/fallback-net
Mon Jan  2 23:35:26 2006: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
Mon Jan  2 23:35:30 2006: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
Mon Jan  2 23:35:30 2006: DHCPOFFER from 192.168.0.1
Mon Jan  2 23:35:30 2006: Starting the Firestarter firewall: failed.
Mon Jan  2 23:35:30 2006: Starting the Firestarter firewall: failed.
Mon Jan  2 23:35:30 2006: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Mon Jan  2 23:35:30 2006: DHCPACK from 192.168.0.1
Mon Jan  2 23:35:30 2006: Starting the Firestarter firewall: done.
Mon Jan  2 23:35:30 2006: bound to 192.168.0.2 -- renewal in 43200 seconds.
Mon Jan  2 23:35:30 2006: done.

muskrat · #3 Post by **muskrat** » 2006-01-04 01:31

Ok thank you, I thought some thing of that was happening, but is that because it's listed to soon in the boot sequnce or just forget it and let it be?

As for my second question, How come I have open ports with Firestarter runing?

And yes I'm using DHCP on a DSL phoneline modem connected to the PC with a cat5 cable.

BullBar · #4 Post by **BullBar** » 2006-01-05 22:52

muskrat wrote:Ok thank you, I thought some thing of that was happening, but is that because it's listed to soon in the boot sequnce or just forget it and let it be?

As for my second question, How come I have open ports with Firestarter runing?

And yes I'm using DHCP on a DSL phoneline modem connected to the PC with a cat5 cable.

Re: your second question. The ports are possibly open on your DSL modem/NAT router or they are being held open (intercepted) by your ISP.

BullBar