02-09-2009
hi,
You have given the output of ifconfig output
#ifconfig -a
lo0: flags=2001000849<up, LOOPBACK, RUNNING, MULTICAST, IPv4,
VIRTUAL> mtu 8232 index 1
zone zone
inet 127.0.0.1 netmask ff000000
hme0: flags=1000803<up, BROADCAST, MULTICAST, IPv4> mtu 1500 index 2
inet 192.168.35.20 netmask ffffff00 broadcast 192.168.35.255 ether 8:0:20:c5:61:68
hme0:1: flags=1000803<up, BROADCAST, MULTICAST, IPv4> mtu 1500 index 2 zone zone
inet 192.168.35.210 netmask ffffff00 broadcast 192.168.35.255
But in this output your ip is showing in Up status, But not in running status, for this you have to add default route through command
route add default 192.168.35.1
default gatway ask your network ok it may be 192.168.35.1
add this entry in cat /etc/defaultrouter like this
default 192.168.35.1
then only you will get the status is Running then only you can ping from one zone to another zone
after adding route entry in globle zone you can see default entry automatically in non-globle zone also ok
check the link is comming in server or not in NIC card
9 More Discussions You Might Find Interesting
1. Solaris
Hi All ,
I try to install some packages in my global zone...
On the execution of the installion of the script it quits by saying the error
"Non global zone check failed"
Kindly help me in this regard
Thanks in advance,
jeganr (7 Replies)
Discussion started by: jegaraman
7 Replies
2. Solaris
How to check the global zone name from local zone. (6 Replies)
Discussion started by: fugitive
6 Replies
3. Solaris
is this the step?
add fs
set dir=/export
set special=/export
set type=lofs
add options rw
end
i notice i can't post immediately, moderator needs to moderate. i have 1 more post still haven't appear in the forum..hmm.... (1 Reply)
Discussion started by: binary0011
1 Replies
4. Solaris
Dears,
I would like to convert solaris 10 x86 and solaris 10 sparc (Global Zones) physical servers into Local zones.
i found a document which seems to be helpful but i'm stuck @ the 1st step.
to test this i want to do it 1st on x86 system running under vmware ESXi and if it succeeds i will... (1 Reply)
Discussion started by: mduweik
1 Replies
5. Solaris
Hi Greetings...
I have an issue in connecting the zone from outside the network and it is because of default gateway. I can ping default gateway from inside the zone and not able to ping from global zone due to different VLAN issue. If i add two different gateways and restart network services,... (2 Replies)
Discussion started by: vvpotugunta
2 Replies
6. Solaris
Hi,
A quick question: Can Solaris 10 local zones be moved to a Solaris 11 global zone and work well?
Thank you in advance! (5 Replies)
Discussion started by: aixlover
5 Replies
7. Solaris
can some one help me out as it is showing 2 different time zones in global zone and nonglobal zone .In global zone it is showing in GMT while in nonglobal zone i it showing as PDT.
System in running with solaris 10 (3 Replies)
Discussion started by: ravijanjanam12
3 Replies
8. Solaris
So this is Solaris 11.1. I have a Global zone that has several non-global zones running in it. I want to change the capped-memory.physical resources setting in ALL the zone configs of the running zones.
if I were to do this manually here's what I would do:
zonecfg -z zone1
select... (2 Replies)
Discussion started by: os2mac
2 Replies
9. Solaris
Hi, hoping someone can help, its been a while since I used Solaris.
After creating a NGZ (non global zone), the NGZ can access the GZ (Global Zone) and the GZ can access the NGZ (using ssh, zlogin)
However, the NGZ cannot access any other netwqork devices, it can't even see the default router
... (2 Replies)
Discussion started by: GazinLincoln
2 Replies
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