On Sun May 3 2009, Andrei Popescu wrote:
> > Firestarter might work, but i really wanted to be able to add my own
> > entry to some file somewhere:) command-line junky :)
>
> Sounds like shorewall to me ;)
ahhh, I might have to look at it. thanks!
per the INTRO page:
http://www.shorewall.net/
Sho
On Sat May 2 2009, Andrei Popescu wrote:
> > need to run:
> > iptables -I INPUT -p tcp -m state --state NEW --dport 80 -i eth0 -j
> > ACCEPT iptables -I INPUT -p tcp -m state --state NEW --dport 22 -i eth0
> > -j ACCEPT /sbin/iptables -N ssh-connection
> > /sbin/iptables -A ssh-connection -i eth0 -
On Sat,02.May.09, 16:32:44, Paul Cartwright wrote:
> Firestarter might work, but i really wanted to be able to add my own
> entry to some file somewhere:) command-line junky :)
Sounds like shorewall to me ;)
Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough
On Sat May 2 2009, Thorny wrote:
> If I understand correctly what you asking:
>
> You will need to option your router to port forward port 80 requests
> from the WAN interface to the static IP Address of the computer on your
> LAN you want them to go to.
I have done that and it works.
>
> If thos
On Sat, 02 May 2009 06:15:04 -0400, Paul Cartwright posted:
[...]
> what I want is a rule tht allows http for my web page to port forward from
> my router to my desktop, and also allow me to ssh into my desktop from my
> laptops.
If I understand correctly what you asking:
You will need to option
On Sat,02.May.09, 06:15:04, Paul Cartwright wrote:
> On Sat May 2 2009, Andrei Popescu wrote:
> > > part of the problem was 2 files I had worked on that did give me
> > > errors, and I removed them. 1 was ipv6,
> >
> > Do yo mean the module? If you don't want it loaded (though I have it and
> > the
On Sat May 2 2009, Andrei Popescu wrote:
> > part of the problem was 2 files I had worked on that did give me
> > errors, and I removed them. 1 was ipv6,
>
> Do yo mean the module? If you don't want it loaded (though I have it and
> there are no problems) just blacklist it in a file (ex. 00local.co
On Sat,02.May.09, 05:38:38, Paul Cartwright wrote:
> well, that seems to work.
...
> part of the problem was 2 files I had worked on that did give me
> errors, and I removed them. 1 was ipv6,
Do yo mean the module? If you don't want it loaded (though I have it and
there are no problems) just
On Sat May 2 2009, Andrei Popescu wrote:
> > #static setup
> > #auto eth0
> > #iface eth0 inet static
> > #address 192.168.10.103
> > #netmask 255.255.255.0
> > #broadcast 192.168.10.255
> > here is what I have now:
>
> Please re-enable this part (and comment out the dhcp parts) and post the
> outp
On Fri,01.May.09, 05:36:06, Paul Cartwright wrote:
> I seemed to have a problem with my static setup of eth0 that stopped my
> debian
> lenny setup from coming up correctly. I kept getting errors in logs.
> To redo my network config, just eth0, what is the best way to do it. I tried
> dpkg-recon
On Fri May 1 2009, Bob Cox wrote:
> What I would expect to see is something a bit like this:
>
> auto lo
> iface lo inet loopback
>
> auto eth0
> iface eth0 inet static
> address 192.168.10.103
> netmask 255.255.255.0
> gateway 192.168.10.1
> network 192.168.10.0
> broadcast 192.168.10.255
>
> (ass
On Fri May 1 2009, Celejar wrote:
> > this is what I had that didn't work:
> > #static setup
> > #auto eth0
> > #iface eth0 inet static
> > #address 192.168.10.103
> > #netmask 255.255.255.0
> > #broadcast 192.168.10.255
> > here is what I have now:
# The loopback network interface
auto lo
iface l
On Fri May 1 2009, Andrei Popescu wrote:
> > auto lo
> > iface lo inet loopback
> >
> > auto eth0
> > iface eth0 inet static
> > address 192.168.10.103
> > netmask 255.255.255.0
> > gateway 192.168.10.1
> > network 192.168.10.0
> > broadcast 192.168.10.255
>
> Nitpick: 'network' and 'broadcast' are
On Fri May 1 2009, Bob Cox wrote:
> > Nitpick: 'network' and 'broadcast' are optional and gateway is necessary
> > only if this interface is used to connect to the internet.
>
> Good points. I like nitpicking ;-)
>
> As an aside, I use static IPs on everything here with no wireless and
> all manua
On Fri, May 01, 2009 at 19:04:25 +0300, Andrei Popescu
(andreimpope...@gmail.com) wrote:
[snip]
> Nitpick: 'network' and 'broadcast' are optional and gateway is necessary
> only if this interface is used to connect to the internet.
Good points. I like nitpicking ;-)
As an aside, I use stati
On Fri,01.May.09, 15:11:17, Bob Cox wrote:
> What I would expect to see is something a bit like this:
>
> auto lo
> iface lo inet loopback
>
> auto eth0
> iface eth0 inet static
> address 192.168.10.103
> netmask 255.255.255.0
> gateway 192.168.10.1
> network 192.168.10.0
> broadcast 192.168.10
On Fri, May 01, 2009 at 05:36:06 -0400, Paul Cartwright (a...@pcartwright.com)
wrote:
> I seemed to have a problem with my static setup of eth0 that stopped my
> debian
> lenny setup from coming up correctly. I kept getting errors in logs.
> To redo my network config, just eth0, what is the be
On Fri, 01 May 2009 05:36:06 -0400, Paul Cartwright posted:
> I seemed to have a problem with my static setup of eth0 that stopped my
> debian lenny setup from coming up correctly.
This doesn't tell us anything that we could use to troubleshoot. Do you
mean the system doesn't come up or just does
On Fri, 1 May 2009 05:36:06 -0400
Paul Cartwright wrote:
> I seemed to have a problem with my static setup of eth0 that stopped my
> debian
> lenny setup from coming up correctly. I kept getting errors in logs.
> To redo my network config, just eth0, what is the best way to do it. I tried
> dp
I seemed to have a problem with my static setup of eth0 that stopped my debian
lenny setup from coming up correctly. I kept getting errors in logs.
To redo my network config, just eth0, what is the best way to do it. I tried
dpkg-reconfigure ifupdown, but that didn't change the interfaces file.
t
20 matches
Mail list logo
