Am 02/17/15 um 21:58 schrieb trondd: > On 2/17/15, Stefan Wollny <stefan.wol...@web.de> wrote: >> Am 02/17/15 um 20:36 schrieb trondd: >>> When you are behind your server are you using NAT to get to the >>> internet or a proxy? If proxy, do you have the proxy environment >>> variables set? >>> >>> Tim. >>> >> Hi Tim, >> >> thanks for caring. >>
> > Yeah, but it also show you have a 192.168 IP address which is not > routable. You have to be connecting to the internet through > something. > >> Another friendly guy suggested to disable pf and give pkg_add a try >> without - I did so but at "gnome-keyrings" the connection was lost. > > So you can reach the server and get some packages? > Yepp - and then (around packages starting with letter 'g' at the latest) the connection is lost... :-( My internal net is 192.168.178.xxx. The NAT is provided by a Fritz!Box. Here is a copy from xterm: ~ $ sudo pkg_add -ui quirks-2.52 signed on 2015-02-17T13:51:20Z quirks-2.52->2.52: ok cmake-3.1.2->3.1.3: ok Error from http://ftp.hostserver.de/pub/OpenBSD/snapshots/packages/amd64/libxml-2.9.2p0.tgz ftp: connect: No route to host cups-2.0.2:foomatic-db-engine-4.0.11p0->4.0.12: ok cups-2.0.2:cups-filters-1.0.63->1.0.65: ok cups-2.0.2->2.0.2: ok .libs1-farstream-0.2.4+farstream-0.2.6->farstream-0.2.7: ok Error from http://ftp.hostserver.de/pub/OpenBSD/snapshots/packages/amd64/freetds-0.92.79.tgz ftp: connect: No route to host ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ AT EACH LINE 'ftp: connect: No route to host' THE CONNECTION WAS LOST! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Here is my little script to reconnect: ~ $ cat reconnect #/bin/sh sudo /sbin/ifconfig em0 down sudo /sbin/ifconfig wpi0 down sudo /sbin/ifconfig rsu0 down sudo /sbin/ifconfig trunk0 down sudo /sbin/route flush sudo sh /etc/netstart After having run this script 'pkg_add' continues as shown in the example ('cups-2.0.2:foomatic-db-engine-4.0.11p0->4.0.12: ok') It's been just a few moments ago. I quit 'pkg_add' after the second 'No route to host'. Well ... it should be nonsense but I will change the way I connect to the net: Disable 'trunk0' and connect directly via 'em0' (feel my desperation?).
