On Sat, Mar 09, 2019 at 12:10:34PM +0100, Michał Koc wrote:
> W dniu 09.03.2019 o 08:15, Otto Moerbeek pisze:
> > On Fri, Mar 08, 2019 at 12:03:25PM +0100, Michał Koc wrote:
> >
> > > Hi all,
> > >
> > > We have a triple redundant vpn gateway setup with sasyncd running and tons
> > > of
The default changed, X does not receive Tcp connections. In FreeBSD
I solved the problem with a file .xserverrc in my home directory
with
exec /usr/X11R6/bin/Xorg -listen tcp
But this does not work with OpenBSD 6.4 (X does not even
execute .xinitrc, I start X with xinit).
Any hint?
Thanks
Well, now the way below reads .xinitrc, perhaps a lapsus when typing before.
With "ssh -X" on the X server I get widgets from the remote server,
but not without "ssh -X".
Typing in the remote computer I get the following error:
# env DISPLAY=192.168.178.47:0.0 xterm
xterm: Xt error: Can't
W dniu 09.03.2019 o 08:15, Otto Moerbeek pisze:
On Fri, Mar 08, 2019 at 12:03:25PM +0100, Michał Koc wrote:
Hi all,
We have a triple redundant vpn gateway setup with sasyncd running and tons
of tunnels, about 1000 flows.
Looking at the graph of memory usage, you can clearly see that
On 3/9/19 2:03 PM, Roderick wrote:
>
> Well, now the way below reads .xinitrc, perhaps a lapsus when typing
> before.
>
> With "ssh -X" on the X server I get widgets from the remote server,
> but not without "ssh -X".
>
> Typing in the remote computer I get the following error:
>
> # env
Hello,
I have a local_machine and testing remote_gateway/NAT with one
remoteLAN_machine behind it. All the boxes are running OpenBSD. I can log in
(ssh) to remoteLAN_machine through port forwarded on remote_gateway/NAT.
I'm trying to setup Site-To-Site VPN between local_machine and the remote
On Sat, 9 Mar 2019, Robert Paschedag wrote:
I think you also need the "-Y" option in ssh.
Thanks, but perhaps I did not express myself correct.
I do not want to use ssh. No encription of X11. Just to do as I always
did: call an x client specifying a remote display (OpenBSD) either
with
I am on OpenBSD 6.4 amd64 also getting this error message. It seems to be
caused by my USB serial device. If I plug it into a Windows machine then
Windows reports that the device is malfunctioning. If I plug into OpenBSD
6.4 then I get the usbd_free_xfer not free error and my USB ports stop
Roderick writes:
>
> The default changed, X does not receive Tcp connections. In FreeBSD
> I solved the problem with a file .xserverrc in my home directory
> with
>
> exec /usr/X11R6/bin/Xorg -listen tcp
>
> But this does not work with OpenBSD 6.4 (X does not even
> execute .xinitrc, I start X
Roderick writes:
> On Sat, 9 Mar 2019, cho...@jtan.com wrote:
>
> > > Any hint?
> >
> > Yes: [...]
>
> Did you try it?
No but I think you missed the part where I said "and editing
/etc/X11/xenodm/Xservers" which is the where the server binary's options
(and server binary) are specified. For
On 2019-03-09, Roderick wrote:
> The default changed, X does not receive Tcp connections.
In addition, the default /etc/pf.conf blocks connections to the
X11 server:
# By default, do not permit remote connections to X11
block return in on ! lo0 proto tcp to port 6000:6010
--
Christian
On Sat, 9 Mar 2019, cho...@jtan.com wrote:
> Any hint?
Yes: [...]
Did you try it?
BTW, I started xenodm, logged in, did "xhost +", tried to run an
X client on another compiter with this display, and got the same
error.
Rodrigo
W dniu 09.03.2019 o 12:43, Otto Moerbeek pisze:
On Sat, Mar 09, 2019 at 12:10:34PM +0100, Michał Koc wrote:
W dniu 09.03.2019 o 08:15, Otto Moerbeek pisze:
On Fri, Mar 08, 2019 at 12:03:25PM +0100, Michał Koc wrote:
Hi all,
We have a triple redundant vpn gateway setup with sasyncd running
On Sat, Mar 09, 2019 at 11:19:11PM +0100, Michał Koc wrote:
> W dniu 09.03.2019 o 12:43, Otto Moerbeek pisze:
> > On Sat, Mar 09, 2019 at 12:10:34PM +0100, Michał Koc wrote:
> >
> > > W dniu 09.03.2019 o 08:15, Otto Moerbeek pisze:
> > > > On Fri, Mar 08, 2019 at 12:03:25PM +0100, Michał Koc
14 matches
Mail list logo
