Sponsored Content
Full Discussion: Zone ipf question
Operating Systems Solaris Zone ipf question Post 302686473 by bitlord on Tuesday 14th of August 2012 04:05:21 PM
Old 08-14-2012
Zone ipf question

Hello,
I was wondering, if your setting ipf filter rules on a Solaris 10 server with one or more full root zones. Where do you set it? I know that the place to set the rules is here; /etc/ipf/ipf.conf. Do I set it in each zone and the global? Or should I just set the rules at the global?

Also the the interfaces are shared. For example if you do an ifconfig -a
Code:
# ifconfig -a
lo0:  flags=2001000849<UP,LOOPBACK,RUNNING,IPv4,VIRTUAL> mtu 8232 index 1 
         inet 127.0.0.1 netmask ff000000
lo0:1:  flags=2001000849<UP,LOOPBACK,RUNNING,IPv4,VIRTUAL> mtu 8232 index 1
           zone zone-name
           inet 127.0.0.1 netmask ff000000
aggr1: flags=1000843<UP,LOOPBACK,RUNNING,IPv4,VIRTUAL> mtu 8232 index 2 
           inet 192.168.120.120 netmask ffffff00 broadcast 192.168.120.255
e1000g0: flags=1000843<UP,LOOPBACK,RUNNING,IPv4,VIRTUAL> mtu 1500 index 3 
           inet 192.168.159.25 netmask fffffe00 broadcast 192.168.159.255
e1000g0:1: flags=1000843<UP,LOOPBACK,RUNNING,IPv4,VIRTUAL> mtu 1500 index 3 
           zone zone-name
           inet 192.168.159.66 netmask fffffe00 broadcast 192.168.159.255

Please let me know what I should do?
 

9 More Discussions You Might Find Interesting

1. Solaris

Question regarding Zone Migration

I have a general question regarding Zone Migration. I have an older system that is currently running a zone configured with ProFTPD & SSL. If I want to migrate or clone that zone to another (much newer) system, will I still have to setup & configure ProFTPD & SSL on the new system? (3 Replies)
Discussion started by: em23
3 Replies

2. Solaris

ipf.conf question

OK I am running solaris 10. I made some changes to my ipf.conf file and issued the command: ipf -Fa -f /etc/ipf/ipf.conf to flush out the old and bring in the new changes. When I ran ipfstat -ioh to verify it had brought in the new rule set I saw something I wasn't expecting to see. I... (3 Replies)
Discussion started by: NewSolarisAdmin
3 Replies

3. Solaris

Some Question's about Zone

Hi all, i am new learner in Zoning and virtualization Technology and i have some question's about it i create zone using this step zonecfg -z app-apache create set zonepath=/zone_adm/app-apache add net set address=192.168.1.250 set physical=bge0 end set autoboot=true verify commit... (13 Replies)
Discussion started by: coxmanchester
13 Replies

4. Solaris

IPF on Solaris 10 prior 10 8/07 releases

I'm trying to enable IPF ( ip filter ) on solaris 10 release 6/06 Solaris 10 6/06 s10s_u2wos_09a SPARC so i enabled svc:/network/ipfilter:default it was disabled by default and svc:/network/pfil:default was enabled and online there only one config file under etc $/etc/ipf/ipf.conf i... (1 Reply)
Discussion started by: h@foorsa.biz
1 Replies

5. Cybersecurity

IPF pass in connection to port 21 even with no explicit rule

I'm running IPF on solaris 10 bash-3.00# ipf -V #display ipf version ipf: IP Filter: v4.1.9 (592) Kernel: IP Filter: v4.1.9 Running: yes Log Flags: 0 = none set Default: pass all, Logging: available Active list: 1 Feature mask: 0x107 with the following rules bash-3.00# ipfstat -o -i... (0 Replies)
Discussion started by: h@foorsa.biz
0 Replies

6. Solaris

Zone failes to boot due to mount issue, dir exists in zone.

I have two physical servers, with zones that mount local storage. We were using "raw device" in the zonecfg to point to a metadevice on the global zone (it was not mounted in the global zone at any point). It failed to mount on every boot because the directory existed in the zone. I... (6 Replies)
Discussion started by: BG_JrAdmin
6 Replies

7. UNIX for Advanced & Expert Users

ipf/ipnat NAT/port forward issues

I've been going crazy trying to get this working. Here's the situation: we have a Solaris 10 box that connects an internal network to an external network. We're using ipf/ipnat on it. We've added a couple of new boxes to the internal network (192.168.1.100, .101) and want to be able to get to port... (1 Reply)
Discussion started by: spakov
1 Replies

8. Solaris

Zone Cluster Question

I have a question about losing a node in a zone cluster. Hopefully I can explain enough for someone to answer. Let's say I have a zone cluster spread over 3 physical nodes. If Node1 crashes, would I be correct in assuming I would lose all zones on Node1? If I lost Node1 below, would I lose... (4 Replies)
Discussion started by: MasonJ
4 Replies

9. UNIX for Advanced & Expert Users

Solaris 10: I forgot to detach a zone before zpool export. Uninstall zone?

Dear all, recently, I migrated a solaris zone from one host to another. The zone was inside of a zpool. The zpool cotains two volumes. I did the following: host1: $ zlogin zone1 shutdown -y -g0 -i0 #Zone status changes from running to installed $ zpool export zone1 host2: $ zpool... (2 Replies)
Discussion started by: custos
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
All times are GMT -4. The time now is 04:21 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy