Re: [389-users] Repair replication
Hi All, I wanted to update this issue as I've made some progress but replication is still not working as it should. I've removed the previous communication as it was getting very long and I began to receive 'message too large' responses from the list server. The history of this post can be read in the archives: http://lists.fedoraproject.org/pipermail/389-users/2012-April/thread.html. So, I've tried to simplify my efforts by removing the consumer replication agreements for now to focus on getting the multi-master replication working first. To briefly review, I inherited two multi-master systems (A B) and A has been the only system running for many years. To get replication working I've done the following: 1. Initialize master B data from a nightly backup from master A as: ./bak2db bak/directory -n my_suffix - I see this in the error log: [20/Apr/2012:10:30:31 -0700] - Add Attribute readonly Value off [20/Apr/2012:10:30:31 -0700] - Add Attribute nsslapd-directory Value /data/LDAP/slapd-master A server name/db/my_suffix [20/Apr/2012:10:30:31 -0700] - Del Attribute nsslapd-directory Value /data/LDAP/slapd-master B server name/db/my_suffix [20/Apr/2012:10:30:31 -0700] - WARNING!!: current Instance Config is different from backed up configuration; The backup is restored. [20/Apr/2012:10:30:31 -0700] - dblayer_restore: Removing staging area /opt/fedora-ds/slapd-master B server name/db/../fribak. *Is there any problem regarding the lines above that change the '**nsslapd-directory attribute from it's original correct master B path to the path of master A**as part of the initialization? Or is this reset to the correct path for master B?* *If I need to reset some attributes, how can I view the current nsslapd-directory attribute from the command line with ldapsearch?* 2. Start slapd deamon on master B. From error log: [20/Apr/2012:10:30:40 -0700] - Fedora-Directory/7.1 B2005.146.2010 starting up [20/Apr/2012:10:30:40 -0700] NSMMReplicationPlugin - replica_check_for_data_reload: Warning: data for replica o=my_suffix was reloaded and it no longer matches the data in the changelog (replica data changelog). Recreating the changelog file. This could affect replication with replica's consumers in which case the consumers should be reinitialized. 3. Create replication agreements between master A and B on both systems. 4. Run an initialization from the DS console on master B to master A. Here is what I see from the logs: error log on master B: [20/Apr/2012:10:30:40 -0700] - slapd started. Listening on All Interfaces port 389 for LDAP requests [20/Apr/2012:10:31:05 -0700] NSMMReplicationPlugin - Beginning total update of replica agmt=cn=my_suffix_to_master_A (master_A:389). [20/Apr/2012:10:31:11 -0700] NSMMReplicationPlugin - Finished total update of replica agmt=cn=my_suffix_to_master_A (master_A:389). Sent 1718 entries. *The above appears to have sent 1718 entries to master A. And replication status' on master B says incremental update succeeded. *error log on master A: [20/Apr/2012:10:30:40 -0700] NSMMReplicationPlugin - conn=1578 op=3 repl=o=my_suffix: Begin incremental protocol [20/Apr/2012:10:30:40 -0700] NSMMReplicationPlugin - conn=1578 op=3 repl=o=my_suffix: Acquired replica [20/Apr/2012:10:30:40 -0700] NSMMReplicationPlugin - conn=1578 op=3 repl=o=my_suffix: StartNSDS50ReplicationRequest: response=0 rc=0 [20/Apr/2012:10:30:40 -0700] NSMMReplicationPlugin - conn=1578 op=5 repl=o=my_suffix: Released replica [20/Apr/2012:10:31:03 -0700] NSMMReplicationPlugin - conn=1579 op=3 repl=o=my_suffix: Begin total protocol [20/Apr/2012:10:31:03 -0700] NSMMReplicationPlugin - conn=1579 op=3 repl=o=my_suffix: Acquired replica [20/Apr/2012:10:31:03 -0700] NSMMReplicationPlugin - multimaster_be_state_change: replica o=my_suffix is going offline; disabling replication [20/Apr/2012:10:31:04 -0700] NSMMReplicationPlugin - agmt=cn=my_suffix_to_master_B (master_B:389): State: backoff - backoff [20/Apr/2012:10:31:04 -0700] NSMMReplicationPlugin - agmt=cn=my_suffix_to_master_B (master_B:389): State: backoff - backoff [20/Apr/2012:10:31:04 -0700] NSMMReplicationPlugin - agmt=cn=my_suffix_to_master_B (master_B:389): No linger to cancel on the connection [20/Apr/2012:10:31:04 -0700] NSMMReplicationPlugin - agmt=cn=my_suffix_to_master_B (master_B:389): Disconnected from the consumer [20/Apr/2012:10:31:05 -0700] NSMMReplicationPlugin - agmt=cn=my_suffix_to_master_B (master_B:389): repl5_inc_stop: protocol stopped after 0 seconds [20/Apr/2012:10:31:05 -0700] NSMMReplicationPlugin - conn=0 op=0 repl=o=my_suffix: Replica in use locking_purl=conn=1579 id=3 [20/Apr/2012:10:31:05 -0700] NSMMReplicationPlugin - replica_disable_replication: replica o=my_suffix is acquired [20/Apr/2012:10:31:05 -0700] - WARNING: Import is running with nsslapd-db-private-import-mem on; No other process is allowed to access the database [20/Apr/2012:10:31:05 -0700] NSMMReplicationPlugin - conn=1579 op=3
Nvidia Resolution settings ?
F17-beta installed kmod-nvidia and blacklisted nouveau . restarting computer and resolution is so high that characters are so small at Desktop you can't see them. Checked Xorg.conf and the only setting is the Device Section no settings for Resolution. What do I put in there for 1280x764 ? Doesn't the setting in grub2.cfg, vga=31B apply any more ? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
XFCE Login Freeze
Hi list, We have a multi-workstation network, with several nodes running F16/XFCE on remote-mounted home directories. All users can log in and out without any difficulty except one. This user gives name and password but then freezes indefinitely. 'ps' shows a variety of tasks running, but nothing appears on screen except the standard wallpaper; time is present but nothing else. Running are startxfce, xfce-session, etc. User can be cleared by kill -15 startxfce-pid and other users can log then log in. What might be causing the freeze - is there some lockfile that needs removing to unlock the user's account? Jonathan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
EXIM, Postgresql and database replication
Hi folks, I am rolling out another Exim mail server into a new site that I am setting up. Based on replies from last week I am going to look into using Postgresql instead of flat files for aliases etc. I have a couple of questions. My aim is to roll this out to my 3 existing mail servers if I like the look of it. One of the reasons I want to do this is for the reverse alias lookup that I asked about last week. As well as being able to convert gary.stainburn@ to gstainb for local delivery I want to be able to convert gstainb back to gary.stainburn@ for vacation messages etc. 1) Does anyone have example Exim and SQL setups that I could crib from? 2) For speed and reliability I want to host the database on the same server as Exim. This will mean having multiple databases. What is the best method of keeping these database copies syncronised? Gary -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: EXIM, Postgresql and database replication
On Fri, Apr 20, 2012 at 9:36 AM, Gary Stainburn gary.stainb...@ringways.co.uk wrote: Hi folks, I am rolling out another Exim mail server into a new site that I am setting up. Based on replies from last week I am going to look into using Postgresql instead of flat files for aliases etc. I have a couple of questions. My aim is to roll this out to my 3 existing mail servers if I like the look of it. One of the reasons I want to do this is for the reverse alias lookup that I asked about last week. As well as being able to convert gary.stainburn@ to gstainb for local delivery I want to be able to convert gstainb back to gary.stainburn@ for vacation messages etc. 1) Does anyone have example Exim and SQL setups that I could crib from? 2) For speed and reliability I want to host the database on the same server as Exim. This will mean having multiple databases. What is the best method of keeping these database copies syncronised? Gary -- please try bucardo. its package for fedora. yum -y install bucardo -- Itamar Reis Peixoto msn, google talk: ita...@ispbrasil.com.br +55 11 4063 5033 (FIXO SP) +55 34 9158 9329 (TIM) +55 34 8806 3989 (OI) +55 34 3221 8599 (FIXO MG) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Nvidia Resolution settings ?
On Fri, 2012-04-20 at 04:04 -0400, binary...@comcast.net wrote: F17-beta Wrong list... installed kmod-nvidia and blacklisted nouveau . restarting computer and resolution is so high that characters are so small at Desktop you can't see them. To which the good way to fix up tiny fonts is to specify using a larger font, not to drop the resolution down on a high-resolution-capable display. Though it may well be that you need to, first, have X know what you resolution actually is, so it produces normal looking sized fonts, for normal sized font settings (i.e. 12 point fonts ought to look so big on any display, not have variable sizing). But again, you're posting to the wrong list. Those who work on the beta releases may not watch this list at all. -- [tim@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Nvidia Resolution settings ?
On Fri, Apr 20, 2012 at 3:04 AM, binary...@comcast.net wrote: F17-beta installed kmod-nvidia and blacklisted nouveau . restarting computer and resolution is so high that characters are so small at Desktop you can't see them. Checked Xorg.conf and the only setting is the Device Section no settings for Resolution. What do I put in there for 1280x764 ? Doesn't the setting in grub2.cfg, vga=31B apply any more ? Since this is about the Nvidia proprietary driver this should probably be sent to the RPM Fusion mailing list... I've always needed a 0x in front of the vga setting, i.e.: vga=0x318 Richard -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Problem with Yum to upgrade Fedora 17.
Hi all, I'm using Fedora 17 on my workstation but I'm having issue to upgrade my system. I think someone pushed some Alpha packages to the updates-testing repository. Does any one know if this is expected? The output below shows yum update --skip-broken. Packages skipped because of dependency problems: 1:libsmbclient-4.0.0-41alpha18.fc17.x86_64 from updates-testing pytalloc-2.0.7-4.fc17.x86_64 from fedora 1:samba4-client-4.0.0-41alpha18.fc17.x86_64 from updates-testing 1:samba4-common-4.0.0-41alpha18.fc17.x86_64 from updates-testing 1:samba4-dc-4.0.0-41alpha18.fc17.x86_64 from updates-testing 1:samba4-dc-libs-4.0.0-41alpha18.fc17.x86_64 from updates-testing 1:samba4-libs-4.0.0-41alpha18.fc17.x86_64 from updates-testing Dependencies Resolved Package Arch Version Repository Size Updating: wpa_supplicantx86_641:1.0-0.3.fc17fedora 409 k Skipped (dependency problems): libsmbclient x86_641:4.0.0-41alpha18.fc17updates-testing 60 k pytalloc x86_642.0.7-4.fc17 fedora 11 k samba4-client x86_641:4.0.0-41alpha18.fc17updates-testing 725 k samba4-common x86_641:4.0.0-41alpha18.fc17updates-testing 587 k samba4-dc x86_641:4.0.0-41alpha18.fc17updates-testing 997 k samba4-dc-libsx86_641:4.0.0-41alpha18.fc17updates-testing 370 k samba4-libs x86_641:4.0.0-41alpha18.fc17updates-testing 3.3 M Transaction Summary Upgrade1 Package Skipped (dependency problems) 7 Packages Total download size: 409 k Is this ok [y/N]: Best regards, --- *Davi Garcia* +55 (21) 8193-0132 http://br.linkedin.com/in/davivcgarcia -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Problem with Yum to upgrade Fedora 17.
On 04/21/2012 12:09 AM, Davi Garcia wrote: I'm using Fedora 17 on my workstation but I'm having issue to upgrade my system. I think someone pushed some Alpha packages to the updates-testing repository. Does any one know if this is expected? The output below shows yum update --skip-broken. You are running F17-BETA. You want this list t...@lists.fedoraproject.org But, the answer isknown issue. Wait a bit -- Never be afraid to laugh at yourself, after all, you could be missing out on the joke of the century. -- Dame Edna Everage -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Problem with Yum to upgrade Fedora 17.
On 20/04/12 17:09, Davi Garcia wrote: Hi all, Aside from posting to the wrong-list, what the problem? Did you check is Samba4 the Alpha? f17 is currently at Beta not alpha. Correct List for test-builds: https://lists.fedoraproject.org/pipermail/test/ -- Regards, Frank Jack of all, fubars -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Problem with Yum to upgrade Fedora 17.
Am 20.04.2012 18:09, schrieb Davi Garcia: Hi all, I'm using Fedora 17 on my workstation but I'm having issue to upgrade my system. I think someone pushed some Alpha packages to the updates-testing repository. Does any one know if this is expected? The output below shows yum update --skip-broken. Packages skipped because of dependency problems: 1:libsmbclient-4.0.0-41alpha18.fc17.x86_64 from updates-testing pytalloc-2.0.7-4.fc17.x86_64 from fedora 1:samba4-client-4.0.0-41alpha18.fc17.x86_64 from updates-testing 1:samba4-common-4.0.0-41alpha18.fc17.x86_64 from updates-testing 1:samba4-dc-4.0.0-41alpha18.fc17.x86_64 from updates-testing 1:samba4-dc-libs-4.0.0-41alpha18.fc17.x86_64 from updates-testing 1:samba4-libs-4.0.0-41alpha18.fc17.x86_64 from updates-testing first you are using a beta version of fedora additionally you are using updates-testing on a beta-release finally samba4 is alpha and will be for the near future you decided to install samba4 instead of samba even Fedora 18 will contain samba-3.x for now http://koji.fedoraproject.org/koji/packageinfo?packageID=360 so why are you explicitly installing alpha software on beta-release? what do you expect now? downgrade to regular samba or simply wait / skip-broken for some time signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Problem with Yum to upgrade Fedora 17.
On 20/04/12 17:17, Reindl Harald wrote: first you are using a beta version of fedora additionally you are using updates-testing on a beta-release That is normal Fedora practice for pre-GA Branched. fedora.repo updates-testing.repo which on GA, updates-testing.repo gets disabled, updates.repo gets enabled. -- Regards, Frank Jack of all, fubars -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Fedora-17 Irritations
Hello list, I've just installed the beta in a VM so as to evaluate GNOME 3.4 (and Fedora-17 as well). Two irritating issues have emerged that would be show stoppers, if incapable of resolution. They are: 1. I choose United Kingdom (English) for the obvious reason - I live here - and I appear to be forced to use the French numbering system, rather than Imperial. 2.I installed an HP printer via the Printers dialogue and I cannot find any way to set paper sizes to A4. I suspect that both of the above are easily fixable, but lack of familiarity with Red Hat since 6.2 means a little help would be appreciated. Thanks in advance. Peter HB -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora-17 Irritations
On 20/04/12 17:27, Peter Hillier-Brook wrote: a little help would be appreciated. Here you go: Correct List for test-builds: https://lists.fedoraproject.org/pipermail/test/ -- Regards, Frank Jack of all, fubars -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
ath9k with hostapd and iPad / iPhone
Hi has somebody magic settings to get Apple mobile-crap working with hostapd instead permanently interrupt the connection? other mobile devices are working fine all the time up to 80 Mbit netto and only recent iPhone / iPad is running in trouble no these are not my devices but my AP :-( the iphone-block from my hostapd.conf below was a try after google around the world, other devies are still happy but the apple crap is still not impressed by the change ___ 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04) 00:1a.0 USB Controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b4) 00:1c.6 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 7 (rev b4) 00:1c.7 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 8 (rev b4) 00:1d.0 USB Controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a4) 00:1f.0 ISA bridge: Intel Corporation Q67 Express Chipset Family LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 04) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04) 01:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection 03:00.0 Network controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01) ___ cat /etc/hostapd/hostapd.conf # default settings ctrl_interface=/var/run/hostapd ctrl_interface_group=0 auth_algs=1 ignore_broadcast_ssid=0 macaddr_acl=1 accept_mac_file=/etc/hostapd/accept # login-data ssid= wpa_passphrase=** # wpa2-only support wpa=2 rsn_pairwise=CCMP # wpa1/wpa2 support # wpa=3 # wpa_key_mgmt=WPA-PSK # wpa_pairwise=TKIP # rsn_pairwise=CCMP # local configuration interface=wlan0 bridge=br0 driver=nl80211 hw_mode=g ieee80211n=1 wmm_enabled=1 channel=11 country_code=AT max_num_sta=100 # iphone ieee8021x=0 eap_server=0 wme_enabled=0 # logging # 0 = verbose debugging # 1 = debugging # 2 = informational messages # 3 = notification # 4 = warning logger_syslog=1 logger_syslog_level=2 ___ Name : hostapd Architektur : x86_64 Version: 0.7.3 Ausgabe: 2.fc15 Größe : 553 k Repo: installed Aus repo: fedora Zusammenfassung : IEEE 802.11 AP, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator URL: http://w1.fi/hostapd Lizenz : BSD Beschreibung : hostapd is a user space daemon for access point and authentication : servers. It implements IEEE 802.11 access point management, IEEE : 802.1X/WPA/WPA2/EAP Authenticators and RADIUS authentication server. : : hostapd is designed to be a daemon program that runs in the back- : ground and acts as the backend component controlling authentication. : hostapd supports separate frontend programs and an example text-based : frontend, hostapd_cli, is included with hostapd. ___ output of lsmod Module Size Used by nf_nat_ftp 12770 0 nf_conntrack_ftp 14484 1 nf_nat_ftp nf_nat_sip 17079 0 nf_conntrack_sip 28807 1 nf_nat_sip xt_state 12578 20 iptable_mangle 12695 0 ipt_MASQUERADE 12880 2 iptable_nat13383 1 nf_nat 25143 4 nf_nat_ftp,nf_nat_sip,ipt_MASQUERADE,iptable_nat nf_conntrack_ipv4 14622 23 iptable_nat,nf_nat nf_conntrack 82286 9 nf_nat_ftp,nf_conntrack_ftp,nf_nat_sip,nf_conntrack_sip,xt_state,ipt_MASQUERADE,iptable_nat,nf_nat,nf_conntrack_ipv4 nf_defrag_ipv4 12673 1 nf_conntrack_ipv4 tun22804 2 bridge 90950 0 stp12823 1 bridge llc14090 2 bridge,stp ipt_LOG12993 1 xt_limit 12711 1 xt_recent 18474 6 xt_multiport 12798 16 coretemp 13401 0 arc4 12529 2 ath9k 134768 0 mac80211 496450 1 ath9k ath9k_common
Re: Fedora-17 Irritations
On 04/20/2012 06:27 PM, Peter Hillier-Brook wrote: 2.I installed an HP printer via the Printers dialogue and I cannot find any way to set paper sizes to A4. Try running system-config-printer Regards, Patrick -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Problem with Yum to upgrade Fedora 17.
On Fri, Apr 20, 2012 at 13:09:45 -0300, Davi Garcia cont...@davigarcia.me wrote: Hi all, I'm using Fedora 17 on my workstation but I'm having issue to upgrade my system. I think someone pushed some Alpha packages to the updates-testing repository. Does any one know if this is expected? The output below shows yum update --skip-broken. Packages skipped because of dependency problems: 1:libsmbclient-4.0.0-41alpha18.fc17.x86_64 from updates-testing pytalloc-2.0.7-4.fc17.x86_64 from fedora 1:samba4-client-4.0.0-41alpha18.fc17.x86_64 from updates-testing 1:samba4-common-4.0.0-41alpha18.fc17.x86_64 from updates-testing 1:samba4-dc-4.0.0-41alpha18.fc17.x86_64 from updates-testing 1:samba4-dc-libs-4.0.0-41alpha18.fc17.x86_64 from updates-testing 1:samba4-libs-4.0.0-41alpha18.fc17.x86_64 from updates-testing Not really. It looks like samba4 is being positioned to replace samba post beta in F17. This doesn't seem like a great idea to me, but probably will work out. The most recent change had libsmbclient4 change to libsmbclient. However since libsmbclient client now depends on samba4 stuff (samba4-common) instead instead samba stuff, updating libsmbclient needs samba4 stuff installed. The problem is that samba4 stuff conflicts with samba stuff and samba4 stuff doesn't obsolete samba stuff. I was planning on filing a bug about this issue if there isn't already one. If you want to switch from samba to samba4 you can do it in yum shell without having to uninstall all of the stuff that depends on samba. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Problem with Yum to upgrade Fedora 17.
Hi all, Thanks for all feedback! Sorry about post question to the wrong list and about my poor problem description. Let me try explain better: I never decided to install Samba or Samba4 in my workstation, these packages were installed by default. I know that I'm using F17 that is still in beta, but I didn't know that alpha packages were being pushed to that repository. My problem is basically that Yum is not able to upgrade my system without use --skip-broken. Since Ed Greshko confirmed that is a known issue, I'll wait the fix. What is very confusing is why do we have alpha packages in a beta repo? Again, sorry about any inconvenience. Best regards, Davi Garcia -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 17 beta not supporting rsolutions above 1024x768 in Nouveau
On 04/19/2012 04:37 PM, Jim wrote: Fedora 17 beta can't get any resolution above 1024x768 with Nouveau driver, I need at least 1280x768 to display fullscreen on 42 TV monitor, worked ok on F14. Please take F17 discussions to t...@lists.fedoraproject.org. F17 is not yet released and as such not a subject for this list (yet). Don't mean to beat up on you, Jim--you're not the only person doing this, but gang, in general, F17 stuff belongs on the test list until it gets released. -- - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com - - AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 - -- - Men occasionally stumble over the truth, but most of them pick - - themselves up and hurry off as if nothing had happened. - - -- Winston Churchill - -- -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora-17 Irritations
On Fri, 20 Apr 2012 17:27:36 +0100 Peter Hillier-Brook wrote: 2.I installed an HP printer via the Printers dialogue and I cannot find any way to set paper sizes to A4. The weird thing is in the US, I constantly run into printers all defaulting to A4 when I want US-Letter. I think there must be a test backward somewhere in the paper handling code :-). Anyway, I did finally decrypt the paper size default secret: yum install libpaper echo Letter /etc/papersize That gets libreoffice (at least) to default to Letter when creating a new document. Presumably you could swap in A4 instead of Letter. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora-17 Irritations
On Fri, 20 Apr 2012, Tom Horsley wrote: On Fri, 20 Apr 2012 17:27:36 +0100 Peter Hillier-Brook wrote: 2.I installed an HP printer via the Printers dialogue and I cannot find any way to set paper sizes to A4. The weird thing is in the US, I constantly run into printers all defaulting to A4 when I want US-Letter. I think there must be a test backward somewhere in the paper handling code :-). Anyway, I did finally decrypt the paper size default secret: yum install libpaper echo Letter /etc/papersize That gets libreoffice (at least) to default to Letter when creating a new document. Presumably you could swap in A4 instead of Letter. Will that necessarily work? It seems to me that you could have a situation in which libreoffice believes in A4, but the printer still believes in Letter. When I had application/printer mismatch problems, it was usually because the application believed in A4 and the printer in Letter. In such cases, the authour had usually added extra u's to the documentation. -- Michael henne...@web.cs.ndsu.nodak.edu On Monday, I'm gonna have to tell my kindergarten class, whom I teach not to run with scissors, that my fiance ran me through with a broadsword. -- Lily -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora-17 Irritations
On Fri, 20 Apr 2012 12:09:42 -0500 (CDT) Michael Hennebry wrote: Will that necessarily work? It seems to me that you could have a situation in which libreoffice believes in A4, but the printer still believes in Letter. True, you have to get everyone on the same page (groan :-). You may need to yum install system-config-printer so you can then run system-config-printer and get the printer itself set to the right default size as well. Or you might be able to use web browser to URL http://localhost:631/ and change the default settings on the printer through the cups web interface. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora-17 Irritations
On 20/04/12 17:31, Patrick Lists wrote: On 04/20/2012 06:27 PM, Peter Hillier-Brook wrote: 2.I installed an HP printer via the Printers dialogue and I cannot find any way to set paper sizes to A4. Try running system-config-printer Regards, Patrick I'll give it a go. Thanks. Peter HB -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora-17 Irritations
On 04/20/2012 10:51 AM, Peter Hillier-Brook wrote: I take it from your response that you think the issue is specific to a test build and not generic? It's quite possible that it is because if it were, as you phrase it, generic, it probably would have been reported long ago and fixed. And, if so, notifying the test list is the best way to get other people checking it to see if it's a real issue or simply a glitch at your end. (always a possibility) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Problem with Yum to upgrade Fedora 17.
On Fri, 2012-04-20 at 13:42 -0300, Davi Garcia wrote: Hi all, Thanks for all feedback! Sorry about post question to the wrong list and about my poor problem description. Let me try explain better: I never decided to install Samba or Samba4 in my workstation, these packages were installed by default. I know that I'm using F17 that is still in beta, but I didn't know that alpha packages were being pushed to that repository. My problem is basically that Yum is not able to upgrade my system without use --skip-broken. Since Ed Greshko confirmed that is a known issue, I'll wait the fix. What is very confusing is why do we have alpha packages in a beta repo? Again, sorry about any inconvenience. Yes, the problem here is that some samba4 packages were pushed to updates-testing that are marked as Obsoleting or otherwise replacing their samba 3.x counterpart. This is bad, and anyone hitting this issue should be adding negative karma to the update (as I am about to do). signature.asc Description: This is a digitally signed message part -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Problem with Yum to upgrade Fedora 17.
On Fri, 2012-04-20 at 15:34 -0400, Stephen Gallagher wrote: On Fri, 2012-04-20 at 13:42 -0300, Davi Garcia wrote: Hi all, Thanks for all feedback! Sorry about post question to the wrong list and about my poor problem description. Let me try explain better: I never decided to install Samba or Samba4 in my workstation, these packages were installed by default. I know that I'm using F17 that is still in beta, but I didn't know that alpha packages were being pushed to that repository. My problem is basically that Yum is not able to upgrade my system without use --skip-broken. Since Ed Greshko confirmed that is a known issue, I'll wait the fix. What is very confusing is why do we have alpha packages in a beta repo? Again, sorry about any inconvenience. Yes, the problem here is that some samba4 packages were pushed to updates-testing that are marked as Obsoleting or otherwise replacing their samba 3.x counterpart. This is bad, and anyone hitting this issue should be adding negative karma to the update (as I am about to do). Replying to myself, I see that a fixed package is already built and is pending the next push to the updates-testing repository. Relevant BZ: https://bugzilla.redhat.com/show_bug.cgi?id=814451 signature.asc Description: This is a digitally signed message part -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: ath9k with hostapd and iPad / iPhone
Am 20.04.2012 22:08, schrieb Heinz Diehl: On 20.04.2012, Reindl Harald wrote: has somebody magic settings to get Apple mobile-crap working with hostapd instead permanently interrupt the connection? Ath9k and interrupted connections? Kernel 3.3.1 (vanilla) has a bug which can cause this, see: http://www.spinics.net/lists/linux-wireless/msg88228.html This is fixed in 3.3.2 and above. not generally, only Aple Devices (iPhone / iPad) no 3.3.1 - 3.3.2-1.fc16.x86_64 i saw the ath9k changes on kernel.org and hoped this is the reason, but no :-( i wonder that apple-tv and IMac are working fine if it would be my devices or i would be permitted i would throw the apple-devices as far as i can but that is no option :-( signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora-17 Irritations
On Fri, 2012-04-20 at 12:09 -0500, Michael Hennebry wrote: It seems to me that you could have a situation in which libreoffice believes in A4, but the printer still believes in Letter. When I had application/printer mismatch problems, it was usually because the application believed in A4 and the printer in Letter. I used to have that problem, *years* ago. Where my locale *only* uses A4, I'd correctly set the system to my locale, *and* I'd have to set up printer configurations correctly for the paper that I put in the printer. Ideally, setting your locale would set the default page type used where you live, somewhere to the system configuration, and everything else would use that as its defaults (printer configuration, word processors, web browsers, etc.). But *every* damn application would ignore the printer settings and require individually setting to A4. Some applications required constantly resetting, since they seem to take the creation of each new document to need resetting to its own defaults. *And* to make things even worse, each user would require their settings to be customised, or they'd be trying to print to the wrong paper size (which produces all sorts of annoying printing problems). Occasionally I'd hear about the opposite (A4 versus Letter) page sizing from other people, over the years, and wondered: * Had they ever set the locale to their area? (Doing so sets up all manner of parameters that will need to be customised to suit them, languages, punctuation rules, monetary systems, timezones and daylight savings changes, paper sizes, et cetera.) * And, if they had set it, did they do it *before* or *after* messing around trying to set page sizes elsewhere. The other localisation issue that routinely irritated me was having to manually set language parameters in applications, such as spell correctors in word processors, because they'd always default to US English, despite my locale being *not* that. Again, finding it'd often need resetting with new documents. I haven't seen these issues for a long time, thankfully. But, my first inclination is to say - make sure that you properly configure your system before use (set your locale, timezones, languages, all that first run stuff). And if you didn't set such things *first*, try creating a new user, setting its settings up properly, and see if that helps when you try printing as that user. Some of the first-run configurations are system settings (e.g. locale), others per user (e.g. language), and need setting up during the login process (select the user name, select your options, *then* type in the password and hit enter to login). -- [tim@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: system-config-users and ldapi
On 4/19/12 9:16 AM, Craig White wrote: On Wed, 2012-04-18 at 10:37 -0400, Braden McDaniel wrote: On Wed, 2012-04-18 at 06:09 -0700, Craig White wrote: On Mon, 2012-04-16 at 22:03 -0400, Braden McDaniel wrote: Can system-config-users be made to use ldapi (i.e., a socket connection to an LDAP server)? According to man 5 libuser.conf, libuser can do this; but I haven't been able to convince system-config-users. It asks for a SASL user on startup (which shouldn't be applicable, as I understand it). I was under the impression that system-config-users would write directly to /etc/passwd (/etc/shadow, /etc/group) and would not be applicable for use with ldap based users. BTW, I tend to use Webmin and it's LDAP Users and Groups module to manage LDAP users groups. If you set create_modules = ldap in /etc/libuser.conf, system-config-users will prompt for several LDAP authentication settings on startup. I have not gotten it to work, yet, though. There is an old comment in this older bug report suggesting that this worked at some time (in some form): https://bugzilla.redhat.com/show_bug.cgi?id=89539 It may be that it requires authentication to be done via LDAP; and I'm using Kerberos for that. If there was actual intent to use it with ldap users groups, there would be configuration possibilities for the schema(s) used. It's not and never was a suitable tool for the purpose. Do your comments extend to libuser? I'm an utter novice at LDAP; but perhaps this depends upon what one is looking for? Clearly system-config-users is not a versatile tool with respect to the variety of LDAP deployments that are possible. But if one is just looking to set up/manage a centralized user account store on a small network, might it be sufficient? Braden -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora-17 Irritations
On 20/04/12 19:01, Joe Zeff wrote: On 04/20/2012 10:51 AM, Peter Hillier-Brook wrote: I take it from your response that you think the issue is specific to a test build and not generic? It's quite possible that it is because if it were, as you phrase it, generic, it probably would have been reported long ago and fixed. And, if so, notifying the test list is the best way to get other people checking it to see if it's a real issue or simply a glitch at your end. (always a possibility) More a probability than a possibility.:-) Thanks for the information. Peter HB -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
ifcfg-ethX voodoo for a second IP on the same interface
For testing purposes I need to add a second IP address to eth0. eth0 is managed by NetworkManager, and uses dhcp. I know that if I get rid of NetworkManager and put static IP addresses in ifcfg-eth0, I can also sprinkle some magic dust into ifcfg-eth0:1, and have the second IP address come up together with the first one. This does not seem to work with a NetworkManager-managed DHCP-based interface. Basically, is there some voodoo I can throw in a file somewhere that would perform the equivalent of: ip addr add 192.168.0.5 dev eth0 label eth0:1 when eth0 comes up via DHCP, by NetworkManager? pgpqOviSdi2pr.pgp Description: PGP signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: ifcfg-ethX voodoo for a second IP on the same interface
On Fri, Apr 20, 2012 at 8:20 PM, Sam Varshavchik mr...@courier-mta.com wrote: For testing purposes I need to add a second IP address to eth0. eth0 is managed by NetworkManager, and uses dhcp. I know that if I get rid of NetworkManager and put static IP addresses in ifcfg-eth0, I can also sprinkle some magic dust into ifcfg-eth0:1, and have the second IP address come up together with the first one. This does not seem to work with a NetworkManager-managed DHCP-based interface. Basically, is there some voodoo I can throw in a file somewhere that would perform the equivalent of: ip addr add 192.168.0.5 dev eth0 label eth0:1 when eth0 comes up via DHCP, by NetworkManager? How about: #file ifcfg-eth0 #UUID #HWADDR #device ONBOOT=yes BOOTPROTO=dhcp NM_CONTROLLED=yes #file ifcfg-eth0:1 #UUID #HWADDR #device ONBOOT=yes BOOTPROTO=none NM_CONTROLLED=no # static IP settings... -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: ifcfg-ethX voodoo for a second IP on the same interface
On 04/21/2012 11:20 AM, Sam Varshavchik wrote: For testing purposes I need to add a second IP address to eth0. eth0 is managed by NetworkManager, and uses dhcp. I know that if I get rid of NetworkManager and put static IP addresses in ifcfg-eth0, I can also sprinkle some magic dust into ifcfg-eth0:1, and have the second IP address come up together with the first one. This does not seem to work with a NetworkManager-managed DHCP-based interface. Basically, is there some voodoo I can throw in a file somewhere that would perform the equivalent of: ip addr add 192.168.0.5 dev eth0 label eth0:1 when eth0 comes up via DHCP, by NetworkManager? Well. I think you can only do this with static IP addresses But, all you have to do is modify /etc/sysconfig/network-scripts/ifcfg-whatever to have IPADDR0=192.168.0.225 IPADDR1=192.168.0.226 for example Then you'd see... 2: p2p1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 08:00:27:36:bf:b0 brd ff:ff:ff:ff:ff:ff inet 192.168.0.225/24 brd 192.168.0.255 scope global p2p1 inet 192.168.0.226/24 brd 192.168.0.255 scope global secondary p2p1 inet6 fe80::a00:27ff:fe36:bfb0/64 scope link valid_lft forever preferred_lft foreve -- Never be afraid to laugh at yourself, after all, you could be missing out on the joke of the century. -- Dame Edna Everage -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: ifcfg-ethX voodoo for a second IP on the same interface
On Fri, Apr 20, 2012 at 9:34 PM, Ed Greshko ed.gres...@greshko.com wrote: On 04/21/2012 11:20 AM, Sam Varshavchik wrote: For testing purposes I need to add a second IP address to eth0. eth0 is managed by NetworkManager, and uses dhcp. I know that if I get rid of NetworkManager and put static IP addresses in ifcfg-eth0, I can also sprinkle some magic dust into ifcfg-eth0:1, and have the second IP address come up together with the first one. This does not seem to work with a NetworkManager-managed DHCP-based interface. Basically, is there some voodoo I can throw in a file somewhere that would perform the equivalent of: ip addr add 192.168.0.5 dev eth0 label eth0:1 when eth0 comes up via DHCP, by NetworkManager? Well. I think you can only do this with static IP addresses But, all you have to do is modify /etc/sysconfig/network-scripts/ifcfg-whatever to have IPADDR0=192.168.0.225 IPADDR1=192.168.0.226 for example Then you'd see... 2: p2p1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 08:00:27:36:bf:b0 brd ff:ff:ff:ff:ff:ff inet 192.168.0.225/24 brd 192.168.0.255 scope global p2p1 inet 192.168.0.226/24 brd 192.168.0.255 scope global secondary p2p1 inet6 fe80::a00:27ff:fe36:bfb0/64 scope link valid_lft forever preferred_lft foreve -- Never be afraid to laugh at yourself, after all, you could be missing out on the joke of the century. -- Dame Edna Everage Then the documentation [1] is either wrong or did I completely read it wrong? [1] http://docs.fedoraproject.org/en-US/Fedora/16/html/System_Administrators_Guide/s2-networkscripts-interfaces-alias.html -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: ifcfg-ethX voodoo for a second IP on the same interface
On 04/21/2012 12:55 PM, Tommy Pham wrote: On Fri, Apr 20, 2012 at 9:34 PM, Ed Greshko ed.gres...@greshko.com wrote: On 04/21/2012 11:20 AM, Sam Varshavchik wrote: For testing purposes I need to add a second IP address to eth0. eth0 is managed by NetworkManager, and uses dhcp. I know that if I get rid of NetworkManager and put static IP addresses in ifcfg-eth0, I can also sprinkle some magic dust into ifcfg-eth0:1, and have the second IP address come up together with the first one. This does not seem to work with a NetworkManager-managed DHCP-based interface. Basically, is there some voodoo I can throw in a file somewhere that would perform the equivalent of: ip addr add 192.168.0.5 dev eth0 label eth0:1 when eth0 comes up via DHCP, by NetworkManager? Well. I think you can only do this with static IP addresses But, all you have to do is modify /etc/sysconfig/network-scripts/ifcfg-whatever to have IPADDR0=192.168.0.225 IPADDR1=192.168.0.226 for example Then you'd see... 2: p2p1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 08:00:27:36:bf:b0 brd ff:ff:ff:ff:ff:ff inet 192.168.0.225/24 brd 192.168.0.255 scope global p2p1 inet 192.168.0.226/24 brd 192.168.0.255 scope global secondary p2p1 inet6 fe80::a00:27ff:fe36:bfb0/64 scope link valid_lft forever preferred_lft foreve -- Never be afraid to laugh at yourself, after all, you could be missing out on the joke of the century. -- Dame Edna Everage Then the documentation [1] is either wrong or did I completely read it wrong? [1] http://docs.fedoraproject.org/en-US/Fedora/16/html/System_Administrators_Guide/s2-networkscripts-interfaces-alias.html I didn't read the documentation :-) I think that method is how to do it when NetworkManager isn't being used. What I was describing was if you were using NetworkManager. One downside if using my method is that ifconfig won't show the second IP address. But since Ifconfig has been depreciated :-) :-) In any case, these configuration won't work when DHCP is desired. -- Never be afraid to laugh at yourself, after all, you could be missing out on the joke of the century. -- Dame Edna Everage -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: ifcfg-ethX voodoo for a second IP on the same interface
On Fri, Apr 20, 2012 at 10:05 PM, Ed Greshko ed.gres...@greshko.com wrote: On 04/21/2012 12:55 PM, Tommy Pham wrote: On Fri, Apr 20, 2012 at 9:34 PM, Ed Greshko ed.gres...@greshko.com wrote: On 04/21/2012 11:20 AM, Sam Varshavchik wrote: For testing purposes I need to add a second IP address to eth0. eth0 is managed by NetworkManager, and uses dhcp. I know that if I get rid of NetworkManager and put static IP addresses in ifcfg-eth0, I can also sprinkle some magic dust into ifcfg-eth0:1, and have the second IP address come up together with the first one. This does not seem to work with a NetworkManager-managed DHCP-based interface. Basically, is there some voodoo I can throw in a file somewhere that would perform the equivalent of: ip addr add 192.168.0.5 dev eth0 label eth0:1 when eth0 comes up via DHCP, by NetworkManager? Well. I think you can only do this with static IP addresses But, all you have to do is modify /etc/sysconfig/network-scripts/ifcfg-whatever to have IPADDR0=192.168.0.225 IPADDR1=192.168.0.226 for example Then you'd see... 2: p2p1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 08:00:27:36:bf:b0 brd ff:ff:ff:ff:ff:ff inet 192.168.0.225/24 brd 192.168.0.255 scope global p2p1 inet 192.168.0.226/24 brd 192.168.0.255 scope global secondary p2p1 inet6 fe80::a00:27ff:fe36:bfb0/64 scope link valid_lft forever preferred_lft foreve -- Never be afraid to laugh at yourself, after all, you could be missing out on the joke of the century. -- Dame Edna Everage Then the documentation [1] is either wrong or did I completely read it wrong? [1] http://docs.fedoraproject.org/en-US/Fedora/16/html/System_Administrators_Guide/s2-networkscripts-interfaces-alias.html I didn't read the documentation :-) I think that method is how to do it when NetworkManager isn't being used. What I was describing was if you were using NetworkManager. One downside if using my method is that ifconfig won't show the second IP address. But since Ifconfig has been depreciated :-) :-) In any case, these configuration won't work when DHCP is desired. -- Never be afraid to laugh at yourself, after all, you could be missing out on the joke of the century. -- Dame Edna Everage -- You're right about the doc and NetworkManager... I had to set it to no and bring down the service to make it work... But then I'm using F17 beta so maybe NM is broken??? [root@fedora network-scripts]# ls ifcfg-p14* ifcfg-p14p1 ifcfg-p14p1:1 [root@fedora network-scripts]# cat ifcfg-p14* UUID=d55f8a84-7d34-48a7-9183-de122db1d244 NM_CONTROLLED=no HWADDR=**:**:**:**:**:** BOOTPROTO=dhcp DEVICE=p14p1 ONBOOT=yes #UUID=d55f8a84-7d34-48a7-9183-de122db1d244 NM_CONTROLLED=no BOOTPROTO=none DEVICE=p14p1:1 ONBOOT=yes USERCTL=yes #TYPE=Ethernet IPADDR=192.168.0.11 NETMASK=255.255.255.0 #PREFIX=24 #DEFROUTE=yes IPV4_FAILURE_FATAL=no #IPV6INIT=no NAME=System p14p1:1 UUID=3b279e0d-a2fe-82a3-d15e-6b6fa922d797 p14p1: flags=4163UP,BROADCAST,RUNNING,MULTICAST mtu 1500 inet 192.168.0.241 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::52e5:49ff:fe4e:e55a prefixlen 64 scopeid 0x20link ether **:**:**:**:**:** txqueuelen 1000 (Ethernet) RX packets 684 bytes 145345 (141.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 703 bytes 88987 (86.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 52 base 0x2000 p14p1:1: flags=4163UP,BROADCAST,RUNNING,MULTICAST mtu 1500 inet 192.168.0.11 netmask 255.255.255.0 broadcast 192.168.0.255 ether **:**:**:**:**:** txqueuelen 1000 (Ethernet) device interrupt 52 base 0x2000 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: ifcfg-ethX voodoo for a second IP on the same interface
On Fri, Apr 20, 2012 at 10:30 PM, Tommy Pham tommy...@gmail.com wrote: On Fri, Apr 20, 2012 at 10:05 PM, Ed Greshko ed.gres...@greshko.com wrote: On 04/21/2012 12:55 PM, Tommy Pham wrote: On Fri, Apr 20, 2012 at 9:34 PM, Ed Greshko ed.gres...@greshko.com wrote: On 04/21/2012 11:20 AM, Sam Varshavchik wrote: For testing purposes I need to add a second IP address to eth0. eth0 is managed by NetworkManager, and uses dhcp. I know that if I get rid of NetworkManager and put static IP addresses in ifcfg-eth0, I can also sprinkle some magic dust into ifcfg-eth0:1, and have the second IP address come up together with the first one. This does not seem to work with a NetworkManager-managed DHCP-based interface. Basically, is there some voodoo I can throw in a file somewhere that would perform the equivalent of: ip addr add 192.168.0.5 dev eth0 label eth0:1 when eth0 comes up via DHCP, by NetworkManager? Well. I think you can only do this with static IP addresses But, all you have to do is modify /etc/sysconfig/network-scripts/ifcfg-whatever to have IPADDR0=192.168.0.225 IPADDR1=192.168.0.226 for example Then you'd see... 2: p2p1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 08:00:27:36:bf:b0 brd ff:ff:ff:ff:ff:ff inet 192.168.0.225/24 brd 192.168.0.255 scope global p2p1 inet 192.168.0.226/24 brd 192.168.0.255 scope global secondary p2p1 inet6 fe80::a00:27ff:fe36:bfb0/64 scope link valid_lft forever preferred_lft foreve -- Never be afraid to laugh at yourself, after all, you could be missing out on the joke of the century. -- Dame Edna Everage Then the documentation [1] is either wrong or did I completely read it wrong? [1] http://docs.fedoraproject.org/en-US/Fedora/16/html/System_Administrators_Guide/s2-networkscripts-interfaces-alias.html I didn't read the documentation :-) I think that method is how to do it when NetworkManager isn't being used. What I was describing was if you were using NetworkManager. One downside if using my method is that ifconfig won't show the second IP address. But since Ifconfig has been depreciated :-) :-) In any case, these configuration won't work when DHCP is desired. -- Never be afraid to laugh at yourself, after all, you could be missing out on the joke of the century. -- Dame Edna Everage -- You're right about the doc and NetworkManager... I had to set it to no and bring down the service to make it work... But then I'm using F17 beta so maybe NM is broken??? [root@fedora network-scripts]# ls ifcfg-p14* ifcfg-p14p1 ifcfg-p14p1:1 [root@fedora network-scripts]# cat ifcfg-p14* UUID=d55f8a84-7d34-48a7-9183-de122db1d244 NM_CONTROLLED=no HWADDR=**:**:**:**:**:** BOOTPROTO=dhcp DEVICE=p14p1 ONBOOT=yes #UUID=d55f8a84-7d34-48a7-9183-de122db1d244 NM_CONTROLLED=no BOOTPROTO=none DEVICE=p14p1:1 ONBOOT=yes USERCTL=yes #TYPE=Ethernet IPADDR=192.168.0.11 NETMASK=255.255.255.0 #PREFIX=24 #DEFROUTE=yes IPV4_FAILURE_FATAL=no #IPV6INIT=no NAME=System p14p1:1 UUID=3b279e0d-a2fe-82a3-d15e-6b6fa922d797 p14p1: flags=4163UP,BROADCAST,RUNNING,MULTICAST mtu 1500 inet 192.168.0.241 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::52e5:49ff:fe4e:e55a prefixlen 64 scopeid 0x20link ether **:**:**:**:**:** txqueuelen 1000 (Ethernet) RX packets 684 bytes 145345 (141.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 703 bytes 88987 (86.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 52 base 0x2000 p14p1:1: flags=4163UP,BROADCAST,RUNNING,MULTICAST mtu 1500 inet 192.168.0.11 netmask 255.255.255.0 broadcast 192.168.0.255 ether **:**:**:**:**:** txqueuelen 1000 (Ethernet) device interrupt 52 base 0x2000 but this last line from the doc... The easiest way to create alias and clone interface configuration files is to use the graphical Network Administration Tool. Perhaps network is not running and let NM take over? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: ifcfg-ethX voodoo for a second IP on the same interface
On 04/21/2012 01:30 PM, Tommy Pham wrote: You're right about the doc and NetworkManager... I had to set it to no and bring down the service to make it work... But then I'm using F17 beta so maybe NM is broken??? [root@fedora network-scripts]# ls ifcfg-p14* ifcfg-p14p1 ifcfg-p14p1:1 [root@fedora network-scripts]# cat ifcfg-p14* UUID=d55f8a84-7d34-48a7-9183-de122db1d244 NM_CONTROLLED=no HWADDR=**:**:**:**:**:** BOOTPROTO=dhcp DEVICE=p14p1 ONBOOT=yes #UUID=d55f8a84-7d34-48a7-9183-de122db1d244 NM_CONTROLLED=no BOOTPROTO=none DEVICE=p14p1:1 ONBOOT=yes USERCTL=yes #TYPE=Ethernet IPADDR=192.168.0.11 NETMASK=255.255.255.0 #PREFIX=24 #DEFROUTE=yes IPV4_FAILURE_FATAL=no #IPV6INIT=no NAME=System p14p1:1 UUID=3b279e0d-a2fe-82a3-d15e-6b6fa922d797 p14p1: flags=4163UP,BROADCAST,RUNNING,MULTICAST mtu 1500 inet 192.168.0.241 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::52e5:49ff:fe4e:e55a prefixlen 64 scopeid 0x20link ether **:**:**:**:**:** txqueuelen 1000 (Ethernet) RX packets 684 bytes 145345 (141.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 703 bytes 88987 (86.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 52 base 0x2000 p14p1:1: flags=4163UP,BROADCAST,RUNNING,MULTICAST mtu 1500 inet 192.168.0.11 netmask 255.255.255.0 broadcast 192.168.0.255 ether **:**:**:**:**:** txqueuelen 1000 (Ethernet) device interrupt 52 base 0x2000 Well, I tested what I did with F17-Beta [egreshko@f17-beta network-scripts]$ cat ifcfg-p2p1 UUID=9f5509c3-6982-4f52-8204-aabcd69985c9 NM_CONTROLLED=yes BOOTPROTO=none DEVICE=p2p1 ONBOOT=yes TYPE=Ethernet DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=no NAME=System p2p1 HWADDR=08:00:27:36:BF:B0 IPADDR0=192.168.0.225 IPADDR1=192.168.0.226 PREFIX0=24 GATEWAY0=192.168.0.1 DNS1=192.168.0.55 But, of course, ifconfig shows this p2p1: flags=4163UP,BROADCAST,RUNNING,MULTICAST mtu 1500 inet 192.168.0.225 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::a00:27ff:fe36:bfb0 prefixlen 64 scopeid 0x20link ether 08:00:27:36:bf:b0 txqueuelen 1000 (Ethernet) RX packets 4969 bytes 403735 (394.2 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 692 bytes 81289 (79.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 and ip shows this p2p1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 08:00:27:36:bf:b0 brd ff:ff:ff:ff:ff:ff inet 192.168.0.225/24 brd 192.168.0.255 scope global p2p1 inet 192.168.0.226/24 brd 192.168.0.255 scope global secondary p2p1 inet6 fe80::a00:27ff:fe36:bfb0/64 scope link valid_lft forever preferred_lft forever So, 2 ways to achieve the goal of multiple IP addresses on a single NIC. -- Never be afraid to laugh at yourself, after all, you could be missing out on the joke of the century. -- Dame Edna Everage -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: ifcfg-ethX voodoo for a second IP on the same interface
On 04/21/2012 01:41 PM, Ed Greshko wrote: You're right about the doc and NetworkManager... I had to set it to no and bring down the service to make it work... But then I'm using F17 beta so maybe NM is broken??? No, AFAIK, NM won't handle that type of configuration. You either do it the way you did, without NM. Or, you do it the way I did, with NM. The other downside is that the NM GUI (at least on KDE) doesn't allow for adding a second IP address. Needs to be done manually. -- Never be afraid to laugh at yourself, after all, you could be missing out on the joke of the century. -- Dame Edna Everage -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
