1. 14 Sep, 2009 9 commits
  2. 07 Sep, 2009 18 commits
  3. 01 Sep, 2009 1 commit
  4. 17 Aug, 2009 1 commit
  5. 15 Aug, 2009 11 commits
    • Jim Pryor's avatar
      quotes! · 09a2212f
      Jim Pryor authored
      
      
      Signed-off-by: default avatarJim Pryor <profjim@jimpryor.net>
      09a2212f
    • Jim Pryor's avatar
      07aa8f78
    • Jim Pryor's avatar
      Isolate ip to ethernet-iproute, ifconfig to ethernet + wireless · 6c5e4f9a
      Jim Pryor authored
      
      
      * The point of having both ethernet and ethernet-iproute
      	  was presumably to transition slowly from ifconfig/net-tools to
      	  iproute2. But the current codebase mixes the two in handling
      	  ethernet and wireless connections. This commit separates
      	  all the ip calls to the newer connections, and the ifconfig
      	  calls to the older connections. The latter now call set_interface
      	  with up-old, down-old, forcedown-old.
      
      	* I'm not urging that ifconfig code sticks around. Just trying
      	  to make the code consistent with what seems to me to be
      	  its implicit design principles.
      
      	* the check for NO-CARRIER in ethernet is now also done without
            calling iproute2 tools. I saw this technique recommended somewhere
      	  but have no citation. I don't know how many kernel revisions one
            can rely on any given part of /sys to remain stable for.
            It may be possible to achieve the same goal here in other ways.
      	  If in fact it's worth the effort to keep the ifconfig code
      	  around.
      
      	* Began also to integrate the IPROUTE variable introduced in
      	  ethernet, but stopped. If that's integrated everywhere, shouldn't
      	  it make connection=ethernet equivalent to
            connection=ethernet-iproute? Is there justification for
      	  using it at some places but not everywhere? I just let it alone
            for now.
      
      Signed-off-by: default avatarJim Pryor <profjim@jimpryor.net>
      6c5e4f9a
    • Jim Pryor's avatar
      start consolidation of ifconfig/ip/set_interface · e27d0945
      Jim Pryor authored
      
      
      * try to factor all the ifconfig/ip set dev code to single location
      	  (currently networks/set_interface, though I recommend a different name
      	  for this function because it's too close in name and different
      	  in functionality from set_iface, set_profile).
      
      	* added "forcedown" option to set_interface, meaning "just go down
      	  don't worry about 'nodown' quirks"
      
      	* even with "forcedown", this factoring would introduce "ip addr
      	  flush dev $INTERFACE" calls to existing code. I assume that's
      	  harmless? or even beneficial?
      
      	* one code block (in ethernet_iproute) had stdout,stderr of the
            down calls redirected to /dev/null. I've moved that to
      	  set_interface, so now everyone's getting that behavior. I assume
      	  that's appropriate...
      
      	* now no more calls to "ip" or "ifconfig" outside of set_interface,
      	  except the checks for NO-CARRIER after ethernet*/set_interface up.
            They might also be moved to network/set_interface?
      
      	* as of this commit, all the set_interface calls are now using ip
      	  instead of ifconfig. A subsequent commit will isolate the ip-use
      	  to ethernet-iproute and the ifconfig-use to ethernet.
      
      	* ALERT: attend to wireless_down, it seems to be calling
      	  set_interface down twice (once in ethernet_down, once in itself).
      	  And neither this commit nor the code it's patching respects
      	  quirk nodown in the ethernet_down block.
      
      Signed-off-by: default avatarJim Pryor <profjim@jimpryor.net>
      e27d0945
    • Jim Pryor's avatar
      2282776f
    • Jim Pryor's avatar
      improve list_networks, report APs too · dc0c1d07
      Jim Pryor authored
      
      
      Signed-off-by: default avatarJim Pryor <profjim@jimpryor.net>
      dc0c1d07
    • Jim Pryor's avatar
      Add AP argument to profile, also let ESSID arguments be regexps · 9578dda4
      Jim Pryor authored
      
      
      * AP= arguments in profiles take precedence over ESSID= arguments
      
      * ESSID= arguments regexps instead of literals. To avoid screwing up
        any currently working profiles, I restricted the interpretation as a
        regexp to just the new wireless-dbus connection types.
      
      * But a global change involved in implementing this is that the
        connection up/down calls will be passed a literal ESSID (which of the
        local networks matches the regexp) as an additional argument.
      
      Signed-off-by: default avatarJim Pryor <profjim@jimpryor.net>
      9578dda4
    • Jim Pryor's avatar
      silence an error in set_iface · c37f2081
      Jim Pryor authored
      
      
      Signed-off-by: default avatarJim Pryor <profjim@jimpryor.net>
      c37f2081
    • Jim Pryor's avatar
      use STATE_DIR in /usr/bin/netcfg · 387472ec
      Jim Pryor authored
      
      
      Signed-off-by: default avatarJim Pryor <profjim@jimpryor.net>
      387472ec
    • Jim Pryor's avatar
      make wep_check more robust · 8b9f249f
      Jim Pryor authored
      
      
      Signed-off-by: default avatarJim Pryor <profjim@jimpryor.net>
      8b9f249f
    • Jim Pryor's avatar
      give wireless-dbus smarter read_config · 03ea8917
      Jim Pryor authored
      
      
      Signed-off-by: default avatarJim Pryor <profjim@jimpryor.net>
      03ea8917