Unless you have changed your router's IP address, neither of these look like a normal router address. 192.168.0.1 or 192.168.1.1 are more common: Google your router's name and "default IP address" to find out what it should be, then browse to that IP it to check it hasn't changed. If it really is 192.168.88.44 then your RPi static address will need to be ...
I just found out that I need these lines on bitcoin.conf to access rpc from outside localhost:
or start bitcoind or bitcoin-qt with -rcpbind=xxx and -rpcallowip=xxx
Apparently if you don´t bind your ip to your lan ip, it will only work with local connections, and rpcallowip=0.0.0.0/0 is not recommended ...
If you want to display X11 apps on your Mac desktop, you don't run startx from the pi - that will attempt to start it on the pi's screen. Instead, run an X11 server on your Mac, configured to allow remote connections. Then, on the Pi, set your DISPLAY environment variable to point to the Mac's server.
In my case (macOS Sierra 10.12.6), I downloaded and ...
You do not need to worry about a crossover ethernet cable. That's a requirement from the last century. Nowadays nearly all ethernet ports have crossover auto detect built-in. You only need one port supporting this and the wired port of the Raspberry Pi do it. So just purchase a proper wired ethernet dongle for the MacBook Pro and use any ethernet cable.
The problem is that you have two interfaces eth0 and wlan0. Internet access is only through wlan0 but the default route is set to eth0 as shown by this line from the routing table:
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 0.0.0.0 0.0.0.0 U 202 0 0 eth0
I have asked for the ...
If you're already running an X server on Windows (as you are with Xming), then the Windows side is mostly done (but see below for a few important details). The key bit remaining is to tell the X11 apps on the pi to send their X11 data to your Windows PC.
This is done via the DISPLAY environment variable. Normally, if the X server and app are running on ...
If you specify now to shutdown or call for reboot, then the command take immediate effect. Among other things it stops the ssh services and you can / will get cold-dropped like that. If you want to get a warning, then you need to specify a future time for the command to execute.
Before you launch the script from ssh:
There are other possible values but, presuming there is only one GUI user logged in on the pi, it will be :0, the first display. You can also get it directly from the desktop (echo $DISPLAY) -- but not from the ssh login.
I solved that problem by using a netgear switch behind my ISP's router. The "Unitymedia ConnectBox" in my case generated about 15% packet loss. I experienced all the problems you described and it's really strange that the wifi connection runs just fine. Also RPi1 and 2 worked with my router as well (haven't bought the RPi3).
All my network devices are now ...
Recently I faced a similar problem.
My issue turned out to be too many splices in the ether cable - I had ~50ft. of cable running through the walls of my house with unknown amount of splices - which caused signal degradation.
When I connected my laptop to this cable, there were minimal to no problems. When I connected my RPi to the same cable, it was not ...