Loading README.md +6 −0 Original line number Diff line number Diff line Loading @@ -82,6 +82,12 @@ Please open an issue on <https://github.com/derf/travelynx/issues> or send a mail to derf+travelynx@finalrewind.org if there is anything missing or ambiguous in this setup manual. Note that Deutsche Bahn have put parts of their API behind an IP reputation filter. In general, checkins with the bahn.de backend will only be possible if travelynx is accessing it from a residential (non-server) IP range. See the dbris bahn.de proxy / proxies setting in `example/travelynx.conf` for workarounds. Updating --- Loading examples/travelynx.conf +19 −2 Original line number Diff line number Diff line Loading @@ -35,14 +35,31 @@ password => die("Changeme!"), }, # Settings specific to the DBRIS bahn.de backend. # Their journey endpoint (which is required for checkins) is behind an IP # reputation filter, denying requests from most non-residential IP ranges. # If needed, you can specify either a single SOCKS proxy or a set of # SOCKS proxies here, and thus work around that limitation. If multiple # proxies are specified, travelynx will choose a random one for each # request. Note that DBRIS bahn.de requests to non-journey endpoints # (such as the departure board) are always sent directly and not passed # through the proxy / proxies specified here. # "proxies" takes precedence over "proxy". dbris => { 'bahn.de' => { # proxy => 'socks://127.0.0.1:18080', # <- either this # proxies => ['socks://127.0.0.1:18080', 'socks://127.0.0.1:18081'], }, }, # Settings specific to HAFAS backends. # For instance, the PKP backend is hidden behind a GeoIP filter, hence # travelynx only supports it if travelynx.conf either indicates that it # is reachable or specifies a proxy. hafas => { PKP => { # geoip_ok => 1, # <- EITHER THIS # proxy => 'socks://...', # <- OR THIS # geoip_ok => 1, # <- either this # proxy => 'socks://...', # <- or this }, }, Loading Loading
README.md +6 −0 Original line number Diff line number Diff line Loading @@ -82,6 +82,12 @@ Please open an issue on <https://github.com/derf/travelynx/issues> or send a mail to derf+travelynx@finalrewind.org if there is anything missing or ambiguous in this setup manual. Note that Deutsche Bahn have put parts of their API behind an IP reputation filter. In general, checkins with the bahn.de backend will only be possible if travelynx is accessing it from a residential (non-server) IP range. See the dbris bahn.de proxy / proxies setting in `example/travelynx.conf` for workarounds. Updating --- Loading
examples/travelynx.conf +19 −2 Original line number Diff line number Diff line Loading @@ -35,14 +35,31 @@ password => die("Changeme!"), }, # Settings specific to the DBRIS bahn.de backend. # Their journey endpoint (which is required for checkins) is behind an IP # reputation filter, denying requests from most non-residential IP ranges. # If needed, you can specify either a single SOCKS proxy or a set of # SOCKS proxies here, and thus work around that limitation. If multiple # proxies are specified, travelynx will choose a random one for each # request. Note that DBRIS bahn.de requests to non-journey endpoints # (such as the departure board) are always sent directly and not passed # through the proxy / proxies specified here. # "proxies" takes precedence over "proxy". dbris => { 'bahn.de' => { # proxy => 'socks://127.0.0.1:18080', # <- either this # proxies => ['socks://127.0.0.1:18080', 'socks://127.0.0.1:18081'], }, }, # Settings specific to HAFAS backends. # For instance, the PKP backend is hidden behind a GeoIP filter, hence # travelynx only supports it if travelynx.conf either indicates that it # is reachable or specifies a proxy. hafas => { PKP => { # geoip_ok => 1, # <- EITHER THIS # proxy => 'socks://...', # <- OR THIS # geoip_ok => 1, # <- either this # proxy => 'socks://...', # <- or this }, }, Loading