I have a 160 gig harddrive.. I've installed Windows first, on 50 gigs (for gaming) and then installed Ubuntu Linux on the leftover 100 gigs of the harddrive. Now the problem is that after I installed Ubuntu I cant get back to Windows. Even when I get into the Boot Menu, I only see 5 things with the name 'Ubuntu' in it. How can I get my Windows back?

 

Thanks for any help given, or even just reading!

SlackWare 10.2 is out [img]<___base_url___>/uploads/emoticons/default_laugh.png[/img]

 

the home page is [/url][url=http://www.slackware.com]http://www.slackware.com o_O

I installed net-snmp on my SlackWare . An I dont know howto config it ? and hot tu use it somone can help ??

 

I olredy tried the net-snmp home page bat ther is mor about mibs not about how to configure it .

Let's say you comiled your kernel & on boot you get an old kernel panic or something else;

 

Get your DVD OR CD install disk or even a netinstall disk should work

 

Boot from the dvd or cd install disk & at the prompt put in # rescue root=/dev/hda5

example_where (dev /hda5 is your debian partition) your root partition

don't hesitate to discover different options with F1

 

Your box should boot up normally with the kernel of the cd or dvd where you will find all your partitions and all your data untouched at the same place you left it before.

 

Now, as everything is almost back ,fix the error or mistake you have done where you have last compiled your kernel & you should be done .

 

johnny06 [img]<___base_url___>/uploads/emoticons/default_laugh.png[/img]

Hey, guys! I'm thinking about switching to eMusic and ditching iTunes, and I could use some advice. Here is what's on the scale:

 

eMusic

Pros: No DRM, flat monthly fee allows me to quickly legitimize my music collection, no special software to use

Cons: Fixed monthly fee makes occasional downloading wasteful, but it's like a "financing program" if you really think about it

 

iTunes

Pros: A-la-carte pricing makes occasional downloading OK, Steve Jobs called the music industry "greedy" for pushing for an increase in price

Cons: Requires use of special software, DRM (which can be broken)

 

What do you think?

What's up with the ads? They are certainly an ugly thing!

Ok, we have a new method of rate limiting.

 

This new method is WAYYY better.

 

 

the old -m limit method limits per packet per port.. if you have someone flooding your ssh connetion, it'll actually disable the service all around, causing YOU not to be able to get on. not really the effect you wanted.

 

This new method, actually bases its rate limit on a per IP basis.

 

So if you are getting flooded from 1 ip specifically, only that 1 ip will be locked down.

 

Everyone else will be able to get on still. as long as they stay within the connection limit itself.

 

 

I'll be honest. *I* didnt figure this out. i found it on a url

 

[/url][url=http://www.debian-administration.org/articles/187]http://www.debian-administration.org/articles/187

 

 

It does work, as a few linux-noob'ers helped me test it successfully.

-----------

 

The way the recent module works is fairly straightforward, you basically add IP addresses to a list, which can then be used in the future to test connection attempts against. This allows you to limit the number of connections against either a number of seconds, or connection attempts. In our example we'll do both.

 

An example is probably the simplest way to illustrate how it works. The following two rules will limit incoming connections to port 22 to no more than 3 attemps in a minute - an more than that will be dropped:

 

iptables -I INPUT -p tcp --dport 22 -i eth0 -m state --state NEW -m recent \

--set

 

iptables -I INPUT -p tcp --dport 22 -i eth0 -m state --state NEW -m recent \

--update --seconds 60 --hitcount 4 -j DROP

 

The --state flag takes a comma seperated list of connection states as an argument, by using "--state NEW" as we did we make sure that only new connections are managed by the module.

 

The --set parameter in the first line will make sure that the IP address of the host which initiated the connection will be added to the "recent list", where it can be tested and used again in the future i.e. in our second rule.

 

The second rule is where the magic actually happens. The --update flag tests whether the IP address is in the list of recent connections, in our case each new connection on port 22 will be in the list because we used the --set flag to add it in the preceeding rule.

 

Once that's done the --seconds flag is used to make sure that the IP address is only going to match if the last connection was within the timeframe given. The --hitcount flag works in a similar way - matching only if the given count of connection attempts is greater than or equal to the number given.

 

Together the second line will DROP an incoming connection if:

 

* The IP address which initiated the connection has previously been added to the list and

* The IP address has sent a packet in the past 60 seconds and

* The IP address has sent more than 4 packets in total.

 

You can adjust the numbers yourself to limit connections further, so the following example will drop incoming connections which make more than 2 connection attempts upon port 22 within ten minutes:

 

iptables -I INPUT -p tcp --dport 22 -i eth0 -m state --state NEW -m recent \

--set

 

iptables -I INPUT -p tcp --dport 22 -i eth0 -m state --state NEW -m recent \

--update --seconds 600 --hitcount 2 -j DROP

 

If you wish to test these rules you can script a number of connection attempts from an external host with the netcat package.

 

The following script attempts to connect to the IP address 192.168.1.1 5 times. The first couple of attempts you should see a welcome banner such as "SSH-2.0-OpenSSH_3.8.1p1 Debian-8.sarge.4" - after that the script will hang as it's packets are dropped and no response is sent:

 

#!/bin/bash

 

for i in `seq 1 5` ; do

echo 'exit' | nc 192.168.1.1 22 ;

done

 

There's a lot of documentation on the netfilter/iptables firewall, and it's available modules which you can find in the Netfilter Extension HOWTO.

 

This HOWTO contains documentation on many different modules, along with examples. A recommended read if you're interested in Linux firewalling.

 

If you wish to experiment with rules and testing it's worth remembering how to remove all active rules. The following commands will flush your iptables filewall, and remove all currently active rules:

 

iptables -F

iptables -X

;) hi, im running Ubuntu Hoary 5.04.

I'm try to set up a webserver

after loging in as root and i type

/etc/network/interfaces

to set up a static ip instead of DHCP

 

after that it repeats what i typed fallowed by Access Denied [img]<___base_url___>/uploads/emoticons/default_mad.gif[/img]

 

anywho if anyone can tell me what i have done wrong i would be thankful.

good times B)

You want to block all incoming network traffic, except from your system itself. Does not affect outgoing traffic.

 

 

 

For iptables:

 

# iptables -F INPUT

# iptables -A INPUT -m state --state ESTABLISHED -j ACCEPT

# iptables -A INPUT -j REJECT

 

 

For ipchains:

 

# ipchains -F input

# ipchains -A input -i lo -j ACCEPT

# ipchains -A input -p tcp --syn -j REJECT

# ipchains -A input -p udp --dport 0:1023 -j REJECT :P

 

 

johnny06

After playing with it for awhile I decided to make my own custon flux menu and tool bar let me know what you think :)

<a class="ipsAttachLink ipsAttachLink_image" href="<fileStore.core_Attachment>/post-204-1127935265.png" data-fileid="391">[img]<fileStore.core_Attachment>/post-204-1127935265.png[/img]</a>

Attached Files

  screenshot.png (Size: 1.21 MB / Downloads: 0)