samba insists on using virbr0
sean darcy
seandarcy2 at gmail.com
Sun Oct 26 02:33:56 UTC 2008
Mikkel L. Ellertson wrote:
> sean darcy wrote:
>> Using f9 updated, with qemu installed, I can't get samba to work.
>>
>> I think it's because samba keeps using virbr0, rather than eth0.
>>
> <----------------------------[SNIP]---------------------->
>> I'm not able to browse the .180 machine. Having gone through the samba
>> troubleshooting fault tree, I came on this problem.
>>
>> Is there a way to keep qemu ( I use it with kvm)?
>>
>> sean
>>
> Did you try to use "interfaces = " option in smb.conf?
>
> Mikkel
>
Yes. That was my first thought:
testparm
Load smb config files from /etc/samba/smb.conf
Processing section "[homes]"
Processing section "[printers]"
Processing section "[storage]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
[global]
workgroup = NEW_NET
netbios name = VIDEO_SERVER_IN_CLOSET
server string = server in closet
interfaces = lo, eth0
passdb backend = tdbsam
log file = /var/log/samba/log.%m
max log size = 50
domain master = No
guest ok = Yes
..............
I think the problem is since you've got to have lo, samba figures virbr0
is a local interface.
Your response prompted me to try:
interfaces = lo, 10.10.11.0/24
bind interfaces only = Yes
which gave me a different, but still wrong response:
nmblookup -d 2 '*'
added interface lo ip=::1 bcast=::1
netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
added interface lo ip=127.0.0.1 bcast=127.255.255.255 netmask=255.0.0.0
interpret_interface: using netmask value 24 from config file on
interface eth0
added interface eth0 ip=10.10.11.180 bcast=10.10.11.255
netmask=255.255.255.0
querying * on 127.255.255.255
Got a positive name query response from 127.0.0.1 ( 10.10.11.180 )
10.10.11.180 *<00>
only broadcasting on the loopback interface.
puzzled,
sean
More information about the fedora-list
mailing list