11-05-2011
forward a Network Device via ssh
Hey foks
my problem looks like this:
Computer 1 has two network interfaces (A and B). It's connected to computer 2 via ssh using network interface A. kann I forward network interface B to computer 2, so it shows up for example in ifconfig on computer 2? how? should i use something else than ssh?
Any ideas??
SMF
8 More Discussions You Might Find Interesting
1. Programming
HI,
I am writing a network device driver for RTL8139c card on 2.6.18 kernel ... I am facing few queries listed below
1. Can i able to at all write a driver for RTL8139C or Realtek had designed new chip for 2.6 series kernel?
2. If no then which driver file 2.6.18 uses .. Is it 8139too.c or... (1 Reply)
Discussion started by: niketan
1 Replies
2. UNIX for Advanced & Expert Users
Hello there,
I have a big problem, and I hope somebody can help me. I try to realize a port forward over three server. Here is a picture...
Client Server1 | Server2
------- ------- | -------
|...... | |...... | | |...... ... (2 Replies)
Discussion started by: Art007
2 Replies
3. IP Networking
hello i have a ubuntu ssh server that i can acess from any of my comnputers but only if they are on the same wireless network as the server. i tested trhis my tehtehring my samsung blackjack to my windows partition and installing openssh to windows it works when windows is on the wireless but no... (1 Reply)
Discussion started by: old noob
1 Replies
4. IP Networking
Thanks in advance!
Ben (1 Reply)
Discussion started by: bigben1220
1 Replies
5. Red Hat
How to monitor network device traffic using MRTG?
How can I add network devices in MRTG configuration to monitor? (2 Replies)
Discussion started by: manalisharmabe
2 Replies
6. Ubuntu
Hi,
I am new to linux stuff. I want to use linux iptables to configure rule so that all my incoming traffic with protocol "tcp" is forwarded to the "FORWARD CHAIN". The traffic i am dealing with has destination addresss of my machine but i want to block it from coming to input chain and somehow... (0 Replies)
Discussion started by: arsipk
0 Replies
7. Shell Programming and Scripting
Hello all,
Here is the explanation of my problem:
I have a cronjob that connects to a NAS to do backups from my laptop to this NAS device.
The script that I wrote does check if there is a host (the NAS) responding on 192.168.1.10 and tries to connect to it with the following command:
mount -v... (3 Replies)
Discussion started by: freddie50
3 Replies
8. Red Hat
Hi All,
Could anyone please help to resolve the below problem.
I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error.
I spent 2 days for the above and go through with several suggestion found by googling. But no luck.
... (0 Replies)
Discussion started by: Tanmoy
0 Replies
EPAIR(4) BSD Kernel Interfaces Manual EPAIR(4)
NAME
epair -- A pair of virtual back-to-back connected Ethernet interfaces.
SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file:
device epair
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
if_epair_load="YES"
DESCRIPTION
The epair is a pair of Ethernet-like software interfaces, which are connected back-to-back with a virtual cross-over cable.
Each epair interface pair is created at runtime using interface cloning. This is most easily done with the ifconfig(8) create command or
using the cloned_interfaces variable in rc.conf(5). While for cloning you only give either epair or epair<n> the epair pair will be named
like epair<n>[ab]. This means the names of the first epair interfaces will be epair0a and epair0b.
Like any other Ethernet interface, an epair needs to have a network address. Each epair will be assigned a locally administered address by
default, that is only guaranteed to be unique within one network stack. To change the default addresses one may use the SIOCSIFADDR ioctl(2)
or ifconfig(8) utility.
The basic intend is to provide connectivity between two virtual network stack instances. When connected to a if_bridge(4) one end of the
interface pair can also be part of another (virtual) LAN. As with any other Ethernet interface one can configure vlan(4) support on top of
it.
SEE ALSO
ioctl(2), altq(4), bpf(4), if_bridge(4), vlan(4), loader.conf(5,) rc.conf(5), ifconfig(8)
HISTORY
The epair interface first appeared in FreeBSD 8.0.
AUTHORS
The epair interface was written by Bjoern A. Zeeb, CK Software GmbH, under sponsorship from the FreeBSD Foundation.
BSD
July 26, 2009 BSD