Can an eGPU work on bootcamp with a thunderbolt 2 port?

I aim to purchase an external gpu (likely this and am wondering if a thunderbolt 2 port will work with an eGPU on windows 10 bootcamp. I know there is a file for the mac OS to be compatible with Thunderbolt 2, but I don’t know if that’s possible on bootcamp.

If that is impossible, how efficient would a windows emulator on the mac OS work with games so I could play windows-only games/editing software? How much of a bottleneck would the emulator be on the eGPU?

macbook pro external monitor flickers when plugged in via mini display port to dvi

So the xternal monitor connected to my mbpro mid 2012 flickers when I’m using a mini dp to dvi.

I can solve this porblem by using a mini dp to vga instead. problem is it won’t output the native 1680×1050 resolution. I’ve tried using screenresx, pressing alt when pressing the scaled radio button with no luck.

So my only choice is to use a minidp to dvi to output the native resolution but with flickering.

Again I can solve the flickering by connecting both vga and dpi to the mini dp converter which has a dvi, vga and a displayport port.

Problem is when 2 cables are connected to the converter the wifi slows down to a point where I can’t use it anymore. So i only have one choice and that is to fix the flickering issue.

Nginx peerjs server returns cors error when trying to acess peerserver port

I’m having an issue with a library called peerjs Which worked on my localhost testing server, but had some growing pains working with nginx reverse proxies. Here are some things I did, but I’m still getting a CORS error when trying to access the peerjs server.

  • used “ufw allow 8696″(the port that peerserver uses)
  • used the CORS library with my nodejs server, as recommended by a different stackoverflow post*
  • Altered my nginx config to allow CORS on all paths**

You can see the error yourself at I’m wondering if there is any way to make my nodejs applications work exactly as they do on my local computer as they do on my server. p.s. I will include any information I neglected to include


var path = require('path'); var express = require('express'); var ExpressPeerServer = require('peer').ExpressPeerServer; var routes = require('./routes'); var app = express(); var cors = require('cors'); app.use(cors()); app.set('views', path.join(__dirname, 'views')); app.set('view engine', 'ejs'); app.use(express.static(path.join(__dirname, 'public'))); app.use('/', routes); var server = require('http').createServer(app); var peerserver = ExpressPeerServer(server); app.use('/ChatPal/cpl', peerserver); server.listen(8696); app.listen(6767); console.log('Listening on 6767'); 


 set $  cors_origin ""; set $  cors_cred   ""; set $  cors_header ""; set $  cors_method "";  if ($  http_origin ~ '^https?://(localhost|\.com)$  ') {         set $  cors_origin $  http_origin;         set $  cors_cred   true;         set $  cors_header $  http_access_control_request_headers;         set $  cors_method $  http_access_control_request_method; }  add_header Access-Control-Allow-Origin      $  cors_origin; add_header Access-Control-Allow-Credentials $  cors_cred; add_header Access-Control-Allow-Headers     $  cors_header; add_header Access-Control-Allow-Methods     $  cors_method; 

How to hide application port of Docker container ? Proxy ? Another solution?

I have a number of containers running of localhost. They have http streams.

They are accessible via path like this:


What I would like to do is remove port number from URL like:


How could I achieve this? What are possible solutions?

Wireguard sends packets with source port 1 when using second routing table

I have a small home server in my basement that’s connected to a router and my home network. As my cable ISP only offers public IPv6 addresses and IPv4 is behind a carrier grade NAT I bought myself a public IPv4 address using a OpenVPN connection to a third party. As the contract with the latter provider includes some traffic limitations I only want to route the “public” server traffic over the VPN connection. All in all, it looks like this:

-------------------------- | WG Host                | |------------------------| | eth0:    | <- dhcp, home network, default gateway | tun0:   | <- vpn with public ipv4 address, gw for public services | vmnet:     | <- virtual machines, server daemons | wg0:    | <- wireguard -------------------------- 

Most services I have are on the vmnet subnet, ssh (on port 110) and wireguard (on port 123) are supposed to run on the host. I have set up a second routing table and route all traffic with source ports like 80 or 443 over the VPN connection unless an internal client connects to the services, because I do not want to route all that traffic over the internet when in fact the server is right inside my home network. To be able to do this, I’ve come up with some rather complex iptables-rules:

iptables -A POSTROUTING -t nat -o tun0 -j MASQUERADE  # Always set source IP to VPN ip, so home network clients do not get confused iptables -A POSTROUTING -t nat -p tcp --sport 80 -j SNAT --to iptables -A POSTROUTING -t nat -p tcp --sport 443 -j SNAT --to  # public services, default gateway via vpn iptables -A PREROUTING -t mangle -p tcp --sport 80 -j MARK --set-mark 2 iptables -A PREROUTING -t mangle -p tcp --sport 443 -j MARK --set-mark 2  # Do the same for ssh & wireguard (123/udp) iptables -A OUTPUT -t mangle -p tcp --sport 22 ! -d -j MARK --set-mark 2 iptables -A OUTPUT -t mangle -p udp --sport 123 ! -d -j MARK --set-mark 2  ip rule add fwmark 2 table 2 ip route add default via dev tun0 table 2 ip route add dev vmnet table 2 ip route add dev eth0 table 2 

This works pretty well for the vmnet services and ssh, but wireguard’s behavior seems to be a little bit strange: It works inside my home network, but when I try to reach it from the outside, it won’t work. When doing a tcpdump on tun0 I can observe that the client’s packets reach wireguard just fine. The answering packets are obviously sent on tun0, too (so routing seems to work). The strange thing is that Wireguard sets the source port of these packets to ‘1’. Unfortunately, they never reach the client. I suppose that is because the NATs in between don’t manage to match the (srcport,dstport) combination anymore.

Ubuntu IoT – (SSH) port 22: connection refused

If I want to ssh my RPi 3 (B+) with Ubuntu Core 18.04.02 LTS installed (ssh from another computer in the same network), I always get:

port 22: Connection refused 

The only thing i can do on the RPi is press “Enter”, this reloads the screen. All other keys won’t do anything. Does anyone know how to start the console on the RPi here or to connect to the RPi?