Apologies for letting this thread[1] drop--I was forced to handle other
interrupts for a few weeks. Basically, I need to make a networking
configuration work, but am currently (apparently) blocked by inability to set a
route. Details:
A brief summary of what I need to do to get back to work on
On 1/25/2015 5:13 AM, Tom Roche wrote:
Tom Roche Sat, 24 Jan 2015 16:00:37 -0500 [1] (envvar names translated to
`bash`ian)
[The "original routeset" on the client/laptop:]
1: default via 192.168.1.1 dev eth0 proto static
2: 169.254.0.0/16 dev eth0 scope link metric 1000
3: 192.168.1.0/24
Tom Roche Sat, 24 Jan 2015 16:00:37 -0500 [1] (envvar names translated to
`bash`ian)
>> [The "original routeset" on the client/laptop:]
>> 1: default via 192.168.1.1 dev eth0 proto static
>> 2: 169.254.0.0/16 dev eth0 scope link metric 1000
>> 3: 192.168.1.0/24 dev eth0 proto kernel scop
On 1/24/2015 6:59 PM, Tom Roche wrote:
Tom Roche Sat, 24 Jan 2015 16:00:37 -0500 [1] (envvar names translated to
`bash`ian)
[The "original routeset" on the client/laptop:]
1: default via 192.168.1.1 dev eth0 proto static
2: 169.254.0.0/16 dev eth0 scope link metric 1000
3: 192.168.1.0/24
Tom Roche Sat, 24 Jan 2015 16:00:37 -0500 [1] (envvar names translated to
`bash`ian)
>> [The "original routeset" on the client/laptop:]
> 1: default via 192.168.1.1 dev eth0 proto static
> 2: 169.254.0.0/16 dev eth0 scope link metric 1000
> 3: 192.168.1.0/24 dev eth0 proto kernel scope l
On 1/24/2015 1:00 PM, Tom Roche wrote:
Sven Hartge Fri, 23 Jan 2015 21:53:35 +0100 [3] (tweaked)
That would complete the VPN Trinity:
* one route 0.0.0.0/1
* one route 128.0.0.0/1
* one host route to the other VPN endpoint (making it reachable regardless of
other routes)
I'm looking at the
summary: How to combine/synthesize OpenVPN and F5VPN routesets, so that
the F5VPN can tunnel through the OpenVPN? 3 more specific questions @ end.
details:
my intent [1]
>>> <-my control | agency control->
>>>|
>>> (DHCP from ISP) (stat
7 matches
Mail list logo