Tom Roche wrote:
> 1. Several years ago (when I was first struggling with getting the
> F5NAP to work directly[6]), I tried to find a headless alternative
> (e.g., something like a NetworkManager plugin), but was told by F5
> that there was no such client for linux (at least, with the
> make/model
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
Back to this task after long detours! well, almost:
Matt Ventura Fri, 23 Jan 2015 12:47:21 -0800 [1]
>> The F5 VPN is throwing its default route over the original one, and that's
>> causing traffic to the OpenVPN server to try to route over the F5 VPN.
>> Obviously this doesn't work because the t
Tom Roche Thu, 22 Jan 2015 12:43:17 -0500 [1]
>> summary: Smells like progress! If I'm guessing correctly, the
>> `route` changes imposed by connecting to the F5VPN[2] are
>> conflicting with my server/jumpbox's current `iptables`[3] (through
>> which my client seeks to tunnel[4]). Does that claim
On 1/22/2015 9:43 AM, Tom Roche wrote:
summary: Smells like progress! If I'm guessing correctly, the `route` changes
imposed by connecting to the F5VPN[3] are conflicting with my server/jumpbox's
current `iptables` (through which my client seeks to tunnel[7]. Does that claim
seem warranted? If
summary: Smells like progress! If I'm guessing correctly, the `route` changes
imposed by connecting to the F5VPN[3] are conflicting with my server/jumpbox's
current `iptables` (through which my client seeks to tunnel[7]. Does that claim
seem warranted? If so, how to fix the server firewall?
de
On 1/21/2015 1:33 PM, Tom Roche wrote:
Tom Roche Wed, 21 Jan 2015 12:50:04 -0500 [1]
I need to tunnel one SSL VPN (F5, running on one debian host) through
another (OpenVPN, running on another debian host), but lose networking
(e.g., `ping`) after the F5 VPN connects. I'm not sure whether this
i
Tom Roche Wed, 21 Jan 2015 12:50:04 -0500 [1]
>> I need to tunnel one SSL VPN (F5, running on one debian host) through
>> another (OpenVPN, running on another debian host), but lose networking
>> (e.g., `ping`) after the F5 VPN connects. I'm not sure whether this
>> is due to my firewall/iptables
On 1/21/2015 9:50 AM, Tom Roche wrote:
[note: following contains ASCII art in the middle, and footnoted links at the
end]
summary: I need to tunnel one SSL VPN (F5, running on one debian host) through
another (OpenVPN, running on another debian host), but lose networking (e.g.,
`ping`) after
Hey, that worked wonderfully. Now I have another question:
I can telnet from one machine, running Debian 1.3, to another, running
2.1, and everything acts normally. When I do it the other way, from the
Slink machine to the Bo machine, it takes forever to get to a login:
prompt. What might be c
Hi
1: run modconf as root, go into the subdir net an press enter on the ne200
module, the module should prompt you for a io adress enter io=0x300 or 330
depending of what you have. Then hopefully you can read Installation
successfull on the screen.
2: Configure the network (/etc/init.d/network)
/ni
the net3 howto is not lacking, believe me ... it can work u miracles if ull
read and really understand it ...
did ur kernel detect ur lan card ? or if u included the module to
autumatically be loaded unpon bootup (/etc/modules), did u see the message
that looks something like eth0: 3c509 at 0
Robert Kerr <[EMAIL PROTECTED]> writes:
> Okay, is there any walk-through written on how to configure my home
> network? I've got two machines, with NE2000-compatible network cards.
> I've recompiled my kernel to give me module support of them, but now I'm
> stuck. Can anyone point me in the rig
But have you read the Ethernet-HOWTO? It should fill in a few of the
blanks.
On Wed, Apr 28, 1999 at 10:44:20AM -0600, Robert Kerr wrote:
> Okay, is there any walk-through written on how to configure my home
> network? I've got two machines, with NE2000-compatible network cards.
> I've recompile
19 matches
Mail list logo
