Need a bridge from an ethernet interface to a serial interface
This is my situation
I connected the linux pc and the dos pc with a SLIP (serial line internet protocol), so they can communicate in the sl0 interface.
I need the DOS pc can reach the router at 192.168.0.1 and the Internet, so i tried to make a bridge between sl0 and eth1
Howto check if a ethernet interface is up?
It's impossible to determine via the ipaddress i have learned, or?
Can someone please give me a hint on howto do?
Environment == Linux x86 GNU GCC.
:D
regards
Esaia (2 Replies)
Hi,
During the installation of solaris suppose I am configuring one ethernet interface that is primary but on my server there are 4 ethernet interfaces,because all other interface not configured,
what is way to find out how many ethernet interfaces are there on Server, (6 Replies)
Dear all,
I am a newbie in solaris and I need your advice.
I have a Solaris version 5.9 installed on Sunfire V240.
I am able to ssh the machine from putty remotely.
My problem is that I cannot see the display from KVM switch I have connected to it. I need also to be able to see the GUI... (2 Replies)
Hi all
I have installed a demo version of SCO OpenServer 5.0.2, I finally found it is Desktop Interface, I would like to know how to change its interface to dos based interface?
If you have any ideas, please tell me then. Thank you (2 Replies)
Hi,
For one of my application(Linux 2.6) I am using a netlink socket to get the interface changes notification.
socket(PF_NETLINK, SOCK_RAW, NETLINK_ROUTE)
Application receives netlink notification for Ethernet, bond interfaces but there is no notification about bridge interfaces changes. ... (6 Replies)
Hi,
is there any method to check the interface collisions on ethernet NIC in AIX. I know that in Solaris it's netstat -i but I've written that in AIX it doesn't show this.
Thanks®ards,
p (1 Reply)
Hi
Had an old ML590 with RS232 serial card that stopped working (spindle that advance ribbon broke) so I purchased a working used on ebay.
Printer powers up and seems fine. Put serial board from old printer in working ebay unit but no printing happens.
Does anyone know if there are any... (0 Replies)
hello,
I have a Linux server with two interfaces eth0 and eth1. I configured two IP addresses from two different networks on 2 interfaces, and I connected both interfaces on two different switches.
the IP address of eth0 is responding without problem to ping from equipment of its home network,... (25 Replies)
Hi Folks,
Here is one for the real Solaris aficionados on the site;
I have a T5240 and have to create an I/O domain with access to the serial port, in this case /dev/term/a and although I have been through the documentation I'm having some issues in identifying the device to assign.
What I... (2 Replies)
Discussion started by: gull04
2 Replies
LEARN ABOUT FREEBSD
gre
GRE(4) BSD Kernel Interfaces Manual GRE(4)NAME
gre -- encapsulating network device
SYNOPSIS
To compile the driver into the kernel, place the following line in the kernel configuration file:
device gre
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
if_gre_load="YES"
DESCRIPTION
The gre network interface pseudo device encapsulates datagrams into IP. These encapsulated datagrams are routed to a destination host, where
they are decapsulated and further routed to their final destination. The ``tunnel'' appears to the inner datagrams as one hop.
gre interfaces are dynamically created and destroyed with the ifconfig(8) create and destroy subcommands.
This driver corresponds to RFC 2784. Encapsulated datagrams are prepended an outer datagram and a GRE header. The GRE header specifies the
type of the encapsulated datagram and thus allows for tunneling other protocols than IP. GRE mode is also the default tunnel mode on Cisco
routers. gre also supports Cisco WCCP protocol, both version 1 and version 2.
The gre interfaces support a number of additional parameters to the ifconfig(8):
grekey Set the GRE key used for outgoing packets. A value of 0 disables the key option.
enable_csum Enables checksum calculation for outgoing packets.
enable_seq Enables use of sequence number field in the GRE header for outgoing packets.
EXAMPLES
192.168.1.* --- Router A -------tunnel-------- Router B --- 192.168.2.*
/
/
+------ the Internet ------+
Assuming router A has the (external) IP address A and the internal address 192.168.1.1, while router B has external address B and internal
address 192.168.2.1, the following commands will configure the tunnel:
On router A:
ifconfig greN create
ifconfig greN inet 192.168.1.1 192.168.2.1
ifconfig greN inet tunnel A B
route add -net 192.168.2 -netmask 255.255.255.0 192.168.2.1
On router B:
ifconfig greN create
ifconfig greN inet 192.168.2.1 192.168.1.1
ifconfig greN inet tunnel B A
route add -net 192.168.1 -netmask 255.255.255.0 192.168.1.1
NOTES
The MTU of gre interfaces is set to 1476 by default, to match the value used by Cisco routers. This may not be an optimal value, depending
on the link between the two tunnel endpoints. It can be adjusted via ifconfig(8).
For correct operation, the gre device needs a route to the decapsulating host that does not run over the tunnel, as this would be a loop.
The kernel must be set to forward datagrams by setting the net.inet.ip.forwarding sysctl(8) variable to non-zero.
SEE ALSO gif(4), inet(4), ip(4), me(4), netintro(4), protocols(5), ifconfig(8), sysctl(8)
A description of GRE encapsulation can be found in RFC 2784 and RFC 2890.
AUTHORS
Andrey V. Elsukov <ae@FreeBSD.org>
Heiko W.Rupp <hwr@pilhuhn.de>
BUGS
The current implementation uses the key only for outgoing packets. Incoming packets with a different key or without a key will be treated as
if they would belong to this interface.
The sequence number field also used only for outgoing packets.
BSD November 7, 2014 BSD