I'm wanting to be able to use VNC from my windows machine so I can
remote in to the Debian box and do admin stuff from within my home LAN.
I' not thinking this is something I want to be able to do from outside
the home.
There seem to be several web walk through articles for this some more detailed than others. I found this one https://tinyurl.com/yxt6ylmp and this other one https://tinyurl.com/yxfuwd2k which both want me to use
ssh and install xfce.
I like the basic Gnome desktop that seems to come with debian but getting
a remote (working) VNC session that is reliable is a nightmare for a
n00b. At least with a raspberry pi they build in a VNC server into the OS... wish Debian did the same.
Do you want to start a virtual (headless) X server or do you want to connect to
the desktop X server that is using the video card/monitor?
On 10-04-20 12:57, Oli wrote to Avon <=-
Do you want to start a virtual (headless) X server or do you want to connect to the desktop X server that is using the video card/monitor?
On 10-04-20 12:57, Oli wrote to Avon <=-
Do you want to start a virtual (headless) X server or do you want to
connect to the desktop X server that is using the video
card/monitor?
What's a good headlexx X server to use nowadays for VNC access? I've got
a use case for one.
On 04 Oct 2020 at 12:57p, Oli pondered and said...
Do you want to start a virtual (headless) X server or do you want to
connect to
the desktop X server that is using the video card/monitor?
Ideally the latter... I'm understanding that I could (if it all works) connect to a different desktop than the one I see with the login/monitor attached but ideally I'd like to be able to just remote connect and
see/use the same desktop I do now.
will be like teamview so traffic is routed via external
servers. If so I think just connecting to a VNC style
server to see my desktop would be preferable.
I thought Teamviewer and AnyDesk would help establish the
initial connection, but then the actual traffic is P2P.
RealVNC has a deb package. I haven't tried it, but maybe it does work
like the RealVNC server on Raspbian. TightVNC has the x0vncserver
command and the xorg-extension:
On 10-05-20 17:45, Oli wrote to Vk3jed <=-
I don't know what the best solution is. I would try TigerVNC first:
https://wiki.archlinux.org/index.php/TigerVNC
On 05 Oct 2020 at 05:57p, Oli pondered and said...
RealVNC has a deb package. I haven't tried it, but maybe it does
work like the RealVNC server on Raspbian. TightVNC has the
x0vncserver command and the xorg-extension:
I mucked around today with tightvnc and got that working well but it only serves us a virtual desktop and not the view of the logged in user on the box.
I intended to write "TigerVNC" not "TightVNC". There are to many options for remote desktop sharing in Linux and most of them are not very good
(if you compare it with a Windows RDP session). Something is always missing. Most VNC projects also don't have good documentation.
Now distributions are switching from X11 to Wayland – even more fun..
If I understand it correctly Gnome Wayland uses the pipewire audio/video server.
Have you tried ssh? I don't mean to be pushy but I think that is just
what you need. :)
I've used Putty to login to a Linux system using a SSH connection and then got to a command line experience...
On 10-07-20 10:42, Avon wrote to Al <=-
Have you tried ssh? I don't mean to be pushy but I think that is just
what you need. :)
I've used Putty to login to a Linux system using a SSH connection and
then got to a command line experience... if that's what you're asking?
Earlier polls to your 3/100 from 1/10 look like this
08 Oct 21:21:24 [50240] trying alterant.leenooks.net [2001:8003:4c06:5742:f1d0:3:279:1fd]...
I've reverted the IPv6 name for now, but we should probably change the
hub to n3.z21.bbs.leenooks.net - that way it'll always point to the
right place.
I could set up a CNAME to that if you want, I was thinking we establish some naming convention in the fsxnet.nz domain space for HUBs and
promote those addresses to nodes... something like net3.fsxnet.nz or similar.. what do you think?
That's not a bad idea. My only concern, is I have a dynamic IP address.
If you do that for net4, you may just want to point to bbs.castlerockbbs.com, as I keep that updated as necessary.
I think my IP address has only changed once or twice in the last 3
years, so it doesn't change often...
I've reverted the IPv6 name for now, but we should probably change the
hub to n3.z21.bbs.leenooks.net - that way it'll always point to the
right place.
I could set up a CNAME to that if you want, I was thinking we establish some naming convention in the fsxnet.nz domain space for HUBs and promote those addresses to nodes... something like net3.fsxnet.nz or similar.. what do you think?
I've started using nN.zZ.bbs.leenooks.net for nets that I hub for, since I've really seperated out the hub from my BBS. And now that I've starting setting up IPv6 it means I dont have NAT to worry about. (But there is a tranisition impact for those that can do IPv6 as we discovered yesterday).
Yeah, that's kinda why I thought a CNAME type alias may be a good move for dynamic domains but I could code any static stuff with ease. I also think for IPv6 we could set static addresses as each person would have one they could
sit on.
On another note, it seems the IPv6 rollout is ramping out (my ISP was quite backwards and concervative, and now I have it), so wondering how many do have an IPv6 address...
I've started using nN.zZ.bbs.leenooks.net for nets that I hub for, since I've really seperated out the hub from my BBS. And now that I've starting setting up IPv6 it means I dont have NAT to worry about. (But there is a tranisition impact for
those that can do IPv6 as we discovered yesterday).
I'm still setup to poll/send to alterant.leenooks.net. Should I be changing this to n3.z21.bbs.leenooks.net?
I've got one!
bbs.nrbbs.net = 2607:fea8:ab00:e4f:934f:85c:ad29:d978
Cool, I probably already connect to you over IPv6? So if you change to the n3.z21... address, you'll connect directly to my container.
Technically, my IPv6 address is dynamic.
I think its tied to the MAC address that connects to the network - so it has changed a couple of times as I've rejigged my equipment. (Not
recently though, which is why I'm more confident to publicize it more).
I will be changing providers soon that guarantee "me" a static IP (both IPv6 and IPv4) - so naturally when I do that, I want that to be as transparent as possible. SO yes, a CNAME back to what I use means your
not involved nor a dependancy in that change.
My static name for hubing networks, going forward will be a semi fido DNS standard, ie: FSX will be nF.zZZ.bbs.leenooks.net (where F and Z are the appropriate net and zone numbers).
On another note, it seems the IPv6 rollout is ramping out (my ISP was quite backwards and concervative, and now I have it), so wondering how many do have an IPv6 address...
I could set up a CNAME to that if you want, I was thinking we establish some naming convention in the fsxnet.nz domain space for HUBs and
promote those addresses to nodes... something like net3.fsxnet.nz or similar.. what do you think?
So, just pondering a naming convention.
net1.fsxnet.nz
So, just pondering a naming convention.
net1.fsxnet.nz
hub1.fsxnet.nz
..then I'm all tapped out - ha!
This is 6, or is it half a dozen? :)
As I tell all the women I meet - I'm easy, still doesnt get me anywhere though .... ?
net1.fsxnet.nz
I think this would be the best choice.
On 08 Oct 2020 at 08:24p, alterego pondered and said...
I've reverted the IPv6 name for now, but we should probably change
the hub to n3.z21.bbs.leenooks.net - that way it'll always point to
the right place.
I could set up a CNAME to that if you want, I was thinking we establish some naming convention in the fsxnet.nz domain space for HUBs and promote those addresses to nodes... something like net3.fsxnet.nz or similar..
what do you think?
I'm still setup to poll/send to alterant.leenooks.net. Should I be
changing this to n3.z21.bbs.leenooks.net?
Yes you can.
I am in the middle of drafting an email, but was going to wait sending it until Avon decides on his CNAME idea.
At the end of the day, Avon's CNAME will point to n3.z21.... so by you using that directly, or whatever Avon configures - it will still work.
I usually use whatever address is in the nodelist. Why not use A and AAAA on the same domain?
On another note, it seems the IPv6 rollout is ramping out (my ISP
was quite backwards and concervative, and now I have it), so
wondering how many do have an IPv6 address...
More than you would expect, I seem to get a few polling in / and can poll them outbound also using it, which is cool.
was quite backwards and concervative, and now I have it), so
wondering how many do have an IPv6 address...
More than you would expect, I seem to get a few polling in / and can them outbound also using it, which is cool.
After being tntroduced in December 1995 (24 years ago) it's finally happening! ;)
By: Avon to All on Fri Oct 09 2020 03:48 pm
So, just pondering a naming convention.
net1.fsxnet.nz
I could set up a CNAME to that if you want, I was thinking we establis some naming convention in the fsxnet.nz domain space for HUBs and prom those addresses to nodes... something like net3.fsxnet.nz or similar.. what do you think?
Would it make things easier or more reliable? Isn't it just an
additional layer
and potential point of failure? What about SRV records?
But what do I care, I'm connecting to the .onion address over Tor anyway
I'm working on this now.
I'm still setup to poll/send to alterant.leenooks.net. Should I bechanging this to n3.z21.bbs.leenooks.net?
Yes you can.
I am in the middle of drafting an email, but was going to wait sending
it until
Avon decides on his CNAME idea.
At the end of the day, Avon's CNAME will point to n3.z21.... so by you using that directly, or whatever Avon configures - it will still work.
Just wondering what are your thoughts about provisioning for a separate IPv4 and IPv6 address to give folks the option of forcing a
poll using a domain
they know will point only to IPv4 or IPv6?
Seems like a good option to offer.
net1.fsxnet.nz to point to both my A and AAAA records and was thinking of something like
ipv4.net1.fsxnet.nz
ipv6.net1.fsxnet.nz
or similar. What do you think?
I have set net3.fsxnet.nz to CNAME to this new schema you have set at
your end. If you do have any specific v4 or v6 addresses I can point to down the track let me know so I can set a A or AAAA record for it :)
I have set net3.fsxnet.nz to CNAME to this new schema you have set at your end. If you do have any specific v4 or v6 addresses I can point to down the track let me know so I can set a A or AAAA record for it
:)
Is this a problem needing a fix?
It would introduce more points of management that I'm not keen on. As I say, technically I'm dynamic IPs until I change suppliers, and i'm a few weeks away from doing that. So if my IP changes I've already got enough moving parts that I need to fix, so not really looking for more (if it isnt a problem).
ipv4.net1.fsxnet.nz
ipv6.net1.fsxnet.nz
or similar. What do you think?
There are advantages to this naming convention - as you can then
delegate out that part of your zone. EG: For those with dynamic IPs, I'm assuming you wont have an API so that folks can dyndns update their
A/AAAA record? But they could delegate that out to cloudflare (for example), and use cloudflares API to do those dyndns updates.
Actually, I'm wondering if Synchronet can do that as well - since DM provides a dynamic DNS service for synchro.net
net3.fsxnet.nz is an alias for n3.z21.bbs.leenooks.net. n3.z21.bbs.leenooks.net is an alias for fidohub.leenooks.net. fidohub.leenooks.net has address 101.186.5.106
fidohub.leenooks.net has IPv6 address 2001:8003:4c06:5742:f1d0:a:1:1
Looks good from here:
Looks good from here:
net3.fsxnet.nz is an alias for n3.z21.bbs.leenooks.net. n3.z21.bbs.leenooks.net is an alias for fidohub.leenooks.net. fidohub.leenooks.net has address 101.186.5.106
fidohub.leenooks.net has IPv6 address 2001:8003:4c06:5742:f1d0:a:1:1
I changed the Mystic HUB over to poll you using the new domain, also seems fine :)
14:00:32 1-Connected by IPV4 SSL to 101.186.5.106
Hmmm.. surprised you came in over IPv4 - I thought you had IPv6?
I know you can setup "preferences" to use one over the other that might
be in play here...
On 10-10-20 13:37, Avon wrote to Oli <=-
Where we have HUBs that don't have static IPv4 or IPv6 addresses then
the option to have a CNAME seemed like a way to offer a standardized fsxNet net domain name to poll without needing to know it's error404 or leenooks etc.
SRV records I know little of but if there's a good way to use them I'm
all ears :)
On 10-10-20 13:19, Avon wrote to alterego <=-
I've set
net1.fsxnet.nz to point to both my A and AAAA records and was thinking
of something like
ipv4.net1.fsxnet.nz
ipv6.net1.fsxnet.nz
or similar. What do you think?
On 09 Oct 2020 at 09:07a, Oli pondered and said...
I could set up a CNAME to that if you want, I was thinking we
establis some naming convention in the fsxnet.nz domain space
for HUBs and prom those addresses to nodes... something like
net3.fsxnet.nz or similar.. what do you think?
Would it make things easier or more reliable? Isn't it just an
additional layer
and potential point of failure? What about SRV records?
Well good question. I'm coming at this from the POV that it's
standardizing the information we can give new nodes such that if they are polling fsxNet NET 1 instead of polling agency.bbs.nz they use net1.fsxnet.nz and certainly cosmetically and perhaps more intuitively seems a better thing to be typing in to the domain field.
Where we have HUBs that don't have static IPv4 or IPv6 addresses then the option to have a CNAME seemed like a way to offer a standardized fsxNet
net domain name to poll without needing to know it's error404 or leenooks etc.
SRV records I know little of but if there's a good way to use them I'm all ears :)
But what do I care, I'm connecting to the .onion address over Tor
anyway
indeed :) I'm not sure if there's a need for me to do any DNS stuff in the fsxnet.nz domain space for this that would help? If there is, lemme know.
Yep it is, just tried IPv6 and got this
20:46:53 1-Using address 2001:8003:4C06:5742:F1D0:000A:0001:0001
20:46:59 1-Unable to connect
Hmm, we actually have hubs with dynamic IPs? Another challenge (though not a big one these days). :)
On 10-10-20 21:32, alterego wrote to Vk3jed <=-
What's the challenge?
I run quite a few services that are at the end of a dynamic IPs, and
been doing it for donkeys.
Sysop: | altere |
---|---|
Location: | Houston, TX |
Users: | 66 |
Nodes: | 4 (0 / 4) |
Uptime: | 00:27:36 |
Calls: | 643 |
Files: | 7,638 |
Messages: | 293,299 |