I just install openSuse13.1 in my environment and I found the issue. Whenever I am connecting OpeneSuse13.1 machine to network, my DHCP server which is setup on another CentOS machines stops working. It keeps rejecting the every IP. I checked DHCP service on OpeneSuse its not running.
Also, when I am disconnection OpenSuse machine from network still its pinging to the network machine.
What configuration do I supposed to do after installing OpenSuse.
If you are using NetworkManager, then Yast will tell you that and will tell you that you cannot change network settings without first turning of NetworkManager. If you are not using NetworkManager, it will allow you to make changes.
If you are not using NetworkManager, then I suggest that you try it. While you still have that Yast module open, click the “Global Options” tab, and select “User Controlled with NetworkManager”.
The reason I suggest that, is because NetworkManager uses a different DHCP client, and that might solve your problem. If that works, post back and I’ll describe how to swich DHCP clients with “ifup” mode (in case you still prefer to use that).
I’m not sure what you are saying there. Can you give a bit more detail?
Hey thanks Nrickert, this worked me for network issue.
No I am facing ssh issue. I am not able to do ssh to this machine. Also could you please let me know the commands through which I can install packages as we install in CentOS using rpm and yum.
Now I am facing ssh issue. I am not able to do ssh to this machine. Also could you please let me know the commands through which I can install packages as we install in CentOS using rpm and yum.
Are you familiar with configuring SSH? There used to be a YaST utility for this, but now you must configure it manually. Assuming you know that and have the sshd service configured and running, then maybe it is a firewall issue? You can configure the firewall to allow ‘Secure Shell Server’.
I configured the LDAP client on it but still I am having issue for authentication.
opensuse:~ # ssh yogesh@192.168.181.36 -v
OpenSSH_6.2p2, OpenSSL 1.0.1e 11 Feb 2013
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 20: Applying options for *
debug1: Connecting to 192.168.181.36 [192.168.181.36] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /root/.ssh/id_rsa type -1
debug1: identity file /root/.ssh/id_rsa-cert type -1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: identity file /root/.ssh/id_dsa-cert type -1
debug1: identity file /root/.ssh/id_ecdsa type -1
debug1: identity file /root/.ssh/id_ecdsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.2
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.2
debug1: match: OpenSSH_6.2 pat OpenSSH*
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5-etm@openssh.com none
debug1: kex: client->server aes128-ctr hmac-md5-etm@openssh.com none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ECDSA 40:09:1f:8c:c1:a4:d3:4c:ef:56:bb:21:66:d9:d1:94
debug1: Host ‘192.168.181.36’ is known and matches the ECDSA host key.
debug1: Found key in /root/.ssh/known_hosts:5
debug1: ssh_ecdsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /root/.ssh/id_rsa
debug1: Trying private key: /root/.ssh/id_dsa
debug1: Trying private key: /root/.ssh/id_ecdsa
debug1: Next authentication method: keyboard-interactive
Password:
debug1: Authentications that can continue: publickey,keyboard-interactive
Password:
debug1: Authentications that can continue: publickey,keyboard-interactive
Password:
debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: No more authentication methods to try.
Permission denied (publickey,keyboard-interactive).
opensuse:~ #
Could you please let me know how can I change authentication to LDAP.
As I’m reading through this thread,
I seem to see a common problem for every issue encountered.
yogesh,
You should take a look at YAST.
It’s unique to openSUSE (not found on any other distro) and it contains applets which can install and automatically configure many of the tasks you’re trying to do manually.
Try it first!
You’ll likely have far more success with far less error and effort…
So, specifically… all you asked can be done from within YAST although can also be done from the CLI (eg zypper and rpm)
Software updates, installation, repositories
Network Device and Services
Firewall configuration
LDAP client installation and configuration
I don’t want to create new thread because it will have very same name So I have a problem with network…
After configuring network for static IP - there is all working fine, but after restart there is no network… Starting Yast again shows that subnet mask is changed from “255.255.255.0” to “/24”. So after changing it back to 255.255.255.0 there’s network again. And that is how every time after rebooting! :sarcastic:
My GW is set correctly (192.168.0.1)- if it would not be so, there would not be network at all - nor before restart nor after. But how changing DNS server to another will help me save subnet mask setting after rebooting? (I’ve added third DNS 8.8.8.8 and of course it not helped) DNS has another purpose by the way - with incorrect address I’ll not have WEB. Is your post some sort of joke? :\
The two ways you describe the subnet mask should be equivalent.
But,
Are you reading the changed subnet mask by stdout (eg ip addr or ifconfig) or in YAST or the actual /etc/sysconfig/network/xxxx file?
As I described earlier, nowadays (not just openSUSE) the actual files are semi auto-generated, so I highly recommend you “go with the flow” and manage/configure settings a recommended way instead of digging directly into the configuration files (which as you’re discovering can be over-written again at some future time).
Without knowing <all> you’ve done, I can’t guess what you have done that’s causing the problem… I only know if you had used YAST from the beginning you likely wouldn’t be experiencing your problems (I currently have 4 “minimal server” 13.1 configured through YAST and networking is working as expected).
Hi!
I’m using SuSE since 9.3 version and have used Yast all the time. I’m using my router for 4-5 years already, and all the setting were always the same and it worked like a charm. But as I know in opensuse 13.1 yast is fully rewritten - so I guess some bug are in
I’ve done some testing - and it looks like problem is not in GW setting… Looks like network interfaces are not starting at boot time(!!!), but only after I start Network Settings and do some changes! That is why it looked like not saving network settings before rebooting! But in Yast there is option “Start on booting” set! Soooo - new Yast is not good Yast! :\
I doubt that this was a Yast problem. I suspect that it was a “dhcpcd” problem.
When using “ifup” settings, the default is to use “dhcpcd” for getting the IP address and other parameters. If you use “NetworkManager”, then “dhclient” is used instead. It is also possible, when using “ifup” to switch to “dhclient” (via Yast sysconfig editor).
Over the years, I have seen problems with “dhcpcd”. I recall a report, several years ago, that it crashed some DHCP servers. I had a problem on my work computer, where it would fail to extend the DHCP lease, so would reset the connect then get a fresh lease. I’ve had problems when testing “ifup” on a laptop, with several WiFi networks. If I reconfigured (using Yast) to a different network, it would connect. But “dhcpcd” would remember the balance of the lease from the previous connection, leaving me with an IP address that was wrong for the network where I had connected. The solution to all of these problems was to switch to “dhclient”.
When, in my first reply in this thread, I suggested switching to “NetworkManager”, that was intended as an easy way to switch from “dhcpcd” to “dhclient”. And it seems to have worked.
Yesterday there was a bug report comment, that “dhcpcd” will be dropped from the distro. I am glad to see this change, which I presume will be for opensuse 13.2.
Yesterday there was a bug report comment, that “dhcpcd” will be dropped from the distro. I am glad to see this change, which I presume will be for opensuse 13.2.
So I have a problem with network…