My friend, Thats true, I did manually network configuration when server is rebooted. But I am right configuration like below. I don't know. All of the network files are right. What is the main problem!. I have one NIC.
Hi all
I am facing some problem with network card
i am using solaris8 and on sunultra10 .As it is my firewal machine i have got on backup harddisk for any emergency.
In one hardidsk while installation only hme0 interface was configured and in the backup hard disk qfe0/hme0 both are... (0 Replies)
Hello,
I need explanations about physical disks and physical volumes. What is the difference between these 2 things?
In fact, i am trying to understand what the AIX lspv2command does.
Thank you in advance. (2 Replies)
How do you test the physical network connection of an interface in solaris. I know that if you have an active connection and the cable gets yanked, you can look in the messages file to check for link failure messages. But is there any better way to see if you have good layer 2 connectivity? (1 Reply)
I was in smit, checking on disc space, etc. and it appears that one of our physical volumes that is part of a large volume group, has no free physical partitions. The server is running AIX 5.1. What would be the advisable step to take in this instance? (9 Replies)
Hello All,
Can anybody please tell me what is the maximum limit of Physical IBM Power Machine which can be handled by single HMC at a single point of time?
Thanks,
Jenish (1 Reply)
Hello Friends,
I need to change network filesystem status as online but it always seems in maintenance mode, I appreciate your any suggestion to change its state as online.
shell>svcadm enable svc:/system/filesystem/local
shell>svcs -l svc:/system/filesystem/local
fmri ... (4 Replies)
After a memory upgrade all network interfaces are misconfigued. How do i resolve this issue. Below are some out puts.thanks.
ifconfig: plumb: SIOCLIFADDIF: eg000g0:2: no such interface
# ifconfig eg1000g0:2 plumb
ifconfig: plumb: SIOCLIFADDIF: eg1000g0:2: no such interface
# ifconfig... (2 Replies)
Dear All,
http:apache2 service on my node is continuously in maintenance mode.
I have tried to enable and disable the service but nothing works.
root@ops # svcs -a | grep apache2
maintenance 15:46:37 svc:/network/http:apache2
When I reboot the system, I get the following error:
... (1 Reply)
All I'm running an OpenSolaris system (Nexenta). When doing a svcs I see that/network/smb/server is in maintenance mode.
I have run a clear on the service and restarted. I see the same service show online* for a bit but then, enters maintenance every time.
In the service log I... (2 Replies)
Discussion started by: dcpatriot
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