Aperture and Bridge interface

I cannot access photos in the Aperture library from Bridge. When I click on the Aperture cube icon (Aperture Library.aplibrary") from Bridge, Aperture opens and nothing more. Is this usual? Or do I need to do something to get Bridge to recognize all the files/albums, etc which were originally imported into Aperture? I can access all the Aperture files from Photoshop but sometimes I just want to view them in Bridge first.

zelsha
Welcome to the Apple Discussions.
No, there is no way to access the files from Bridge. Bridge and Aperture don't play well together (nor does it play well with iPhoto) because Bridge attempts to do part of Apertures job.
I can access all the Aperture files from Photoshop but sometimes I just want to view them in Bridge first.
Well that's exactly where you would use Aperture and not Bridge.
Regards
TD

Similar Messages

  • Aperture and Bridge

    I have avoided using Bridge (much to my annoyance) as I cannot access the folders within my Aperture library (which are in the Pictures folder).
    Can someone take pity on this photographer here, whose workflow has become rather cumbersome of late.....
    Much much appreciated!!

    Easy solution; don't import files into Aperture. Use referenced files so 1) your Aperture library isn't huge and 2) you won't lose files if or when Aperature totally crashes/blows up.
    With my images securely located on their HDDs I can work with them and make corrections in CS5 Photoshop as well as work with them in Aperture. The Aperture libraries are backed up twice (on separate drives) and Bridge/Camera Raw corrections and metadata are backed up with both xmp files and a cache download into the files' folders. The HHDs are also backed up
    It works great and gives me complete freedom to use or not use A3 and CS5 at will.

  • File adjustments in aperture and bridge

    Why are mey aperture adjustments won't follow when I open them in bridge camera raw
    Thanks

    hello, barto
    quote: "Why are mey aperture adjustments won't follow when I open them in bridge camera raw"
    Because you're opening a RAW file instead of an adjusted Aperture photograph.
    What is your workflow?
    How are you exporting them? Are you exporting a Master or Version?
    victor

  • ACE bridge and routed interface in the same context

    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:Standardowy;
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-parent:"";
    mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
    mso-para-margin:0cm;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:10.0pt;
    font-family:"Times New Roman";
    mso-ansi-language:#0400;
    mso-fareast-language:#0400;
    mso-bidi-language:#0400;}
    Hello
    I am wondering if it is possible to configure one ACE context to support both routed and bridge interface?
    I would like to have a bridge-mode context but in the same time I would like to have a separated OOB interface for management.
    If it is possible how they could interact to each other?
    Thank you in advance for any answer
    Regards
    Lukasz

    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:Standardowy;
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-parent:"";
    mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
    mso-para-margin:0cm;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:10.0pt;
    font-family:"Times New Roman";
    mso-ansi-language:#0400;
    mso-fareast-language:#0400;
    mso-bidi-language:#0400;}
    Hello
    We've just tried to configure bridged and routed interfaces at the same time in the lab and we've had a problem.
    When we added the def gw for the bridged config we noticed that we had an issue with the traffic src by the rservers in the routed config.
    When we deleted the new def gw, the problem disappeared.
    I am attaching the lab config.
    When we added to it the following line
    ip route 0.0.0.0 0.0.0.0 10.1.1.163
    reals B1-B10 could not communicate to the outside world.
    Do you know why it does not worked and what could we do to fix it ?
    Thank you in advance.
    Regards
    Lukas

  • PowerMac DP 2 Ghz vs 15" Powerbook & Aperture vs Bridge-ACR and 10 D2X nefs

    10 D2X nefs, equal settings(including sharpening) on each file.
    Test: Time the export/saving 10 full sized JPGs(level 10) on both systems under both Aperture and Bridge/ACR
    In Aperture, stamp the same settings to 10 nefs, wait for the changes to appear on each thumbnail, then select the 10 nefs, and select export versions.
    In Bridge, paste the camera raw settings to the 10 nefs, wait for the thumbnails to show changes(building cache), select the 10 nefs, open ACR under Bridge(not CS2) by pressing CMD-R, in the ACR dialog, select all images on the left, click "Save 10 images".
    PowerMac: G5 dual 2 Ghz, 2 GB RAM, X 800 XT vid card, Aperture library and Bridge cache on separte SATA 7200 RPM internal disk
    PowerBook: 15" 1.5 Ghz, 1.5 GB RAM, ATI Mobility Radeon 9700, and 80 GB disk
    Aperture results:
    PowerMac: 2:07
    PowerBook: 5:06
    Bridge/ACR results:
    PowerMac: 1:18
    PowerBook: 2:12
    As you can see Aperture requires 2x the time to export/save when compared to Bridge/ACR.
    Further, it is amazing that the Powerbook could plow through the images in Bridge in the same time it took the Powermac to export the Aperture images...
    Hmmm, then that would imply the best money is on a Powerbook running Bridge/ACR/CS2?
    Sooooo, if you can cull/sort the images and apply raw settings in Aperture three to four times as fast as in Bridge then it is a wash...

    zozi56 wrote:Can you reproduce the problem without Skype, Bastian?
    From what I remember I have also had this issue when Skype wasn't open.
    Yesterday my computer started up beeping - I took the harddisk out and it started normally (initramfs tho). Then I put it back in and the laptop have been running fine so far. I suspect it might just have been a bad connection, but I am giving it time..
    EDIT: Still experiencing the issue..
    Last edited by Bastian (2014-01-19 18:09:08)

  • Annoture - Metadata Bridging Solution for Aperture and iView

    Aperture and iView users:
    I just released Annoture, a metadata bridging solution for Aperture and iView MediaPro! With Annoture, you’re just a click away from sharing metadata between these two popular image management and cataloguing applications. Spend more time working with your decisive moments than worrying about double-entry and incomplete metadata!
    Annoture lets you transfer annotations from iView MediaPro catalogs to Aperture projects and albums and back. This two-way transfer of IPTC and metadata information means you are not tied to any one application for your image management and workflow needs. Annoture also features a modular interface that can be extended to support additional applications in the future.
    http://www.tow.com/software/annoture/
    Users of Aperture and iView can download a fully-functional version of Annoture. The unregistered version will occasionally display a reminder to register, and all images processed in Aperture by Annoture will have a custom “Annotated with Annoture!” tag added. You can remove these items with the full version after purchasing and entering your license code.
    Enjoy!
    -adam

    Congratulations on getting this working and available so quickly! I bet many late nights went into this
    It's definitely providing some motivation for me to learn more Applescript...

  • How do I transfer photos from aperture and iPhoto to bridge?

    How do I transfer photos from Aperture and iPhoto to Adobe Bridge.  I am using Photoshop CS6.  Many of my original photos were stored as raw files.

    Here's how to access Mac iPhoto images for use in Photoshop
    and so that they may be viewed by choosing that folder in Bridge..
    1. In the Finder, navigate to Users > [user name} > Pictures > iPhoto Library.  
    2. Control-click (Right-click) the iPhoto Library file and choose Show Package Contents.
    3. A Finder window opens that shows the contents. The Masters folder (or called Originals folder) contains all of the photographs that are in iPhoto.
    Photoshop cannot access this folder, but if you make a duplicate of the folder, the dupe will be accessible -- so:
    4. Control-click (Right-click) the folder named Masters (or Originals) and choose Duplicate.
    5, Drag the duplicate folder which is named "Masters copy" or “Originals copy” from the iPhoto Library Finder window to the Desktop.
    6. Open images in Photoshop from file on desktop or view them in Bridge.
    7  Rename the folder and move it elsewhere (probably to the Pictures folder), if desired. 
    And here is a Forum thread related to Aperture-to-Bridge
    How do I transfer Apple Aperture library to Bridge?

  • Aperture 3 library, CS6 and Bridge Library

    I have been using Aperture for a long time. I just got CS6 CC and Bridge. Question: Is it possible to keep two idenitical ORIGINAL library's - one in Aperture and the other in Bridge?

    Of course it is possible but you do realize that each library will be independent of the other. Changes made in one will not affect the other and your storage requirements will be doubled.
    Running two completely different programs that do basically the same task seems wasteful both in terms of system resources and the time needed to maintain and use each program efficiently. Why are you looking to do this?

  • Cisco 877w -Configuration of subinterfaces and main interface within the same bridge group is not permitted

    Hi,
    I have another problem - after upgrade ios wirelles connection not work.
    After reload i have :
    Configuration of subinterfaces and main interface
    within the same bridge group is not permitted
    STP: Unable to get the port parameters.
    Please configure the bridge group on this interface first.
    Please configure the bridge group on this interface first.
    Please configure the bridge group on this interface first.
    SETUP: new interface NVI0 placed in "shutdown" state
    my old configuration work propertly in the old software, but after update i have notificatio.
    Old thread:
    https://supportforums.cisco.com/discussion/12379491/cisco-877w-no-wireless-connection
    my current sh run:
    version 12.4 
    no service pad 
    service tcp-keepalives-in 
    service tcp-keepalives-out 
    service timestamps debug datetime msec localtime 
    service timestamps log datetime msec localtime 
    service password-encryption 
    hostname cisco 
    boot-start-marker 
    boot system flash:c870-advipservicesk9-mz.124-24.T6.bin 
    boot-end-marker 
    logging message-counter syslog 
    logging buffered 4096 informational 
    enable secret 5 $1$eCNp$rWuBfZ/cexnwnkm7L447s. 
    aaa new-model 
    aaa session-id common 
    dot11 syslog 
    dot11 ssid ciscowifi 
     vlan 1 
     authentication open 
     authentication key-management wpa 
     guest-mode 
     wpa-psk ascii 7 050D031D26595D0617 
    dot11 wpa handshake timeout 500 
    ip source-route 
    no ip dhcp use vrf connected 
    ip dhcp excluded-address 192.168.56.1 
    ip dhcp pool CLIENT 
       import all 
       network 192.168.56.0 255.255.255.0 
       default-router 192.168.56.1 
       dns-server 8.8.8.8 194.204.159.1 194.204.152.34 
       lease 0 2 
    ip cef 
    no ip domain lookup 
    no ipv6 cef 
    multilink bundle-name authenticated 
    username marek password 7 00121A0908500A 
    archive 
     log config 
      hidekeys 
    ip tcp path-mtu-discovery 
    bridge irb 
    interface ATM0 
     description Polaczenie ADSL do ISP$ES_WAN$ 
     no ip address 
     no atm ilmi-keepalive 
     pvc 0/35 
      encapsulation aal5mux ppp dialer 
      dialer pool-member 1 
     hold-queue 224 in 
    interface FastEthernet0 
     description Edzia 
    interface FastEthernet1 
     description dom 
    interface FastEthernet2 
     description Dziadek 
    interface FastEthernet3 
    interface Dot11Radio0 
     no ip address 
     no ip redirects 
     ip local-proxy-arp 
     ip nat inside 
     ip virtual-reassembly 
     no dot11 extension aironet 
     encryption vlan 1 mode ciphers tkip 
     encryption mode ciphers aes-ccm tkip 
     broadcast-key change 3600 
     ssid ciscowifi 
     speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 36.0 48.0 54.0 
     station-role root 
     world-mode dot11d country AU indoor 
     no cdp enable 
     bridge-group 1 
     bridge-group 1 subscriber-loop-control 
     bridge-group 1 spanning-disabled 
     bridge-group 1 block-unknown-source 
     no bridge-group 1 source-learning 
     no bridge-group 1 unicast-flooding 
    interface Dot11Radio0.1 
     description ciscowifi 
     encapsulation dot1Q 1 native 
     no cdp enable 
    interface Vlan1 
     no ip address 
     bridge-group 1 
    interface Dialer0 
     description Interfejs dzwoniacy 
     ip address negotiated 
     ip nat outside 
     ip virtual-reassembly 
     encapsulation ppp 
     dialer pool 1 
     dialer-group 1 
     ppp chap hostname [email protected] 
     ppp chap password 7 xxxxxxxxxxxxxxxxxxxxxx 
    interface BVI1 
     description Polaczenie dla sieci LAN 
     ip address 192.168.56.1 255.255.255.0 
     ip nat inside 
     ip virtual-reassembly 
    no ip forward-protocol nd 
    ip route 0.0.0.0 0.0.0.0 Dialer0 
    no ip http server 
    no ip http secure-server 
    ip nat inside source list 100 interface Dialer0 overload 
    ip nat inside source static tcp 192.168.56.10 80 interface Dialer0 80 
    ip nat inside source static tcp 192.168.56.10 22 interface Dialer0 22 
    logging trap debugging 
    logging 192.168.56.10 
    access-list 100 permit ip 192.168.56.0 0.0.0.255 any 
    access-list 100 deny   ip any any 
    no cdp run 
    snmp-server community ciskacz RO 
    snmp-server chassis-id ciskacz 
    control-plane 
    bridge 1 protocol ieee 
    bridge 1 route ip 
    line con 0 
     no modem enable 
    line aux 0 
    line vty 0 4 
     exec-timeout 0 0 
     transport preferred ssh 
     transport input ssh 
    scheduler max-task-time 5000 
    end 
    please help - thanks!

    Hello Marek,
    I suppose you are not planning to do any kinds of advanced config using several VLANs and multiple SSIDs so let's just make your configuration simple and working.
    In short, you need to remove all references to VLAN 1 and to any subinterfaces possibly related to the VLAN 1. This means in particular (follow these steps in sequence):
    Remove the Dot11Radio0.1 subinterface entirely
    In the Dot11Radio0 section, remove the encryption vlan 1 mode ciphers tkip command
    In the dot11 ssid ciscowifi section, remove the vlan 1 command
    After performing these steps, make sure that the ssid ciscowifi and encryption mode commands are still present in the Dot11Radio0 configuration, and if not, reenter them.
    Best regards,
    Peter

  • Aperture Metadata and Bridge Metadata

    I am a photographer and my workflow is to import all my images into Aperture library and add metadata.
    When exporting an image is it possible to integrate Apertures metadata with Bridge metadata? This is important feature as most people do not import images with Aperture. The issue is that many of the field names are different or non existent between the two programs. For example Location field in Bridge is Sub location in Aperture.
    Can you add fields such contact info such as URL, email that are included within Bridge ITPC Metadata?
    Is there a way to customize the metadata fields to work with CS3?

    Unfortunatelly, not really.
    I am currently using Nikon Transfer (latest version) to download the pictures from the camera. This software allows me to enter quite a number of IPTC data (including contact information, url, mail, phone, etc.), but maybe not all which are available in CS3.
    Then I do import the pictures from the folder into Aperture where I only add contact information in the respective IPTC field. From the tests, I did I do know, that with this step I am using the "old IPTC standard" with Aperture and the new IPTC standard with Nikon Transfer. Clearly the newer is better and meets the needs you described.
    In Aperture, I do only see the IPTC data fields, which are common between the two standards (copyright, keywords and description).
    When I go to CS3 Bridge, I can see the IPTC data from both, but only of you turn on the "IPTC old" in the Photoshop Bridge settings.
    This is how far I have come. I have tested the export with the original and the aperture work copy. As a test reader/viewer of the pics I used Photoshop Elements 5.0 ... but except the copyright information, key words and description, I could not find "my" IPTC data. So there was no contact info. This may be a problem of the old version, so I also checked on a windows PC the file properties (picture viewer), which has more or less the same information.
    So the only work around maybe to add contact information into the copyright field - which is not ideal.
    Regards
    Diethard

  • Aperture and ACR workflow

    For those who find Aperture's Camera RAW conversion too primitive, the program can be used in a simple workflow that maximizes your productivity while insuring maximum quality conversion.
    1- IMPORT your RAW images into Aperture and add keywords and other tags.
    Aperture brings in the RAW image UNALTERED.
    2- COMPARE AND SORT your images using the EXCELLENT TOOLS in Aperture.
    You can also freely experiment with versions to test ideas for everything from exposure to B&W conversions.
    3- SELECT YOUR BEST IMAGES inside Aperture.
    Most of us working in the professional world are really only interested in using the top 1% or less of a typical shoot. It is only those that need to be converted as output for Giclee printing or as digital masters for retouching and CMYK printing.
    4- EXPORT THOSE BEST IMAGES using the export "DIGITAL MASTERS..." command.
    Many of us find Aperture's RAW conversion to be excellent but for those who don't, you can choose at this point all your selected images, which by now should be a very short list, and export them as UNALTERED RAW files to a folder outside of Aperture.
    5- CONVERT those exported camera RAW images using whatever conversion program you want, for many it will be ACR, and do any extra retouching in Photoshop.
    And for those worried about Aperture's filing system, you can store these exported "Best Images" exactly like you used to do, in old fashioned folders on your hard disk, in whatever categories make sense to you.
    For those of us producing professional work on always shorter deadlines, Aperture is an outstanding tool that makes our job much easier.
      Mac OS X (10.4.3)  

    Tom, first allow me to congratulate you on starting a practical thread. Now that many of us own Aperture, and I'm not saying the issues threads aren't useful, figuring out where it fits in our workflow is a fine idea.
    Here is my (pre-Aperture) workflow, and some ideas for an interim (working with what we have) post-Aperture flow. I'd really appreciate any advice or suggestions.
    Pre: Conversion mostly in ACR/Bridge (occasionally in C1Pro-generally fleshtones). Color Space generaly set in camera as Adobe RGB, same for PS. Preliminary sharpening with PhotoKit, noise reduction if necessary with neat image or noise ninja, adjustments, aspect ratio crops, etc. Save as TIFF/16bit layered if necessary/add "Base" to filename when saving. Reopen in PS for output specific sharpening, save flattened copy. Open in ImagePrint-Print. Library has been on external HDs, backed up to duplicate HDs which are taken off premises. Current library size:700Gigs and growing fast.
    Post: Import into Aperture from Card, also backup RAWs to DVD. As suggested here, do sorts and picks in Aperture. Maybe do some crude adjusting for low res images for client proofs (web or contact sheets-sorry, haven't tried using Aperture with Epson drivers or tried the web posting). Export RAW picks for conversion and editing elsewhere (I have tested and the camera EXIFs are still there in PS (I'm not sure they will be on re-import?). So, now I've got a RAW with an attached .xmp, one or more Tiffs. I can reimport the TIFFs, but can I re-associate them with the Master? Is there any way that I can import the .xmp and associate it with the master? So, I can pick, web, go to printer and archive (although I'll hit a disk space issue-ideas there?)
    I tried to do this without asking for changes in Aperture, but not using Aperture where I felt it was immature. There are already enough discussions about conversion, editing and storage. The interface is promising and I would welcome any shortcuts you can come up with. Meanwhile, I'm going to try with new shoots, and a few existing shoots for experimanetation, but leave my old library intact. Then I'm going to put Aperture's library on an 800Gig external eSATA RAID0 -two disk; and back up to another. Wish me luck.

  • [SOLVED] NAT gateway and bridge

    Hello. I'm having hard time trying to setup a  small nat gateway. The whole point of me doing this is to learn more.
    Here is brief idea of what I'm trying to achieve. I have done it in the past with netcfg and it worked well but then I left my project to do other things. Now I'm back and after fresh install I can't start bridge interface with netctl.
    DSL_router|<--------->|ARCH | |+------->Gentoo/windows
    gateway 192.168.0.1| |gateway 192.168.1.1| br0 |
    |+dual_port_nic |<----+
    |
    +-------->5port switch(RsPI/printer/tv/ps3)
    So my Arch is connected to DSL router with static address on
    enp4s0. I have a dual port NIC (like this) that I want to bridge but for some reason I'm unable to.
    I configured my iptables according to Simple Stateful Firewall section of NAT gateway so it looks like this:
    # Generated by iptables-save v1.4.19.1 on Fri Aug 2 00:59:59 2013
    *nat
    :PREROUTING ACCEPT [5:576]
    :INPUT ACCEPT [5:576]
    :OUTPUT ACCEPT [0:0]
    :POSTROUTING ACCEPT [0:0]
    -A POSTROUTING -s 192.168.1.0/24 -o enp4s0 -j MASQUERADE
    COMMIT
    # Completed on Fri Aug 2 00:59:59 2013
    # Generated by iptables-save v1.4.19.1 on Fri Aug 2 00:59:59 2013
    *filter
    :INPUT ACCEPT [828:78883]
    :FORWARD DROP [0:0]
    :OUTPUT ACCEPT [559:82036]
    :fw-interfaces - [0:0]
    :fw-open - [0:0]
    -A FORWARD -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
    -A FORWARD -j fw-interfaces
    -A FORWARD -j fw-open
    -A FORWARD -j REJECT --reject-with icmp-host-unreachable
    -A fw-interfaces -i br0 -j ACCEPT
    COMMIT
    # Completed on Fri Aug 2 00:59:59 2013
    I know its basic one but its all I need atm until I will get over that problem.
    My dnsmasq.conf:
    # Configuration file for dnsmasq.
    # Format is one option per line, legal options are the same
    # as the long options legal on the command line. See
    # "/usr/sbin/dnsmasq --help" or "man 8 dnsmasq" for details.
    # Listen on this specific port instead of the standard DNS port
    # (53). Setting this to zero completely disables DNS function,
    # leaving only DHCP and/or TFTP.
    #port=5353
    # The following two options make you a better netizen, since they
    # tell dnsmasq to filter out queries which the public DNS cannot
    # answer, and which load the servers (especially the root servers)
    # unnecessarily. If you have a dial-on-demand link they also stop
    # these requests from bringing up the link unnecessarily.
    # Never forward plain names (without a dot or domain part)
    domain-needed
    # Never forward addresses in the non-routed address spaces.
    bogus-priv
    # Uncomment this to filter useless windows-originated DNS requests
    # which can trigger dial-on-demand links needlessly.
    # Note that (amongst other things) this blocks all SRV requests,
    # so don't use it if you use eg Kerberos, SIP, XMMP or Google-talk.
    # This option only affects forwarding, SRV records originating for
    # dnsmasq (via srv-host= lines) are not suppressed by it.
    #filterwin2k
    # Change this line if you want dns to get its upstream servers from
    # somewhere other that /etc/resolv.conf
    #resolv-file=
    # By default, dnsmasq will send queries to any of the upstream
    # servers it knows about and tries to favour servers to are known
    # to be up. Uncommenting this forces dnsmasq to try each query
    # with each server strictly in the order they appear in
    # /etc/resolv.conf
    #strict-order
    # If you don't want dnsmasq to read /etc/resolv.conf or any other
    # file, getting its servers from this file instead (see below), then
    # uncomment this.
    #no-resolv
    # If you don't want dnsmasq to poll /etc/resolv.conf or other resolv
    # files for changes and re-read them then uncomment this.
    #no-poll
    # Add other name servers here, with domain specs if they are for
    # non-public domains.
    #server=/localnet/192.168.0.1
    # Example of routing PTR queries to nameservers: this will send all
    # address->name queries for 192.168.3/24 to nameserver 10.1.2.3
    #server=/3.168.192.in-addr.arpa/10.1.2.3
    # Add local-only domains here, queries in these domains are answered
    # from /etc/hosts or DHCP only.
    #local=/localnet/
    # Add domains which you want to force to an IP address here.
    # The example below send any host in double-click.net to a local
    # web-server.
    #address=/double-click.net/127.0.0.1
    # --address (and --server) work with IPv6 addresses too.
    #address=/www.thekelleys.org.uk/fe80::20d:60ff:fe36:f83
    # Add the IPs of all queries to yahoo.com, google.com, and their
    # subdomains to the vpn and search ipsets:
    #ipset=/yahoo.com/google.com/vpn,search
    # You can control how dnsmasq talks to a server: this forces
    # queries to 10.1.2.3 to be routed via eth1
    # server=10.1.2.3@eth1
    # and this sets the source (ie local) address used to talk to
    # 10.1.2.3 to 192.168.1.1 port 55 (there must be a interface with that
    # IP on the machine, obviously).
    # [email protected]#55
    # If you want dnsmasq to change uid and gid to something other
    # than the default, edit the following lines.
    #user=
    #group=
    # If you want dnsmasq to listen for DHCP and DNS requests only on
    # specified interfaces (and the loopback) give the name of the
    # interface (eg eth0) here.
    # Repeat the line for more than one interface.
    #interface=
    # Or you can specify which interface _not_ to listen on
    #except-interface=
    # Or which to listen on by address (remember to include 127.0.0.1 if
    # you use this.)
    #listen-address=
    # If you want dnsmasq to provide only DNS service on an interface,
    # configure it as shown above, and then use the following line to
    # disable DHCP and TFTP on it.
    #no-dhcp-interface=
    # On systems which support it, dnsmasq binds the wildcard address,
    # even when it is listening on only some interfaces. It then discards
    # requests that it shouldn't reply to. This has the advantage of
    # working even when interfaces come and go and change address. If you
    # want dnsmasq to really bind only the interfaces it is listening on,
    # uncomment this option. About the only time you may need this is when
    # running another nameserver on the same machine.
    #bind-interfaces
    # If you don't want dnsmasq to read /etc/hosts, uncomment the
    # following line.
    #no-hosts
    # or if you want it to read another file, as well as /etc/hosts, use
    # this.
    #addn-hosts=/etc/banner_add_hosts
    # Set this (and domain: see below) if you want to have a domain
    # automatically added to simple names in a hosts-file.
    #expand-hosts
    # Set the domain for dnsmasq. this is optional, but if it is set, it
    # does the following things.
    # 1) Allows DHCP hosts to have fully qualified domain names, as long
    # as the domain part matches this setting.
    # 2) Sets the "domain" DHCP option thereby potentially setting the
    # domain of all systems configured by DHCP
    # 3) Provides the domain part for "expand-hosts"
    #domain=thekelleys.org.uk
    # Set a different domain for a particular subnet
    #domain=wireless.thekelleys.org.uk,192.168.2.0/24
    # Same idea, but range rather then subnet
    #domain=reserved.thekelleys.org.uk,192.68.3.100,192.168.3.200
    # Uncomment this to enable the integrated DHCP server, you need
    # to supply the range of addresses available for lease and optionally
    # a lease time. If you have more than one network, you will need to
    # repeat this for each network on which you want to supply DHCP
    # service.
    dhcp-range=192.168.1.0,192.168.1.150,12h
    # This is an example of a DHCP range where the netmask is given. This
    # is needed for networks we reach the dnsmasq DHCP server via a relay
    # agent. If you don't know what a DHCP relay agent is, you probably
    # don't need to worry about this.
    #dhcp-range=192.168.0.50,192.168.0.150,255.255.255.0,12h
    # This is an example of a DHCP range which sets a tag, so that
    # some DHCP options may be set only for this network.
    #dhcp-range=set:red,192.168.0.50,192.168.0.150
    # Use this DHCP range only when the tag "green" is set.
    #dhcp-range=tag:green,192.168.0.50,192.168.0.150,12h
    # Specify a subnet which can't be used for dynamic address allocation,
    # is available for hosts with matching --dhcp-host lines. Note that
    # dhcp-host declarations will be ignored unless there is a dhcp-range
    # of some type for the subnet in question.
    # In this case the netmask is implied (it comes from the network
    # configuration on the machine running dnsmasq) it is possible to give
    # an explicit netmask instead.
    #dhcp-range=192.168.0.0,static
    # Enable DHCPv6. Note that the prefix-length does not need to be specified
    # and defaults to 64 if missing/
    #dhcp-range=1234::2, 1234::500, 64, 12h
    # Do Router Advertisements, BUT NOT DHCP for this subnet.
    #dhcp-range=1234::, ra-only
    # Do Router Advertisements, BUT NOT DHCP for this subnet, also try and
    # add names to the DNS for the IPv6 address of SLAAC-configured dual-stack
    # hosts. Use the DHCPv4 lease to derive the name, network segment and
    # MAC address and assume that the host will also have an
    # IPv6 address calculated using the SLAAC alogrithm.
    #dhcp-range=1234::, ra-names
    # Do Router Advertisements, BUT NOT DHCP for this subnet.
    # Set the lifetime to 46 hours. (Note: minimum lifetime is 2 hours.)
    #dhcp-range=1234::, ra-only, 48h
    # Do DHCP and Router Advertisements for this subnet. Set the A bit in the RA
    # so that clients can use SLAAC addresses as well as DHCP ones.
    #dhcp-range=1234::2, 1234::500, slaac
    # Do Router Advertisements and stateless DHCP for this subnet. Clients will
    # not get addresses from DHCP, but they will get other configuration information.
    # They will use SLAAC for addresses.
    #dhcp-range=1234::, ra-stateless
    # Do stateless DHCP, SLAAC, and generate DNS names for SLAAC addresses
    # from DHCPv4 leases.
    #dhcp-range=1234::, ra-stateless, ra-names
    # Do router advertisements for all subnets where we're doing DHCPv6
    # Unless overriden by ra-stateless, ra-names, et al, the router
    # advertisements will have the M and O bits set, so that the clients
    # get addresses and configuration from DHCPv6, and the A bit reset, so the
    # clients don't use SLAAC addresses.
    #enable-ra
    # Supply parameters for specified hosts using DHCP. There are lots
    # of valid alternatives, so we will give examples of each. Note that
    # IP addresses DO NOT have to be in the range given above, they just
    # need to be on the same network. The order of the parameters in these
    # do not matter, it's permissible to give name, address and MAC in any
    # order.
    # Always allocate the host with Ethernet address 11:22:33:44:55:66
    # The IP address 192.168.0.60
    #dhcp-host=11:22:33:44:55:66,192.168.0.60
    # Always set the name of the host with hardware address
    # 11:22:33:44:55:66 to be "fred"
    #dhcp-host=11:22:33:44:55:66,fred
    # Always give the host with Ethernet address 11:22:33:44:55:66
    # the name fred and IP address 192.168.0.60 and lease time 45 minutes
    #dhcp-host=11:22:33:44:55:66,fred,192.168.0.60,45m
    # Give a host with Ethernet address 11:22:33:44:55:66 or
    # 12:34:56:78:90:12 the IP address 192.168.0.60. Dnsmasq will assume
    # that these two Ethernet interfaces will never be in use at the same
    # time, and give the IP address to the second, even if it is already
    # in use by the first. Useful for laptops with wired and wireless
    # addresses.
    #dhcp-host=11:22:33:44:55:66,12:34:56:78:90:12,192.168.0.60
    # Give the machine which says its name is "bert" IP address
    # 192.168.0.70 and an infinite lease
    #dhcp-host=bert,192.168.0.70,infinite
    # Always give the host with client identifier 01:02:02:04
    # the IP address 192.168.0.60
    #dhcp-host=id:01:02:02:04,192.168.0.60
    # Always give the host with client identifier "marjorie"
    # the IP address 192.168.0.60
    #dhcp-host=id:marjorie,192.168.0.60
    # Enable the address given for "judge" in /etc/hosts
    # to be given to a machine presenting the name "judge" when
    # it asks for a DHCP lease.
    #dhcp-host=judge
    # Never offer DHCP service to a machine whose Ethernet
    # address is 11:22:33:44:55:66
    #dhcp-host=11:22:33:44:55:66,ignore
    # Ignore any client-id presented by the machine with Ethernet
    # address 11:22:33:44:55:66. This is useful to prevent a machine
    # being treated differently when running under different OS's or
    # between PXE boot and OS boot.
    #dhcp-host=11:22:33:44:55:66,id:*
    # Send extra options which are tagged as "red" to
    # the machine with Ethernet address 11:22:33:44:55:66
    #dhcp-host=11:22:33:44:55:66,set:red
    # Send extra options which are tagged as "red" to
    # any machine with Ethernet address starting 11:22:33:
    #dhcp-host=11:22:33:*:*:*,set:red
    # Give a fixed IPv6 address and name to client with
    # DUID 00:01:00:01:16:d2:83:fc:92:d4:19:e2:d8:b2
    # Note the MAC addresses CANNOT be used to identify DHCPv6 clients.
    # Note also the they [] around the IPv6 address are obilgatory.
    #dhcp-host=id:00:01:00:01:16:d2:83:fc:92:d4:19:e2:d8:b2, fred, [1234::5]
    # Ignore any clients which are not specified in dhcp-host lines
    # or /etc/ethers. Equivalent to ISC "deny unknown-clients".
    # This relies on the special "known" tag which is set when
    # a host is matched.
    #dhcp-ignore=tag:!known
    # Send extra options which are tagged as "red" to any machine whose
    # DHCP vendorclass string includes the substring "Linux"
    #dhcp-vendorclass=set:red,Linux
    # Send extra options which are tagged as "red" to any machine one
    # of whose DHCP userclass strings includes the substring "accounts"
    #dhcp-userclass=set:red,accounts
    # Send extra options which are tagged as "red" to any machine whose
    # MAC address matches the pattern.
    #dhcp-mac=set:red,00:60:8C:*:*:*
    # If this line is uncommented, dnsmasq will read /etc/ethers and act
    # on the ethernet-address/IP pairs found there just as if they had
    # been given as --dhcp-host options. Useful if you keep
    # MAC-address/host mappings there for other purposes.
    #read-ethers
    # Send options to hosts which ask for a DHCP lease.
    # See RFC 2132 for details of available options.
    # Common options can be given to dnsmasq by name:
    # run "dnsmasq --help dhcp" to get a list.
    # Note that all the common settings, such as netmask and
    # broadcast address, DNS server and default route, are given
    # sane defaults by dnsmasq. You very likely will not need
    # any dhcp-options. If you use Windows clients and Samba, there
    # are some options which are recommended, they are detailed at the
    # end of this section.
    # Override the default route supplied by dnsmasq, which assumes the
    # router is the same machine as the one running dnsmasq.
    #dhcp-option=3,1.2.3.4
    # Do the same thing, but using the option name
    #dhcp-option=option:router,1.2.3.4
    # Override the default route supplied by dnsmasq and send no default
    # route at all. Note that this only works for the options sent by
    # default (1, 3, 6, 12, 28) the same line will send a zero-length option
    # for all other option numbers.
    #dhcp-option=3
    # Set the NTP time server addresses to 192.168.0.4 and 10.10.0.5
    #dhcp-option=option:ntp-server,192.168.0.4,10.10.0.5
    # Send DHCPv6 option. Note [] around IPv6 addresses.
    #dhcp-option=option6:dns-server,[1234::77],[1234::88]
    # Send DHCPv6 option for namservers as the machine running
    # dnsmasq and another.
    #dhcp-option=option6:dns-server,[::],[1234::88]
    # Ask client to poll for option changes every six hours. (RFC4242)
    #dhcp-option=option6:information-refresh-time,6h
    # Set the NTP time server address to be the same machine as
    # is running dnsmasq
    #dhcp-option=42,0.0.0.0
    # Set the NIS domain name to "welly"
    #dhcp-option=40,welly
    # Set the default time-to-live to 50
    #dhcp-option=23,50
    # Set the "all subnets are local" flag
    #dhcp-option=27,1
    # Send the etherboot magic flag and then etherboot options (a string).
    #dhcp-option=128,e4:45:74:68:00:00
    #dhcp-option=129,NIC=eepro100
    # Specify an option which will only be sent to the "red" network
    # (see dhcp-range for the declaration of the "red" network)
    # Note that the tag: part must precede the option: part.
    #dhcp-option = tag:red, option:ntp-server, 192.168.1.1
    # The following DHCP options set up dnsmasq in the same way as is specified
    # for the ISC dhcpcd in
    # http://www.samba.org/samba/ftp/docs/textdocs/DHCP-Server-Configuration.txt
    # adapted for a typical dnsmasq installation where the host running
    # dnsmasq is also the host running samba.
    # you may want to uncomment some or all of them if you use
    # Windows clients and Samba.
    #dhcp-option=19,0 # option ip-forwarding off
    #dhcp-option=44,0.0.0.0 # set netbios-over-TCP/IP nameserver(s) aka WINS server(s)
    #dhcp-option=45,0.0.0.0 # netbios datagram distribution server
    #dhcp-option=46,8 # netbios node type
    # Send an empty WPAD option. This may be REQUIRED to get windows 7 to behave.
    #dhcp-option=252,"\n"
    # Send RFC-3397 DNS domain search DHCP option. WARNING: Your DHCP client
    # probably doesn't support this......
    #dhcp-option=option:domain-search,eng.apple.com,marketing.apple.com
    # Send RFC-3442 classless static routes (note the netmask encoding)
    #dhcp-option=121,192.168.1.0/24,1.2.3.4,10.0.0.0/8,5.6.7.8
    # Send vendor-class specific options encapsulated in DHCP option 43.
    # The meaning of the options is defined by the vendor-class so
    # options are sent only when the client supplied vendor class
    # matches the class given here. (A substring match is OK, so "MSFT"
    # matches "MSFT" and "MSFT 5.0"). This example sets the
    # mtftp address to 0.0.0.0 for PXEClients.
    #dhcp-option=vendor:PXEClient,1,0.0.0.0
    # Send microsoft-specific option to tell windows to release the DHCP lease
    # when it shuts down. Note the "i" flag, to tell dnsmasq to send the
    # value as a four-byte integer - that's what microsoft wants. See
    # http://technet2.microsoft.com/WindowsServer/en/library/a70f1bb7-d2d4-49f0-96d6-4b7414ecfaae1033.mspx?mfr=true
    #dhcp-option=vendor:MSFT,2,1i
    # Send the Encapsulated-vendor-class ID needed by some configurations of
    # Etherboot to allow is to recognise the DHCP server.
    #dhcp-option=vendor:Etherboot,60,"Etherboot"
    # Send options to PXELinux. Note that we need to send the options even
    # though they don't appear in the parameter request list, so we need
    # to use dhcp-option-force here.
    # See http://syslinux.zytor.com/pxe.php#special for details.
    # Magic number - needed before anything else is recognised
    #dhcp-option-force=208,f1:00:74:7e
    # Configuration file name
    #dhcp-option-force=209,configs/common
    # Path prefix
    #dhcp-option-force=210,/tftpboot/pxelinux/files/
    # Reboot time. (Note 'i' to send 32-bit value)
    #dhcp-option-force=211,30i
    # Set the boot filename for netboot/PXE. You will only need
    # this is you want to boot machines over the network and you will need
    # a TFTP server; either dnsmasq's built in TFTP server or an
    # external one. (See below for how to enable the TFTP server.)
    #dhcp-boot=pxelinux.0
    # The same as above, but use custom tftp-server instead machine running dnsmasq
    #dhcp-boot=pxelinux,server.name,192.168.1.100
    # Boot for Etherboot gPXE. The idea is to send two different
    # filenames, the first loads gPXE, and the second tells gPXE what to
    # load. The dhcp-match sets the gpxe tag for requests from gPXE.
    #dhcp-match=set:gpxe,175 # gPXE sends a 175 option.
    #dhcp-boot=tag:!gpxe,undionly.kpxe
    #dhcp-boot=mybootimage
    # Encapsulated options for Etherboot gPXE. All the options are
    # encapsulated within option 175
    #dhcp-option=encap:175, 1, 5b # priority code
    #dhcp-option=encap:175, 176, 1b # no-proxydhcp
    #dhcp-option=encap:175, 177, string # bus-id
    #dhcp-option=encap:175, 189, 1b # BIOS drive code
    #dhcp-option=encap:175, 190, user # iSCSI username
    #dhcp-option=encap:175, 191, pass # iSCSI password
    # Test for the architecture of a netboot client. PXE clients are
    # supposed to send their architecture as option 93. (See RFC 4578)
    #dhcp-match=peecees, option:client-arch, 0 #x86-32
    #dhcp-match=itanics, option:client-arch, 2 #IA64
    #dhcp-match=hammers, option:client-arch, 6 #x86-64
    #dhcp-match=mactels, option:client-arch, 7 #EFI x86-64
    # Do real PXE, rather than just booting a single file, this is an
    # alternative to dhcp-boot.
    #pxe-prompt="What system shall I netboot?"
    # or with timeout before first available action is taken:
    #pxe-prompt="Press F8 for menu.", 60
    # Available boot services. for PXE.
    #pxe-service=x86PC, "Boot from local disk"
    # Loads <tftp-root>/pxelinux.0 from dnsmasq TFTP server.
    #pxe-service=x86PC, "Install Linux", pxelinux
    # Loads <tftp-root>/pxelinux.0 from TFTP server at 1.2.3.4.
    # Beware this fails on old PXE ROMS.
    #pxe-service=x86PC, "Install Linux", pxelinux, 1.2.3.4
    # Use bootserver on network, found my multicast or broadcast.
    #pxe-service=x86PC, "Install windows from RIS server", 1
    # Use bootserver at a known IP address.
    #pxe-service=x86PC, "Install windows from RIS server", 1, 1.2.3.4
    # If you have multicast-FTP available,
    # information for that can be passed in a similar way using options 1
    # to 5. See page 19 of
    # http://download.intel.com/design/archives/wfm/downloads/pxespec.pdf
    # Enable dnsmasq's built-in TFTP server
    #enable-tftp
    # Set the root directory for files available via FTP.
    #tftp-root=/var/ftpd
    # Make the TFTP server more secure: with this set, only files owned by
    # the user dnsmasq is running as will be send over the net.
    #tftp-secure
    # This option stops dnsmasq from negotiating a larger blocksize for TFTP
    # transfers. It will slow things down, but may rescue some broken TFTP
    # clients.
    #tftp-no-blocksize
    # Set the boot file name only when the "red" tag is set.
    #dhcp-boot=tag:red,pxelinux.red-net
    # An example of dhcp-boot with an external TFTP server: the name and IP
    # address of the server are given after the filename.
    # Can fail with old PXE ROMS. Overridden by --pxe-service.
    #dhcp-boot=/var/ftpd/pxelinux.0,boothost,192.168.0.3
    # If there are multiple external tftp servers having a same name
    # (using /etc/hosts) then that name can be specified as the
    # tftp_servername (the third option to dhcp-boot) and in that
    # case dnsmasq resolves this name and returns the resultant IP
    # addresses in round robin fasion. This facility can be used to
    # load balance the tftp load among a set of servers.
    #dhcp-boot=/var/ftpd/pxelinux.0,boothost,tftp_server_name
    # Set the limit on DHCP leases, the default is 150
    #dhcp-lease-max=150
    # The DHCP server needs somewhere on disk to keep its lease database.
    # This defaults to a sane location, but if you want to change it, use
    # the line below.
    #dhcp-leasefile=/var/lib/misc/dnsmasq.leases
    # Set the DHCP server to authoritative mode. In this mode it will barge in
    # and take over the lease for any client which broadcasts on the network,
    # whether it has a record of the lease or not. This avoids long timeouts
    # when a machine wakes up on a new network. DO NOT enable this if there's
    # the slightest chance that you might end up accidentally configuring a DHCP
    # server for your campus/company accidentally. The ISC server uses
    # the same option, and this URL provides more information:
    # http://www.isc.org/files/auth.html
    #dhcp-authoritative
    # Run an executable when a DHCP lease is created or destroyed.
    # The arguments sent to the script are "add" or "del",
    # then the MAC address, the IP address and finally the hostname
    # if there is one.
    #dhcp-script=/bin/echo
    # Set the cachesize here.
    #cache-size=150
    # If you want to disable negative caching, uncomment this.
    #no-negcache
    # Normally responses which come from /etc/hosts and the DHCP lease
    # file have Time-To-Live set as zero, which conventionally means
    # do not cache further. If you are happy to trade lower load on the
    # server for potentially stale date, you can set a time-to-live (in
    # seconds) here.
    #local-ttl=
    # If you want dnsmasq to detect attempts by Verisign to send queries
    # to unregistered .com and .net hosts to its sitefinder service and
    # have dnsmasq instead return the correct NXDOMAIN response, uncomment
    # this line. You can add similar lines to do the same for other
    # registries which have implemented wildcard A records.
    #bogus-nxdomain=64.94.110.11
    # If you want to fix up DNS results from upstream servers, use the
    # alias option. This only works for IPv4.
    # This alias makes a result of 1.2.3.4 appear as 5.6.7.8
    #alias=1.2.3.4,5.6.7.8
    # and this maps 1.2.3.x to 5.6.7.x
    #alias=1.2.3.0,5.6.7.0,255.255.255.0
    # and this maps 192.168.0.10->192.168.0.40 to 10.0.0.10->10.0.0.40
    #alias=192.168.0.10-192.168.0.40,10.0.0.0,255.255.255.0
    # Change these lines if you want dnsmasq to serve MX records.
    # Return an MX record named "maildomain.com" with target
    # servermachine.com and preference 50
    #mx-host=maildomain.com,servermachine.com,50
    # Set the default target for MX records created using the localmx option.
    #mx-target=servermachine.com
    # Return an MX record pointing to the mx-target for all local
    # machines.
    #localmx
    # Return an MX record pointing to itself for all local machines.
    #selfmx
    # Change the following lines if you want dnsmasq to serve SRV
    # records. These are useful if you want to serve ldap requests for
    # Active Directory and other windows-originated DNS requests.
    # See RFC 2782.
    # You may add multiple srv-host lines.
    # The fields are <name>,<target>,<port>,<priority>,<weight>
    # If the domain part if missing from the name (so that is just has the
    # service and protocol sections) then the domain given by the domain=
    # config option is used. (Note that expand-hosts does not need to be
    # set for this to work.)
    # A SRV record sending LDAP for the example.com domain to
    # ldapserver.example.com port 389
    #srv-host=_ldap._tcp.example.com,ldapserver.example.com,389
    # A SRV record sending LDAP for the example.com domain to
    # ldapserver.example.com port 389 (using domain=)
    #domain=example.com
    #srv-host=_ldap._tcp,ldapserver.example.com,389
    # Two SRV records for LDAP, each with different priorities
    #srv-host=_ldap._tcp.example.com,ldapserver.example.com,389,1
    #srv-host=_ldap._tcp.example.com,ldapserver.example.com,389,2
    # A SRV record indicating that there is no LDAP server for the domain
    # example.com
    #srv-host=_ldap._tcp.example.com
    # The following line shows how to make dnsmasq serve an arbitrary PTR
    # record. This is useful for DNS-SD. (Note that the
    # domain-name expansion done for SRV records _does_not
    # occur for PTR records.)
    #ptr-record=_http._tcp.dns-sd-services,"New Employee Page._http._tcp.dns-sd-services"
    # Change the following lines to enable dnsmasq to serve TXT records.
    # These are used for things like SPF and zeroconf. (Note that the
    # domain-name expansion done for SRV records _does_not
    # occur for TXT records.)
    #Example SPF.
    #txt-record=example.com,"v=spf1 a -all"
    #Example zeroconf
    #txt-record=_http._tcp.example.com,name=value,paper=A4
    # Provide an alias for a "local" DNS name. Note that this _only_ works
    # for targets which are names from DHCP or /etc/hosts. Give host
    # "bert" another name, bertrand
    #cname=bertand,bert
    # For debugging purposes, log each DNS query as it passes through
    # dnsmasq.
    #log-queries
    # Log lots of extra information about DHCP transactions.
    #log-dhcp
    # Include another lot of configuration options.
    #conf-file=/etc/dnsmasq.more.conf
    #conf-dir=/etc/dnsmasq.d
    Basically it has only 3 lines:
    domain-needed
    bogus-priv
    dhcp-range=192.168.1.0,192.168.1.150,12h
    I also turned the forwarding on
    # echo 1 >/proc/sys/net/ipv4/ip_forward
    This is my bridge-profile
    /etc/netctl/bridge-profile
    Description="Bridge"
    Interface=br0
    Connection=bridge
    BindsToInterfaces=(enp11s0f0 enp11s0f1)
    IP=dhcp
    #Address=('192.168.1.1/24')
    #SkipNoCarrier=yes
    #Broadcast="192.168.1.255"
    ## sets forward delay time
    #FwdDelay=0
    ## sets max age of hello message
    #MaxAge=10
    when i try to start this profile with netctl start bridge-profile nothing happens and after I will abort process (ctrl+c) this is what i find in journalctl -xn
    Aug 05 11:31:09 localhost dnsmasq-dhcp[497]: DHCP packet received on enp11s0f0 which has no address
    Aug 05 11:31:13 localhost dnsmasq-dhcp[497]: DHCP packet received on enp11s0f0 which has no address
    Aug 05 11:31:14 localhost dnsmasq-dhcp[497]: DHCP packet received on enp11s0f0 which has no address
    Aug 05 11:31:19 localhost dnsmasq-dhcp[497]: DHCP packet received on enp11s0f0 which has no address
    Aug 05 11:32:24 localhost dnsmasq-dhcp[497]: DHCP packet received on enp11s0f0 which has no address
    Aug 05 11:32:29 localhost dnsmasq-dhcp[497]: DHCP packet received on enp11s0f0 which has no address
    Same happens is i try to assign static ip for the bridge. Any help is much appreciated as i have loads of equipment behind that network adapter that i can't run right now.
    Last edited by verb0ss (2013-08-07 18:27:36)

    It appears that I can't set up my bridge interface.
    Description="Bridge"
    Interface=br0
    Connection=bridge
    BindsToInterfaces=(enp11s0f0 enp11s0f1)
    IP=static
    Address=('192.168.1.1/24')
    And this is my journalctl -xn output:
    [root@localhost ~]# journalctl -xn
    -- Logs begin at Tue 2013-07-30 23:47:51 BST, end at Tue 2013-08-06 10:28:45 BST. --
    Aug 06 10:28:44 localhost network[308]: /usr/lib/network/network: line 17: /sys/class/net/br0/flags: No such file or directory
    Aug 06 10:28:44 localhost network[308]: /usr/lib/network/network: line 17: /sys/class/net/br0/flags: No such file or directory
    Aug 06 10:28:44 localhost network[308]: /usr/lib/network/network: line 17: /sys/class/net/br0/flags: No such file or directory
    Aug 06 10:28:45 localhost network[308]: /usr/lib/network/network: line 17: /sys/class/net/br0/flags: No such file or directory
    Aug 06 10:28:45 localhost network[308]: Cannot find device "br0"
    Aug 06 10:28:45 localhost network[308]: Could not add address '192.168.1.1/24' to interface 'br0'
    Aug 06 10:28:45 localhost network[308]: Failed to bring the network up for profile 'bridge-profile'
    Aug 06 10:28:45 localhost systemd[1]: netctl@bridge\x2dprofile.service: main process exited, code=exited, status=1/FAILURE
    Aug 06 10:28:45 localhost systemd[1]: Failed to start Networking for netctl profile bridge-profile.
    -- Subject: Unit netctl@bridge\x2dprofile.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
    -- Unit netctl@bridge\x2dprofile.service has failed.
    -- The result is failed.
    Aug 06 10:28:45 localhost systemd[1]: Unit netctl@bridge\x2dprofile.service entered failed state.
    I'm even unable to make a working profile just for one of the ports:
    ip link set enp11s0f0 down
    ip link set enp11s0f1 down
    Description="Bridge"
    Interface=enp11s0f0
    Connection=ethernet
    IP=static
    Address=('192.168.1.1/24')
    I'm ending up with this:
    [root@localhost netctl]# journalctl -xn
    -- Logs begin at Tue 2013-07-30 23:47:51 BST, end at Tue 2013-08-06 10:32:57 BST. --
    Aug 06 10:32:52 localhost systemd[1]: Starting Networking for netctl profile enp11s0f0...
    -- Subject: Unit [email protected] has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit [email protected] has begun starting up.
    Aug 06 10:32:52 localhost network[381]: Starting network profile 'enp11s0f0'...
    Aug 06 10:32:52 localhost kernel: e1000e 0000:0b:00.0: irq 57 for MSI/MSI-X
    Aug 06 10:32:52 localhost kernel: e1000e 0000:0b:00.0: irq 57 for MSI/MSI-X
    Aug 06 10:32:52 localhost kernel: IPv6: ADDRCONF(NETDEV_UP): enp11s0f0: link is not ready
    Aug 06 10:32:57 localhost network[381]: No connection on interface 'enp11s0f0'
    Aug 06 10:32:57 localhost network[381]: Failed to bring the network up for profile 'enp11s0f0'
    Aug 06 10:32:57 localhost systemd[1]: [email protected]: main process exited, code=exited, status=1/FAILURE
    Aug 06 10:32:57 localhost systemd[1]: Failed to start Networking for netctl profile enp11s0f0.
    -- Subject: Unit [email protected] has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
    -- Unit [email protected] has failed.
    -- The result is failed.
    Aug 06 10:32:57 localhost systemd[1]: Unit [email protected] entered failed state.

  • Aperture + Adobe Bridge: does that increase amount of storage per image?

    I recently installed Aperture after using Photoshop CS3 and Bridge for some years. When I import images into Aperture that have already been downloaded into Bridge, does that increase the amount of storage space I'm using and if so by how much? I am saving all files to the same folders but what about the various versions created. How much storage are they taking up. My iMac 24 w. 320 Gig is almost full so storage is important.
    Also, if I start using Aperture 3 to download from my camera, do I need Bridge? Any danger in getting rid of Bridge?
    Thanks,
    Cliff

    Cliff,
    The first question is whether you want to run a Managed or Referenced library. The difference is that Managed copies and stores the images inside the Aperture Library package, where a Referenced library locates the master images in Finder somewhere.
    The import procedure is done in both cases, but you use the 'Store Files' drop-down to tell Aperture where to store the master image files.
    With Bridge, you were probably using 'Photo Downloader' to import the files to a selected folder, name the files using some options for format and counting, and perhaps adding basic or predefined metadata on import. This results in a Finder folder structure of your choosing (as well as file names).
    With Aperture, you can do the same thing by selecting 'Choose' under the 'Store Files' drop-down (where you choose or create a new folder). Once you select a location, two other options become available; (1) to move or copy the files and, (2) to pick a sub-folder preset - or choose 'Edit' at bottom of list to design your own folder preset.
    Once you have your location and folder settings selected, you can then use the 'Import Settings' drop-down to select 'Rename Files' option. This gives you a 'Version Name' drop-down in the pane which you can again select a preset or use the 'Edit' at bottom to design your own.
    The items I listed would allow you to keep working like you have been with Bridge to import your images. If your current folder structure can be replicated in the Folder Naming preset dialog, then you could easily continue as you were with Aperture.
    If you want to run the Managed Library, then importing your folders is possible, but you will need to decide how you want to organize the library structure when compared to your current hierarchy.
    The thing to remember about Aperture is that 'Projects' are the only part that actually contain images (whether masters inside or references to masters outside). So, for example; you could use a 'Blue Folder' named 'Year 2010' and then have a 'Project' for each month under the Blue Folder. You could then make an 'Album' for day inside a month Project.
    The result of the aforementioned structure would be a top level folder which then contains projects for each month (where each project is divided up using Albums). Because Projects are the only thing holding images, the albums use aliases for the various images inside that project. Clicking on a days' album would show just the images of that day, where clicking on the Project name would show all images for that month. The blue folder is just an organization tool to help control the clutter.
    Before mentioning my workflow or suggesting another, I would like to compare Bridge/ACR/PS to Aperture work flow.
    With Bridge, you import and organize images in a folder structure, then add metadata (keywords, personal info, etc.) You can also create collections and smart collections for quick references (which are generated by Bridge when asked, which can be a bit slow with smart collections). You then use ACR plug-in to make 'non-destructive' parameter decisions before sending to Photoshop for rendering and more specific edits and output.
    With Aperture, you import into the library (where most of the processing is done on the front end for previews and database storage). You are then in a one-stop workshop where you just use the Inspector pane and toolbars to add metadata, create albums and smart albums, and add adjustments to the versions. At this point, you are set to decide on any output (using the print, image export or web/book album features).
    In essence, and IMHO, you are changing from three separate programs to one program with three Inspector panes.
    Workflow:
    I use a managed library because I have the disc space. I also like the fact that I can copy the library package once a month (at least) to an external drive and have a full working backup which can be run from that drive or copied onto a new drive and double-clicked to load it. The downside to this approach is space. I typically shoot RAW + JPEG and import just the JPEG's to start > decide on the keepers and reject the rest > import the matching RAW's to the project. I use JPEG as Master, because they are all that is needed in many cases. I can switch to the RAW version at any time if I want something more than the JPEG can provide.
    My first suggestion to you would be to create a new empty library as follows:
    1 - Launch Aperture while pressing the 'Option' (Alt) key
    2 - Select 'Create New' button
    3 - Select a location and name the library with a unique name
    This will allow you to import say a few folders (make sure to copy images, not move) and test out how you want to organize the library. You can always delete the library and start over. Look in to the File Naming and Folder Naming items under 'Aperture menu > Presets' to get a feel for the options you have and perhaps create a custom preset or two. These become options in the 'Rename Files> Version Name' and 'Store Files > Subfolder' drop-downs in the Import Pane.
    Here are a few links from the online User Manual that might help clarify:
    *Import folders of images*:
    http://documentation.apple.com/en/aperture/usermanual/#chapter=4%26section=9
    Pay special note to the statement under step #5: *"The top-level folder is converted to a project. If the folder you imported contains a hierarchy of subfolders and images, the subfolders appear as albums."*
    That may address your importing of current image folders (or will give you a good test scenario for the empty library).
    *Planning import strategy*:
    http://documentation.apple.com/en/aperture/usermanual/#chapter=4%26section=3
    *General importing files on computer*:
    http://documentation.apple.com/en/aperture/usermanual/#chapter=4%26section=5
    *Working with Referenced Images*:
    http://documentation.apple.com/en/aperture/usermanual/#chapter=5%26section=16%26 hash=apple_ref:doc:uid:Aperture-UserManual-91292BSR-1037525
    This last link should give you an overview of the options for working with and troubleshooting a referenced image scheme.
    Okay, that should be enough for you to think about for a few. Feel free to ask more as needed. There are many here who know a lot more than I.

  • How do aperture and iphoto interact

    I am purchasing a new imac this week and am trying to get an idea on what software I want.  I've been using adobe photoshop elements for the past few years when I needed to fix any photos and iphoto to sort and 'hold' my collection.  I've been reading about aperture 3 and cannot find clear information on how it does or doesn't interact with iphoto. 
    From what I've been able to discern, aperture is more of a photo management system and PSE is more of a photo adjustment program.. correct?
    So if I buy aperture3, when I download photos, does Aperture receive them or do they still come in through iphoto?  And if it is the latter, do iphoto and aperture work together? 
    I've looked at some earlier posts but I have not found a clear answer.  I do not want to duplicate software but I also was not that clear before on how iphoto and PSE might work together.  It seemed like I had iphoto import the pictures and when I needed to, I opened pse and used it to fix or play with a photo. 
    I also have my camera software, but the sort of adds to my confusion.  But maybe computers that don't have a program like iphoto need the camera software.
    I'd appreciate hearing what works and what experienced aperture and/or PSE might tell me.

    Hello Calxoddity, Roger and Kirby,
    All three of your answers were very helpful and I appreciate your time.  I tried to send this reply message a few minutes ago and when I went to hit send, it said I was not logged in... I HAD been logged in so maybe it timed out.  Anyway, this post comes through twice I am sorry.
    I was feeling pretty befuddled with what to do, adding this topic to the decision on which computer to buy, etc.  So your time and wisdom helped me to get my needs into perspective.  I think I will start with the newer iphoto that comes on my imac and get PSE9 since my version of PSE is very old.. LOL  and then, spend some time learning about aperture 3, since as Roger mentioned, I can import/move the files over to aperture at a future time.  Since aperture 3 is the most expensive, it seems a wise move. 
    Oh, did read Kirby's article/post, thank you, very well written to help a newbie get a handle, and will watch the online tutorial for aperture 3 as well.  And maybe it will tell me there, but right now, with iphoto I can easily email a photo and I think it will easily be shared with an ipad2.  If I get aperture 3 and use it instead of iphoto, does it have an easy interface for sharing via email and/or the ipad?
    Thanks again, you are great!
    michelle

  • RIGHT SIDE OF BRIDGE INTERFACE "FADED OUT"

    I just upgraded from CS5 to CS6, and I get a "strange" occurrence in which a portion of the right side of the Bridge interface, where 2/3s of  the area of the METADATA/KEYWORDS are no longer visible, & the Window or Page "under" it shows through.
    EXAMPLE:  In Photoshop, the lower, right half of my interface has the History Palette.  When I "switch" to Bridge, though the Preview "Window" in the top right remains in tact, the Photoshop History Pallete is "covering" the right 2\3s of the METADATA panel.
    It occurs with any "page" below the Bridge interface; for example with the Bridge Forum web page open, the portiion that depicts "Top Participants" etc. covers the Bridge METADATA panel.
    I tried taking a screen shot but the problem "went away" in the screen shot interface.
    Leigh 

    Selecting "NEW SYNCHRONIZED WINDOW" has apparently fixed the problem, but can't help but wonder why it happens at all.

Maybe you are looking for