[04:15] <Voyage> what does it takes to setup an smtp server and get your email passed through the automatic email spam filters?
[07:58] <lordievader> Good morning.
[11:53] <Rovanion> Hi, I'm getting the following errors on one of my drives in syslog and after a while it's lost to the system: http://paste.ubuntu.com/10855746/
[11:54] <Rovanion> Does anyone know how to find the cause of this issue?
[12:01] <Rovanion> This is my complete dmesg for ata1: http://paste.ubuntu.com/10855773/
[12:23] <lordievader> Rovanion: Drive failure? Check smart.
[12:26] <Rovanion> lordievader: Nothing notable on the smart record as far as I can see. Though they're hard to read. At least smartctl0 -H /dev/sdx returns passed on all devices.
[12:26] <Walex> Voyage__: setting up an SMTP server is not complicated if it is simple. For spam filters sometimes it helps to do SPF or some other idiotic authentication scheme.
[12:29] <lordievader> Rovanion: Could you pastebin the output of 'smartctl -a /dev/sdx'?
[12:31] <Rovanion> lordievader: Here it is: http://paste.ubuntu.com/10855877/
[12:32] <lordievader> Drive seems to be fine, indeed.
[12:33] <Rovanion> I've read a bunch of different causes for erros like this. But I'm having a hard time discerning which could cause mine. Some are kernel, some are cable, some are controller and some are power issues.
[12:35] <Rovanion> So the disks works for something like half a day while inside a ZPool while resilvering(rebuilding) a mirror, then disappears from Linux totally. /dev/sdx isn't there anymore.
[15:40] <coetry> Can someone please help me with Amazon EC2? I have an instance that i changed the security group to accept all tcp connections from port ranges 0 - 65535, and i have rails serving on 0.0.0.0:3000
[15:40] <coetry> but i can't seem to connect to the server from the public ip
[15:41] <coetry> its ubuntu server 14.04
[15:41] <coetry> is there a firwall on the server or something thats stopping it from accepting connections?
[15:44] <coetry> http://pastie.org/10103500
[15:48] <excalibr> coetry, iptables -nvL
[15:50] <coetry> excalibr: http://pastie.org/10103513
[15:54] <excalibr> coetry, I see nothing is blocking on your server so it must be your network firewall then
[15:56] <excalibr> Have you tried giving your ec2 instance a reboot?
[15:57] <coetry> excalibr, i did reboot it :/
[16:07] <excalibr> coetry, sorry I can't offer any further help. Ive never ran into such problem last time I used ec2. I did something differently though. I allowed all ports and proto in the security group and managed the firewall from within my instance
[16:08] <teward> coetry: check the EC2 control panel
[16:08] <teward> coetry: the security 'firewall' is controlled there, not at iptables
[16:08] <teward> you have to enter 'security group' allowed ports to permit access to the systems
[16:08] <teward> otherwise the default is block all but SSH
[16:09] <teward> (that Standard Operating Procedure hasn't changed in Amazon EC2 ever)
[17:03] <tyhicks> jamespage: hello - we've finally got through all the MIR security reviews that were ahead of the conntrack MIR (LP: #1381450)
[17:03] <tyhicks> jamespage: but we're not sure if it is still useful to do this week
[17:04] <tyhicks> jamespage: if sarnold could get through it in the next day or two, would it still be useful for 15.04?
[17:07] <Voyage> Walex,  SPF ?
[17:07] <sarnold> Voyage: Y
[17:07] <sarnold> Voyage: http://en.wikipedia.org/wiki/Sender_Policy_Framework
[17:19] <jamespage> tyhicks, yes please
[17:20] <tyhicks> sarnold: ^ could you focus on that and cve triage today?
[17:20] <sarnold> tyhicks: sure
[17:21] <tyhicks> sarnold: thanks! :)
[17:23]  * sbeattie assumes tyhicks meant s/cve triage/community/ today
[17:24] <tyhicks> sbeattie, sarnold: ah, I got your roles mixed up
[17:24] <tyhicks> that's even better for sarnold :)
[17:25]  * sbeattie *knew* not to get his hopes up. :)
[17:25] <sarnold> yes, yes it is :)
[17:25] <sarnold> sorry sbeattie
[17:26] <sarnold> sbeattie: I've already started process_cve with the kjernel-team merge.. I'll finish just that bit..
[17:26] <tyhicks> doh
[17:26] <sarnold> .. unless you've already started, then I'll try to figure out how to bail
[17:26] <tyhicks> I really screwed that up
[17:27] <sbeattie> sarnold: no, go ahead and finish that bit.
[17:29] <sarnold>  CVE-2013-4866    (1/78: 1%)
[17:29] <sarnold> ouch..
[17:29] <sarnold> sbeattie: okay, kernel team merge checked in, thanks
[17:30]  * sbeattie cries
[17:31] <sarnold> ... if there's any bright side, the first issue from debian that it prompted for me was this: (The LIXIL Corporation My SATIS Genius Toilet application for Android ...)
[17:32] <sarnold> which is hilarious in itself
[17:32] <sarnold> but also hopefully means debian went crazy finding NFUs to document.. I hope.
[17:35] <Alina-malina> lol at dan bilzerian
[17:47] <Voyage> sarnold,  ok. what precautions should be made while making an smpt server
[17:48] <sarnold> Voyage: keep up on your logs
[17:48] <Voyage> sarnold,  need my emails to not go in spam folders
[17:56] <lazyPower> Voyage: thats a trust based system that takes time
[17:57] <lazyPower> the easiest thing you can do starting off is set DKIM validation on your dns for the server, then you have to wait and send mail while it builds trust
[17:57] <Voyage> k
[17:58] <lazyPower> http://en.wikipedia.org/wiki/DomainKeys_Identified_Mail <- outlines it pretty well
[19:34] <tychicus> has anyone run into issues with tagged vlan's on 14.04, specifically with regards to intervlan routing?
[19:35] <tychicus> I'm running into an issue that seems to only affect my ubuntu machines, thinking maybe I have something wrong on the ubuntu configuration side
[19:36] <patdk-lap> what is intervlan routing?
[19:37] <tychicus> sorry inter vlan routing
[19:37] <tychicus> routing packets between vlan's
[19:37] <patdk-lap> I don't understand the usage of inter
[19:37] <patdk-lap> that would be external vlan routing
[19:37] <patdk-lap> inside vlan is l2, bridge
[19:37] <patdk-lap> so you just have normal l3 routing issues
[19:38] <tychicus> interVLAN is just the cisco nomenclature
[19:38] <tychicus> 2 vlan's
[19:38] <tychicus> default vlan 1
[19:39] <tychicus> then vlan 200
[19:39] <tychicus> vlan 200 is able to pickup an IP from local dhcp, or static assignment
[19:39] <tychicus> can talk to other devices on the same subnet, but can't see to exit the subnet
[19:40] <ay_caramba> wait till you get to routing on a stick
[19:40] <ay_caramba> ;)
[19:40] <tychicus> Kernel IP routing table
[19:40] <tychicus> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
[19:40] <tychicus> 0.0.0.0         192.168.28.254  0.0.0.0         UG    0      0        0 eth2
[19:40] <tychicus> 0.0.0.0         192.168.200.254 0.0.0.0         UG    100    0        0 eth2.200
[19:40] <tychicus> 192.168.28.0    0.0.0.0         255.255.255.0   U     0      0        0 eth2
[19:40] <tychicus> 192.168.200.0   0.0.0.0         255.255.255.0   U     0      0        0 eth2.200
[19:40] <tychicus> is how the local routing table is configured
[19:42] <tychicus> everything is fine with the default vlan
[19:42] <tychicus> it can talk to other devices on vlan 200
[19:49] <patdk-lap> all this talk, but no question for what is wrong?
[19:49] <tychicus> what is wrong is that as soon as I ifup eth2.200
[19:50] <patdk-lap> ?
[19:50] <tychicus> the vlan attached to eth2 can not communicate with vlan 200
[19:50] <patdk-lap> what does routing tables have to do with that?
[19:51] <patdk-lap> that has to do with forwarding
[19:51] <tychicus> as in ip_forward
[19:51] <tychicus> ?
[19:51] <patdk-lap> and routefilters, and ....
[19:52] <tychicus> here is the tutorial I used https://wiki.ubuntu.com/vlan
[19:52] <tychicus> is there something that is more complete?
[19:53] <tychicus> the ubuntu systems are the only ones having this issue, so I am trying to track down where I went wrong in the configureation
[19:57] <patdk-lap> that tutorial is complete, to setup a vlan
[19:57] <patdk-lap> that tutorial has NOTHING to do with routing between vlans
[19:57] <patdk-lap> for that, consult any firewall config tutorial you want
[19:58] <tychicus> the function of routing between vlan's is set up on the router
[19:58] <patdk-lap> so this is just an end machine?
[19:58] <tychicus> it works for every machine in the network execpt ubuntu machines
[19:58] <tychicus> yes
[19:58] <patdk-lap> well, fix up your default route then
[19:58] <patdk-lap> or turn of rp_filter
[19:58] <patdk-lap> rp_filter is a GOOD THING to have on
[19:58] <patdk-lap> but it doesn't work for multible default routes
[20:01] <tychicus> would I need to be disabled for eth2 the physical interface, or only for eth2.200 (vlan interface)?
[20:03] <patdk-lap> disabled for anything with a default gateway on it
[20:03] <patdk-lap> in your case, all
[20:10] <tychicus> what is the preferred way to do this? sudo echo 0 > sudo /proc/sys/net/ipv4/conf/all/rp_filter
[20:10] <tychicus> does not seem to work
[20:11] <sarnold> echo 0 | sudo tee /proc/sys/net/ipv4/conf/all/rp_filter  or use sudo -s to get a shell first, then just echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter
[20:11] <tychicus> sysctl -w
[20:12] <tychicus> ok thanks
[20:14] <tychicus> patdk-lap: thank you that worked
[20:14] <tychicus> sarnold: thank you toot
[20:14] <tychicus> s/toot/too
[20:27] <patdk-lap> add it into a /etc/sysctl.d/xxxx file