Hi folks!
i've just downloaded the three SOlaris 8 Free install-CDs, then went to install it in a VM on VMware 2.0.3, okay DCA and CD inserted, DCA configured all devices - THEN
at the selection of the boot device - selected CD - getting DISK READ ERROR at sector 120.
Can anyone help?!!!... (1 Reply)
WEe have installed Intel version of Solaris 8 in a machine .we skipped the network configuration at the begning.we selected unnetworked.Now we need to connect the same machine to a network.
We configured the Card using ifconfig but its taking the ip address itself as the Default G/W.
I need help... (4 Replies)
hello
i had soloaris 8 installed . at the beggining it sees my network
card( intel i815/82559 onboard)(my mainboard is GA-8IRXP);
but during the installation when I fill the ip address and the dns
at the end that i should confirm it says:
no dns find (i'm sure about the dns... (4 Replies)
Hi all,
I tried to install Solaris 10 and then VMware ESX server v3.02 on the same PC (or hard drive). But after successfully installing Solaris 10, when I installed Vmware ESX Server on the same drive(but on different partition, boot menu is not coming.
It is just booting Vmware only.
Pls... (1 Reply)
I am running solaris 10 on VMware and I do not know how to setup the USB drive. After refer to few doc from sun still unable to get what i should do.
Can someone help?
On VMware I have added a USB controller.
Oh yes, from prtconf and dmesg, it don't seem to reganize the usb controller. I... (0 Replies)
Hi there,
I run a SunFire v245 with solaris 10. I run a custom ERP on that. my clients are connecting via telnet and run the application...
my last "server" was a sun blade 100 with solaris 8, everything was running correctly.
Since I have the new server, I have many problem with my... (5 Replies)
Hi all,
I have install sun solaris 10 on vmware server and i cant ping the solaris guest machine from the host and vice versa.
The enable network card in the host machine is an wifi card so I know that i can't use bridged network from Vmware.
I tried to use host or NAT but it seem not to work... (1 Reply)
Hi All,
We have configured an hp network printer on a Solaris-sparc machine.
We are unable to print any files from this machine.
The following are the other details:
lpstat -p hpnic -l
printer hpnic waiting for auto-retry. available.
exec exit fault
Form mounted:
... (0 Replies)
I am going to take up a position in Data & Network Security.
I would need to write network shell scripts doing the following task:
Going to around 2000 servers and findout which groups has access to each servers and which ids are there in each group that has access.
I need to implement... (1 Reply)
Hello all, thanks for reading my question:
So I've been a Unix/Linux SysAdmin for a couple years, and I'm a bit over my head running solo, trying to set up LDoms using Oracle VM Server 3.1 for SPARC. I've been very careful, and things have gone well up until the point I try to access the new... (9 Replies)
Discussion started by: Lyxix
9 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