[Samba] try to bind samba traffic to specific interface - without
success
Jan
jan at mailbone.de
Sat Aug 4 20:23:41 GMT 2007
Hey Bjørn,
the traffic isn't send by a different subnet ...
eth1 = 192.168.0.100 ( default route via 192.168.0.150 )
eth2 = 192.168.0.200
both interfaces belonging to the same net (255.255.255.0) ...
eth2 is not configurated with an default route. could this be the failure?
(i don't think so because the route for the default gateway was set for eth1 only by /etc/conf.d/net)
output of route table:
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.0.150 0.0.0.0 UG 0 0 0 eth1
i hope that could bring some light on this situation ...
greetings
Jan
Bjørn Tore Sund schrieb:
> Jan wrote:
>> Jan schrieb:
>>> Hello,
>>>
>>> tonight my home samba server attracted my attention because i had
>>> seen that the complete
>>> traffic (copy user->server / server->user) goes via eth0 and not
>>> how specified in smb.con
>>> via the eth2 interface.
>>>
>>> i tried to bind it like this:
>>>
>>> *interfaces = lo eth2
>>>
>>>
>>> *
>>>
>>> in smb.conf ... any idea?
>>>
> Depends wat you mean by "goes via". Does it _accept_ traffic via
> eth0, or does it _send_ traffic via eth0? If the latter, are
> connections coming from outside the eth2 subnet, while default gateway
> is through eth0?
>
> -BT
>
More information about the samba
mailing list