RE: [Samba] Traffic going to wrong interface?
So, it seems that Windows XP specifies the primary IP address as the source address of the TCP connection when connecting to \\192.168.2.200 !!?? On linux host netstat -an: tcp0 1239 192.168.2.200:139 216.254.100.242:2894 ESTABLISHED I would have expected this to read tcp0 1239 192.168.2.200:139 192.168.2.201:2894 ESTABLISHED Where 192.168.2.201 is the second ethernet adapter on the windows client. Hmmm -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 06, 2004 1:17 PM To: Andrew Athan Cc: [EMAIL PROTECTED] Subject: Re: [Samba] Traffic going to wrong interface? assuming you are using linux: Have you tried the below GLOBAL setting? interfaces = 172.16.92.245 This asks samba to listen on that interface only, I don't know if it will also force samba to use this interface as the source for any outbound connections. Making the gigabit interface your primary interface may also work. You might be able to kludge this from within the /etc/modules.conf file if you are using modules to drive the cards. alias eth0 tg3 alias eth1 e100 Then there is the route method. you can add static routes to the client. Host routes are honored over network routes. I'd use this as a last resort, it seems wrong. route add -host 172.16.92.245 eth0 I have a few more but I think one of these might work. good luck with it. peace. Andrew Athan wrote: If I connect via \\gige.ethernet.address\foo , and copying a large file, windows reports outbound traffic on the gige port and return traffic on the 100Meg port. Thus, it seems the samba server sees the client-server traffic via gige but is responding via the slower interface. Not what I want. -- UNIX is user friendly, it's just selective about who its friends are. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Traffic going to wrong interface?
On Wednesday 07 January 2004 03:09, Andrew Athan wrote: So, it seems that Windows XP specifies the primary IP address as the source address of the TCP connection when connecting to \\192.168.2.200 !!?? I think that Windows only binds NetBIOS to its primary interface. If your GbE device is not the primary interface this may be the problem. If so, uninstall the nics and reinstall so that the GbE card is the primary device. -- Chris Do not reply to the email address. Please use the contact page below for any desired direct replies. Apologies for the inconvenience. realcomputerguy dot com slash contact dot html -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Traffic going to wrong interface?
I have a samba server with 2 ethernet ports, one of which is a gigabit port. When connecting from a windows client that has a crossover to the gigabit port, and a crossover to the 100Meg port: If I connect via \\gige.ethernet.address\foo , and copying a large file, windows reports outbound traffic on the gige port and return traffic on the 100Meg port. Thus, it seems the samba server sees the client-server traffic via gige but is responding via the slower interface. Not what I want. Any clues? Thanks, A. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Traffic going to wrong interface?
assuming you are using linux: Have you tried the below GLOBAL setting? interfaces = 172.16.92.245 This asks samba to listen on that interface only, I don't know if it will also force samba to use this interface as the source for any outbound connections. Making the gigabit interface your primary interface may also work. You might be able to kludge this from within the /etc/modules.conf file if you are using modules to drive the cards. alias eth0 tg3 alias eth1 e100 Then there is the route method. you can add static routes to the client. Host routes are honored over network routes. I'd use this as a last resort, it seems wrong. route add -host 172.16.92.245 eth0 I have a few more but I think one of these might work. good luck with it. peace. Andrew Athan wrote: If I connect via \\gige.ethernet.address\foo , and copying a large file, windows reports outbound traffic on the gige port and return traffic on the 100Meg port. Thus, it seems the samba server sees the client-server traffic via gige but is responding via the slower interface. Not what I want. -- UNIX is user friendly, it's just selective about who its friends are. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Traffic going to wrong interface?
I need/want samba to be active on both interfaces so the first solution below is not applicable. Perhaps I do not understand the Linux TCP stack very well, but it seems to me that if the socket (samba is TCP right?) connected through eth1 that traffic back to that host should go back through eth1, especially if the source is on the subnet to which eth1 is connected (but not in the subnet to which eth0 is connected). If samba is using UDP, then it seems it somehow decides to address the packets to the wrong IP ... perhaps there is only a single name for my client in its lists and it uses the first ip address for that client name? Anyway ... seems strange I have to solve this at the routing layer. A. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 06, 2004 1:17 PM To: Andrew Athan Cc: [EMAIL PROTECTED] Subject: Re: [Samba] Traffic going to wrong interface? assuming you are using linux: Have you tried the below GLOBAL setting? interfaces = 172.16.92.245 This asks samba to listen on that interface only, I don't know if it will also force samba to use this interface as the source for any outbound connections. Making the gigabit interface your primary interface may also work. You might be able to kludge this from within the /etc/modules.conf file if you are using modules to drive the cards. alias eth0 tg3 alias eth1 e100 Then there is the route method. you can add static routes to the client. Host routes are honored over network routes. I'd use this as a last resort, it seems wrong. route add -host 172.16.92.245 eth0 I have a few more but I think one of these might work. good luck with it. peace. Andrew Athan wrote: If I connect via \\gige.ethernet.address\foo , and copying a large file, windows reports outbound traffic on the gige port and return traffic on the 100Meg port. Thus, it seems the samba server sees the client-server traffic via gige but is responding via the slower interface. Not what I want. -- UNIX is user friendly, it's just selective about who its friends are. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
