Showing posts with label ubuntu. Show all posts
Showing posts with label ubuntu. Show all posts

Friday, July 26, 2019

Ubuntu 18 : Kannel : Sendsms failed : Connection refused

accessing the sendsms function returns "failed: Connection refused."

a telnet to the smsbox port has a similar response, which means no service is accessible on that port
allowing the port on the firewall still returns the same status

tail on the bearer box log shows:
INFO: ----------------------------------------
INFO: Kannel bearerbox II version 1.4.4 starting
INFO: MAIN: Start-up done, entering mainloop
INFO: AT2[xxxxxxxxxxx]: Logging in
INFO: AT2[xxxxxxxxxxx]: init device
INFO: AT2[xxxxxxxxxxx]: speed set to 115200
INFO: AT2[xxxxxxxxxxx]: Phase 2+ is supported
INFO: AT2[xxxxxxxxxxx]: AT SMSC successfully opened.

compared to a working installation, it's missing a "INFO: Client connected from <127 .0.0.1="">" message. hmmm... something is not running. looks like the smsbox is not starting by default.

modify /etc/defaults/kannel to enable smsbox
#START_WAPBOX=1
START_SMSBOX=1

restarting the service now shows:
INFO: ----------------------------------------
INFO: Kannel bearerbox II version 1.4.4 starting
INFO: MAIN: Start-up done, entering mainloop
INFO: AT2[xxxxxxxxxxx]: Logging in
INFO: AT2[xxxxxxxxxxx]: init device
INFO: AT2[xxxxxxxxxxx]: speed set to 115200
INFO: AT2[xxxxxxxxxxx]: Phase 2+ is supported
INFO: AT2[xxxxxxxxxxx]: AT SMSC successfully opened.
INFO: Client connected from <127 .0.0.1="">

a telnet test to the smsbox port connects!
sendsms works!</127></127>

Ubuntu 16 : Kannel : System error 13

got an error 13 when running kannel service

AT2[xxxxxxxxxxx]: open failed!
ERRNO=13 ERROR: System error 13: Permission denied

to resolve, add kannel to dialout group

usermod -a -G dialout kannel


Wednesday, December 12, 2018

Ubuntu 16 : Certificate Verify Failed

An application, hosted on an Ubuntu 16 box, calling a URL returned "certificate verify failed".

Checking if the URL is accessible, tested calling it via wget. Got "Unable to locally verify the issuer's authority."

To test URL access and response, use openssl...

# openssl s_client -showcerts -connect <host>:<port>






To install the needed certificate...

# cd /usr/local/share/ca-certificates/


# sudo mkdir <source name>
# sudo chmod 755 <source name>


# cp .crt .


# sudo chmod 644 .crt

# sudo dpkg-reconfigure ca-certificates


select new certificate to allow, then click ok

# sudo update-ca-certificates


Retest URL access and response...








OK.

Friday, January 13, 2012

ubuntu: enable ip forwarding using ufw

ufw is ubuntu's firewall configuration tool

to enable ufw
# ufw enable

to allow a port
# ufw allow <port>
ex. # ufw allow 22

edit /etc/default/ufw to accept forwarding requests
default_forward_policy = "accept"

edit /etc/ufw/sysctl.conf to allow forwarding
net.ipv4.ip_forward=1

edit /etc/ufw/before.rules, add the ff. after the first comment

# nat Table rules
*nat
:PREROUTING ACCEPT [0:0]

:POSTROUTING ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]

# Forward traffic from eth1 through eth0.
-A POSTROUTING -s 223.223.223.0/24 -j SNAT --to 192.168.0.145
#-A POSTROUTING -s 223.223.223.1 -o eth0 -j MASQUERADE
-A POSTROUTING -s 223.223.223.1 -j SNAT --to 192.168.0.145
-A POSTROUTING -s 223.223.223.2 -j SNAT --to 192.168.0.145

# don't delete the 'COMMIT' line or these table rules won't be processed
COMMIT



reload ufw by disabling and enabling the firewall

# ufw disable
# ufw enable

SSH : No matching host key type found. Their offer: ssh-rsa,ssh-dss

Got this while connecting to my mikrotik router via ssh   Unable to negotiate with <ip address> port <ssh port>: no matching hos...