Re: Slightly OT: Setting the primary NIC
I had the same problem, with a different app, But needed to swop my primaty NIC with another one, as my apps Bound to the wrong NIC How to Set the Primary NIC on a Windows 2000 XP Use this procedure to determine and set the primary NIC on a Windows 2000 Server: 1. Right-click the Network Neighborhood /my network places icon and choose Properties. 2. From the menu of the Network and Dial-up Connections window, choose Advanced Advanced Settings. 3. On the Adapter and Binding tabs, in the Connections area, ensure that the primary NIC is listed first. You can click the Move Up or Move Down buttons to arrange the adapters and select your primary NIC. 4. From a DOS prompt, issue the ipconfig /all command to verify that your selected primary NIC appears first in the list. Hope this helps Cheers C
Re: Slightly OT: Setting the primary NIC
On Sunday 21 March 2004 10:20, Sven Riedel wrote: Hi, Can anyone tell me how I can tell the machine which NIC is the primary? If your looking for a way to determine which NIC is which then maybe nameif(8) is what your looking for. -- Ole-Christian S. Hagenes
Slightly OT: Setting the primary NIC
Hi, I'm struggeling with a problem on a multi-homed host running debian, and as the problem is somewhat security related, I hope you'll tolerate the question on this list :) Anyway, the Host has an internal NIC and an external NIC (acting among other things as a firewall). For some reason, all services think the external NIC is the primary, and will try to bind to that/all requests from samba/cups etc have a source IP from the external NIC, which complicates the setups of the internal hosts. I've tried switching the order in which the modules for the NICs are loaded (eth0 became eth1 and vice versa), the order in which the NICs are activated with ifup and some other things, to no avail. I haven't found anything at the debian site wrt this problem either - all I can say is that the old distribution on the machine didn't have this problem (but that was the only saving grace of that distro). Can anyone tell me how I can tell the machine which NIC is the primary? Regs, Sven -- Sven Riedel [EMAIL PROTECTED] Liebigstr. 38 30163 Hannover Python is merely Perl for those who prefer Pascal to C (anon) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Slightly OT: Setting the primary NIC
On Sun, Mar 21, 2004 at 10:20:06AM +0100, Sven Riedel wrote: I'm struggeling with a problem on a multi-homed host running debian, and Well, it's not actually multi-homed. I'll bet both of your NIC's are contained inside the same ASN and that they aren't even running BGP ;-) Anyway, the Host has an internal NIC and an external NIC (acting among other things as a firewall). For some reason, all services think the external NIC is the primary, and will try to bind to that/all requests from samba/cups etc have a source IP from the external NIC, which complicates the setups of the internal hosts. Many daemons have config statements for binding to particular ports. You'll have to set them up on a case by case basis. Most of them will bind by default to all ip's defined for the host. -- -- Dale Amon [EMAIL PROTECTED]+44-7802-188325 International linux systems consultancy Hardware software system design, security and networking, systems programming and Admin Have Laptop, Will Travel -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Slightly OT: Setting the primary NIC
On Sunday, 2004-03-21 at 10:20:06 +0100, Sven Riedel wrote: I'm struggeling with a problem on a multi-homed host running debian, and as the problem is somewhat security related, I hope you'll tolerate the question on this list :) This isn't freebsd-security ;-) Anyway, the Host has an internal NIC and an external NIC (acting among other things as a firewall). For some reason, all services think the external NIC is the primary, and will try to bind to that/all requests from samba/cups etc have a source IP from the external NIC, which complicates the setups of the internal hosts. Are yousaying packets are being sent out of your internal interface with the source address set to that of the external interface?!? That should not happen. Please supply the output of ifconfig -a and netstat -an. I've tried switching the order in which the modules for the NICs are loaded (eth0 became eth1 and vice versa), the order in which the NICs are activated with ifup and some other things, to no avail. I haven't found anything at the debian site wrt this problem either - all I can say is that the old distribution on the machine didn't have this problem (but that was the only saving grace of that distro). You are most definitely looking in the wrong place. Can anyone tell me how I can tell the machine which NIC is the primary? There is no such thing as a primary NIC. Unless a daemon explicitly binds a socket to a specific IP address and send a packet through that socket, the source IP address is set to that of the interface the packet is sent on. So you have a weird configuration for sure. Lupe Christoph -- | [EMAIL PROTECTED] | http://www.lupe-christoph.de/ | | Violence is the resort of the violent Lu Tze | | Thief of Time, Terry Pratchett | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Slightly OT: Setting the primary NIC
On Sun, Mar 21, 2004 at 11:58:00AM +0100, Lupe Christoph wrote: Can anyone tell me how I can tell the machine which NIC is the primary? There is no such thing as a primary NIC. Unless a daemon explicitly binds a socket to a specific IP address and send a packet through that Could it be that he means the NIC that the default route applies to? netstat -rn would show that. -B -- Brandon High [EMAIL PROTECTED] ZX-7R Wasabi, '02 BMW R1150RS Troll I'm at an age where it's healthy to develop a debilitating chemical dependence. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Slightly OT: Setting the primary NIC
On Sunday, 2004-03-21 at 03:17:45 -0800, Brandon High wrote: On Sun, Mar 21, 2004 at 11:58:00AM +0100, Lupe Christoph wrote: Can anyone tell me how I can tell the machine which NIC is the primary? There is no such thing as a primary NIC. Unless a daemon explicitly binds a socket to a specific IP address and send a packet through that Could it be that he means the NIC that the default route applies to? netstat -rn would show that. I doubt that. he couldn't reach the others machine if the packets went the default route. Sven? Lupe Christoph -- | [EMAIL PROTECTED] | http://www.lupe-christoph.de/ | | Violence is the resort of the violent Lu Tze | | Thief of Time, Terry Pratchett | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Slightly OT: Setting the primary NIC
On Sunday 21 March 2004 10:20, Sven Riedel wrote: Hi, Can anyone tell me how I can tell the machine which NIC is the primary? If your looking for a way to determine which NIC is which then maybe nameif(8) is what your looking for. -- Ole-Christian S. Hagenes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Slightly OT: Setting the primary NIC
Hi, I'm struggeling with a problem on a multi-homed host running debian, and as the problem is somewhat security related, I hope you'll tolerate the question on this list :) Anyway, the Host has an internal NIC and an external NIC (acting among other things as a firewall). For some reason, all services think the external NIC is the primary, and will try to bind to that/all requests from samba/cups etc have a source IP from the external NIC, which complicates the setups of the internal hosts. I've tried switching the order in which the modules for the NICs are loaded (eth0 became eth1 and vice versa), the order in which the NICs are activated with ifup and some other things, to no avail. I haven't found anything at the debian site wrt this problem either - all I can say is that the old distribution on the machine didn't have this problem (but that was the only saving grace of that distro). Can anyone tell me how I can tell the machine which NIC is the primary? Regs, Sven -- Sven Riedel [EMAIL PROTECTED] Liebigstr. 38 30163 Hannover Python is merely Perl for those who prefer Pascal to C (anon)
Re: Slightly OT: Setting the primary NIC
On Sun, Mar 21, 2004 at 10:20:06AM +0100, Sven Riedel wrote: I'm struggeling with a problem on a multi-homed host running debian, and Well, it's not actually multi-homed. I'll bet both of your NIC's are contained inside the same ASN and that they aren't even running BGP ;-) Anyway, the Host has an internal NIC and an external NIC (acting among other things as a firewall). For some reason, all services think the external NIC is the primary, and will try to bind to that/all requests from samba/cups etc have a source IP from the external NIC, which complicates the setups of the internal hosts. Many daemons have config statements for binding to particular ports. You'll have to set them up on a case by case basis. Most of them will bind by default to all ip's defined for the host. -- -- Dale Amon [EMAIL PROTECTED]+44-7802-188325 International linux systems consultancy Hardware software system design, security and networking, systems programming and Admin Have Laptop, Will Travel --
Re: Slightly OT: Setting the primary NIC
On Sunday, 2004-03-21 at 10:20:06 +0100, Sven Riedel wrote: I'm struggeling with a problem on a multi-homed host running debian, and as the problem is somewhat security related, I hope you'll tolerate the question on this list :) This isn't freebsd-security ;-) Anyway, the Host has an internal NIC and an external NIC (acting among other things as a firewall). For some reason, all services think the external NIC is the primary, and will try to bind to that/all requests from samba/cups etc have a source IP from the external NIC, which complicates the setups of the internal hosts. Are yousaying packets are being sent out of your internal interface with the source address set to that of the external interface?!? That should not happen. Please supply the output of ifconfig -a and netstat -an. I've tried switching the order in which the modules for the NICs are loaded (eth0 became eth1 and vice versa), the order in which the NICs are activated with ifup and some other things, to no avail. I haven't found anything at the debian site wrt this problem either - all I can say is that the old distribution on the machine didn't have this problem (but that was the only saving grace of that distro). You are most definitely looking in the wrong place. Can anyone tell me how I can tell the machine which NIC is the primary? There is no such thing as a primary NIC. Unless a daemon explicitly binds a socket to a specific IP address and send a packet through that socket, the source IP address is set to that of the interface the packet is sent on. So you have a weird configuration for sure. Lupe Christoph -- | [EMAIL PROTECTED] | http://www.lupe-christoph.de/ | | Violence is the resort of the violent Lu Tze | | Thief of Time, Terry Pratchett |
Re: Slightly OT: Setting the primary NIC
On Sun, Mar 21, 2004 at 11:58:00AM +0100, Lupe Christoph wrote: Can anyone tell me how I can tell the machine which NIC is the primary? There is no such thing as a primary NIC. Unless a daemon explicitly binds a socket to a specific IP address and send a packet through that Could it be that he means the NIC that the default route applies to? netstat -rn would show that. -B -- Brandon High [EMAIL PROTECTED] ZX-7R Wasabi, '02 BMW R1150RS Troll I'm at an age where it's healthy to develop a debilitating chemical dependence.
Re: Slightly OT: Setting the primary NIC
On Sunday, 2004-03-21 at 03:17:45 -0800, Brandon High wrote: On Sun, Mar 21, 2004 at 11:58:00AM +0100, Lupe Christoph wrote: Can anyone tell me how I can tell the machine which NIC is the primary? There is no such thing as a primary NIC. Unless a daemon explicitly binds a socket to a specific IP address and send a packet through that Could it be that he means the NIC that the default route applies to? netstat -rn would show that. I doubt that. he couldn't reach the others machine if the packets went the default route. Sven? Lupe Christoph -- | [EMAIL PROTECTED] | http://www.lupe-christoph.de/ | | Violence is the resort of the violent Lu Tze | | Thief of Time, Terry Pratchett |
