2 NIC with 2 Subnets

I've got to setup a Small server (2008) but I'm trying to know how to do a few simple things.
1) The network has 2 Networks a 10.10.x.x network that's connected to a Static IP & DLS Line, and a 192.168.x.x network that's connected to a Fiber Line (Dynamic IP Address)
2) The Server is only running as a Web server, but pulls data from a second computer on the 10.10.x.x network
3) We need to be able to access the Intranet Website from Either Network, so I'm guessing for both Networks the computer will need 2 Static IP Addresses
4) We would like for all Internet Calls (Web Services) that the server only uses the 192.168.x.x Network
I've done configurations for single Subnet networks, but not this dual network configuration.  Can it be done, and if so, how?

Hi,
It may not work like you expected. See:
Configuring multiple gateways on a network
http://windows.microsoft.com/en-us/windows/configuring-multiple-network-gateways#1TC=windows-7
To solve this problem, do the following:
Configure a default gateway for the network adapter that's connected to the network with the most routes (usually the network adapter that's connected to the Internet).
Don't configure a default gateway for any other network adapter. Instead, use static routes or dynamic routing protocols to add the routes for the other disjoint networks to the local IP routing table. If the routing infrastructure uses Routing Information
Protocol (RIP) for IPv4, you can turn on RIP Listener in Windows, which allows your computer to learn other routes on the network by "listening" to broadcast RIP messages, and then adding IPv4 routes to the routing table. If the routing infrastructure
doesn't use RIP, you can't use RIP listening. The alternative is to use the route add -p command to manually add the individual routes to the IPv4 routing table. For IPv6, you must use the netsh interface ipv6 add route command.

Similar Messages

  • Need help Please. Which play nice with macs? Palm Treo's Or Tmobile MDA?

    Hi all, I post on here from time to time, but hardly anyone ever answers my questions. Here's my dilema. I bought a Tmobile MDA over the weekend that runs microsoft windows mobile 5.0. And while playing with it have noticed some things about it that i think are'nt that good. For example, I like the fact that its a windows os, but think that it's flawed. I have done quite a bit of research but don't think that it's active sync software is even compatible with mac osx. so have'nt even tried to mess with it. now i'm still in the 14 day window and am thinking about returning it. but here's the thing....
    I know that tmobile has EDGE, and it's considerably slower than verizon or sprints EVDO. (since i've researched it i know that edge is around the 70-170KBPS range when EVDO has 300-700KBPS) And tonight i was messing with this tmobile MDA and finally got it to work to connect to the net with it using bluetooth and it's "modem" ability to connect it to the web. But it S U C K S! i went to and did a bandwith test and i was only getting like 12.1-27.1kbps download (after running 2 tests) dude, it feels slower than dialup!
    so with that bullet against it, comes the compatible part. I can't sycn this thing with my mac for NOTHING! do any of you out there have a palm treo? (either verizon, sprint, or att.... carrier X?) How does it sync with your mac? is it hard? any extra software i need to get/buy? have any of you used it to connect to the net? and if so, how's the speed? And here's an even bettter question... How long did it take to config it to work using the phone as a modem? Did you use bluetooth? or serial link? was it easy to config? Where did you find the instructions?
    I know these are a lot of questions, but this is a large investment for me. I mean this thing ain't cheap and it does'nt really play nice. I don't mind paying a little extra, for some peace of mind, and knowing that it won't crash often and will work with my mac. Anyone out there got any other suggestions? I would really appreciate it. I would like your opinion on which one is the easiest to use that plays nice with a mac, and has a interface that's almost as nice. Thank you so much for your time. I will be following this post closely and comment you all back for your replys
    Mac Book Pro 1.83 GHZ 512 Ram   Mac OS X (10.4.5)  

    It really is a toss up cause Ive owned two Treo's and Ive read extensive reviews on Windows mobile devices and it seems to me like they're pretty similar in the way of hardware and software(minus the fact of using different operating systems). So I think the determining factor really ought to be more focused on how much you're willing to pay, and the level of support you get for each device. I recently got rid of my Treo 650 due to an interesting touchscreen problem and got a windows mobile device(should come tomorrow)
    in the way of syncing with a mac:
    The Treo is extremely simple to set up and use with a Mac(keep in mind Im not talking about the 700w/wx)in every aspect. Palm provides OSx compatible software(though its almost impossible to get rid of after installation). However, in my experience, Palm does not really do a good job in the customer service department. While they have a rather extensive support page for each device(some of the info is outdated), that's pretty much all you get unless you don't mind spending hrs scouring various forums. Talking to customer service is a joke. Like I said I had a problem with the touchscreen and the best the rep could give me was "try a hard reset" and "send it in for repair".
    I have yet to experience what windows mobile will be like. At the very least with syncing, theres syncing software made by people who had OSx in mind(ie: Missing Sync or Pocketmac) who will probably be able to help out a lot more in this area and possible also be able to help out with the other issues you mentioned.
    a good place to check out would be howardforums.com, you'll probably get better answers there.

  • I had an iphone 4s and it worked nice with facetime and imessage using my phone number but  it was stolen on December so I buy a new iphone 4s using the same cellphone number  but now imessage and facetime does not work with my number, it only works with

    I had an iphone 4s and it worked nice with facetime and imessage using my phone number but  it was stolen on December so I buy a new iphone 4s using the same cellphone number  but now imessage and facetime does not work with my number, it only works with my apple ID.   Please Help me I speak Spanish so  if my English is not ok  I´m sorry about it.
    Do you think that apple has to   reset in their database of the old serial number attached with my phone number and that’s why I can´t activate imessage and facetime with my number in the new iphone 4s?? 

    I understand all of this Meg; that is why I bought an Iphone; but never expected my phone not even give a at least a 24 or even 12 hours....I work 12 hour shifts and also would expect to have to charge each night but not twice a day or more.  I am not always somewhere I can charge my phone.
    Your points are true; however it doesn't help me......

  • How to get the MAC address of the additional 10G NIC with ILO command line

    how to get the MAC address of the additional 10G NIC with ILO command line?
    thanks.
    This question was solved.
    View Solution.

    Hi Bruce,
    Out from what I can find on this network card is it not possible to get the mac address without a OS. I would recommend you to get/burn a Linux/Ubuntu live CD/DVD and run a Ifconfig in there.
    Hope it helps you.
    Best regards
    Zincas
    I work on behalf of HP

  • NICs with the same MAC on one switch

    Hi all,
    Presuming that we connect 2 NICs with the same MAC to one switch (port1 and port2), what would a switch handle such condition? Will the MAC table be messed up?
    Actually, in a cloud computing environment, different VMs from different customer might connect with the same virtual switch and both VM could have the same MAC and/or IP address.
    I just wondering how could a switch handle this.
    thank you!

    Alain's answer is a good one..
    It breaks the fundamentals of switching to have TWO separate physical ports registering the same MAC address in the CAM table. As he mentioned, the switch would have to constantly rewrite the CAM entry each time a frame appears from a different physical interface.
    If the two identical MAC addresses appeared on the same physical port, that does not break any "rules" of switching - all you would see is 1 entry in the switch for that physical interface.
    As for your follow-up question regarding the cloud environment. I can't say I have any experience in that type of environment, but I would say that Private VLANs might be one of the potential answers.

  • "IP and router address not consistent with subnet mask"

    Hi all,
    i have one of the old Powermac G5's running os x 10.3.5 "Panther" with a dual 2.5ghz processor, 512mb or ram, 160 gig hd, and no wireless card. I've been trying to hook the computer up to my network via an Ethernet cable (I have a Linksys WRT54G series router).
    the problem is this: When I go through the Network utilities using the "assist me" option, select the LAN option, put in the necessary information (IP address, subnet mask, router address, and the dns host), and select continue, this message pops up:"IP and router address not consistent with subnet mask".
    What I've found is that no matter if the computer is plugged in with a cable to the Ethernet port the message comes up which is very unusual.
    Thanks in advance.

    Have you verified that you indeed have the proper subnet entered?
    Why don't you just let the Mac obtain its ip address from the router via DHCP?

  • Why won't iTunes 'play nice' with Windows 8.1

    After following painstaking, tedious Troubleshooting hoop-jumping**, iTunes (latest version) STILL refuses to "play nice" with Windows 8.1
    Stalls out (Windows Task Manager reports "not responding") and does truly nasty things like blanking computer display and making Windows 8.1 system commands non-responsive (iTunes also has to be Forced closed ['End Task'] using Task Manager)
    My question:
    ANY HOPE that iTunes will EVENTUALLY actually work with Windows 8.1?? (Of course, there's NO '8.1' listed in drop-down menu, inspiring further confidence!)
    Adding INSULT to INJURY - Apple programmers DEMAND/FORCE creation of NSA-grade Password to Login to iTunes!!?!  (8 minimum, mandatory Capital and lower case letters, plus number(s), plus NO repeats, plus NO "common passwords" [whatever THOSE are] etc. etc. etc....ad nauseum)
    ARGGGH!
    ** Update iTunes, start in Safe mode, re-start (iTunes & Windows), check AV status, shut down AV & firewall, scan for viruses, check status of all drivers, all DLL's, any "possibly conflicting" applications [whatever THOSE are], create new User Account, etc. etc. etc. ad nauseum!
    At the risk of repeating myself ...  ARGGGH!

    Just checking that you've tried "iTunes Safe Mode" as opposed to "Windows Safe Mode"?
    Press and hold down CTRL+SHIFT the instant you click the icon that launches iTunes and keep holding until this message appears.
    Click Continue, then close iTunes and reopen. Some people seem to have had success with this approach...
    Alternatively, have you tried removing all iTunes components and then reinstalling as shown in the second box of Troubleshooting issues with iTunes for Windows updates?
    tt2

  • Make Illustrator play nice with OS X Spaces, eh?

    Hey Mr & Mrs Adobe --
    Can you pretty please make your apps play nice with OS X Spaces? It's only been around since October 2007. I'm tired of having documents in two different spaces.  k'thanks.

    While I don't believe this discussion belongs here (try Feature Requests, next time), I think Adobe is not completely innocent here. Spaces is a feature of the OS that's been around for two years, and that Adobe has had access to for even longer. Other companies with fewer resources than Adobe, and without developer seeds, were able to support Spaces from day 1. Even programs released before Leopard usually work with it.
    Adobe has proven that they do not care about Mac OS conventions or about fully supporting the Macintosh OS. For the amount of money they charge for their programs and upgrades (which are often little more than bug fixes that should be no charge) it is not asking too much for support of basic OS features.

  • How to get iPod 4 to play wifi-nice with my other wireless devices?

    Anyone has this problem? It's either iPod 4 or everything else!
    I just bought a new iPod 4 in additional to my iPod 3. I doesn't feel as good as my current iPod, but that's beside the point. My iPod 3 is still the favorite, even before I found the problem.
    All of my wireless devices at home work just fine:
    . -Motorola Wireless Modem (set to g, wep sec)
    . -iPod 3
    . -Apple Macbook
    . -Gateway laptop
    . -Lenovo laptop
    . -2 Sony laptops
    . -Nokia tablet
    . -HTC winmo phone
    *iPod 4 join my Motorolla wireless
    . +*ONLY IPOD 4 WORKS*
    . +The following wireless STOP working
    . -iPod 3
    . -Apple Macbook
    . -Gateway laptop
    . -Lenovo laptop
    . -2 Sony laptops
    . -Nokia tablet
    . -HTC winmo phone
    *Poweroff iPod 4
    . -All wireless devices work
    *Poweron iPod 4, Airplane on
    . -All wireless devices work
    *Poweron ipod 4, Airplane off
    . -All wireless devices work
    *Poweron iPod 4, but not join Motorola wireless
    . -All wireless devices work
    How to get iPod 4 to play wifi-nice with my other wireless devices?
    Message was edited by: iUser

    Thanks again for you help.  I finally got the music resting on my iPad moved into iTunes and then got the music resting on my iPod backed up in iTunes.  Final step was to get the music on my iPad onto my iPod without loading the iPod music onto the iPad.  I use my iPod strictly for music and don't want to clog my iPad with all those songs.   Anyway, long process but it worked.  Thanks again.

  • If apple is dropping iDisk are they going to play nice with others?

    If apple is dropping iDisk are they going to play nice with Pages amd Numbers apps and let me access SkyDrive, DropBox, Box and so on?  Or am I stuck with the lame iWork?

    Whether Apple will ever support direct connections to any of the other cloud services is something no one here knows or can say. You can comment to Apple on the matter here, if you wish:
    http://www.apple.com/feedback
    For now, there is a workaround for DropBox by using an intervening service and the Copy to WebDAV option. Whether there's a similar option for other services I don't know. Otherwise, the only option is sharing via email or synchronzation via iCloud.
    Regards.

  • Cheap wireless router that plays nice with macs??

    Greetings:
    I have the older cone-shaped airport extreme base station...
    it's working fine & I'm very happy with it.
    My situation is this....
    Periodically I go thru times of network degradation when I pull my hair out trying to ascertain if the issue is my ISP mothership, my cable modem, the airport extreme base station, or any of the myriad of links in the chain along the way.
    It's struck me on more than one occasion that it sure would be handy if I had *another wireless router on the shelf that I could grab & go with.
    At issue, however are several matters:
    --the fact that many other routers don't play nice with macs
    --the fact that I **need to do WEP security (it seems to be being dropped by a lot of newer routers).......but my TIVO won't do WPA & also I still have 2 older imacs on my home wireless network.
    I would LOVE to hear a recommendation of something cheap & locally plentiful (like at the local best buy) that still does WEP & will play nice with macs.
    Thanks for your help.
    tm

    You have the option to configure both your AirPort Extreme and the AirPort Express to "participate in a WDS network, so the Express will connect to the AiirPort Extreme using wireless only and then "extend" the reach of the wireless network.
    Or, connect the Express to the Extreme using an Ethernet cable and configure it to "create a wireless nework", which will also provide more wireless coverage.....with greater bandwidth because you are connecting routers together using Ethernet, not wireless.
    The following Apple document will give  you all the options:
    http://support.apple.com/kb/HT4145

  • 2 IP for a NIC with Solaris 8

    Hi, i would like to know if it's possible to assign 2 IP to a NIC with Solaris 8?
    I looked high and low and can't find the answer to my question...
    Please can someone help me?
    If you guys got any good website (English / French) that explain how to do that it would be really appreciated.
    Thx

    ISTR you could also go about it another way --
    "ifconfig hme0:1 plumb" (for example).Yes, absolutely.
    addif is probably the more graceful way, to avoid
    name collisions.In this case I picked it just because I thought the man page could explain 'addif' more easily than the entire concept of virtual interfaces (which you then have to plumb..).
    Of course I also think that the configuration of the virtual interface is simpler
    echo "xx.xx.xx.xx" > /etc/hostname.<int>:1
    To do it with addif, you have to make additional changes to /etc/hostname.<int> that makes it a little less nice.
    Darren

  • Multiple NICs, same subnet

    I am building a test device requiring 6 IP addresses on the same subnet, unique 4th octets (xxx.xxx.xxx.101,102,103,...).  I am using 6 pxi 8231 NICs., 8108 controller, and 1045 PXI chaasis.  MAX will allow the target to configure 3 channels with an odd 4th octet, using 255.255.255.254.  The even IP addresses are disabled with the message one device per subnet.  The mask 255.255.255.255 is defined as an invalid mask by MAX.  Are there any suggestions to resolve this?  Can it be done using a hub or switch and a single card  (NIC)by tricking up the mask (255.255.255.0)?  I have also attempted this programmatically but could not confirm the IP addresses that have been set on the NICS
    Thanks,
    Phil.

    The use of the 255.255.255.254 was recommended by the NI engineer who is attempting to help me resolve this problem.  I have attempted to use several masks without success.  I understand the mask is currently inhibiting my ability to load the even ip addresses. 

  • Need to have mail1 play nice with upstream mail server....

    Switched to new mail server and hitting a problem. We have a debian linux box doing SPAM filtering further upstream from the mail server and then sending down to the new leopard mail1 box.
    On the debian box we're seeing:
    2009-04-03 09:14:08 H=216-174-222-148.atgi.net (email.wdcsc.org) [216.174.222.148] F=<[email protected]> temporarily rejected RCPT <[email protected]>: remote host address is the local host
    2009-04-03 09:14:08 1Lpfar-0004fh-Ku ** [email protected] R=dnslookup T=remote_smtp: SMTP error from remote mail server after RCPT TO:<[email protected]>: host nescosrv.nesco.ee [194.204.28.195]: 550 5.1.1 <[email protected]>: Recipient address rejected: User unknown in local recipient table
    And mail isn't piping thru to the mail1 box. Here's the main.cf
    sh-3.2# cat main.cf
    # Global Postfix configuration file. This file lists only a subset
    # of all parameters. For the syntax, and for a complete parameter
    # list, see the postconf(5) manual page (command: "man 5 postconf").
    # For common configuration examples, see BASIC_CONFIGURATION_README
    # and STANDARD_CONFIGURATION_README. To find these documents, use
    # the command "postconf html_directory readme_directory", or go to
    # http://www.postfix.org/.
    # For best results, change no more than 2-3 parameters at a time,
    # and test if Postfix still works after every change.
    # SOFT BOUNCE
    # The soft_bounce parameter provides a limited safety net for
    # testing. When soft_bounce is enabled, mail will remain queued that
    # would otherwise bounce. This parameter disables locally-generated
    # bounces, and prevents the SMTP server from rejecting mail permanently
    # (by changing 5xx replies into 4xx replies). However, soft_bounce
    # is no cure for address rewriting mistakes or mail routing mistakes.
    #soft_bounce = no
    # LOCAL PATHNAME INFORMATION
    # The queue_directory specifies the location of the Postfix queue.
    # This is also the root directory of Postfix daemons that run chrooted.
    # See the files in examples/chroot-setup for setting up Postfix chroot
    # environments on different UNIX systems.
    queue_directory = /private/var/spool/postfix
    # The command_directory parameter specifies the location of all
    # postXXX commands.
    command_directory = /usr/sbin
    # The daemon_directory parameter specifies the location of all Postfix
    # daemon programs (i.e. programs listed in the master.cf file). This
    # directory must be owned by root.
    daemon_directory = /usr/libexec/postfix
    # QUEUE AND PROCESS OWNERSHIP
    # The mail_owner parameter specifies the owner of the Postfix queue
    # and of most Postfix daemon processes. Specify the name of a user
    # account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
    # AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
    # particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
    # USER.
    mail_owner = _postfix
    # The default_privs parameter specifies the default rights used by
    # the local delivery agent for delivery to external file or command.
    # These rights are used in the absence of a recipient user context.
    # DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
    #default_privs = nobody
    # INTERNET HOST AND DOMAIN NAMES
    # The myhostname parameter specifies the internet hostname of this
    # mail system. The default is to use the fully-qualified domain name
    # from gethostname(). $myhostname is used as a default value for many
    # other configuration parameters.
    #myhostname = host.domain.tld
    #myhostname = virtual.domain.tld
    # The mydomain parameter specifies the local internet domain name.
    # The default is to use $myhostname minus the first component.
    # $mydomain is used as a default value for many other configuration
    # parameters.
    #mydomain = domain.tld
    # SENDING MAIL
    # The myorigin parameter specifies the domain that locally-posted
    # mail appears to come from. The default is to append $myhostname,
    # which is fine for small sites. If you run a domain with multiple
    # machines, you should (1) change this to $mydomain and (2) set up
    # a domain-wide alias database that aliases each user to
    # [email protected].
    # For the sake of consistency between sender and recipient addresses,
    # myorigin also specifies the default domain name that is appended
    # to recipient addresses that have no @domain part.
    #myorigin = $myhostname
    #myorigin = $mydomain
    # RECEIVING MAIL
    # The inet_interfaces parameter specifies the network interface
    # addresses that this mail system receives mail on. By default,
    # the software claims all active interfaces on the machine. The
    # parameter also controls delivery of mail to user@[ip.address].
    # See also the proxy_interfaces parameter, for network addresses that
    # are forwarded to us via a proxy or network address translator.
    # Note: you need to stop/start Postfix when this parameter changes.
    #inet_interfaces = all
    #inet_interfaces = $myhostname
    #inet_interfaces = $myhostname, localhost
    # The proxy_interfaces parameter specifies the network interface
    # addresses that this mail system receives mail on by way of a
    # proxy or network address translation unit. This setting extends
    # the address list specified with the inet_interfaces parameter.
    # You must specify your proxy/NAT addresses when your system is a
    # backup MX host for other domains, otherwise mail delivery loops
    # will happen when the primary MX host is down.
    #proxy_interfaces =
    #proxy_interfaces = 1.2.3.4
    # The mydestination parameter specifies the list of domains that this
    # machine considers itself the final destination for.
    # These domains are routed to the delivery agent specified with the
    # local_transport parameter setting. By default, that is the UNIX
    # compatible delivery agent that lookups all recipients in /etc/passwd
    # and /etc/aliases or their equivalent.
    # The default is $myhostname + localhost.$mydomain. On a mail domain
    # gateway, you should also include $mydomain.
    # Do not specify the names of virtual domains - those domains are
    # specified elsewhere (see VIRTUAL_README).
    # Do not specify the names of domains that this machine is backup MX
    # host for. Specify those names via the relay_domains settings for
    # the SMTP server, or use permit_mx_backup if you are lazy (see
    # STANDARD_CONFIGURATION_README).
    # The local machine is always the final destination for mail addressed
    # to user@[the.net.work.address] of an interface that the mail system
    # receives mail on (see the inet_interfaces parameter).
    # Specify a list of host or domain names, /file/name or type:table
    # patterns, separated by commas and/or whitespace. A /file/name
    # pattern is replaced by its contents; a type:table is matched when
    # a name matches a lookup key (the right-hand side is ignored).
    # Continue long lines by starting the next line with whitespace.
    # See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
    #mydestination = $myhostname, localhost.$mydomain, localhost
    #mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
    mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
    # mail.$mydomain, www.$mydomain, ftp.$mydomain
    # REJECTING MAIL FOR UNKNOWN LOCAL USERS
    # The local_recipient_maps parameter specifies optional lookup tables
    # with all names or addresses of users that are local with respect
    # to $mydestination, $inet_interfaces or $proxy_interfaces.
    # If this parameter is defined, then the SMTP server will reject
    # mail for unknown local users. This parameter is defined by default.
    # To turn off local recipient checking in the SMTP server, specify
    # local_recipient_maps = (i.e. empty).
    # The default setting assumes that you use the default Postfix local
    # delivery agent for local delivery. You need to update the
    # local_recipient_maps setting if:
    # - You define $mydestination domain recipients in files other than
    # /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
    # For example, you define $mydestination domain recipients in
    # the $virtual_mailbox_maps files.
    # - You redefine the local delivery agent in master.cf.
    # - You redefine the "local_transport" setting in main.cf.
    # - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
    # feature of the Postfix local delivery agent (see local(8)).
    # Details are described in the LOCAL_RECIPIENT_README file.
    # Beware: if the Postfix SMTP server runs chrooted, you probably have
    # to access the passwd file via the proxymap service, in order to
    # overcome chroot restrictions. The alternative, having a copy of
    # the system passwd file in the chroot jail is just not practical.
    # The right-hand side of the lookup tables is conveniently ignored.
    # In the left-hand side, specify a bare username, an @domain.tld
    # wild-card, or specify a [email protected] address.
    #local_recipient_maps = unix:passwd.byname $alias_maps
    local_recipient_maps = proxy:unix:passwd.byname $alias_maps
    #local_recipient_maps =
    # The unknown_local_recipient_reject_code specifies the SMTP server
    # response code when a recipient domain matches $mydestination or
    # ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
    # and the recipient address or address local-part is not found.
    # The default setting is 550 (reject mail) but it is safer to start
    # with 450 (try again later) until you are certain that your
    # local_recipient_maps settings are OK.
    unknown_local_recipient_reject_code = 550
    # TRUST AND RELAY CONTROL
    # The mynetworks parameter specifies the list of "trusted" SMTP
    # clients that have more privileges than "strangers".
    # In particular, "trusted" SMTP clients are allowed to relay mail
    # through Postfix. See the smtpd_recipient_restrictions parameter
    # in postconf(5).
    # You can specify the list of "trusted" network addresses by hand
    # or you can let Postfix do it for you (which is the default).
    # By default (mynetworks_style = subnet), Postfix "trusts" SMTP
    # clients in the same IP subnetworks as the local machine.
    # On Linux, this does works correctly only with interfaces specified
    # with the "ifconfig" command.
    # Specify "mynetworks_style = class" when Postfix should "trust" SMTP
    # clients in the same IP class A/B/C networks as the local machine.
    # Don't do this with a dialup site - it would cause Postfix to "trust"
    # your entire provider's network. Instead, specify an explicit
    # mynetworks list by hand, as described below.
    # Specify "mynetworks_style = host" when Postfix should "trust"
    # only the local machine.
    #mynetworks_style = class
    #mynetworks_style = subnet
    #mynetworks_style = host
    # Alternatively, you can specify the mynetworks list by hand, in
    # which case Postfix ignores the mynetworks_style setting.
    # Specify an explicit list of network/netmask patterns, where the
    # mask specifies the number of bits in the network part of a host
    # address.
    # You can also specify the absolute pathname of a pattern file instead
    # of listing the patterns here. Specify type:table for table-based lookups
    # (the value on the table right-hand side is not used).
    #mynetworks = 168.100.189.0/28, 127.0.0.0/8
    #mynetworks = $config_directory/mynetworks
    #mynetworks = hash:/etc/postfix/network_table
    # The relay_domains parameter restricts what destinations this system will
    # relay mail to. See the smtpd_recipient_restrictions description in
    # postconf(5) for detailed information.
    # By default, Postfix relays mail
    # - from "trusted" clients (IP address matches $mynetworks) to any destination,
    # - from "untrusted" clients to destinations that match $relay_domains or
    # subdomains thereof, except addresses with sender-specified routing.
    # The default relay_domains value is $mydestination.
    # In addition to the above, the Postfix SMTP server by default accepts mail
    # that Postfix is final destination for:
    # - destinations that match $inet_interfaces or $proxy_interfaces,
    # - destinations that match $mydestination
    # - destinations that match $virtual_alias_domains,
    # - destinations that match $virtual_mailbox_domains.
    # These destinations do not need to be listed in $relay_domains.
    # Specify a list of hosts or domains, /file/name patterns or type:name
    # lookup tables, separated by commas and/or whitespace. Continue
    # long lines by starting the next line with whitespace. A file name
    # is replaced by its contents; a type:name table is matched when a
    # (parent) domain appears as lookup key.
    # NOTE: Postfix will not automatically forward mail for domains that
    # list this system as their primary or backup MX host. See the
    # permit_mx_backup restriction description in postconf(5).
    #relay_domains = $mydestination
    # INTERNET OR INTRANET
    # The relayhost parameter specifies the default host to send mail to
    # when no entry is matched in the optional transport(5) table. When
    # no relayhost is given, mail is routed directly to the destination.
    # On an intranet, specify the organizational domain name. If your
    # internal DNS uses no MX records, specify the name of the intranet
    # gateway host instead.
    # In the case of SMTP, specify a domain, host, host:port, [host]:port,
    # [address] or [address]:port; the form [host] turns off MX lookups.
    # If you're connected via UUCP, see also the default_transport parameter.
    #relayhost = $mydomain
    #relayhost = [gateway.my.domain]
    #relayhost = [mailserver.isp.tld]
    #relayhost = uucphost
    #relayhost = [an.ip.add.ress]
    # REJECTING UNKNOWN RELAY USERS
    # The relay_recipient_maps parameter specifies optional lookup tables
    # with all addresses in the domains that match $relay_domains.
    # If this parameter is defined, then the SMTP server will reject
    # mail for unknown relay users. This feature is off by default.
    # The right-hand side of the lookup tables is conveniently ignored.
    # In the left-hand side, specify an @domain.tld wild-card, or specify
    # a [email protected] address.
    #relay_recipient_maps = hash:/etc/postfix/relay_recipients
    # INPUT RATE CONTROL
    # The in_flow_delay configuration parameter implements mail input
    # flow control. This feature is turned on by default, although it
    # still needs further development (it's disabled on SCO UNIX due
    # to an SCO bug).
    # A Postfix process will pause for $in_flow_delay seconds before
    # accepting a new message, when the message arrival rate exceeds the
    # message delivery rate. With the default 100 SMTP server process
    # limit, this limits the mail inflow to 100 messages a second more
    # than the number of messages delivered per second.
    # Specify 0 to disable the feature. Valid delays are 0..10.
    #in_flow_delay = 1s
    # ADDRESS REWRITING
    # The ADDRESS_REWRITING_README document gives information about
    # address masquerading or other forms of address rewriting including
    # username->Firstname.Lastname mapping.
    # ADDRESS REDIRECTION (VIRTUAL DOMAIN)
    # The VIRTUAL_README document gives information about the many forms
    # of domain hosting that Postfix supports.
    # "USER HAS MOVED" BOUNCE MESSAGES
    # See the discussion in the ADDRESS_REWRITING_README document.
    # TRANSPORT MAP
    # See the discussion in the ADDRESS_REWRITING_README document.
    # ALIAS DATABASE
    # The alias_maps parameter specifies the list of alias databases used
    # by the local delivery agent. The default list is system dependent.
    # On systems with NIS, the default is to search the local alias
    # database, then the NIS alias database. See aliases(5) for syntax
    # details.
    # If you change the alias database, run "postalias /etc/aliases" (or
    # wherever your system stores the mail alias file), or simply run
    # "newaliases" to build the necessary DBM or DB file.
    # It will take a minute or so before changes become visible. Use
    # "postfix reload" to eliminate the delay.
    #alias_maps = dbm:/etc/aliases
    #alias_maps = hash:/etc/aliases
    #alias_maps = hash:/etc/aliases, nis:mail.aliases
    #alias_maps = netinfo:/aliases
    # The alias_database parameter specifies the alias database(s) that
    # are built with "newaliases" or "sendmail -bi". This is a separate
    # configuration parameter, because alias_maps (see above) may specify
    # tables that are not necessarily all under control by Postfix.
    #alias_database = dbm:/etc/aliases
    #alias_database = dbm:/etc/mail/aliases
    #alias_database = hash:/etc/aliases
    #alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
    # ADDRESS EXTENSIONS (e.g., user+foo)
    # The recipient_delimiter parameter specifies the separator between
    # user names and address extensions (user+foo). See canonical(5),
    # local(8), relocated(5) and virtual(5) for the effects this has on
    # aliases, canonical, virtual, relocated and .forward file lookups.
    # Basically, the software tries user+foo and .forward+foo before
    # trying user and .forward.
    #recipient_delimiter = +
    # DELIVERY TO MAILBOX
    # The home_mailbox parameter specifies the optional pathname of a
    # mailbox file relative to a user's home directory. The default
    # mailbox file is /var/spool/mail/user or /var/mail/user. Specify
    # "Maildir/" for qmail-style delivery (the / is required).
    #home_mailbox = Mailbox
    #home_mailbox = Maildir/
    # The mail_spool_directory parameter specifies the directory where
    # UNIX-style mailboxes are kept. The default setting depends on the
    # system type.
    #mail_spool_directory = /var/mail
    #mail_spool_directory = /var/spool/mail
    # The mailbox_command parameter specifies the optional external
    # command to use instead of mailbox delivery. The command is run as
    # the recipient with proper HOME, SHELL and LOGNAME environment settings.
    # Exception: delivery for root is done as $default_user.
    # Other environment variables of interest: USER (recipient username),
    # EXTENSION (address extension), DOMAIN (domain part of address),
    # and LOCAL (the address localpart).
    # Unlike other Postfix configuration parameters, the mailbox_command
    # parameter is not subjected to $parameter substitutions. This is to
    # make it easier to specify shell syntax (see example below).
    # Avoid shell meta characters because they will force Postfix to run
    # an expensive shell process. Procmail alone is expensive enough.
    # IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
    # ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
    #mailbox_command = /some/where/procmail
    #mailbox_command = /some/where/procmail -a "$EXTENSION"
    # The mailbox_transport specifies the optional transport in master.cf
    # to use after processing aliases and .forward files. This parameter
    # has precedence over the mailbox_command, fallback_transport and
    # luser_relay parameters.
    # Specify a string of the form transport:nexthop, where transport is
    # the name of a mail delivery transport defined in master.cf. The
    # :nexthop part is optional. For more details see the sample transport
    # configuration file.
    # NOTE: if you use this feature for accounts not in the UNIX password
    # file, then you must update the "local_recipient_maps" setting in
    # the main.cf file, otherwise the SMTP server will reject mail for
    # non-UNIX accounts with "User unknown in local recipient table".
    #mailbox_transport = lmtp:unix:/file/name
    #mailbox_transport = cyrus
    # The fallback_transport specifies the optional transport in master.cf
    # to use for recipients that are not found in the UNIX passwd database.
    # This parameter has precedence over the luser_relay parameter.
    # Specify a string of the form transport:nexthop, where transport is
    # the name of a mail delivery transport defined in master.cf. The
    # :nexthop part is optional. For more details see the sample transport
    # configuration file.
    # NOTE: if you use this feature for accounts not in the UNIX password
    # file, then you must update the "local_recipient_maps" setting in
    # the main.cf file, otherwise the SMTP server will reject mail for
    # non-UNIX accounts with "User unknown in local recipient table".
    #fallback_transport = lmtp:unix:/file/name
    #fallback_transport = cyrus
    #fallback_transport =
    # The luser_relay parameter specifies an optional destination address
    # for unknown recipients. By default, mail for unknown@$mydestination,
    # unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
    # as undeliverable.
    # The following expansions are done on luser_relay: $user (recipient
    # username), $shell (recipient shell), $home (recipient home directory),
    # $recipient (full recipient address), $extension (recipient address
    # extension), $domain (recipient domain), $local (entire recipient
    # localpart), $recipient_delimiter. Specify ${name?value} or
    # ${name:value} to expand value only when $name does (does not) exist.
    # luser_relay works only for the default Postfix local delivery agent.
    # NOTE: if you use this feature for accounts not in the UNIX password
    # file, then you must specify "local_recipient_maps =" (i.e. empty) in
    # the main.cf file, otherwise the SMTP server will reject mail for
    # non-UNIX accounts with "User unknown in local recipient table".
    #luser_relay = [email protected]
    #luser_relay = [email protected]
    #luser_relay = admin+$local
    # JUNK MAIL CONTROLS
    # The controls listed here are only a very small subset. The file
    # SMTPD_ACCESS_README provides an overview.
    # The header_checks parameter specifies an optional table with patterns
    # that each logical message header is matched against, including
    # headers that span multiple physical lines.
    # By default, these patterns also apply to MIME headers and to the
    # headers of attached messages. With older Postfix versions, MIME and
    # attached message headers were treated as body text.
    # For details, see "man header_checks".
    #header_checks = regexp:/etc/postfix/header_checks
    # FAST ETRN SERVICE
    # Postfix maintains per-destination logfiles with information about
    # deferred mail, so that mail can be flushed quickly with the SMTP
    # "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
    # See the ETRN_README document for a detailed description.
    # The fast_flush_domains parameter controls what destinations are
    # eligible for this service. By default, they are all domains that
    # this server is willing to relay mail to.
    #fast_flush_domains = $relay_domains
    # SHOW SOFTWARE VERSION OR NOT
    # The smtpd_banner parameter specifies the text that follows the 220
    # code in the SMTP server's greeting banner. Some people like to see
    # the mail version advertised. By default, Postfix shows no version.
    # You MUST specify $myhostname at the start of the text. That is an
    # RFC requirement. Postfix itself does not care.
    #smtpd_banner = $myhostname ESMTP $mail_name
    #smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
    # PARALLEL DELIVERY TO THE SAME DESTINATION
    # How many parallel deliveries to the same user or domain? With local
    # delivery, it does not make sense to do massively parallel delivery
    # to the same user, because mailbox updates must happen sequentially,
    # and expensive pipelines in .forward files can cause disasters when
    # too many are run at the same time. With SMTP deliveries, 10
    # simultaneous connections to the same domain could be sufficient to
    # raise eyebrows.
    # Each message delivery transport has its XXX_destination_concurrency_limit
    # parameter. The default is $default_destination_concurrency_limit for
    # most delivery transports. For the local delivery agent the default is 2.
    #local_destination_concurrency_limit = 2
    #default_destination_concurrency_limit = 20
    # DEBUGGING CONTROL
    # The debug_peer_level parameter specifies the increment in verbose
    # logging level when an SMTP client or server host name or address
    # matches a pattern in the debug_peer_list parameter.
    debug_peer_level = 2
    # The debug_peer_list parameter specifies an optional list of domain
    # or network patterns, /file/name patterns or type:name tables. When
    # an SMTP client or server host name or address matches a pattern,
    # increase the verbose logging level by the amount specified in the
    # debug_peer_level parameter.
    #debug_peer_list = 127.0.0.1
    #debug_peer_list = some.domain
    # The debugger_command specifies the external command that is executed
    # when a Postfix daemon program is run with the -D option.
    # Use "command .. & sleep 5" so that the debugger can attach before
    # the process marches on. If you use an X-based debugger, be sure to
    # set up your XAUTHORITY environment variable before starting Postfix.
    debugger_command =
    PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
    xxgdb $daemon_directory/$process_name $process_id & sleep 5
    # If you can't use X, use this to capture the call stack when a
    # daemon crashes. The result is in a file in the configuration
    # directory, and is named after the process name and the process ID.
    # debugger_command =
    # PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
    # echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
    # >$config_directory/$process_name.$process_id.log & sleep 5
    # Another possibility is to run gdb under a detached screen session.
    # To attach to the screen sesssion, su root and run "screen -r
    # <id_string>" where <id_string> uniquely matches one of the detached
    # sessions (from "screen -list").
    # debugger_command =
    # PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
    # -dmS $process_name gdb $daemon_directory/$process_name
    # $process_id & sleep 1
    # INSTALL-TIME CONFIGURATION INFORMATION
    # The following parameters are used when installing a new Postfix version.
    # sendmail_path: The full pathname of the Postfix sendmail command.
    # This is the Sendmail-compatible mail posting interface.
    sendmail_path = /usr/sbin/sendmail
    # newaliases_path: The full pathname of the Postfix newaliases command.
    # This is the Sendmail-compatible command to build alias databases.
    newaliases_path = /usr/bin/newaliases
    # mailq_path: The full pathname of the Postfix mailq command. This
    # is the Sendmail-compatible mail queue listing command.
    mailq_path = /usr/bin/mailq
    # setgid_group: The group for mail submission and queue management
    # commands. This must be a group name with a numerical group ID that
    # is not shared with other accounts, not even with the Postfix account.
    setgid_group = _postdrop
    # html_directory: The location of the Postfix HTML documentation.
    html_directory = no
    # manpage_directory: The location of the Postfix on-line manual pages.
    manpage_directory = /usr/share/man
    # sample_directory: The location of the Postfix sample configuration files.
    # This parameter is obsolete as of Postfix 2.1.
    sample_directory = /usr/share/doc/postfix/examples
    # readme_directory: The location of the Postfix README files.
    readme_directory = /usr/share/doc/postfix
    mydomain_fallback = localhost
    message_size_limit = 52428800
    myhostname = mail1.stanwood.wednet.edu
    mailbox_transport = cyrus
    mydomain = stanwood.wednet.edu
    mailbox_size_limit = 0
    enable_server_options = yes
    inet_interfaces = all
    mynetworks = 127.0.0.0/8,172.16.0.0/17,169.204.240.0/25,172.29.1.22,169.204.240.2
    smtpd_use_tls = yes
    smtpd_enforce_tls = no
    smtpd_tls_cert_file = /etc/certificates/mail1.stanwood.wednet.edu.crt
    smtpd_tls_key_file = /etc/certificates/mail1.stanwood.wednet.edu.key
    smtpd_sasl_auth_enable = yes
    smtpd_use_pw_server = yes
    smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,permit
    smtpd_pw_server_security_options = gssapi,cram-md5,login,plain
    content_filter = smtp-amavis:[127.0.0.1]:10024
    mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
    owner_request_special = no
    recipient_delimiter = +
    alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
    # 02/02/09 Server Checkup by Alex
    bounce_queue_lifetime = 6h
    delay_warning_time = 6h
    maximal_queue_lifetime = 2d
    # Topicdesk Frontline Defense
    disable_vrfy_command = yes
    smtpd_client_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_rbl_client zen.spamhaus.org, permit
    smtpd_helo_required = yes
    smtpd_helo_restrictions = permit_sasl_authenticated, permit_mynetworks, check_helo_access hash:/etc/postfix/helo_access, reject_non_fqdn_hostname,reject_invalid_hostname, permit
    smtpd_sender_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_non_fqdn_sender, permit
    smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,permit
    smtpd_data_restrictions = permit_mynetworks, reject_unauth_pipelining, permit
    virtual_transport = virtual
    virtual_mailbox_domains =
    sh-3.2#

    Right, what was happening is that it was a big loop. We had to modify our DNS and some other settings on the spam bucket... but... wondering if there's another solution...
    mail1:~ admin$ postconf -n
    alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
    bouncequeuelifetime = 6h
    command_directory = /usr/sbin
    config_directory = /etc/postfix
    content_filter = smtp-amavis:[127.0.0.1]:10024
    daemon_directory = /usr/libexec/postfix
    debugpeerlevel = 2
    delaywarningtime = 6h
    disablevrfycommand = yes
    enableserveroptions = yes
    html_directory = no
    inet_interfaces = all
    localrecipientmaps = proxy:unix:passwd.byname $alias_maps
    mail_owner = _postfix
    mailboxsizelimit = 0
    mailbox_transport = cyrus
    mailq_path = /usr/bin/mailq
    manpage_directory = /usr/share/man
    maximalqueuelifetime = 2d
    messagesizelimit = 52428800
    mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
    mydomain = stanwood.wednet.edu
    mydomain_fallback = localhost
    myhostname = mail1.stanwood.wednet.edu
    mynetworks = 127.0.0.0/8,172.16.0.0/17,169.204.240.0/25,172.29.1.22,169.204.240.2
    newaliases_path = /usr/bin/newaliases
    ownerrequestspecial = no
    queue_directory = /private/var/spool/postfix
    readme_directory = /usr/share/doc/postfix
    recipient_delimiter = +
    sample_directory = /usr/share/doc/postfix/examples
    sendmail_path = /usr/sbin/sendmail
    setgid_group = _postdrop
    smtpdclientrestrictions = permitsaslauthenticated, permit_mynetworks, rejectrblclient zen.spamhaus.org, permit
    smtpddatarestrictions = permit_mynetworks, rejectunauthpipelining, permit
    smtpdenforcetls = no
    smtpdhelorequired = yes
    smtpdhelorestrictions = permitsaslauthenticated, permit_mynetworks, checkheloaccess hash:/etc/postfix/helo_access, rejectnon_fqdn_hostname,reject_invalidhostname, permit
    smtpdpw_server_securityoptions = gssapi,cram-md5,login,plain
    smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
    smtpdsasl_authenable = yes
    smtpdsenderrestrictions = permitsaslauthenticated, permit_mynetworks, rejectnon_fqdnsender, permit
    smtpdtls_certfile = /etc/certificates/mail1.stanwood.wednet.edu.crt
    smtpdtls_keyfile = /etc/certificates/mail1.stanwood.wednet.edu.key
    smtpduse_pwserver = yes
    smtpdusetls = yes
    unknownlocal_recipient_rejectcode = 550
    virtualmailboxdomains =
    virtual_transport = virtual
    mail1:~ admin$

  • WRT54G2 with Subnetted Virtual Machines

    I am unable to access the internet from guest virtual machines on a /25 subnet, although local lan connectivity seems to work fine, and local lan access to the internet works fine. My setup: WRT54G2 in Gateway mode 10.100.200.1/25 Host machine 10.100.200.4/25 Guests (Virtual machines) on the host: : 10.100.200.128 -254 (Host and Guests are Ubuntu 10.11 under KVM, w/virt-manager "routed networking" Static route on WRT54G2: 10.100.200.128/25 gw: 10.100.200.4 Local LAN connectivity is complete. For example, ssh from the lan to any guest works, as does ssh from any guest to any lan machine. Local lan internet access is complete, includiing the vm Host. Ping and traceroute from the WRT54G2 to lan machines, Host, and guests is successful. Failure: Guest machines cannot reach the internet. They can reach the router. Traceroute to an internet address from a guest machine returns responses from the WRT54G2, followed by time-outs. Ping from a guest machine to the internet fails. I have experimented with both /25 and /24 subnet masks on the WRT54G2 lan port without apparent effect. At this point I am rapidly running out of ideas. The WRT54G2 seems to refuse to pass guest machine packets out to the internet. I have found suggestions on various web fora that NAT difficulties can arise when using subnets with the WRT54G2, but I've been unable to track down details. Any suggestions would be deeply appreciated. Thanks in advance...

    Linksys routers are consumer routers. They don't really support more complex network configurations.
    In your case, the problem is that the WRT only does NAT for it's own LAN IP subnet.
    If a computer inside your LAN (e.g. 10.100.200.4/25) sends something into the internet, the WRT will do source IP NAT from 10.10.200.4 to its public IP address. This happens for all source IP addresses inside 10.100.200.4/25 but not for any other IP address.
    This means, if your VM with 10.100.200.200/25 would send something, it is routed through the host machine to the WRT, i.e. the WRT receives a packet from 10.100.200.200 to an internet IP address for forwarding. As the source IP address is not in 10.100.200.0/25 it won't go through NAT, i.e. the WRT will route the packet with unmodified source IP address 10.100.200.200 into the internet where it will be quickly discarded.
    That's a known limitation of Linksys routers and they don't have any configuration options to configure the NAT function in detail (like you would find in a Cisco IOS router). The Linksys always does NAT for the LAN IP subnet but for nothing else.
    You only have two options:
    1. use NAT on the host machine, i.e. the host machine does NAT between the VMs and the host network. Of course this way, the VMs are not accessible from the outside.
    2. use ethernet bridging instead of routing between VMs and host network. This would create a single ethernet network and you only need a single LAN IP subnet for VMs and the normal network.

Maybe you are looking for