On Mon, 31 Jul 2017 13:14:31 +0200, Carlos E. R. wrote:
On 2017-07-31 12:39, Istvan Gabor wrote:
On Mon, 31 Jul 2017 11:45:41 +0200, Carlos E. R. wrote:
Ahh! I start to understand.
Still, Samba needs an interface to hook on network when it starts.
You have a ppp0, with an internet address. So not this one. You have an eth2 that is connected to a modem DSL device. This one is not working, gets neither IPv4, nor IPv6 address (not one that counts). What is confusing about this is that you already have a ppp0 for internet, so what is this, a LAN of some sort, another internet connection? Nevermind, it does not matter, I think, but it would be interesting to know. The problem is making it work.
network card in 12.2: eth0
There are things transmitted and received, but no address at all.
network card in Leap 42.2: eth2
A link local IPv6 address, this doesn't count, it is automatic. No IPv4 address, no IPv4 address. But 26 megabytes received, 3 sent.
You use network manager on both operating systems, works in neither. So I assume that NM is not the issue, because I assume that 12.2 was the original working setup.
So we get back to "Why there is no IPv4/IPv6 address in eth2"?
I would be looking at that DSL device. Is it supposed to give you an address via DHCP? Or are you supposed to assign an IP to the interface manually? That is the most important question now.
Thanks Carlos. It seems we are getting closer.
I do not think it's the DSL modem itself. It's the configuration. The two systems are not configured the same, and they are using different samba versions too.
In openSUSE 12.2 I don't use network manager, I use traditional ifup method. DSL is configured in YaST. In Leap 42.2 I use network manager (because in Leap it's not possible to set up DSL with traditional ifup/wicked).
In 12.2 YaST IPv6 is disabled. I don't use DHCP, zeroconf is set. In Leap network manager I don't know how the IP address is assigned because I can't see any options changing/reporting this.
But in 12.2 you also do not get an IP on the ethernet card, so it is also broken there, either in the configuration or in the modem. We can not try to imitate the config in 42.2 because in 12.2 it doesn't work.
So there are several options to identify the cause of the problem:
-- Test network manager in 12.2 if it's network manager issue.
-- Test traditional ifup in Leap 42.2 - not possilke
-- Install 12.2 samba version in Leap and test it if works.
no.
-- Install Leap samba version in 12.2 and test it - may not be possible.
no.
Though it would be nice to find some more trivial and easier way to troubleshoot and fix this.
You have two avenues: make samba work even if there is no networking interface active. I have no idea if this is possible.
Hello again: To fix my problem I tried to shortcut the no-local IPv4 address problem and set up a router. Now I have local IPv4 address, I have LAN, the computer connects to the internet through the router, still nmbd doesn't start.
/sbin/ifconfig -a eth2 Link encap:Ethernet HWaddr ........... inet addr:192.168.1.64 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::........./64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:179 errors:0 dropped:0 overruns:0 frame:0 TX packets:184 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:16462 (16.0 Kb) TX bytes:20544 (20.0 Kb)
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
systemctl status nmb ● nmb.service - Samba NMB Daemon Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled; vendor preset: disabled) Active: failed (Result: timeout) since Thu 2017-08-03 13:32:45 CEST; 9s ago Main PID: 2213 Status: "nmbd: No local IPv4 non-loopback interfaces available, waiting for interface ..." Tasks: 0 (limit: 512) CGroup: /system.slice/nmb.service
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
systemctl status smb ● smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2017-08-03 13:32:46 CEST; 2min 28s ago Process: 2602 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS) Main PID: 2613 (smbd) Status: "smbd: ready to serve connections..." Tasks: 4 (limit: 512) CGroup: /system.slice/smb.service ├─2613 /usr/sbin/smbd -D ├─2614 /usr/sbin/smbd -D ├─2615 /usr/sbin/smbd -D └─2618 /usr/sbin/smbd -D
Might be the device name eth2 the problem? Network-manager gave this device name and I could not find any option to change that (eg to eth0) in network manager connection editor. I have no clue what to do now. Any idea? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org