[opensuse] cannot start samba nmbd
Hello: I have this problem in openSUSE Leap 42.2 with its default samba version (4.4.2). nmbd service is not started at boot and I cannot start it manually. # systemctl start nmb.service Job for nmb.service failed because a timeout was exceeded. See "systemctl status nmb.service" and "journalctl -xe" for details. # systemctl status nmb.service ● nmb.service - Samba NMB Daemon Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled; vendor preset: disabled) Active: failed (Result: timeout) since Sun 2017-07-30 11:37:52 CEST; 5min ago Main PID: 4235 Status: "nmbd: No local IPv4 non-loopback interfaces available, waiting for interface ..." Tasks: 0 (limit: 512) CGroup: /system.slice/nmb.service Jul 30 11:37:37 linux nmbd[4235]: [2017/07/30 11:37:37.475899, 0] ../source3/lib/interface.c:652(load_interfaces) Jul 30 11:37:37 linux nmbd[4235]: WARNING: no network interfaces found Jul 30 11:37:42 linux nmbd[4235]: [2017/07/30 11:37:42.504127, 0] ../source3/lib/interface.c:652(load_interfaces) Jul 30 11:37:42 linux nmbd[4235]: WARNING: no network interfaces found Jul 30 11:37:47 linux nmbd[4235]: [2017/07/30 11:37:47.531053, 0] ../source3/lib/interface.c:652(load_interfaces) Jul 30 11:37:47 linux nmbd[4235]: WARNING: no network interfaces found Jul 30 11:37:52 linux systemd[1]: nmb.service: Start operation timed out. Terminating. Jul 30 11:37:52 linux systemd[1]: Failed to start Samba NMB Daemon. Jul 30 11:37:52 linux systemd[1]: nmb.service: Unit entered failed state. Jul 30 11:37:52 linux systemd[1]: nmb.service: Failed with result 'timeout'. According to this the problem is that I don't have a IPv4 non-localhost network insterface, which is true according to ifconfig: # ifconfig eth2 Link encap:Ethernet HWaddr xxxxxxxxxxxxx inet6 addr: abcd::abcd:abcd:abcd:abcd/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:24766 errors:0 dropped:0 overruns:0 frame:0 TX packets:20994 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:22671550 (21.6 Mb) TX bytes:3075937 (2.9 Mb) 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) ppp0 Link encap:Point-to-Point Protocol inet addr:xx.x.xxx.xxx P-t-P:xx.xxx.xxx.xx Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:24466 errors:0 dropped:0 overruns:0 frame:0 TX packets:20666 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:22115202 (21.0 Mb) TX bytes:2606771 (2.4 Mb) I have a DSL connection configured in network manager. Why does not eth2 get an IPv4 addres? How can I fix this? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 30 Jul 2017 12:07:46 +0200, Istvan Gabor wrote:
Hello:
I have this problem in openSUSE Leap 42.2 with its default samba version (4.4.2).
nmbd service is not started at boot and I cannot start it manually.
# systemctl start nmb.service Job for nmb.service failed because a timeout was exceeded. See "systemctl status nmb.service" and "journalctl -xe" for details.
# systemctl status nmb.service ● nmb.service - Samba NMB Daemon Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled; vendor preset: disabled) Active: failed (Result: timeout) since Sun 2017-07-30 11:37:52 CEST; 5min ago Main PID: 4235 Status: "nmbd: No local IPv4 non-loopback interfaces available, waiting for interface ..." Tasks: 0 (limit: 512) CGroup: /system.slice/nmb.service
Jul 30 11:37:37 linux nmbd[4235]: [2017/07/30 11:37:37.475899, 0] ../source3/lib/interface.c:652(load_interfaces) Jul 30 11:37:37 linux nmbd[4235]: WARNING: no network interfaces found Jul 30 11:37:42 linux nmbd[4235]: [2017/07/30 11:37:42.504127, 0] ../source3/lib/interface.c:652(load_interfaces) Jul 30 11:37:42 linux nmbd[4235]: WARNING: no network interfaces found Jul 30 11:37:47 linux nmbd[4235]: [2017/07/30 11:37:47.531053, 0] ../source3/lib/interface.c:652(load_interfaces) Jul 30 11:37:47 linux nmbd[4235]: WARNING: no network interfaces found Jul 30 11:37:52 linux systemd[1]: nmb.service: Start operation timed out. Terminating. Jul 30 11:37:52 linux systemd[1]: Failed to start Samba NMB Daemon. Jul 30 11:37:52 linux systemd[1]: nmb.service: Unit entered failed state. Jul 30 11:37:52 linux systemd[1]: nmb.service: Failed with result 'timeout'.
According to this the problem is that I don't have a IPv4 non-localhost network insterface, which is true according to ifconfig:
# ifconfig eth2 Link encap:Ethernet HWaddr xxxxxxxxxxxxx inet6 addr: abcd::abcd:abcd:abcd:abcd/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:24766 errors:0 dropped:0 overruns:0 frame:0 TX packets:20994 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:22671550 (21.6 Mb) TX bytes:3075937 (2.9 Mb)
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)
ppp0 Link encap:Point-to-Point Protocol inet addr:xx.x.xxx.xxx P-t-P:xx.xxx.xxx.xx Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:24466 errors:0 dropped:0 overruns:0 frame:0 TX packets:20666 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:22115202 (21.0 Mb) TX bytes:2606771 (2.4 Mb)
I have a DSL connection configured in network manager. Why does not eth2 get an IPv4 addres? How can I fix this?
I went back to openSUSE 12.2 where nmb starts at boot and runs normal. I use ifup method (not network manager) in 12.2 but the network card doesn't get an IPv4 address either; still nmb starts normal. # ifconfig dsl0 Link encap:Point-to-Point Protocol inet addr:xx.xxx.xxx.xxx P-t-P:xxx.xxx.xxx.xx Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:67 errors:0 dropped:0 overruns:0 frame:0 TX packets:36 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:6192 (6.0 Kb) TX bytes:2353 (2.2 Kb) eth0 Link encap:Ethernet HWaddr ............. UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:77 errors:0 dropped:0 overruns:0 frame:0 TX packets:46 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:8326 (8.1 Kb) TX bytes:3496 (3.4 Kb) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:12 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:600 (600.0 b) TX bytes:600 (600.0 b) # ps -e| grep -i nmb 3208 ? 00:00:00 nmbd Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-07-30 12:56, Istvan Gabor wrote:
I have this problem in openSUSE Leap 42.2 with its default samba version (4.4.2). ... According to this the problem is that I don't have a IPv4 non-localhost network insterface, which is true according to ifconfig:
I went back to openSUSE 12.2 where nmb starts at boot and runs normal. I use ifup method (not network manager) in 12.2 but the network card doesn't get an IPv4 address either; still nmb starts normal.
Forget samba. Investigate the no IPv4 issue, unless it is intentional and you only want IPv6. How is your IPv4 networking configured? Automatic? then look at your router.
# ifconfig dsl0 Link encap:Point-to-Point Protocol inet addr:xx.xxx.xxx.xxx P-t-P:xxx.xxx.xxx.xx Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:67 errors:0 dropped:0 overruns:0 frame:0 TX packets:36 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:6192 (6.0 Kb) TX bytes:2353 (2.2 Kb)
eth0 Link encap:Ethernet HWaddr ............. UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:77 errors:0 dropped:0 overruns:0 frame:0 TX packets:46 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:8326 (8.1 Kb) TX bytes:3496 (3.4 Kb)
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:12 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:600 (600.0 b) TX bytes:600 (600.0 b)
# ps -e| grep -i nmb 3208 ? 00:00:00 nmbd
Istvan
-- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On Sun, 30 Jul 2017 16:41:05 +0200, Carlos E. R. wrote:
On 2017-07-30 12:56, Istvan Gabor wrote:
I have this problem in openSUSE Leap 42.2 with its default samba version (4.4.2). ... According to this the problem is that I don't have a IPv4 non-localhost network insterface, which is true according to ifconfig:
I went back to openSUSE 12.2 where nmb starts at boot and runs normal. I use ifup method (not network manager) in 12.2 but the network card doesn't get an IPv4 address either; still nmb starts normal.
Forget samba. Investigate the no IPv4 issue, unless it is intentional and you only want IPv6.
How is your IPv4 networking configured? Automatic? then look at your router.
I don't have a router. I have a DSL modem. The computer is directly connected to the DSL modem and network is configured with network manager. DSL connection is added by/to network manager. I could not find any option to set IPv4 properties in network manager for DSL connection. But: How can I find out if I have IPv4 configured or not? Ifconfig doesn't indicate an IPv4 address for the network card either in openSUSE 12.2 or Leap 42.2, still in 12.2 it doesn't seem to be a problem for samba. How do I investigate IPv4 issue which, which you recommend? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/30/2017 02:33 PM, Istvan Gabor wrote:
How can I find out if I have IPv4 configured or not? Ifconfig doesn't indicate an IPv4 address for the network card either in openSUSE 12.2 or Leap 42.2, still in 12.2 it doesn't seem to be a problem for samba.
How do I investigate IPv4 issue which, which you recommend?
If you're connected directly to the DSL modem, it should be providing IPv4 addresses via DHCP. Fire up Wireshark and see what happens when you connect the computer to the modem. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 30 Jul 2017 14:59:43 -0400, James Knott wrote:
On 07/30/2017 02:33 PM, Istvan Gabor wrote:
How can I find out if I have IPv4 configured or not? Ifconfig doesn't indicate an IPv4 address for the network card either in openSUSE 12.2 or Leap 42.2, still in 12.2 it doesn't seem to be a problem for samba.
How do I investigate IPv4 issue which, which you recommend?
If you're connected directly to the DSL modem, it should be providing IPv4 addresses via DHCP. Fire up Wireshark and see what happens when you connect the computer to the modem.
I have IPv4 address for ppp0 interface (Leap 42.2) or dsl0 interface (openSUSE 12.2), but not for the network card interface (eth0/eth2). It's in my original 2 posts, full ifconfig outputs on Leap and 12.2 (though I replaced IPv4 address numbers by xxx - but those are valid working IPv4 addresses). Once more: --- network card in 12.2: eth0 Link encap:Ethernet HWaddr xxxxxxxxxxxx UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:77 errors:0 dropped:0 overruns:0 frame:0 TX packets:46 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:8326 (8.1 Kb) TX bytes:3496 (3.4 Kb) --- network card in Leap 42.2: eth2 Link encap:Ethernet HWaddr xxxxxxxxxxxxx inet6 addr: abcd::abcd:abcd:abcd:abcd/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:24766 errors:0 dropped:0 overruns:0 frame:0 TX packets:20994 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:22671550 (21.6 Mb) TX bytes:3075937 (2.9 Mb) --- DSL/modem interface in 12.2: dsl0 Link encap:Point-to-Point Protocol inet addr:xx.xxx.xxx.xxx P-t-P:xxx.xxx.xxx.xx Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:67 errors:0 dropped:0 overruns:0 frame:0 TX packets:36 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:6192 (6.0 Kb) TX bytes:2353 (2.2 Kb) --- DSL/modem interface in Leap: ppp0 Link encap:Point-to-Point Protocol inet addr:xx.x.xxx.xxx P-t-P:xx.xxx.xxx.xx Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:24466 errors:0 dropped:0 overruns:0 frame:0 TX packets:20666 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:22115202 (21.0 Mb) TX bytes:2606771 (2.4 Mb) The only difference between 12.2 and Leap network card outputs is the inet6 addr: abcd::abcd:abcd:abcd:abcd/64 Scope:Link line in Leap 42.2. ??? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/30/2017 03:30 PM, Istvan Gabor wrote:
I have IPv4 address for ppp0 interface (Leap 42.2) or dsl0 interface (openSUSE 12.2), but not for the network card interface (eth0/eth2). It's in my original 2 posts, full ifconfig outputs on Leap and 12.2 (though I replaced IPv4 address numbers by xxx - but those are valid working IPv4 addresses).
Every DSL modem I've worked with, in the past several years, has a built in router that must be specifically disabled, if you want to use your own router. If you're configuring for DSL, when you in fact have modem with built in router, you will not be able to connect. Try just a plain DHCP Ethernet connection. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 30 Jul 2017 16:11:46 -0400, James Knott wrote:
On 07/30/2017 03:30 PM, Istvan Gabor wrote:
I have IPv4 address for ppp0 interface (Leap 42.2) or dsl0 interface (openSUSE 12.2), but not for the network card interface (eth0/eth2). It's in my original 2 posts, full ifconfig outputs on Leap and 12.2 (though I replaced IPv4 address numbers by xxx - but those are valid working IPv4 addresses).
Every DSL modem I've worked with, in the past several years, has a built in router that must be specifically disabled, if you want to use your own router. If you're configuring for DSL, when you in fact have modem
I never wrote I wanted to use my own router. Where did you read it? I do not have router at all.
with built in router, you will not be able to connect. Try just a plain DHCP Ethernet connection
Patrick, James, thank you for trying to help, but it seems you are unfamiliar with the type of DSL connection I have, and you are trying to lead me to the wrong direction. My DSL modem has no router or if it has, it's not configurable. I don't either need DHCP since zeroconfig works with this type of connection. Here are photos of the modem I have: http://oldradio.tesla.hu/szetszedtem/039adslmodemek/008dlink360r/dlink360r.h... Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Istvan Gabor <suseuser04@gmail.hu> [07-30-17 17:42]: [...]
Patrick, James, thank you for trying to help, but it seems you are unfamiliar with the type of DSL connection I have, and you are trying to lead me to the wrong direction. My DSL modem has no router or if it has, it's not configurable. I don't either need DHCP since zeroconfig works with this type of connection.
you are correct. my *only* efforts are to lead you in the wrong direction. but I am suddenly very dis-interested in any further effort. and am not very fluent in hungarian, barely read english. gud luk -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 30 Jul 2017 17:49:03 -0400, Patrick Shanahan wrote:
* Istvan Gabor <suseuser04@gmail.hu> [07-30-17 17:42]: [...]
Patrick, James, thank you for trying to help, but it seems you are unfamiliar with the type of DSL connection I have, and you are trying to lead me to the wrong direction. My DSL modem has no router or if it has, it's not configurable. I don't either need DHCP since zeroconfig works with this type of connection.
you are correct. my *only* efforts are to lead you in the wrong direction. but I am suddenly very dis-interested in any further effort. and am not very fluent in hungarian, barely read english. gud luk
Patrick, you have no reason to be offended. I did not say you intentionally tried to lead me to the wrong direction. If it could have been understood like that, I apologize. I meant that you insisted that I have a router which is incorrectly configured, or something like this. I have a simple DSL (PPPoE) connection. Using the same modem, the same computer, if I boot Leap 42.2 nmbd is not started, if I boot openSUSE 12.2 nmbd is started. So it is the difference between 12.2 and Leap, no router/modem issue. I thought it was clear from my precious posts. Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/30/2017 05:38 PM, Istvan Gabor wrote:
Patrick, James, thank you for trying to help, but it seems you are unfamiliar with the type of DSL connection I have, and you are trying to lead me to the wrong direction. My DSL modem has no router or if it has, it's not configurable. I don't either need DHCP since zeroconfig works with this type of connection.
Does your PPPoE connection work? You said it has an address. If so, then why do you need an IPv4 address on the network card. All you need for PPPoE is a working Ethernet connection, not IP. PPPoE means Point to Point Protocol over Ethernet. What a lot of people have forgotten or never knew is that IP is just one protocol of many that can be used over an Ethernet connection. Years ago, Novell's IPX was common, along with the IBM & Microsoft NetBIOS/NetBEUI. It was only in the mid, late 90's that we started seeing IPv4 commonly used on networks. Back when I was at IBM, in the late '90s, we had NetBios, SNA & IPv4 on the token ring network, but NetBIOS & SNA carried the bulk of the traffic. IPv4 was used only for accessing the Internet. Then, we moved Lotus Notes and a few other apps onto IPv4 and went from there. These days, the world is moving to IPv6. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 30 Jul 2017 17:57:33 -0400, James Knott wrote:
On 07/30/2017 05:38 PM, Istvan Gabor wrote:
Patrick, James, thank you for trying to help, but it seems you are unfamiliar with the type of DSL connection I have, and you are trying to lead me to the wrong direction. My DSL modem has no router or if it has, it's not configurable. I don't either need DHCP since zeroconfig works with this type of connection.
Does your PPPoE connection work? You said it has an address.
Thanks James. Yes, my PPPoE is working, and it has a publicly available IPv4 address.
If so, then why do you need an IPv4 address on the network card.
I don't need it. But samba complains that it cannot start nmbd because there is no-local IPv4 address. Do you rememeber the OP? Status: "nmbd: No local IPv4 non-loopback interfaces available, waiting for interface ..."
All you need for PPPoE is a working Ethernet connection, not IP. PPPoE means Point to Point Protocol over Ethernet.
OK, I understand this, but how do I tell it to samba nmbd service? Thanks again, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-07-30 23:38, Istvan Gabor wrote:
On Sun, 30 Jul 2017 16:11:46 -0400, James Knott wrote:
On 07/30/2017 03:30 PM, Istvan Gabor wrote:
I have IPv4 address for ppp0 interface (Leap 42.2) or dsl0 interface (openSUSE 12.2), but not for the network card interface (eth0/eth2). It's in my original 2 posts, full ifconfig outputs on Leap and 12.2 (though I replaced IPv4 address numbers by xxx - but those are valid working IPv4 addresses).
Every DSL modem I've worked with, in the past several years, has a built in router that must be specifically disabled, if you want to use your own router. If you're configuring for DSL, when you in fact have modem
I never wrote I wanted to use my own router. Where did you read it? I do not have router at all.
with built in router, you will not be able to connect. Try just a plain DHCP Ethernet connection
Patrick, James, thank you for trying to help, but it seems you are unfamiliar with the type of DSL connection I have, and you are trying to lead me to the wrong direction. My DSL modem has no router or if it has, it's not configurable. I don't either need DHCP since zeroconfig works with this type of connection.
Because you need a Local Area Network in order to use Samba, and typically everybody has it on the eth connection (or the wlan), and the eth is connected to a router and to the rest of the computers on the LAN. We are trying to find your LAN. So, explain where is your LAN. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 2017-07-30 21:30, Istvan Gabor wrote:
On Sun, 30 Jul 2017 14:59:43 -0400, James Knott wrote:
On 07/30/2017 02:33 PM, Istvan Gabor wrote:
How can I find out if I have IPv4 configured or not? Ifconfig doesn't indicate an IPv4 address for the network card either in openSUSE 12.2 or Leap 42.2, still in 12.2 it doesn't seem to be a problem for samba.
How do I investigate IPv4 issue which, which you recommend?
If you're connected directly to the DSL modem, it should be providing IPv4 addresses via DHCP. Fire up Wireshark and see what happens when you connect the computer to the modem.
I have IPv4 address for ppp0 interface (Leap 42.2) or dsl0 interface (openSUSE 12.2), but not for the network card interface (eth0/eth2). It's in my original 2 posts, full ifconfig outputs on Leap and 12.2 (though I replaced IPv4 address numbers by xxx - but those are valid working IPv4 addresses).
Then you do not want Samba in that interface. Where is your local network? You want samba there. Normally the LAN is on ETH or WLAN, not on PPP0. You do not want samba on Internet. I don't understand your setup. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
* Istvan Gabor <suseuser04@gmail.hu> [07-30-17 14:36]: [...]
I don't have a router. I have a DSL modem. The computer is directly connected to the DSL modem and network is configured with network manager. DSL connection is added by/to network manager. I could not find any option to set IPv4 properties in network manager for DSL connection.
your dsl modem probably contains a router. look on the lables for a network address to connect by browser. there will also be a password. if no network address is there, look for the service and modem on google or your choice for means to access the internal router. my at&t dsl modem contains a router, 192.168.1.254 my brighthouse modem also did, 192.168.1.1 one of my business support client has, 10.10.1.1 -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2017-07-30 at 12:07 +0200, Istvan Gabor wrote:
According to this the problem is that I don't have a IPv4 non-localhost network insterface, which is true according to ifconfig:
# ifconfig eth2 Link encap:Ethernet HWaddr xxxxxxxxxxxxx inet6 addr: abcd::abcd:abcd:abcd:abcd/64 Scope:Link
This inet 6 address is a public internet address? I can understand you obscuring an internet address, but not a local address.
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:24766 errors:0 dropped:0 overruns:0 frame:0 TX packets:20994 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:22671550 (21.6 Mb) TX bytes:3075937 (2.9 Mb)
ppp0 Link encap:Point-to-Point Protocol inet addr:xx.x.xxx.xxx P-t-P:xx.xxx.xxx.xx Mask:255.255.255.255
Again, is this a local network address, or a publick internet address? We can not judge your network if you hide so many detains from us.
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:24466 errors:0 dropped:0 overruns:0 frame:0 TX packets:20666 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:22115202 (21.0 Mb) TX bytes:2606771 (2.4 Mb)
I have a DSL connection configured in network manager. Why does not eth2 get an IPv4 addres? How can I fix this?
- -- Cheers, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAll+UFcACgkQtTMYHG2NR9VqQgCfb8DsFVkE7gOTylSavX8dhj6d obIAniqyvuS5cwIVQ3svrXKpkfbbKKIk =c6oD -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 30 Jul 2017 23:32:06 +0200 (CEST), Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sunday, 2017-07-30 at 12:07 +0200, Istvan Gabor wrote:
According to this the problem is that I don't have a IPv4 non-localhost network insterface, which is true according to ifconfig:
# ifconfig eth2 Link encap:Ethernet HWaddr xxxxxxxxxxxxx inet6 addr: abcd::abcd:abcd:abcd:abcd/64 Scope:Link
This inet 6 address is a public internet address?
I don't know, I think probably not. It is a link-local address if I remember correctly. I cannot check, because I am at another system now. It looked something like fe80::..........
I can understand you obscuring an internet address, but not a local address.
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:24766 errors:0 dropped:0 overruns:0 frame:0 TX packets:20994 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:22671550 (21.6 Mb) TX bytes:3075937 (2.9 Mb)
ppp0 Link encap:Point-to-Point Protocol inet addr:xx.x.xxx.xxx P-t-P:xx.xxx.xxx.xx Mask:255.255.255.255
Again, is this a local network address, or a publick internet address?
This is a working public IPv4 address, like 80.249.170.197. Not a local network address (like 192.168.0.15). The same applies to openSUSE 12.2 but there is no IPv6 address line there. Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-07-31 00:22, Istvan Gabor wrote:
On Sun, 30 Jul 2017 23:32:06 +0200 (CEST), Carlos E. R. wrote:
On Sunday, 2017-07-30 at 12:07 +0200, Istvan Gabor wrote:
According to this the problem is that I don't have a IPv4 non-localhost network insterface, which is true according to ifconfig:
# ifconfig eth2 Link encap:Ethernet HWaddr xxxxxxxxxxxxx inet6 addr: abcd::abcd:abcd:abcd:abcd/64 Scope:Link
This inet 6 address is a public internet address?
I don't know, I think probably not. It is a link-local address if I remember correctly. I cannot check, because I am at another system now. It looked something like fe80::..........
Then it has neither IPv4 nor IPv6 addresses.
I can understand you obscuring an internet address, but not a local address.
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:24766 errors:0 dropped:0 overruns:0 frame:0 TX packets:20994 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:22671550 (21.6 Mb) TX bytes:3075937 (2.9 Mb)
ppp0 Link encap:Point-to-Point Protocol inet addr:xx.x.xxx.xxx P-t-P:xx.xxx.xxx.xx Mask:255.255.255.255
Again, is this a local network address, or a publick internet address?
This is a working public IPv4 address, like 80.249.170.197. Not a local network address (like 192.168.0.15).
The same applies to openSUSE 12.2 but there is no IPv6 address line there.
Well, you don't have a LAN. I do not see where are you going to use SAMBA. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 07/30/2017 06:32 PM, Carlos E. R. wrote:
The same applies to openSUSE 12.2 but there is no IPv6 address line there. Well, you don't have a LAN. I do not see where are you going to use SAMBA.
It is possible to use it over the 'net, but that would be a bad idea. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-07-31 00:36, James Knott wrote:
On 07/30/2017 06:32 PM, Carlos E. R. wrote:
The same applies to openSUSE 12.2 but there is no IPv6 address line there. Well, you don't have a LAN. I do not see where are you going to use SAMBA.
It is possible to use it over the 'net, but that would be a bad idea.
A very bad idea. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On Mon, 31 Jul 2017 00:32:01 +0200, Carlos E. R. wrote:
On 2017-07-31 00:22, Istvan Gabor wrote:
On Sun, 30 Jul 2017 23:32:06 +0200 (CEST), Carlos E. R. wrote:
On Sunday, 2017-07-30 at 12:07 +0200, Istvan Gabor wrote:
According to this the problem is that I don't have a IPv4 non-localhost network insterface, which is true according to ifconfig:
# ifconfig eth2 Link encap:Ethernet HWaddr xxxxxxxxxxxxx inet6 addr: abcd::abcd:abcd:abcd:abcd/64 Scope:Link
This inet 6 address is a public internet address?
I don't know, I think probably not. It is a link-local address if I remember correctly. I cannot check, because I am at another system now. It looked something like fe80::..........
Then it has neither IPv4 nor IPv6 addresses.
I can understand you obscuring an internet address, but not a local address.
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:24766 errors:0 dropped:0 overruns:0 frame:0 TX packets:20994 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:22671550 (21.6 Mb) TX bytes:3075937 (2.9 Mb)
ppp0 Link encap:Point-to-Point Protocol inet addr:xx.x.xxx.xxx P-t-P:xx.xxx.xxx.xx Mask:255.255.255.255
Again, is this a local network address, or a publick internet address?
This is a working public IPv4 address, like 80.249.170.197. Not a local network address (like 192.168.0.15).
The same applies to openSUSE 12.2 but there is no IPv6 address line there.
Well, you don't have a LAN. I do not see where are you going to use SAMBA.
I have an old Windows installation in virtualbox. Occasionally I have to print from there with my local printer. Also I have a samba shared folder to copy files between Windows and openSUSE host. I used samba to share my printer and the shared folder. This works in openSUSE 12.2. virtualbox offers a vmnet0 network interface but it's not started until virtualbox is started. Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/30/2017 03:54 PM, Istvan Gabor wrote:
Well, you don't have a LAN. I do not see where are you going to use SAMBA.
I have an old Windows installation in virtualbox. Occasionally I have to print from there with my local printer. Also I have a samba shared folder to copy files between Windows and openSUSE host. I used samba to share my printer and the shared folder. This works in openSUSE 12.2. virtualbox offers a vmnet0 network interface but it's not started until virtualbox is started.
Istvan
First of all, it doesn't MATTER what anyone thinks about your use case... If you have the use case, you have no need or obligation to explain or justify it to ANYONE. What I suspect if going on is that NetworkManager isn't starting. Try this as root: systemctl start NetworkManager The do ifconfig to see of the LAN interface started and got an IP address. That said, I do agree, it's probably not a very good idea to expose samba to the general internet unless you know exactly what you're doing... And I know some very large companies that do know what they're doing and they do it pretty routinely and still have issues. Cheers! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-07-31 08:22, Bruce Ferrell wrote:
On 07/30/2017 03:54 PM, Istvan Gabor wrote:
Well, you don't have a LAN. I do not see where are you going to use SAMBA.
I have an old Windows installation in virtualbox. Occasionally I have to print from there with my local printer. Also I have a samba shared folder to copy files between Windows and openSUSE host. I used samba to share my printer and the shared folder. This works in openSUSE 12.2. virtualbox offers a vmnet0 network interface but it's not started until virtualbox is started.
Istvan
First of all, it doesn't MATTER what anyone thinks about your use case... If you have the use case, you have no need or obligation to explain or justify it to ANYONE.
Yes, it does. If there is no LAN, there is no SAMBA. We need to know where is the LAN, where is the missing network interface that SAMBA uses. It turns out to be an internal interface, virtual. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 2017-07-31 00:54, Istvan Gabor wrote:
On Mon, 31 Jul 2017 00:32:01 +0200, Carlos E. R. wrote:
Well, you don't have a LAN. I do not see where are you going to use SAMBA.
I have an old Windows installation in virtualbox. Occasionally I have to print from there with my local printer. Also I have a samba shared folder to copy files between Windows and openSUSE host. I used samba to share my printer and the shared folder. This works in openSUSE 12.2. virtualbox offers a vmnet0 network interface but it's not started until virtualbox is started.
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. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On Mon, 31 Jul 2017 11:45:41 +0200, Carlos E. R. wrote:
On 2017-07-31 00:54, Istvan Gabor wrote:
On Mon, 31 Jul 2017 00:32:01 +0200, Carlos E. R. wrote:
Well, you don't have a LAN. I do not see where are you going to use SAMBA.
I have an old Windows installation in virtualbox. Occasionally I have to print from there with my local printer. Also I have a samba shared folder to copy files between Windows and openSUSE host. I used samba to share my printer and the shared folder. This works in openSUSE 12.2. virtualbox offers a vmnet0 network interface but it's not started until virtualbox is started.
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. 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. -- Install Leap samba version in 12.2 and test it - may not be possible. Though it would be nice to find some more trivial and easier way to troubleshoot and fix this. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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. Get a network interface working on eth. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 07/31/2017 04:14 AM, Carlos E. R. wrote:
You have two avenues: make samba work even if there is no networking interface active. I have no idea if this is possible.
Get a network interface working on eth.
While traveling with my laptop, I used to often encounter this. Frequently I do not bother to connect to any network, because I'm going to be working on software for my day-job, which requires a couple windows virtual machines. Of course the Linux machine itself was the samba server for these virtual machines. I found I had to start at least one VMWare machine to get vmware to start it's network so that Adapter Vmnet(x) would appear and make samba happy. I could also user VMware's "host only" networking for this, which causes a new adapter to appear on the host but which needs no external connection. Virtualbox also supports a Host Only Adapter that operates similarly. You just have to add this adapter to the list of adapters that Samba services in smb.conf Somewhere along the way Vmware Workstation gained the ability to start its network at boot time and the problem pretty much vanished. -- After all is said and done, more is said than done.
On 07/31/2017 09:22 AM, John Andersen wrote:
On 07/31/2017 04:14 AM, Carlos E. R. wrote:
You have two avenues: make samba work even if there is no networking interface active. I have no idea if this is possible.
Get a network interface working on eth. While traveling with my laptop, I used to often encounter this.
Frequently I do not bother to connect to any network, because I'm going to be working on software for my day-job, which requires a couple windows virtual machines. Of course the Linux machine itself was the samba server for these virtual machines.
I found I had to start at least one VMWare machine to get vmware to start it's network so that Adapter Vmnet(x) would appear and make samba happy.
I could also user VMware's "host only" networking for this, which causes a new adapter to appear on the host but which needs no external connection.
Virtualbox also supports a Host Only Adapter that operates similarly.
You just have to add this adapter to the list of adapters that Samba services in smb.conf
Somewhere along the way Vmware Workstation gained the ability to start its network at boot time and the problem pretty much vanished. The thing to keep in mind about samba is that unless you have a "bind interfaces only" statement in the smb.conf (I do) to restrict smbd, it automatically binds to ALL interfaces, configured or not. use lsof to check it for yourself.
Keep in mind, ifconfig, if executed with NO parameters only displayed interfaces that are configured. ifconfig -a will show all interfaces, configured or not. If the drivers for the interfaces on eth0 and eth1 are loaded and eth0 is NOT configured, but eth1 IS, eth0 will not display... But it IS present and available to be bound to. This is why you can use tcpdump and wireshark on unconfigured interfaces (not to mention connecting more exotic things like openvswitch and constructing bridges using interfaces without IP addresses). One final thing, configured does NOT mean a cable is plugged in and connected to a hub or switch. That is indicated by a "link up" state. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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)
systemctl status nmb ● nmb.service - Samba NMB Daemon Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled; vendor
systemctl status smb ● smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor
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) 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. 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
On 2017-08-03 13:46, Istvan Gabor wrote:
On Mon, 31 Jul 2017 13:14:31 +0200, Carlos E. R. wrote:
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.
That's the status. Dis you try to restart the service manually? If still doesn't work, it would seem a bug to me.
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
But here it is running. Ah, that's smbd, not nmb -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On Thu, 3 Aug 2017 17:04:12 +0200, Carlos E. R. wrote:
On 2017-08-03 13:46, Istvan Gabor wrote:
On Mon, 31 Jul 2017 13:14:31 +0200, Carlos E. R. wrote:
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.
That's the status. Dis you try to restart the service manually? If still doesn't work, it would seem a bug to me.
# systemctl restart nmb Job for nmb.service failed because a timeout was exceeded. See "systemctl status nmb.service" and "journalctl -xe" for details. # 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 Sat 2017-08-05 12:49:59 CEST; 22s ago Main PID: 4439 Status: "nmbd: No local IPv4 non-loopback interfaces available, waiting for interface ..." Tasks: 0 (limit: 512) CGroup: /system.slice/nmb.service Aug 05 12:49:44 linux nmbd[4439]: [2017/08/05 12:49:44.359197, 0] ../source3/lib/interface.c:652(load_interfaces) Aug 05 12:49:44 linux nmbd[4439]: WARNING: no network interfaces found Aug 05 12:49:49 linux nmbd[4439]: [2017/08/05 12:49:49.369442, 0] ../source3/lib/interface.c:652(load_interfaces) Aug 05 12:49:49 linux nmbd[4439]: WARNING: no network interfaces found Aug 05 12:49:54 linux nmbd[4439]: [2017/08/05 12:49:54.377952, 0] ../source3/lib/interface.c:652(load_interfaces) Aug 05 12:49:54 linux nmbd[4439]: WARNING: no network interfaces found Aug 05 12:49:59 linux systemd[1]: nmb.service: Start operation timed out. Terminating. Aug 05 12:49:59 linux systemd[1]: Failed to start Samba NMB Daemon. # ifconfig -a eth2 Link encap:Ethernet HWaddr ........... inet addr:192.168.1.101 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:45208 errors:0 dropped:0 overruns:0 frame:0 TX packets:33541 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:43052934 (41.0 Mb) TX bytes:3966816 (3.7 Mb) 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:28602 errors:0 dropped:0 overruns:0 frame:0 TX packets:28602 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:21357532 (20.3 Mb) TX bytes:21357532 (20.3 Mb) Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-08-05 12:50, Istvan Gabor wrote:
On Thu, 3 Aug 2017 17:04:12 +0200, Carlos E. R. wrote:
That's the status. Dis you try to restart the service manually? If still doesn't work, it would seem a bug to me.
# systemctl restart nmb Job for nmb.service failed because a timeout was exceeded. See "systemctl status nmb.service" and "journalctl -xe" for details.
Well, I don't understand it. See if the configuration mentions a particular network interface. :-? Report in bugzilla. Some google hits: http://linuxadmin.melberi.com/2015/04/nmbd-no-local-ipv4-non-loopback.html No. But Says: +++---------- Also check /etc/samba/smb.conf and configure the available interfaces. In my case, interfaces = eth0, lo modified to interfaces = ens32, lo ----------++- In your case: interfaces = eth2, lo -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 07/30/2017 06:22 PM, Istvan Gabor wrote:
According to this the problem is that I don't have a IPv4 non-localhost network insterface, which is true according to ifconfig:
# ifconfig eth2 Link encap:Ethernet HWaddr xxxxxxxxxxxxx inet6 addr: abcd::abcd:abcd:abcd:abcd/64 Scope:Link
This inet 6 address is a public internet address?
I don't know, I think probably not. It is a link-local address if I remember correctly. I cannot check, because I am at another system now. It looked something like fe80::..........
Yes, that's a link local address, which starts with fe80. There's no need to hide it, as no one can reach it from outside your network. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Bruce Ferrell -
Carlos E. R. -
Istvan Gabor -
James Knott -
John Andersen -
Patrick Shanahan