Everyone:
Have you ever seen this result from the command route -n?
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 1024 0 0 wlp3s0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp3s0
The "wlp3s0" is a wireless interface.
But I have another computer that uses a regular Ethernet interface. The result, except for a different interface name, is the same.
As a result, Samba suddenly won't work for me anymore.
The only difference is, I permanently retired an old computer from my home network. That computer had been running Fedora 20, and I had made updates since Fedora 12. Now, with that computer no longer part of the network, neither of the two Linux boxes can see the other. But either of them can see a Windows physical box, so long as that box is turned on.
Temlakos
On 06/18/14 06:43, Temlakos wrote:
Everyone:
Have you ever seen this result from the command route -n?
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 1024 0 0 wlp3s0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp3s0
The "wlp3s0" is a wireless interface.
But I have another computer that uses a regular Ethernet interface. The result, except for a different interface name, is the same.
As a result, Samba suddenly won't work for me anymore.
The only difference is, I permanently retired an old computer from my home network. That computer had been running Fedora 20, and I had made updates since Fedora 12. Now, with that computer no longer part of the network, neither of the two Linux boxes can see the other. But either of them can see a Windows physical box, so long as that box is turned on.
[root@meimei ~]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 1024 0 0 p128p1 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 p128p1
wired interface....and all is well.
I never knew what "see" means.
On Tue, Jun 17, 2014 at 6:43 PM, Temlakos temlakos@gmail.com wrote:
Have you ever seen this result from the command route -n?
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 1024 0 0 wlp3s0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp3s0
The "wlp3s0" is a wireless interface.
But I have another computer that uses a regular Ethernet interface. The result, except for a different interface name, is the same.
As a result, Samba suddenly won't work for me anymore.
Do you have a restriction on the interface(s) to use in the samba config? (An "interfaces =" line.)
On 06/18/2014 12:45 AM, Tom H wrote:
On Tue, Jun 17, 2014 at 6:43 PM, Temlakos temlakos@gmail.com wrote:
Have you ever seen this result from the command route -n?
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 1024 0 0 wlp3s0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp3s0
The "wlp3s0" is a wireless interface.
But I have another computer that uses a regular Ethernet interface. The result, except for a different interface name, is the same.
As a result, Samba suddenly won't work for me anymore.
Do you have a restriction on the interface(s) to use in the samba config? (An "interfaces =" line.)
It was commented out. I took out the semicolon. It now includes "lo" and "192.169.1.0/24" plus the two named connections, one wired and one wireless, I have available. They are named "p37p1" and "wlp3s0." Of these only "wlp3s0" is listed because I disconnected the wired interface.
I just took that semicolon out a minute ago. How long do I have to wait for it to start listening in on "lo" and the others?
Temlakos
On 2014-06-18 11:37, Temlakos wrote:
On 06/18/2014 12:45 AM, Tom H wrote:
On Tue, Jun 17, 2014 at 6:43 PM, Temlakos temlakos@gmail.com wrote:
Have you ever seen this result from the command route -n?
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 1024 0 0 wlp3s0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp3s0
The "wlp3s0" is a wireless interface.
But I have another computer that uses a regular Ethernet interface. The result, except for a different interface name, is the same.
As a result, Samba suddenly won't work for me anymore.
Do you have a restriction on the interface(s) to use in the samba config? (An "interfaces =" line.)
It was commented out. I took out the semicolon. It now includes "lo" and "192.169.1.0/24" plus the two named connections, one wired and one wireless, I have available. They are named "p37p1" and "wlp3s0." Of these only "wlp3s0" is listed because I disconnected the wired interface.
I just took that semicolon out a minute ago. How long do I have to wait for it to start listening in on "lo" and the others?
Temlakos
If the interfaces are up and running, they are working immediately. This is not DNS, where you have to wait for the end of the DNS-propagation-delay.
suomi
On 06/18/2014 07:32 AM, fedora wrote:
On 2014-06-18 11:37, Temlakos wrote:
On 06/18/2014 12:45 AM, Tom H wrote:
On Tue, Jun 17, 2014 at 6:43 PM, Temlakos temlakos@gmail.com wrote:
Have you ever seen this result from the command route -n?
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 1024 0 0 wlp3s0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp3s0
The "wlp3s0" is a wireless interface.
But I have another computer that uses a regular Ethernet interface. The result, except for a different interface name, is the same.
As a result, Samba suddenly won't work for me anymore.
Do you have a restriction on the interface(s) to use in the samba config? (An "interfaces =" line.)
It was commented out. I took out the semicolon. It now includes "lo" and "192.169.1.0/24" plus the two named connections, one wired and one wireless, I have available. They are named "p37p1" and "wlp3s0." Of these only "wlp3s0" is listed because I disconnected the wired interface.
I just took that semicolon out a minute ago. How long do I have to wait for it to start listening in on "lo" and the others?
Temlakos
If the interfaces are up and running, they are working immediately. This is not DNS, where you have to wait for the end of the DNS-propagation-delay.
suomi
The problem is now solved.
To make a long story short: I uncommented the interfaces = and hosts allow lines in smb.conf. I specified the named interfaces on each of two computers, and the localhost (127.) and "down number" (192.168.) sources for allowed hosts.
Then I started smbd and nmbd.
And now each machine can share files to the other.
This brings up a different problem, which I will mention on a new thread.
Temlakos
-
Ed Greshko -
fedora -
Temlakos -
Tom H