May 2015 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Configuring DHCP client on Opensuse. Which one -- dhcpcd, dhclient or wicked?
by robert.devanna＠nospammail.net 27 May '15

27 May '15

I'm setting up a DHCP client on Opensuse. I'm coming from Debian; apparently things are done differently here in Opensuse. My very-techie friend also from Debian has given up trying to help me with figuring this out on Opensuse :-( This box is being set up as an edge router+firewall. It connects directly to an ISP's DSL modem - an AT&T Uverse-compatible Pace 5031NV. Iiuc, on Opensuse there are 3 different clients -- dhcpcd, dhclient & wicked. I don't know much of anything about 'wicked' yet. From reading in the docs https://www.suse.com/documentation/sles-12/book_sle_admin/data/sec_basicnet… and a bunch of posts scattered acorss the mailing lists and bug reports it sounds like wicked is the right way going forward @ opensuse and that dhcpcd and dhclient are going away eventually. I really want to understand how to do this manually if I have to and am uncomfortable with 'fuzzy' configs scattered all over the place. 'Everybody' just keeps saying "use yast" to configure but won't answer the question *which* dhcp client is used in that case and where the config goes. The docs seems to bounce between using the old /etc/sysconfig/network/* configs and the new /etc/wicked/* configs. My questions for starters are (A) Is it true that on opensuse going forward wicked is the right way to configure network connections, and that all of its configs go into /etc/wicked/*? (B) Is there any documentation that gives an EXAMPLE of a working /etc/wicked/*-only config for connecting a server to an ISP's modem using DHCP? I'm not looking for an encyclopedia of options, there's already too much of that causing me confusion. I'm looking for a working, practical example I can start with and learn from. Cheers, Bob -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 18

[opensuse] Recent bind 9 - DNS error (FORMERR) resolving 'dns4.registrar-servers.com/AAAA/IN'
by David C. Rankin 27 May '15

27 May '15

All, I have had a rash of DNS errors logged recently through bind 9. The errors are like: May 26 16:44:24 nirvana named[23136]: DNS format error from 208.67.222.222#53 resolving dns3.registrar-servers.com/AAAA: invalid response May 26 16:44:24 nirvana named[23136]: error (FORMERR) resolving 'dns3.registrar-servers.com/AAAA/IN': 208.67.222.222#53 May 26 16:44:24 nirvana named[23136]: DNS format error from 208.67.222.222#53 resolving dns4.registrar-servers.com/AAAA: invalid response May 26 16:44:24 nirvana named[23136]: error (FORMERR) resolving 'dns4.registrar-servers.com/AAAA/IN': 208.67.222.222#53 May 26 16:44:24 nirvana named[23136]: DNS format error from 208.67.222.222#53 resolving dns2.registrar-servers.com/AAAA: invalid response May 26 16:44:24 nirvana named[23136]: error (FORMERR) resolving 'dns2.registrar-servers.com/AAAA/IN': 208.67.222.222#53 May 26 16:44:24 nirvana named[23136]: DNS format error from 208.67.220.220#53 resolving dns3.registrar-servers.com/AAAA: invalid response May 26 16:44:24 nirvana named[23136]: error (FORMERR) resolving 'dns3.registrar-servers.com/AAAA/IN': 208.67.220.220#53 May 26 16:44:24 nirvana named[23136]: DNS format error from 208.67.220.220#53 resolving dns4.registrar-servers.com/AAAA: invalid response May 26 16:44:24 nirvana named[23136]: error (FORMERR) resolving 'dns4.registrar-servers.com/AAAA/IN': 208.67.220.220#53 May 26 16:44:24 nirvana named[23136]: DNS format error from 208.67.220.220#53 resolving dns2.registrar-servers.com/AAAA: invalid response May 26 16:44:24 nirvana named[23136]: error (FORMERR) resolving 'dns2.registrar-servers.com/AAAA/IN': 208.67.220.220#53 I have run bind for the better part of 15 years and haven't seen this frequency of errors until the last few weeks. Anybody else notice this or have any ideas on the cause? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

Re: [opensuse] failed installation, system inaccessible
by Carlos E. R. 27 May '15

27 May '15

On 2015-05-26 22:00, davidousley(a)verizon.net wrote: > Thanks for your help. I have installed 13.2 to a new root partition. > There is also a separate and new boot partition. Installation completes > and system reboots. > Reboothangs however with message that the swap partition (identified as > /dev/mapper/pdc...) does not exist. It leaves me at a Dracut prompt. The > rdosreport.txt file it mentions is empty. > > Booting recovery mode produces recurring lines : > > sdc: sdc1 sdc2 ( sdc5 sdc6 sdc7 sdc8) > and same for sdb. These are the disks where swap and /home are located. > > I am sending this from my phone and hope it will be plain text and not > top posted. Neither :-p > Sent from my HTC So it did not arrive at the list. I'm replying with your full text so that others can see it and participate. I would edit fstab and comment out the swap line. Then boot, to text mode perhaps, and find out if the line was correct or not, and correct it or find why the swap definition failed. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

4 5

[opensuse] How to build a "caching only" local repository for use by many machines on my LAN?
by arvindg＠emailuser.net 26 May '15

26 May '15

Hi I have a bunch of opensuse machines on a lan. They're all the same version of opensuse (13.2), all the same arch (x86_64), and all use the same set of repos (in /etc/zypp/repos.d). I update them all regularly. They all have a common core set of installed packages, and each machine has additional (groups of) pacakges unique to its user and usage. When updating, I can either (1) update them all individually, each machine pulling its pkgs from the repo mirrors or (2) rsync all the full source repos to a single instance on the lan, and update the clients from the local collection Each has its drawbacks: (1) leads to a lot of redundant traffic (2) leads to rsync of lots of unneeded packages What I'd LIKE to do instead is set up some sort of caching on the LAN so that when any machine downloads any new or upgraded package, the rpms are FIRST cached to a lan machine that then makes those packages available to other machines as they need it. Since all the machines are pretty similar, and there's always at least a couple of machines that need the same package, this would (1) make sure that I'm not re-downloading the same package over and over (2) prevent rsync/storing packages that are never used at all The question is -- can I do this with zypper, or some other tool? Cheers Arvind -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 11

[opensuse] On Opensuse 13.2, Shorewall firewall's installed, de-installs Susefirewall2, but "Yast2 -Network Settings" complains about it?
by robert.devanna＠nospammail.net 26 May '15

26 May '15

When I open "YaST2 - Network Settings" on Opensuse 13.2 I get a dialog box that says These packages need to be installed: SuSEfirewall2 I don't use or want SuSEfirewall2 to manage my firewall, I use Shorewall instead. With Shorewall installed It doesn't make sense to have other firewall pacakges installed And in the Shorewall rpm spec on the Build system https://build.opensuse.org/package/view_file/openSUSE:13.2/shorewall/shorew… 84 %if 0%{?suse_version} 85 Conflicts: SuSEfirewall2%endif 86 %endif And after an install of shorewall I get only these packages installed rpm -qa | egrep -i "susefirewall|shorewall" | sort shorewall-4.6.9-183.1.noarch shorewall6-4.6.9-183.1.noarch shorewall6-lite-4.6.9-183.1.noarch shorewall-core-4.6.9-183.1.noarch shorewall-docs-4.6.9-183.1.noarch shorewall-init-4.6.9-183.1.noarch shorewall-lite-4.6.9-183.1.noarch So I don't know why the YaST2 app complains about the missing Susefirewall app. The warning https://build.opensuse.org/package/view_file/openSUSE:13.2/shorewall/README… WARNING ======== Some openSUSE packages include a service file for ease of the SuSEfirewall2 configuration and opening the necessary ports. You have to open the required ports yourself using the Shorewall configuration files. SuSEfirewall2 is integrated with Yast so configuration can be done via a GUI. This is not the case for Shorewall. Enabling Firewall in /etc/sysconfig/network/config or in individual ifcfg-xxx files is not enough. /etc/sysconfig/shorewall should be configured. implies that you have to "do something" to make YaST2 happy. How do you install Shorewall AND have the system accept and use it without any errors? Cheers, Bob -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 18

[opensuse] Re: Time Clock solution
by Linda Walsh 25 May '15

25 May '15

Michael Dunsavage wrote: > On Sat, May 23, 2015 at 8:46 PM, Linda Walsh <suse(a)tlinx.org> wrote: >> Michael Dunsavage wrote: >>> Hi. I'm looking for a time clock solution, preferably not web based. >>> But preferably gui and networkable. >>> >> xclock? >> (you aren't very specific on what you want...) > > No. A time clock. Where people punch in and out > Are they called something else? --- suggest "time punch clock"? goog/sourceforge? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 6

[opensuse] wired to wifi
by buhorojo 25 May '15

25 May '15

Hi We have a wired connection to each room (dating to 2003). I want a cheap way to go wireless from that. This works using old stuff: wall to up on switch switch to existing computer 172.16.. switch to wifi router 172.16.. to 192.168.1. 2 boxes and a mess of cables. Total cost, about €30 per room tested on a mix of devices. We've tested it with 20 or so of us doing random stuff. Only problem: Getting our existing files. Looking at windows explorer on the existing wired computer we can see the files at \\172.16.5.105\estudiantes One unusual feature is that to get that unc, we have to mask 255.255.255.0. Before the route, we can see them at: smb://172.16.5.105/estudiantes On wifi, smb:// always asks us for a username and password. None of our passwords work. So 2 questions: 1. Any advance on €30 per room, preferably on 1 box. The existing computer has to remain. We are not allowed to alter that. 2. The smb:// rubbish. We may be able to have access to the file server or will get it if we can get specific help. But please, no general advice on how or how not to do networks. Thanks. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

14 131

[opensuse] Time Clock solution
by Michael Dunsavage 24 May '15

24 May '15

Hi. I'm looking for a time clock solution, preferably not web based. But preferably gui and networkable. Does any or has any one used such a beast? Thanks. -- Michael Dunsavage Please excuse any typos or brevity. This message may have been sent via my mobile device. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 3

[opensuse] upgrade help
by Fr David Ousley 22 May '15

22 May '15

I'd like to upgrade from 12.3 to 13.2. I was assuming a clean install, but I would like to retain my current /home partition rather than have to restore everything from backups. I cannot do an upgrade to 13.1 or 13.2 because the /boot partition is too small. The hard drive does not have unallocated space on it; /boot is next to /swap. What I think I'd like to do is to shrink or wipe the Windows partition on the SSD (almost never boot into Windows) and put the boot partition there, keeping the other partitions on the hard drives (RAID, mirrored). But I don't know how to do this. The Yast partitioner gags when trying to resize the NTFS partition on the SSD. The 13.2 installer will do so, but only to install the / partition on the SSD, which (if I understand its proposal) would put everything including /home on the SSD. How do I get from here to there? Or is there a better solution? (Or have I omitted some crucial piece of information?) (I've been using Unix & Linux for 25 years, but as an end user -- I don't do a lot of sysadmin stuff.) Thanks for your help! Fr Ousley -- Church of St Michael the Archangel Fr David Ousley 6611 Ardleigh Street Philadelphia, PA 19119 215-247-1092 ordinariatephiladelphia.org newmanfellowship.org dao(a)anglicanphiladelphia.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 5

[opensuse] Mix NewtorkManager and traditional ethernet configuration
by Roger Oberholtzer 22 May '15

22 May '15

Would there be any real technical reasons to not allow both the traditional method of setting up Ethernet devices and NetworkManager at the same time? More specifically, I would like to have some Ethernet devices set up the traditional way (meaning they come up when the system boots and are only modifiable by root), and others that can be managed by the user, like NetworkManager allows. Why? We have a system that collects data from lots of Ethernet-based transducers. These are really rather static. The user is not expected to change them. In fact, they are really discouraged from mucking about with them. At the same time, there may be other interfaces that could be more flexible. Like a wifi device. Or a USB-tethered telephone. These devices are really managed quite well by NetworkManager. A while back I posted about not getting udev to do as I wanted. I don't see, for example, how to let the user select which wireless access point to connect to and how to let them set things like the password. Network Manager does this well. A per-interface flag to say how it is managed? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 3