IRC Logs

Network: freenode Channel: #iptables

	Enter your search terms Submit search form
	Web www.irclog.org

[00:12]<vyrn-vnzsr>omi: sledgehammers ??? :0
[00:14]<sgnzcm_bzsvzzm>if they destroy the box, they sure aren't getting the data off it :p
[00:16]<2punpjwo1>ok, so i have 3 ip's in the resolv.conf
[00:16]<2punpjwo1>do i need to use those in the windows machine?
[00:16]<wacw>I need a rule to say my firewall will allow only downloads until 5mb, up to 5mb it will deny, how do
[00:16]<wacw>how do I do?
[00:17]<2punpjwo1>that's bandwidth throttling...i dunno o.o
[00:22]<wacw>:/
[00:24]<vyrn-vnzsr>bluefox83: yes
[00:24]<2punpjwo1>vice-versa, to connect my two computers together..can i use a standard ethernet cable or do i need some kinda crossover cable?
[00:24]<vyrn-vnzsr>crossover for nic to nic
[00:25]<2punpjwo1>all i have is ethernet
[00:25]<vyrn-vnzsr>and you'll only get 10mbps iirc
[00:25]<2punpjwo1>so this wont work at all?
[00:25]<vyrn-vnzsr>sure it will, with the right cable
[00:26]<2punpjwo1>i don't have the money for a 75 foot crossover cable :(
[00:26]<vyrn-vnzsr>re-terminate one end of the cable then
[00:27]<jdy>xjkx: there's frottle, I'm sure it also works for wired networks
[00:27]<2punpjwo1>do what? O.o
[00:27]<vyrn-vnzsr>bluefox83: or get a crossover coupler for a few bucks
[00:28]<vyrn-vnzsr>bluefox83: putting the connectors on a cable if known as terminating
[00:29]<2punpjwo1>whats a crossover coupler and how does it work?
[00:31]<ucrse>hi
[00:31]<vyrn-vnzsr>bluefox83: http://www.cablesunlimited.com/products/Product_Links.aspx?M1=Networking%20Products&Sub1=UTP/Components&sub2=Couplers
[00:32]<ucrse>have you ever encountered this problem
[00:32]<ucrse> No chain/target/match by that name
[00:32]<vyrn-vnzsr>yes
[00:32]<ucrse>i have it when i want to add rule for connections
[00:32]<vyrn-vnzsr>what's the rule
[00:32]<drwygn>rumour has it the rule is simple - wait 2 weeks before updating (or not) to the next 2.6.x
[00:32]<ucrse>i want to restrict 10 connections per user
[00:32]<vyrn-vnzsr>lol
[00:33]<vyrn-vnzsr>what's the rule
[00:33]<drwygn>the rule is simple - wait 2 weeks before updating (or not) to the next 2.6.x
[00:33]<vyrn-vnzsr>piss off maxine :)
[00:34]<ucrse>iptables -A FORWARD -s 192.168.1.2 -p tcp --syn -m connlimit --connlimit-above 10 -j DROP
[00:34]<ucrse>and i have No chain/target/match by that name
[00:35]<vyrn-vnzsr>do you have connlimit support in the kernel or a module?
[00:36]<ucrse>no i have it compiled normaly
[00:36]<ucrse>not as a module
[00:36]<ucrse>i have 2.4 kernel and 1.2.11 iptables with patch connlimit
[00:37]<vyrn-vnzsr>what's the result of iptables -nvL FORWARD
[00:39]<ucrse>Chain FORWARD (policy DROP 5 packets, 240 bytes)
[00:39]<ucrse> pkts bytes target prot opt in out source destination
[00:39]<ucrse> 1462 318K ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 MAC 00:01:29:FD:46:0B
[00:39]<ucrse>17591 899K ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 MAC 00:30:4F:1B:6C:24
[00:39]<ucrse> 4438 864K ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 MAC 00:00:39:39:40:F0
[00:39]<ucrse> 0 0 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 MAC 00:50:8D:7D:4F:76
[00:39]<ucrse> 0 0 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 MAC 00:13:D3:3B:8D:69
[00:39]<ucrse> 0 0 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 MAC 00:15:60:B3:AA:9F
[00:39]<ucrse>31373 39M ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
[00:41]<vyrn-vnzsr>so is connlimit something you recently added to your kernel?
[00:41]<ucrse>yes
[00:41]<ucrse>i am sure
[00:46]<vyrn-vnzsr>grep your .config for CONFIG_IP_NF_MATCH_LIMIT
[00:48]<ucrse>I HAVE IT AS YES
[00:48]<vyrn-vnzsr>iptables -m connlimit -h
[00:48]<vyrn-vnzsr>does that show help for connlimit at the bottom?
[00:49]<ucrse>yes it does
[00:50]<vyrn-vnzsr>and iptables -m connlimit-above -h
[00:51]<ucrse>no it doesn't
[00:51]<vyrn-vnzsr>there's your problem then
[00:53]<ucrse>sory but i am newbie and i don't know where i am making a mistake
[00:53]<ucrse> iptables -A FORWARD -s 192.168.1.2 -p tcp --syn -m connlimit --connlimit-above 10 -j DROP
[00:53]<ucrse>where is it
[00:53]<ucrse>i will be thankfull
[01:04]<ucrse>vice-versa ?
[01:31]<2punpjwo1>ok...can i connect my router to my eth1 without a crossover cable?
[01:31]<2punpjwo1>because i seem to be having problems getting my router to fetch an ip from the modem
[01:32]<vyrn-vnzsr>on the WAN port or one of the LAN ports?
[01:32]<2punpjwo1>WAN
[01:33]<vyrn-vnzsr>bluefox83: depends on the router, I've seen some work with either...some not
[01:34]<vyrn-vnzsr>bluefox83: what kind of connection you have from yourISP?
[01:35]<vyrn-vnzsr>bluefox83: just thinking they may do MAC authentication hence the reason the router doesn't get an IP
[01:36]<vyrn-vnzsr>bluefox83: does your router have a MAC spoofing option?
[01:38]<vyrn-vnzsr>bluefox83: ?
[01:38]<vyrn-vnzsr>bah
[01:39]<2punpjwo1>this is getting on my nerves -_-
[01:39]<vyrn-vnzsr>mine too
[01:39]<vyrn-vnzsr>lol
[01:39]<2punpjwo1>my whole damn system froze
[01:40]<2punpjwo1>i leaned over it to plug something in, and when i looked back everything was frozen on my screen
[01:40]<vyrn-vnzsr>sensitive
[01:40]<vyrn-vnzsr>old or new?
[01:40]<2punpjwo1>year and a half
[01:40]<vyrn-vnzsr>overheating?
[01:40]<2punpjwo1>os[Linux 2.6.16-1-k7 - Debian testing/unstable] up[3 minutes] cpu[AMD Sempron(tm), 1333.594 MHz (2669.79 bogomips) at 59.0°C] xchat[Version: 2.6.1]
[01:40]<2punpjwo1>no..not really
[01:40]<vyrn-vnzsr>bad caps, RAM ???
[01:40]<2punpjwo1>nah
[01:41]<2punpjwo1>i think i leaned against a power button or something
[01:41]<vyrn-vnzsr>that wouldn't freeze it, reboot it shut it down mabe
[01:42]<2punpjwo1>i don't think my linksys 4 port router likes being on eth1
[01:42]<vyrn-vnzsr>bluefox83: you get my last couple questions before you dropped the last time?
[01:43]<vyrn-vnzsr>what kind of connection you have from yourISP?
[01:43]<2punpjwo1>no, all i got was that some routers will work on WAN
[01:43]<2punpjwo1>i have a dynamic ip, basic cable
[01:43]<2punpjwo1>nothing fancy
[01:43]<vyrn-vnzsr>just thinking they may do MAC authentication hence the reason the router doesn't get an IP

Back to #iptables
Or go to some related logs:
#gentoo
#netbsd
#gentoo
#gentoo
#gentoo