[11:59] <phalor> When I run (ufw allow in on ens3 proto tcp from any port any to 192.168.2.1 port 25), it says "ERROR: Could not find protocol". Does anyone know why?
[12:01] <sixwheeledbeast> have you tried reordering the syntax?
[12:02] <phalor> Accoring to the manual, its in the correct order
[12:03] <sixwheeledbeast> ok if that's what manpage says. i have never used "in on" and "proto" together.
[12:03] <phalor> Thanks anyway :)
[12:19] <sixwheeledbeast> ufw allow in on ens3 proto tcp from any port 25 to 192.168.2.1 port 25
[12:20] <phalor> That won't work. The connection will come in from random ports
[12:31] <sixwheeledbeast> something must be expecting traffic on a specific port? be it here or downstream?
[12:31] <phalor> sorry man?
[12:32] <phalor> yeah a mail server is expecting traffic
[12:32] <phalor> i need to get it through the firewall
[12:33] <sixwheeledbeast> so you'd need one rule for each port or pass all the traffic through
[12:33] <phalor> exactly, so i am trying to pass port 25 through
[12:34] <phalor> no sorry, i am not trying to reroute the server with this command, though that is what is happening with iptables, but its unrelated
[12:36] <sixwheeledbeast> You can do "any port > any port" or "port 25 > port 25" but not "any port > port 25"
[12:37] <phalor> from any... port any...
[12:37] <phalor> from any ip addres... from any port...
[12:38] <sixwheeledbeast> so if your expecting multiple ports inbound then route each one. 25, 587, 465, 2525 etc?
[12:38] <phalor> thats not how it works, inbound ports will be random
[12:41] <phalor> take care
[18:35] <maru> hello :) I've got question about clock in ubuntu mate 22.04 beta
[18:35] <maru> it shows 2022:35
[18:36] <maru> where 2022 is year (?) and 35 in [min]
[18:36] <maru> *is
[18:36] <maru> i want it to show hh:mm
[18:36] <maru> not yyyy:mm
[18:36] <maru> how to set it?
[19:04] <superkuh> Right click, preferences.
[19:05] <superkuh> I don't think it can display 2022:35 though.
[19:05] <superkuh> That's weird.
[19:14] <maru> wait a moment for print screen :D
[19:16] <maru> https://zapodaj.net/e115bb78b95a6.png.html
[19:16] <maru> preferences looks OK for me
[19:16] <maru> but it says 2022:16 :D
[19:31] <superkuh> Sometimes the clock applet needs you to toggle preferences before they take effect is some other thing had changed the gconf/dconf prefs settings.
[19:31] <superkuh> And vice versa.
[19:31] <superkuh> I notice this a lot changing my clock from shell scripts.
[19:31] <superkuh> Although I suppose you've toggled a bunch in trying things.
[19:32] <maru> :)
[19:32] <superkuh> If nothing else, remove that clock applet.
[19:32] <superkuh> Then add a new one.
[19:32] <superkuh> Or try adding a second.
[19:32] <superkuh> To see if it behaves badly too.
[19:33] <maru> yes I changed to manual settings, set other time, back to auto
[19:33] <maru> OK I will try to remove it and add new clock
[19:40] <maru> new clock works good! yay! :D
[19:40] <superkuh> Cool.