Hi Doctor,
On 26/05/2020 20:11, The Doctor via Openvpn-users wrote:
> Just testing out a site, but it gave us the wrong city
> and province.
>
> Wonder if this issue can be resolved by telling the client which region to
> resolve to.
>
What's the connection between your statement and the Open
Good suggestion, thanks Selva! I get exactly two duplicated messages (same
timing and everything). Let me dig into that … but it does seem that the
client-connect approach will work.
Appreciate the pointers!
… Russell
From: Selva Nair
Sent: Tuesday, May 26, 2020 8:02 PM
To: Morris, Russell
Hi,
Try this: from a command line run
$ /usr/bin/logger -t test some message
If that generates two messages you know its not openvpn but the syslog
setup. May be something not right in (r)syslog.conf, rsyslog.conf.d/* etc?
logger defaults to user.notice so you may want to try it with -p option to
You may be on to something ... 😊. I'm not running journald though (I don't
think ... just checked via ps, not seeing it a least).
I did try something, based on your comments. I created a short script (below),
configured OpenVPN up to call it (on client-connect),
#!/bin/sh
echo "`date` OpenVPN
Hi
On Tue, May 26, 2020 at 2:28 PM Morris, Russell wrote:
>
> It's possible, I won't say it's not ... LOL. FYI, all I did was add this to
> the server config file (for testing for now),
> client-connect "/usr/bin/logger -t openvpn client connect successful"
>
> And then I monitored network traff
It's possible, I won't say it's not ... LOL. FYI, all I did was add this to the
server config file (for testing for now),
client-connect "/usr/bin/logger -t openvpn client connect successful"
And then I monitored network traffic ... tcpdump on the (syslog) sender and
receiver end. I see the doub
Just testing out a site, but it gave us the wrong city
and province.
Wonder if this issue can be resolved by telling the client which region to
resolve to.
--
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President Republic
On 26/05/2020 14:48, Morris, Russell wrote:
> [...] it does trigger, but the message seems to be sent more than once? Not
> sure why, still working through that. But I did confirm, the double send is
> happening on the sending end (i.e. not the remote syslog).
Could it be that your script both p
Hi,
Thanks very much! It's funny, but I was actually trying exactly this last
night, just hadn't reported back as I was seeing one oddity with it ... it does
trigger, but the message seems to be sent more than once? Not sure why, still
working through that. But I did confirm, the double send is
On 26/05/2020 03:28, Morris, Russell wrote:
> BTW, one other minor question ... is there a particular message (from syslog)
> to check for, to know when a connection does in fact happen? It seems like
> this may be the best option?
>> ACCT/IP:PORT MULTI_sva: pool returned IPv4=192.168.xxx.xxx, IP
10 matches
Mail list logo
