I want to bond two NIC to the same IP, I was able to do this for Static IP but not DHCP.
Does anyone have any idea about the possibility of this?
The process at which i reached to this question is explained here:
http://ubuntuforums.org/showthread.php?t=1645440
Yes, another newbie question. Just loaded and updated FC 10. Everything works great with dhcp. Tried to setup static ip to learn more about how to set it up and nothing seems to work. I'm connected to DSL via a router when I ifconfig I get:(basic stuff)inet addr: 192.168.1.7 Bcast: 192.168.1.255 Mask: 255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
I have also tried default gateway 192.168.1.255 and 192.168.1.254.Most of what I have tried above has come from linux websites and faq's.Keeping in mind I am worst than any new newbie you have ever worked with
I'm pulling my hair out to figure out what's gone wrong. I have a small home network with a router and 4 computers, 3 linux boxes and 1 windoze machine.The windoze machine and 2 of the linux boxes (newer ones, one with FC11 and the other with Ubuntu Hardy) are using the router's "Set Static IP" option just fine. However an older FC5 machine I have always gets its IP assigned randomly. As this is the machine I ssh into from overseas via a Dynamic DNS, this is a huge frustration when the power goes off or I need to restart the machine. It's usually 192.168.0.2 but sometimes 192.168.0.3 and occasionally other numbers as well. It _should_ be 192.168.0.130. As near as I can tell, I'm doing everything the same between the machines. The router config is very simple and works for the other systems so I suspect I may have a legacy tweak that I did years ago that's causing the problem.
Anyone know what I can try? I'm afraid I'm not a networking guru (ahem, wouldn't be posting if I were!) so things like "check the this" will be more helpful if there's a clear example. "Check the this...emacs /etc/thisfile/config" and see if XYZ option is TRUE" is far more useful. Again, many thanks. If none of the systems were working right then it would be totally different...but 3 seem to work just fine and happily get their assigned static IPs. It's the one non-conformist that's the trouble...
Ubuntu 9.10 2.6.31-17-generic
ISC DHCPd version 3.1.2
The DHCP service starts fine on boot and with manual start then works fine for about 4-5 hours. After that it just stops on its own. I start the service up and everything works fine for about 4-5 more hours untul it stops again.
What do I need to do to ensure that the service will stay uo 24x7x365?
I am running FC10, How to NIC bonding ..
View 1 Replies View RelatedI just put a pfSense firewall inbetween my ADSL router and my LAN. It's configured to have a cachng DNS server and a DHCP server. Among other things. For reasons beyond this post the address range served by DHCP changed from 10.0.0.x to 192.168.1.x. The new DHCP server gives 192.168.1.1 as gateway and DNS server name and not the public IP addresses of our internet provider.
After reconnecting our client machines everything worked just fine on the win-xp boxes, but the Debian Squeeze servers and Ubuntu 10.4 clients all started to get network timeouts. If I ping public websites it works but browsing to the same servers fails. Other services like POP3 and IMAP also fails. All machines use WiFi to connect and the access point is the same as before.
What could it be that make the debian boxes fail? My laptop runs squeeze too and also fails. But when connecting to various other access points at hotels and such I do not get this problem.
Another weird thing is that the debian server running virtualbox cannot do things online but the virtual windows boxes running on this machine can. Weird! Where should I start looking? How is networking/dhcp clients on Debian different from Windows XP?
Back in April I set up a Ubuntu DHCP server and a multiple VLAN network [URL] to migrate our various servers, workstations, etc off the 192.168.1.1 /24 network that everything was on because we where running out of address space. I built out the new network and everything worked great except our AD server would never get an IP address from the DHCP server (static reservation) and even if I set the IP statically on the AD server it couldn't ping the gateway and noone could log in. After several attempts to resolve this, including bringing in outside help, we where never able to figure out what the problem was.
Now 6 months later I have time to revisit the issue without effecting the live network. I used Acronis and imaged the AD server last Friday, cloned it on to another box with the same hardware, and put it up on the new network that's been sitting unused for the last 6 months. Today when I statically set the IP on the AD server (which is what I want) it connects and I can ping it's gateway 192.168.1.1 and all the way across vlans to a test sales agent workstation at 192.168.8.xxx on vlan 800 but only if I statically assign the agents station an IP address. When I try to get an IP address via DHCP it fails as destination unreachable. Nothing has changed in the last 6 months on the DHCP server but now it for some reason can't ping its default gateway 192.168.1.1. All of the config files are the same as they where left from the post linked above aside from the vlan id's used where changed from 1's to 100's (i.e. vlan 3 is now vlan 300) /etc/network/interfaces
Code:
auto lo
iface lo inet loopback
auto vlan100
iface vlan100 inet static
[code]....
why it can't reach the gateway, when I do a tcpdump I can see the DHCP requests come in on eth0 but the server never responds and I'm pretty sure its because it isn't "seeing" them since it thinks there isn't a network connection but I don't know how to trouble shoot to find out where the problem lies.
Back in April I set up a Ubuntu DHCP server and a multiple VLAN network [URL] to migrate our various servers, workstations, etc off the 192.168.1.1 /24 network that everything was on because we where running out of address space. I built out the new network and everything worked great except our AD server would never get an IP address from the DHCP server (static reservation) and even if I set the IP statically on the AD server it couldn't ping the gateway and noone could log in. After several attempts to resolve this, including bringing in outside help, we where never able to figure out what the problem was.
Now 6 months later I have time to revisit the issue without effecting the live network. I used Acronis and imaged the AD server last Friday, cloned it on to another box with the same hardware, and put it up on the new network that's been sitting unused for the last 6 months. Today when I statically set the IP on the AD server (which is what I want) it connects and I can ping it's gateway 192.168.1.1 and all the way across vlans to a test sales agent workstation at 192.168.8.xxx on vlan 800 but only if I statically assign the agents station an IP address.
When I try to get an IP address via DHCP it fails as destination unreachable. Nothing has changed in the last 6 months on the DHCP server but now it for some reason can't ping its default gateway 192.168.1.1. All of the config files are the same as they where left from the post linked above aside from the vlan id's used where changed from 1's to 100's (i.e. vlan 3 is now vlan 300) /etc/network/interfaces
Code:
auto lo
iface lo inet loopback
auto vlan100
[code]....
why it can't reach the gateway, when I do a tcpdump I can see the DHCP requests come in on eth0 but the server never responds and I'm pretty sure its because it isn't "seeing" them since it thinks there isn't a network connection but I don't know how to trouble shoot to find out where the problem lies.
I am puzzled with trying to configure a linux (openSUSE) client to dhcp to eBox DHCP server. I am using dhclient to lease an IP address with dhclient eth0 -s 10.45.48.108 and get a response
openSUSE11232CL1 dhclient: DHCPDISCOVER on eth0 to 10.45.48.108 port 67 interval 4
openSUSE11232CL1 dhclient: DHCPOFFER from 10.45.48.108
openSUSE11232CL1 dhclient: DHCPREQUEST on eth0 to 10.45.48.108 port 67
openSUSE11232CL1 dhclient: send_packet: Network is unreachable
openSUSE11232CL1 dhclient: send_packet: please consult README file regarding broadcast address.
The server reports eBox141 dhcpd: DHCPDISCOVER from 00:0c:29:3e:57:a3 (openSUSE11232CL1.domain.net) via eth0
eBox141 dhcpd: DHCPOFFER on 10.45.200.2 to 00:0c:29:3e:57:a3 (openSUSE11232CL1.domain.net) via eth0
I interpret this as the server receives the request and the client accepting it but the lease does not last long and the connection breaks. what this could be and why the connection breaks? Or my undestanding is totally wrong on how it works and should work? And BTW, where is that README file that's referenced in the message I receive on the client?
Currently I have my eth0 interface getting a DHCP address but at times the DHCP server will not be reachable. Sooo what I would like my server to do is if it cannot find a DHCP server assign a static address to eth0. Then start the DHCP service so it can then dish out some addresses.How can I do this? Surely it is possible
View 2 Replies View RelatedI've run across a few threads in the archived forums regarding nic bonding. I could be wrong but I imagine most of the people that are looking at bonding are probably really wanting what they would get out of creating a LAG between their Ubuntu Server and a managed switch capable of LACP trunks. If you have two NICS on your ubuntu server and want 2gps throughput & failover check out the page on creating a LAG. Obviously this requires your switch to be compatible though. [URL]...
View 1 Replies View RelatedI installed Fedora 10 and used dynamic IP first. Then I found out that bonding works with static ip only so I switched to static IP. But then, since I have 3 NIC cards, I configured bonding. I need help in these points:
1- steps to follow so that I switch from dynamic to static IP
2- steps to follow so that I configure bonding
I have 2 Net connection and 2 NIC. I want to know how to make bonding for that. I am using Ubuntu Server Natty 11.04 - 64bit
[code]....
Is it possible to make Bonding?
I am seeing an issue on a few servers where it doesn't appear all NICs in the 802.3ad lag are all operating at the same level. A few of the servers have two bonds each with two NICs in each bond.I have two NFS servers that each has 1 bond with 3 NICs.All are RHEL5 x64 2.6.18.I think the reason why I see one interface dominating RX and another dominating TX is due to the xmit_hash_policy but there are three hosts that use this particular server for network traffic.That's 3 different physical mac addresses.The layer2 algorithm should be fine in that situation I would think.Would I just be better off with balance-rr?
View 3 Replies View Relatedis possible to use linux (especially slackware) to bond 2 (ethernet modems) adsl connections. For example if i have 2 connection of 24mbs download and 512 upload i will create achieve 48 mgps dowload and 1 mgps upload . something like that
adsl1 modem <------ eth1--- (slackbox router) --- eth0---> my server
adsl2 modem <------ eth2----
I am confused as to what is going on with a particular box that I am working with.As you can see in the attached ifconfig print out, one eth port is basically only used as a output while the other is only really used as an input.I connect to the box via 10.20.40.104 for ssh,ftp,http,etc.I just want to know the name of what is happening (is it bonding,bridging?) and maybe some information about where it is configured.I looked in modprobe.conf
eth0 Link encap:Ethernet HWaddr 00:1E:C9:EE:5A:91
inet addr:10.20.40.105 Bcast:10.20.40.255 Mask:255.255.255.0
inet6 addr: fe80::21e:c9ff:feee:5a91/64 Scope:Link
I'm having some problems bringing up my wireless card at boot time on my Red Hat Linux 9.0 box. After some investigation with the boot scripts, I noticed that it was having problems with the DHCP negotiations when the ifup wlan0 command is issued.I then tested the command outside of the booting process and everytime the command is issued the first time, the dhclient fails to get any DHCP offers and returns with the message Unable to obtain a lease on first try. Exiting. and then exits.
If I then issue the same ifup command again a second time, it successfully receives a DHCP offer from the router and receives the needed IP address, and after this, the Internet connection on the box works fine. It is consistently doing this everytime. Why is it failing to obtain a lease the first time?
I have a question about bonded NICs and the switches they are connected to.
I have a server which needs to send a lot of data to another server quickly. Both have multiple GbE NICs. I understand what is required at the server end (I think) in that a pseudo-interface is created such as bond0 with the IP applied to that interface rather than eth0 and eth1.
My question relates to the connection between the servers, i.e. the switch. Is a specific type of switch required for this to work, as an IP will have 2 (or more) MAC addresses associated with it, or how does the switch decide to which port to route the traffic for the bond0 IP?
Also, will this only work when multiple connections are being made? What I mean is, will each individual TCP connection only use either the physical eth0 OR the physical eth1 interface, or can a single connection make use of the aggregated bandwidth, sending one packet to one physical interface and another to the other physical interface, using the bond0 IP as the destination?
What I am trying to work out is if I had a storage server connected to an application server and exporting storage using NFS or GlusterFS, would an aggregated link improve throughput?
I have 4 DSL modems connected with 4 different ISP's my scenario is
a) My FC-2 machine with LAN IP=192.168.10.1 and Bond0 IP=192.168.1.1
b) Modem-A LAN IP= 192.168.1.2 , ext IP=xxx.xxx.xxx.xxx
c) Modem-B LAN IP=192.168.1.3, ext IP=xxx.xxx.xxx.xxx
d) Modem-C LAN IP=192.168.1.4, ext IP=xxx.xxx.xxx.xxx
e) Modem-D LAN IP=192.168.1.5, ext IP=xxx.xxx.xxx.xxx
Modem-A, B, C, and D LAN connected with my FC-2 machine, and all 4 interfaces of my machine are in Bond0, Now please help me what default Gateway I should set in my FC-2 machine?>??? or I have to set 4 gateways in my machine?and will this configuration works?
I'm trying to set-up a back-up (mode 1) bonding nic. I can't ping the LAN, pinging bond0 locally however works. Here is my config:
/etc/modprobe.conf
Code:
alias eth0 e1000e
alias eth1 e1000e
alias eth2 e1000e
alias eth3 e1000e
alias scsi_hostadapter ahci
alias scsi_hostadapter1 usb-storage
alias bond0 bonding
[Code].....
As Xen is based on LINUX I'm hoping that someone out there could help me. I'm struggling with 802.3ad on a cisco switch (LACP). I'm going to be using this for my storage network on a dedicated cisco switch talking to a teamed pair of intel NIC's ISCSI storage. From the intel side I can set them to Link aggregated one team 2GB this is fine and my config shows active active on the NICs. How would I go about doing this from a LINUX box. In order to remove any bottle necks it needs to be active active from Xen. If I do a pif-forget uuid= on a XEN server I'm in complete control using Linux.
View 9 Replies View RelatedI instaled HPML350 G6 server. I would like to configure ethernet fail over. I got the script from my friend and configured and restarted the network services. I am getting the error message that ""Deprecated configure file /etc/modprobe.conf, all config files belonging to /etc/modprobe.d". System automatically assigning IP address also.
View 2 Replies View RelatedI just set up NIC bonding in Ubuntu 10.4, following these instructions, and I've got it working except for one problem: Every time I up or down a network device, or every time the system reboots, my routes go all to hell with eth0 and eth1 entries next to my bond0 entries. When the eth0 and eth1 entries show up, my connection is hosed and I have to go in via the maintenance IP to kill each route one at a time, leaving only bond0. Here's how I want my routes to look at all times:
Code:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.87.9.0 0.0.0.0 255.255.255.0 U 0 0 0 bond0
0.0.0.0 10.87.9.1 0.0.0.0 UG 100 0 0 bond0
Here's my /etc/network/interfaces:
[Code]...
Just for the learning sake, I was going through this document for Bonding of Two Ethernet Cards for Fault-Tolerance (active-backup). Here, /etc/modprobe.conf is as
Code:
alias bond0 bonding
options bond0 mode=1 arp_ip_target=192.168.1.1 arp_interval=200 primary=eth0
Now, I just wanted to to know,
- What parameter is arp_ip_target and why it is used.
- Why the IP is 192.168.1.1, whereas the IP in /etc/sysconfig/network-script/ifcfg-bond0 is 192.168.1.5.
- Can I use the below /etc/modprobe.conf ?
Code:
alias bond0 bonding
options bond0 miimon=100 mode=1 primary=eth0
Upgraded a school network from FastEthernet to GigabitEthernet. Broke the network up into VLANs. Discovered that the router (Cisco 2821) could only route between the VLANs at around 400Mb/s. Tested out some layer three switches. They work very nicely, but are more than we need. So I started putting some spare equipment we had together as a Linux router.
Result: Underwhelmed. The machine has two Intel GigE interfaces. With the machine configured to route between two test VLANs I get about 855Mb/s with a single interface (all VLANs trunked over the single interface). That's about what I'd expect. Maybe a little low. With the two interfaces bonded, I get about the same.
For testing, I set up eight Windows machines, four on each VLAN. The Linux router is the only machine that can route between the two VLANs. I used Iperf to generate traffic and measure throughput between pairs of machines. Two machines on the same VLAN get about 300Mb/s between themselves. With the four machines organized into cross-VLAN pairs, I get about 855Mb/s total throughput on a single interface and very slightly more with two interfaces bonded.
The Linux router has an Intel Xeon E5506 CPU running at 2.13GHz and these are Intel GigE interfaces (built-in). I would expect to get a large boost by adding the second interface. I've confirmed that bonding is working (by pulling either of the cables and watching everything continue to function).
I am running RHEL 5.3 on a blade server w/ 2 NICs that are bonded. I have 2 VLANs that I am trying to configure. I have created the network-scripts ifcfg-bond0.<vlan#>. I can ping the device but the gateway won't ping. I am in console mode so cutting and pasting output doesn't work.
View 2 Replies View RelatedIs it possible to bond an existing bond. I have 4 nics assigned to 2 bonds for link aggregation. ie
e1000g0 - bond1 - mode =4
e1000g1 - bond1 - mode =4
e1000g2 - bond2 - mode =4
e1000g3 - bond2 - mode =4
I would have presumed that you have 2 x agregates giving 2 x 2gig links and the resilience is that if one nic fails in either bond you carry on with that bond running a 1 gig link until fixed. But, our architect wants to have an active/passive (mode 1) accross bond2 and bond3. I have setup tons of mode 1 bonds and mode 4 bonds but never tried bonding 2 x mode 4 bonds!
On my previous release *cough* if inenslave was needed, bonding instructions didn't work through aggregation did.
cat /etc/network/interfaces
auto lo
iface lo inet loopback
auto bond0
iface bond0 inet static
address 192.168.1.149
netmask 255.255.255.0
gateway 192.168.1.1
dns-nameservers 127.0.0.1
broadcast 192.128.1.255
post-up ifenslave bond0 eth0 eth1
pre-down ifenslave -d bond0 eth0 eth1
#auto wlan0
#iface wlan0 inet dhcp
#netmask 255.255.255.0
#wpa-conf /etc/wpa_supplicant.conf
For some reason the unmentioned former disto, I could not get wireless networking under this configuration and a simple wlan0 interface, in case either cable were to sever it would retain a wireless. The bonding was done for speed, and I believe I can't get faster than mode=4.
We run redundant switches that two nic's on each server connect to. We also run bonding on our servers. Because we have two switches, we can't run lacp or anything. If a switch goes into a crashed state where it doesn't pass traffic but still provides link, bonding thinks the interface is still up and thus will still send traffic through it. Does anybody know a better way to configure the fail over of the interface? This would be a similar situation to somebody using a media converter.
View 1 Replies View RelatedI'm trying to configure my Red Hat server to use port bonding for two interfaces going to a switch, and I followed this redhat guide [URL]...-redhat-server but when I attempt to bring the bond up, it simply uses mode 0 (round robin) instead of mode 1, which I specifically configured in /etc/modprobe.conf by doing
Code:
options bond0 mode=1
Any ideas why the bond would continue to use round robin when I set it to active-backup?