11-20-2018
In global zone, a network interface (VNIC) is created on L2 (MAC layer), with unique MAC address.
That is created/assigned to a zone, during zone install/creation or can be done manually as you did in first example.
When using exclusive IP stack, global zone does nothing on IP layer (L3).
So you do not need or require those forwarding options on global zone, or anything really outside vnic definition for zone.
As for your original problem, i presume KVM virtual switch discards everything not coming from assigned interface MAC from options for solaris 11 guest.
For a lab enviroment you can probably a tcpdump or snoop on kvm hypervisor interface and global zone guest, then see if network works in non global zone when dumps are running.
Hope that helps
Regards
Peasant.
7 More Discussions You Might Find Interesting
1. IP Networking
Hi,
Is there any way that i can directly take out the IP packet and see its contents.
Waiting for your answer ..............
Bye (4 Replies)
Discussion started by: manjunath
4 Replies
2. IP Networking
Hi,
I am involved in a project on Debian. One of my requirement is to route an IP packet in my application to a proxy server and receive the reply from the proxy server as an IP packet. My application handles data at the IP frame level. My application creates an IP packet(with all the necessary... (0 Replies)
Discussion started by: Rajesh_BK
0 Replies
3. Programming
can anyone tell me how can i capture the packets. i have tried ethernet software to capture them but its not doing what i want it to do it (1 Reply)
Discussion started by: dazdseg
1 Replies
4. Cybersecurity
Exercise:
Protection of WEB and DNS servers using the context-free rules for packet filtering:
- Protect your WEB-server, so that would be for him can be accessed by browsers, and could go to dns.
- Protect your primary DNS-server so that it could be to contact clients and secondary servers.... (1 Reply)
Discussion started by: numeracy
1 Replies
5. AIX
(5 Replies)
Discussion started by: Vishal_dba
5 Replies
6. UNIX for Dummies Questions & Answers
Hi all. Linux noob here.
I was hoping someone could help me with configuring some routing rules on my router, an Asus AC68.
The router is connected to two gateways, wan0_gateway and wan1_gateway.
I have rules set up in the router gui that will push all traffic from every IP other than my own... (0 Replies)
Discussion started by: Bishi
0 Replies
7. IP Networking
RHEL 7.0, IPV6
Scenario:
I have routed specific network using network scripts.
1. "ip -6 route show" shows that route has been added. ( with metric 1024)
2. Ping of the specific IP through that route is successful.
3. Now after few days, for some reason, we see that cache route appears for... (3 Replies)
Discussion started by: msr1981
3 Replies
KVM(3) BSD Library Functions Manual KVM(3)
NAME
kvm -- kernel memory interface
LIBRARY
Kernel Data Access Library (libkvm, -lkvm)
DESCRIPTION
The kvm library provides a uniform interface for accessing kernel virtual memory images, including live systems and crash dumps. Access to
live systems is via /dev/mem while crash dumps can be examined via the core file generated by savecore(8). The interface behaves identically
in both cases. Memory can be read and written, kernel symbol addresses can be looked up efficiently, and information about user processes
can be gathered.
kvm_open() is first called to obtain a descriptor for all subsequent calls.
FILES
/dev/mem interface to physical memory
COMPATIBILITY
The kvm interface was first introduced in SunOS. A considerable number of programs have been developed that use this interface, making back-
ward compatibility highly desirable. In most respects, the Sun kvm interface is consistent and clean. Accordingly, the generic portion of
the interface (i.e., kvm_open(), kvm_close(), kvm_read(), kvm_write(), and kvm_nlist()) has been incorporated into the BSD interface.
Indeed, many kvm applications (i.e., debuggers and statistical monitors) use only this subset of the interface.
The process interface was not kept. This is not a portability issue since any code that manipulates processes is inherently machine depen-
dent.
Finally, the Sun kvm error reporting semantics are poorly defined. The library can be configured either to print errors to stderr automati-
cally, or to print no error messages at all. In the latter case, the nature of the error cannot be determined. To overcome this, the BSD
interface includes a routine, kvm_geterr(3), to return (not print out) the error message corresponding to the most recent error condition on
the given descriptor.
SEE ALSO
kvm_close(3), kvm_getargv(3), kvm_getenvv(3), kvm_geterr(3), kvm_getkernelname(3), kvm_getloadavg(3), kvm_getlwps(3), kvm_getprocs(3),
kvm_nlist(3), kvm_open(3), kvm_openfiles(3), kvm_read(3), kvm_write(3)
BSD
September 14, 2011 BSD