I can connect to Internet only if AT&T client is running

Hi,

I have the next problem on OpenSuse 11.2:
I needed to connect remote to my computer at work. I’ve installed AT&T client (agnclient-1.0-2.0.1.3003.i386.rpm + prerequisites). All is working fine, I can connect to my computer from work using KRDC. But I have the next problem:
From that point on I can browse the internet only after I start AT&T client.
Probably AT&T client broke the ip table, but I really don’t know how to fix this. It is interesting that Skype works with/without AT&T client running. But it is the only one.
I used AT&T client with OpenSuse 11.0 and I didn’t have this problem.
I’m not a linux specialist. I started to use linux in order to see how Java programs look/run on linux systems (I’m a java programmer).
Has somebody any idea how to fix this?
Thank you for any suggestion.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

It’d be useful to have a list of tests done to verify some things work
while others do not. For example, post the output from the following:

ip addr
ip route
cat /etc/resolv.conf
dig novell.com
dig -x 130.57.5.70
ping -c 1 novell.com
ping -c 1 130.57.5.70

I doubt iptables is at fault, though it could be if something went in
there and changed the allowances for outbound traffic. To get the current
iptables settings:

sudo /usr/sbin/iptables-save

Good luck.

rneagoie wrote:
> Hi,
>
> I have the next problem on OpenSuse 11.2:
> I needed to connect remote to my computer at work. I’ve installed AT&T
> client (agnclient-1.0-2.0.1.3003.i386.rpm + prerequisites). All is
> working fine, I can connect to my computer from work using KRDC. But I
> have the next problem:
> From that point on I can browse the internet only after I start AT&T
> client.
> Probably AT&T client broke the ip table, but I really don’t know how to
> fix this. It is interesting that Skype works with/without AT&T client
> running. But it is the only one.
> I used AT&T client with OpenSuse 11.0 and I didn’t have this problem.
> I’m not a linux specialist. I started to use linux in order to see how
> Java programs look/run on linux systems (I’m a java programmer).
> Has somebody any idea how to fix this?
> Thank you for any suggestion.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJLLAK7AAoJEF+XTK08PnB5YT8QAJpDqfDS1s4yogahriklHTvK
6cppxjA1zUOlrUVul9Q3mTWSS80oh3NAJLRssFY3ZaSQBWS4kKQxpVq6UwDSlInE
RJf8q3qGL2/hJZVskskRcoyl9tK6eAKLB6VIdkym1sPJkCFUB/InthSjWbzoMiiu
uNmtfyCVAbMyeMD/51+Vox+tDI0elbAfN38EYFNEIYitlFQKO3MiQwh995mnmxQX
O8RWk8Zf5rS5bJhFjvz2wrfh0LtPXU0wC1WYWXfUAOwVlWQfbWbcUTbBizyA1M9X
0LztmJov+ej8HVr8ZBNMFv5h5H/Mu8CmJ+yI+Z0p9wQyHz20jAzafGhjsi/bxnng
46fCAOTj1Msdvr0KYvRDU0j1W9Sp2a0jWmAQuyutbKOVAR7H59ETRXXsiDaZPNRE
Cxjh6IPLY0QHbPJQy7/pNIEf0+ni0USQxhUr/ObHJaTBvIwLnYsY3dyiYryLUOjn
D1bl9uZLxkirLHYFx5BR9z1Zp0MUaHdFzdLtaYzAzyVo1h9M28Of25uGRMQZQk+p
zLyNeDTybo3KzJFDPwu/p0fOpYYDvURm86bJbhiVWR2qkCtUHMzSqTRdyy6vX8uZ
BPhQL4RLBdrG6G3ijgrQBTthpMxgynHHZkpZmPdV6/mqlTLf1UnSJvHsThTCfbdE
aj68/UWrsiwsoG8M91ga
=r987
-----END PGP SIGNATURE-----

Thank you for quick reply.

I attach below the output of the commands you indicated for test.
Sure, I issued the commands without having AT&T client running.
In /etc/resolv.conf I have a lot of next entry (so that I list it only once):
#@NETVPN_GENERATED@ – this file is generated by NetVPN

and will be overwritten by NetVPN

as long as the above mark is intact

nameserver 9.64.163.21
nameserver 9.64.162.21

So:


linux-9dj0:/home # ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
link/ether 00:0a:e4:b5:11:23 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.113/24 brd 192.168.0.255 scope global eth0
inet6 fe80::20a:e4ff:feb5:1123/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:16:6f:25:42:02 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.111/24 brd 192.168.0.255 scope global eth1
inet6 fe80::216:6fff:fe25:4202/64 scope link
valid_lft forever preferred_lft forev

linux-9dj0:/home # ip route
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.113 metric 1
192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.111 metric 2
default via 192.168.0.1 dev eth0 proto static


linux-9dj0:/home # cat /etc/resolv.conf
#@NETVPN_GENERATED@ – this file is generated by NetVPN

and will be overwritten by NetVPN

as long as the above mark is intact

nameserver 9.64.163.21
nameserver 9.64.162.21

/etc/resolv.conf file autogenerated by netconfig!

Before you change this file manually, consider to define the

static DNS configuration using the following variables in the

/etc/sysconfig/network/config file:

NETCONFIG_DNS_STATIC_SEARCHLIST

NETCONFIG_DNS_STATIC_SERVERS

NETCONFIG_DNS_FORWARDER

or disable DNS configuration updates via netconfig by setting:

NETCONFIG_DNS_POLICY=’’

See also the netconfig(8) manual page and other documentation.

Note: Manual change of this file disables netconfig too, but

may get lost when this file contains comments or empty lines

only, the netconfig settings are same with settings in this

file and in case of a “netconfig update -f” call.

Please remove (at least) this line when you modify the file!

nameserver 193.231.189.18
nameserver 192.168.0.1


linux-9dj0:/home # dig novell.com

; <<>> DiG 9.6.1-P1 <<>> novell.com
;; global options: +cmd
;; connection timed out; no servers could be reached


linux-9dj0:/home # dig -x 130.57.5.70

; <<>> DiG 9.6.1-P1 <<>> -x 130.57.5.70
;; global options: +cmd
;; connection timed out; no servers could be reached


linux-9dj0:/home # ping -c 1 novell.com
ping: unknown host novell.com


linux-9dj0:/home # ping -c 1 130.57.5.70
PING 130.57.5.70 (130.57.5.70) 56(84) bytes of data.

— 130.57.5.70 ping statistics —
1 packets transmitted, 0 received, 100% packet loss, time 0ms


linux-9dj0:/home # sudo /usr/sbin/iptables-save

Generated by iptables-save v1.4.4 on Sat Dec 19 14:56:53 2009

*raw
:PREROUTING ACCEPT [733:436887]
:OUTPUT ACCEPT [852:89956]
-A PREROUTING -i lo -j NOTRACK
-A OUTPUT -o lo -j NOTRACK
COMMIT

Completed on Sat Dec 19 14:56:53 2009

Generated by iptables-save v1.4.4 on Sat Dec 19 14:56:53 2009

*filter
:INPUT DROP [0:0]
:FORWARD DROP [0:0]
:OUTPUT ACCEPT [0:0]
:forward_ext - [0:0]
:input_ext - [0:0]
:reject_func - [0:0]
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state ESTABLISHED -j ACCEPT
-A INPUT -p icmp -m state --state RELATED -j ACCEPT
-A INPUT -i eth0 -j input_ext
-A INPUT -i eth1 -j input_ext
-A INPUT -j input_ext
-A INPUT -m limit --limit 3/min -j LOG --log-prefix "SFW2-IN-ILL-TARGET " --log-tcp-options --log-ip-options
-A INPUT -j DROP
-A FORWARD -m limit --limit 3/min -j LOG --log-prefix "SFW2-FWD-ILL-ROUTING " --log-tcp-options --log-ip-options
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -m state --state NEW,RELATED,ESTABLISHED -j ACCEPT
-A OUTPUT -m limit --limit 3/min -j LOG --log-prefix "SFW2-OUT-ERROR " --log-tcp-options --log-ip-options
-A input_ext -m pkttype --pkt-type broadcast -j DROP
-A input_ext -p icmp -m icmp --icmp-type 4 -j ACCEPT
-A input_ext -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A input_ext -m pkttype --pkt-type multicast -j DROP
-A input_ext -m pkttype --pkt-type broadcast -j DROP
-A input_ext -p tcp -m limit --limit 3/min -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -j LOG --log-prefix "SFW2-INext-DROP-DEFLT " --log-tcp-options --log-ip-options
-A input_ext -p icmp -m limit --limit 3/min -j LOG --log-prefix "SFW2-INext-DROP-DEFLT " --log-tcp-options --log-ip-options
-A input_ext -p udp -m limit --limit 3/min -m state --state NEW -j LOG --log-prefix "SFW2-INext-DROP-DEFLT " --log-tcp-options --log-ip-options
-A input_ext -j DROP
-A reject_func -p tcp -j REJECT --reject-with tcp-reset
-A reject_func -p udp -j REJECT --reject-with icmp-port-unreachable
-A reject_func -j REJECT --reject-with icmp-proto-unreachable
COMMIT

Completed on Sat Dec 19 14:56:53 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

A couple things make me suspicious. First and foremost, you appear to
have two NICs with different IP addresses on the same network. Usually
that’s a bad thing unless you are REALLY sure it is not, and even then I’d
question it.

Second, you have four nameservers listed in /etc/resolv.conf which is not,
by itself, a bad thing. What makes me suspicious is that you have the
“far” nameservers 9.x.x.x listed first and should probably have
192.168.0.1 listed first assuming your local router/modem/whatever can
handle DNS like it probably can. This is not the root problem, though,
since you cannot even ping the Internet properly by IP address. Other
tests to do:

ping 192.168.0.1

then, after turning off one NIC as shown below, try again and see if it
improves assuming it did not work before:

sudo /sbin/ifdown eth1
ping 192.168.0.1

If that works try the other ping/dig tests mentioned before. If pinging
130.57.5.70 works but pinging novell.com does not then fix your hosts file
by putting the 192.168.0.1 entry at the top of the list, or make it the
only ‘nameserver’ entry in there.

Good luck.

rneagoie wrote:
> Thank you for quick reply.
>
> I attach below the output of the commands you indicated for test.
> Sure, I issued the commands without having AT&T client running.
> In /etc/resolv.conf I have a lot of next entry (so that I list it only
> once):
> #@NETVPN_GENERATED@ – this file is generated by NetVPN
> # and will be overwritten by NetVPN
> # as long as the above mark is intact
> nameserver 9.64.163.21
> nameserver 9.64.162.21
>
> So:
>
> -----------------------------------------------------------------
> linux-9dj0:/home # ip addr
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> state UNKNOWN qlen 1000
> link/ether 00:0a:e4:b5:11:23 brd ff:ff:ff:ff:ff:ff
> inet 192.168.0.113/24 brd 192.168.0.255 scope global eth0
> inet6 fe80::20a:e4ff:feb5:1123/64 scope link
> valid_lft forever preferred_lft forever
> 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> state UP qlen 1000
> link/ether 00:16:6f:25:42:02 brd ff:ff:ff:ff:ff:ff
> inet 192.168.0.111/24 brd 192.168.0.255 scope global eth1
> inet6 fe80::216:6fff:fe25:4202/64 scope link
> valid_lft forever preferred_lft forev
> ---------------------------------------------------------------
> linux-9dj0:/home # ip route
> 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.113
> metric 1
> 192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.111
> metric 2
> default via 192.168.0.1 dev eth0 proto static
>
> -----------------------------------------------------------------
> linux-9dj0:/home # cat /etc/resolv.conf
> #@NETVPN_GENERATED@ – this file is generated by NetVPN
> # and will be overwritten by NetVPN
> # as long as the above mark is intact
> nameserver 9.64.163.21
> nameserver 9.64.162.21
> ### /etc/resolv.conf file autogenerated by netconfig!
> #
> # Before you change this file manually, consider to define the
> # static DNS configuration using the following variables in the
> # /etc/sysconfig/network/config file:
> # NETCONFIG_DNS_STATIC_SEARCHLIST
> # NETCONFIG_DNS_STATIC_SERVERS
> # NETCONFIG_DNS_FORWARDER
> # or disable DNS configuration updates via netconfig by setting:
> # NETCONFIG_DNS_POLICY=’’
> #
> # See also the netconfig(8) manual page and other documentation.
> #
> # Note: Manual change of this file disables netconfig too, but
> # may get lost when this file contains comments or empty lines
> # only, the netconfig settings are same with settings in this
> # file and in case of a “netconfig update -f” call.
> #
> ### Please remove (at least) this line when you modify the file!
> nameserver 193.231.189.18
> nameserver 192.168.0.1
>
> -----------------------------------------------------------------
> linux-9dj0:/home # dig novell.com
>
> ; <<>> DiG 9.6.1-P1 <<>> novell.com
> ;; global options: +cmd
> ;; connection timed out; no servers could be reached
>
> -----------------------------------------------------------------
> linux-9dj0:/home # dig -x 130.57.5.70
>
> ; <<>> DiG 9.6.1-P1 <<>> -x 130.57.5.70
> ;; global options: +cmd
> ;; connection timed out; no servers could be reached
>
> -----------------------------------------------------------------
> linux-9dj0:/home # ping -c 1 novell.com
> ping: unknown host novell.com
>
> -----------------------------------------------------------------
> linux-9dj0:/home # ping -c 1 130.57.5.70
> PING 130.57.5.70 (130.57.5.70) 56(84) bytes of data.
>
> — 130.57.5.70 ping statistics —
> 1 packets transmitted, 0 received, 100% packet loss, time 0ms
>
> -----------------------------------------------------------------
> linux-9dj0:/home # sudo /usr/sbin/iptables-save
> # Generated by iptables-save v1.4.4 on Sat Dec 19 14:56:53 2009
> *raw
> :PREROUTING ACCEPT [733:436887]
> :OUTPUT ACCEPT [852:89956]
> -A PREROUTING -i lo -j NOTRACK
> -A OUTPUT -o lo -j NOTRACK
> COMMIT
> # Completed on Sat Dec 19 14:56:53 2009
> # Generated by iptables-save v1.4.4 on Sat Dec 19 14:56:53 2009
> *filter
> :INPUT DROP [0:0]
> :FORWARD DROP [0:0]
> :OUTPUT ACCEPT [0:0]
> :forward_ext - [0:0]
> :input_ext - [0:0]
> :reject_func - [0:0]
> -A INPUT -i lo -j ACCEPT
> -A INPUT -m state --state ESTABLISHED -j ACCEPT
> -A INPUT -p icmp -m state --state RELATED -j ACCEPT
> -A INPUT -i eth0 -j input_ext
> -A INPUT -i eth1 -j input_ext
> -A INPUT -j input_ext
> -A INPUT -m limit --limit 3/min -j LOG --log-prefix "SFW2-IN-ILL-TARGET
> " --log-tcp-options --log-ip-options
> -A INPUT -j DROP
> -A FORWARD -m limit --limit 3/min -j LOG --log-prefix
> "SFW2-FWD-ILL-ROUTING " --log-tcp-options --log-ip-options
> -A OUTPUT -o lo -j ACCEPT
> -A OUTPUT -m state --state NEW,RELATED,ESTABLISHED -j ACCEPT
> -A OUTPUT -m limit --limit 3/min -j LOG --log-prefix "SFW2-OUT-ERROR "
> --log-tcp-options --log-ip-options
> -A input_ext -m pkttype --pkt-type broadcast -j DROP
> -A input_ext -p icmp -m icmp --icmp-type 4 -j ACCEPT
> -A input_ext -p icmp -m icmp --icmp-type 8 -j ACCEPT
> -A input_ext -m pkttype --pkt-type multicast -j DROP
> -A input_ext -m pkttype --pkt-type broadcast -j DROP
> -A input_ext -p tcp -m limit --limit 3/min -m tcp --tcp-flags
> FIN,SYN,RST,ACK SYN -j LOG --log-prefix "SFW2-INext-DROP-DEFLT "
> --log-tcp-options --log-ip-options
> -A input_ext -p icmp -m limit --limit 3/min -j LOG --log-prefix
> "SFW2-INext-DROP-DEFLT " --log-tcp-options --log-ip-options
> -A input_ext -p udp -m limit --limit 3/min -m state --state NEW -j LOG
> --log-prefix "SFW2-INext-DROP-DEFLT " --log-tcp-options
> --log-ip-options
> -A input_ext -j DROP
> -A reject_func -p tcp -j REJECT --reject-with tcp-reset
> -A reject_func -p udp -j REJECT --reject-with icmp-port-unreachable
> -A reject_func -j REJECT --reject-with icmp-proto-unreachable
> COMMIT
> # Completed on Sat Dec 19 14:56:53 2009
> ----------------------------------------------------------------
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJLLNo1AAoJEF+XTK08PnB53FIQAKJec6E1HjH+fpztdpUyrHTx
VBsRjq064CRSrYuidcznBrcY5gxIlGDkzC90iWNhzZv69FiRC1T8ymo8uPDzPjCQ
/b2xsTmlc0ECwBPrf8nj/taYxsS1tmgDjyZdE+n8ZaEeHMBFoUVQ5Dssv/+y+ObP
OuAS/lcQV9EGvbnqB7HcbpTVNcHrbo5yBAiWw7o0ZG+bogjieK7NoKXIPt062Pah
5tw67R7XixoW9/I2g6imbWaa5/vedNc+UdqF6pOz71ji1GzDZHL1DsDU32PICRQC
4WqBi8NXg79cQLQJoxDvodDlpJhz8AMCojZDiBtEGmsVL8at4Zw7Dd9A27HYeEJp
maniMCjRS6qBcX2WeFC/NMVX9MHCiyPplN/lu3PAe4L93KfqyNk2LmpCSUG1r+Ur
8PdGEVF7dglY43B4QvBjFQoQFYEIPIlIOCud/wheFE25p2tjeCFEq387YZjdHqTZ
LMmyo5sBPJjj5XBHcXOrYQgJmR+LQLhct55CWoSXoglH9nC+ysSc4fv/anQJVXd5
bYWwbrS3C3vUAcZN4TN7gbbDaoizwB3ppf8tsL1Qdl2k41Dw9vofm1u25TfBCmW9
P/GBM6yse7Jq9inEGuCh1+ExZYxlu4LvVHYab2ffI+gaMy+ys1HMrdxBkTs5R5rP
M5GZCwsUI7zowzcuF2qd
=oHP1
-----END PGP SIGNATURE-----

Problem fixed. Thank you very much!
The problem was indeed the /etc/resolv.conf file, where, there were a lot of occurrences of the 9.x.x.x IP addresses.
I checked the /etc/resolv.conf.netconfig file and it has only these entries:
nameserver 82.76.253.115
nameserver 192.168.0.1

I’m behind of a router and 82.76.253.115 is the primary DNS listed by the router’s admin console, for WAN IP address.
So resolv.conf.netconfig looked OK. I deleted resolv.conf in order to be recreated after its template (resolv.conf.netconfig).
I restarted the network service (/etc/init.d/network restart) and… Internet is working without AT&T!

I checked, after I start AT&T client, those two entries are added in /etc/resolv.conf (9.x.x.x); they are probably the DNS used by VPN generated IP address. But these entries are removed after I close AT&T client. Seems to work OK now.
Probably AT&T client didn’t work properly at a moment and it added those DNSs (9.x.x.x) for so many times.

Thank you again for your help.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Good to hear. Thank-you for posting back your results.

Good luck.

rneagoie wrote:
> Problem fixed. Thank you very much!
> The problem was indeed the /etc/resolv.conf file, where, there were a
> lot of occurrences of the 9.x.x.x IP addresses.
> I checked the /etc/resolv.conf.netconfig file and it has only these
> entries:
> nameserver 82.76.253.115
> nameserver 192.168.0.1
>
> I’m behind of a router and 82.76.253.115 is the primary DNS listed by
> the router’s admin console, for WAN IP address.
> So resolv.conf.netconfig looked OK. I deleted resolv.conf in order to
> be recreated after its template (resolv.conf.netconfig).
> I restarted the network service (/etc/init.d/network restart) and…
> Internet is working without AT&T!
>
> I checked, after I start AT&T client, those two entries are added in
> /etc/resolv.conf (9.x.x.x); they are probably the DNS used by VPN
> generated IP address. But these entries are removed after I close AT&T
> client. Seems to work OK now.
> Probably AT&T client didn’t work properly at a moment and it added
> those DNSs (9.x.x.x) for so many times.
>
> Thank you again for your help.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJLLSjgAAoJEF+XTK08PnB53JIP/j4LLABtk6duq099yY0ryf5K
yyG65KVssJHakI8qYIgvGoa2s/vk1eQ55+1uAT43JPFy4+iFjTCri626BMM6beG2
Cx3av1LsDIyoPcpuRf23gu8h+riydTaiED+WLj0bt4n1b/2vIkTczNhCw+NBKPvX
TqaSaM6bI9Kvn/SuEN/Evs9pye+RrwAQhjkKELc2ggypfxY0Gj3XQms6HswOmFrx
mc7xL7Nei6QyJQd0tSjLkbGXOy9HFsHC5yUuBAUDXoi3diusqSwtUS2Q2j+W56eT
zyhAQiFO4ecxizo9JdEDR7pOdIkY9oXsJfDMMuvYFRwzZQKAC7SHP3jlfmVuei0d
vquZgrVl/dQkNjtSONHpkK0zr6bbHcSmzJgl32XXlm9XKm0/+DwBNCaLNwup4vUu
It/dDIxX+hpAiGHAUAlri0MJEBwA29cV0iU1bhqAaL5N13FoRjti+FMc4jpvsRFI
lXI406HMSo7ih9U/hUWpsgwdtzMTwNtBSM6F22nVVzyrGwXlc4+zbGADBpQNuI8D
X0fYlboDAHxqXAlqbdT6le8A4JbqnsTdkP+OH6Ty6CfThdG42D0xDKvWJ+cTDktX
dlRfHC72ENC0sOul8C0eVdqGLIgkKHw6iPj/XH7PaFv07UPPEDowM03fwdA/t2ME
solSWkxkKiow2cBWtckM
=gzSv
-----END PGP SIGNATURE-----