divzeroweb

2f30.org website
git clone git://git.2f30.org/divzeroweb.git
Log | Files | Refs | README | LICENSE

commit a0ac812a5f861195ed16f3333e3922d8dd239aa9
parent 9ae5a4ff5973448b2b11203ea90a61686f313640
Author: sin <sin@2f30.org>
Date:   Wed Apr 30 13:04:08 +0100

Rephrase article

Diffstat:
guides/trunk.md | 10+++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/guides/trunk.md b/guides/trunk.md @@ -1,12 +1,12 @@ ### Trunk failover setup on OpenBSD -I have a dedicated machine at home that I use it mainly for sending and +I have a dedicated machine at home that I use mainly for sending and receiving e-mails. The machine has one wired interface as well as a -wireless interface. My wired interface goes over powerline adapter. +wireless interface. My wired interface goes over a powerline adapter. For various reasons every once in a while, the powerline adapter loses sync and as a result I cannot access my machine remotely. One way to solve this problem is to take advantage of the wireless interface -and transparently switch over to it when the wired interface becomes unavailable. +and transparently switch over to it whenever the wired interface becomes unavailable. To do this we'll use a simple form of interface aggregation, also known as trunk failover. For the gory details please refer to: @@ -48,8 +48,8 @@ At this point restart the interfaces: Generate some network activity by copying a large file via scp and pull the ethernet cable from your machine. The copy operation might stall but it will automatically -fallthrough to the wireless interface. If you plug your ethernet cable back in -it will switch back to the wired interface. +switch over to the wireless interface. If you plug your ethernet cable back in +it will switch to the wired interface. A sample ifconfig follows from my particular setup: