Back to Home / #debian / 2013 / 05 / Next Day
#debian IRC Logs for 2013-05-18

---Logopened Sat May 18 22:23:32 2013
22:23-!-mikegrb [] has joined #debian
22:23-!-Irssi: #debian: Total of 556 nicks [1 ops, 0 halfops, 0 voices, 555 normal]
22:23-!-colaborador [] has joined #debian
22:24-!-colaborador [] has left #debian []
22:25-!-Irssi: Join to #debian was synced in 145 secs
22:26-!-ckoch786 [] has quit [Read error: Operation timed out]
22:26-!-noahfx [~noahfx@] has joined #debian
22:28-!-jimh [] has joined #debian
22:28-!-lanthan [] has joined #debian
22:28-!-kenifanying [~kenifanyi@] has joined #debian
22:29-!-jimh [] has quit []
22:30-!-jimh [] has joined #debian
22:30-!-miksuh [] has joined #debian
22:31-!-jimh_ [] has joined #debian
22:32-!-jimh [] has left #debian []
22:32-!-jimh_ [] has left #debian []
22:32-!-q66 [~q66@] has quit [Remote host closed the connection]
22:32-!-servidor [] has joined #debian
22:33-!-alvarezp [~alvarezp@2001:470:d:872:e9f7:d78a:12f2:1b22] has joined #debian
22:33-!-alvarezp [~alvarezp@2001:470:d:872:e9f7:d78a:12f2:1b22] has quit [Remote host closed the connection]
22:33-!-alvarezp [~alvarezp@2001:470:d:872:e9f7:d78a:12f2:1b22] has joined #debian
22:34-!-nickdaly [] has quit [Ping timeout: 480 seconds]
22:34-!-servidor [] has quit []
22:35-!-servidor [] has joined #debian
22:37-!-servidor [] has left #debian []
22:37<somiaj>youlysses: it may ignore devices in your interfaces file. By default (unless you disabled it) the daemon should load at boot. You can double check with /etc/init.d/wicd status and run it with /etc/init.d/wicd start
22:37-!-qerter [] has joined #debian
22:37<somiaj>youlysses: you could change your home network to use an alias (so put home in place of wlan0)
22:38<somiaj>youlysses: then bring up that network with ifup wlan0=home (that way it won't ignore it. Though you may want to turn off wicd before doing so as it likes to take control)
22:39<youlysses>somiaj: I forgot to mention, my in-built network card is defaulting to wlan1. Could this be part of the problem?
22:40<sney>you can change that in /etc/udev/rules.d/70-persistent-net.rules, but it shouldn't make a difference for wicd
22:42<youlysses>somiaj: wicd daemon is currently running.
22:43<somiaj>youlysses: I was just using wlan0 as an example of syntax. I belive if your interface is explicting mentioned in /etc/network/interfaces it will ignore it. Change your interfaces file (use an alias) and then restart the deamon. See if that gets wicd to see the card
22:43<somiaj>youlysses: and as sney said you can change it to be wlan0 if you desire
22:44-!-Infiltrator [] has quit [Quit: leaving]
22:44-!-byonk [] has joined #debian
22:45-!-youlysses [] has quit [Remote host closed the connection]
22:48-!-pos [~mark@] has joined #debian
22:50-!-fr33k [] has joined #debian
22:52-!-dg4prez [~quassel@2607:f3f0:2::cf34:f2b0] has quit [Remote host closed the connection]
22:53-!-vishwanath [~vishwanat@] has joined #debian
22:53-!-dg4prez [~quassel@2607:f3f0:2::cf34:f2b0] has joined #debian
22:54-!-vishwanath [~vishwanat@] has quit []
22:54-!-chitchat [] has joined #debian
22:55-!-vishwanath [~vishwanat@] has joined #debian
22:55-!-wardhan [~wardhan@] has joined #debian
22:55-!-vishwanath [~vishwanat@] has quit []
22:56-!-vishwanath [~vishwanat@] has joined #debian
22:57-!-vishwanath [~vishwanat@] has quit []
22:58-!-kingsley [] has quit [Read error: Operation timed out]
23:00-!-Freejack [] has joined #debian
23:03-!-alphanum [] has joined #debian
23:03<alphanum>hi guys.
23:05-!-daemonkeeper [] has quit [Ping timeout: 480 seconds]
23:05-!-SparTaKo [] has joined #debian
23:05-!-SparTaKo [] has left #debian []
23:05-!-daemonkeeper [] has joined #debian
23:06-!-martin_ [~martin@] has joined #debian
23:06-!-jimh [] has joined #debian
23:06-!-martin_ [~martin@] has quit []
23:06-!-alphanum [] has quit []
23:07-!-lanthan [] has quit [Remote host closed the connection]
23:07-!-lanthan [] has joined #debian
23:07-!-msantana [] has quit [Ping timeout: 480 seconds]
23:07-!-TheBonsai [] has quit [Ping timeout: 480 seconds]
23:08-!-jimh [] has left #debian []
23:08-!-ngranek [~bigjocker@] has joined #debian
23:09-!-Jekyll [~whodare@] has quit [Quit: Konversation terminated!]
23:13-!-bullgard4 [] has joined #debian
23:13-!-kingsley [] has joined #debian
23:14<Elv13>Does anyone of you have an idea how to stop ARP attack?
23:14<Elv13>they are eating up my bandwidth
23:16-!-endived [] has joined #debian
23:16-!-Konrad127123 [] has quit [Ping timeout: 480 seconds]
23:17<kerneld>Elv13: more VLANS
23:17<kerneld>smaller subnets
23:17<Elv13>the attack is comming from thw WAN
23:17<Elv13>I got a debian box just to stop ot
23:20-!-dvs [] has joined #debian
23:20<kerneld>does your ISP have a lot of customers on the same L2 segement as you?
23:20-!-TheBonsai [] has joined #debian
23:21<Elv13>yea, the whole sector is on a cooperative-ish ISP and there seem to be no afirewall blocking 192.168.* from being routed and nothing block ARP packets
23:22<kerneld>You could figure out the MAC of your upstream gateway and any other servers you care to talk to and drop inbound packets from other MACs
23:23<kerneld>careful as they prob have VRRP and have a clustered gateway
23:23<Elv13>I already block inbound trafic, but that keep adding to my bandwidth
23:23<Elv13>(I got a cap)
23:23<kerneld>Are you linked to them with 802.1q port, or an access port?
23:23<Elv13>it is over 1gB per hours
23:23-!-egwk [] has quit [Remote host closed the connection]
23:24<Elv13>classic RJ45 jack cable to the wall
23:24<kerneld>Seems like your upstream has problems with their network design if you are all on a party line
23:25<Elv13>This ISP is not _that_ bad, as they let me have multiple public IPs (well, they failed to block that too)
23:25-!-theos911 [] has quit [Ping timeout: 480 seconds]
23:26-!-orangensaft8 [~orangensa@2a02:908:f441:ed80:213:a9ff:fe48:6647] has joined #debian
23:26<Elv13>it is so bad that the mb/second cap is on the IP, not the MAC, so I can multiplex over 10 IPs and get 200mbps for the price of 20
23:27<kerneld>on your router, do an arp -a
23:28-!-Konrad127123 [] has joined #debian
23:28<kerneld>do you have arptables setup?
23:29-!-claw__ [] has joined #debian
23:30-!-mode/#debian [+l 580] by debhelper
23:31<Elv13>kerneld: the table is free of the IPs that the attack try to push into it, at least I got this right
23:33<kerneld>well if you are dropping the bad MACs thats all you can do. If ISP is charging for theier uncrontrolled ARP traffic that you are not responding to, not much you can do there. Best you can do is ignore the bad traffic
23:34<kerneld>you can whitelist the good MACs, or blacklist the bad MACs
23:34<Elv13>or try to DOS the author
23:34-!-AzaToth [] has quit [Remote host closed the connection]
23:34<kerneld>I would recommend blacklisting the BAD MACs at that insulates you from losing connectivity in future when ISP makes hardware changes on the router
23:34<Elv13>03:17:58.860179 ARP, Request who-has tell, length 46
23:34-!-youlysses [] has joined #debian
23:34-!-coldfire [] has joined #debian
23:34-!-youlysses [] has quit [Remote host closed the connection]
23:35-!-coldfire [] has left #debian []
23:35<Elv13>kerneld: what is the preferred method to block the MAC?
23:35-!-youlysses [] has joined #debian
23:36<kerneld>arptables, but be careful
23:36-!-claw_ [] has quit [Ping timeout: 480 seconds]
23:37<kerneld>it is was a set more intended for ether bridge security
23:37<Elv13>I don't know if it is a reall attack or just too many peoples that plugged the wrong router wire into the WAN
23:37-!-brdxufan [~brdxufan@] has joined #debian
23:37-!-brdxufan [~brdxufan@] has quit []
23:39-!-Auroch [] has joined #debian
23:41<kerneld>iptables has a MAC module to
23:42<kerneld>but arptables would be the right tool
23:44-!-overflow [~overflow@] has joined #debian
23:44-!-bluewater [] has joined #debian
23:47-!-orangensaft8 [~orangensa@2a02:908:f441:ed80:213:a9ff:fe48:6647] has quit [Quit: Leaving.]
23:47-!-orangensaft8 [~orangensa@2a02:908:f441:ed80:213:a9ff:fe48:6647] has joined #debian
23:48-!-orangensaft8 [~orangensa@2a02:908:f441:ed80:213:a9ff:fe48:6647] has quit []
23:51-!-overflow [~overflow@] has quit [Quit: Saliendo]
23:52-!-youlysses [] has quit [Remote host closed the connection]
23:53<bullgard4>[Wheezy] What grub2 file includes a kernel command line?
23:53-!-qerter [] has quit [Ping timeout: 481 seconds]
23:54<Elv13>in the end, grub.cfg, but dont edit that file
23:56-!-ryerke [] has quit [Remote host closed the connection]
---Logclosed Sun May 19 00:00:20 2013