heriyanto shell <[email protected]> wrote: > I'am put server as colocation in datacenter, what i get: > 1. One cable from DataCenter goes to Switch > 2. assignable IP range. > 3. Information for me to setup on my network (IP for gateway and nameserver, > Broadcast, netmask)
OK, so you will have some information like : Subnet: 211.111.51.80/29 SUbnet mask: 255.255.255.248 Gateway: 211.111.51.81 Usable IPs 211.111.51.82 to 211.111.51.86 At the moment you have one interface, eth1, with IP 211.111.51.82 > About last 3 years, so far I just put one public IP for one host, i'am use > this config in shorewall and work perfectly: > interfaces: > int eth0 > ext eth1 > > policy: > fw all ACCEPT > int all DROP info > all all REJECT info > > rtrules: > eth1 - Otong 1000 > > zones: > fw firewall > int ipv4 > ext ipv4 blacklist > > Providers: > Otong 1 1 main eth1 211.111.51.81 track > > This week i'am trying add network interface into one of my host, then put the > Public IP to the new network interface. > So i have 3 eth now, 1 is internal(vpn) and 2 for external(public IP), OK, you don't need a providers file, and you don't need an additional interface. You just need to set the IP address and default gateway in the system network config. To use a second public IP, all you need to do is add it to the same interface - in Debian (and derivatives) this can be done by adding "post-up ip addr add 211.111.51.83/29 dev eth1" to the config section for eth1 in /etc/network/interfaces. If you do want to add a second interface, then add the section in /etc/network/interfaces (but don't specify a default gateway here). Just add eth2 to the ext zone in Shorewall. At this point, any Shorewall rules allowing inbound traffic will allow the traffic on either interface/IP. One of the easiest ways to limit inbound traffic to a specific IP/interface is to use the "ext:211.111.51.82" style in the destination column of the rules file. If you don't want to embed the IP address lots of times, you can use an entry in params - eg specify "Email=211.111.51.83" in params and use ext:$Email as the destination zone. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
