I'm trying to build a linux(fedora 12) dhcpd server(and gateway), that have 3 network cards(eth0 have with public ip, eth1 192.168.2.1 class and eth3 with 192.168.3.1 class).
Because I have just a switch, I want to put both cables(from eth1, eth2) in the switch. Every client has 2 network card(eth0, eth1). My question is, is there any way to conf eth0 to take from server ip from 192.168.2.1 class, and eth1 from 192.168.3.1? The internet will work only on eth0.
What I need is some information to be studied and learned by me in order to be able to create with Ubuntu Server an Internet Gateway Server. From my ISP I get about 50 public routable IPs through DHCP. Into my LAN I need to forward this public routable IPs to machines but I want to be able to manage bandwidth and also to be able to enable or disable Internet access for every client machine. Maybe with subnets? Maybe with dchp really? It would be nice if it would possible through DHCP!
I've got a machine running Ubuntu Server that is on several VLANs. Each VLAN has its own subnet and the server has an address on each subnet. The switches are set to allow tagged traffic to the server for each VLAN that it is on. Switch ports ending with workstations are given untagged ports on whatever VLAN is appropriate. Workstations are given addresses on a subnet for each VLAN via DHCP. All this works great and hosts on any subnet/VLAN can access the server as normal via its address on that subnet/VLAN.
Accessing the machine by its address on a non-local subnet is where I run into a problem. Inter-subnet traffic has to go through a router, which has been set up appropriately. Running tcpdump on the server and pinging it from a workstation on a subnet, using its address on a different subnet, shows the server receives the ping, but sends no response:
Code: sudo tcpdump -i vlan4 -n tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
i have two subnets with different gateways.i am thinking of connecting them via a linux server which would enable them to communicate.but i dont know how to proceed for getting this done.how should the connection be made and what should be the configuration settings on the linux server.
I have a Ubuntu server with multiple NICs and I'm just thinking about a potential scenario that might come up soon.
Imagine I have a network on floor 1 with an independent cable connection to my Ubuntu server -> switch -> assorted devices, on the subnet 192.168.0.x Now imagine friends upstairs have another independent network with cable -> router -> assorted devices, on subnet 192.168.1.x.
How can I set up my server to provide access for the 1.x subnet to the 0.x and vice versa. Ideally the devices all access internet from their appropriate subnet. I've read something about bridging, is this what I need?
I have one main subnet 192.168.50.0/24 with a defaultrouter 192.168.50.1 connected to the internet. I have an NFS server on that network. Everything is working as desired and machines are able to see each other and access the internet.
Now, I would like to add two more interfaces to the NFS server (running Slackware Linux), each on its own different subnet, say 192.168.51.0/24 and 192.168.52.0/24. The clients on those new subnets should also be able to access the internet (through the router 192.168.50.1). how to setup routing? Do I need any additional hardware router in between, or just a software configuration on the NFS server?
On a side note I have VLAN capable switches (couple of ProCurve 1800-24G) and would like to separate the three subnets using VLANs instead of using three separate switches.
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?
I am trying to setup a HP blade (BL460) server with 2 nics on sles10sp3. I want one nic to connect to a management vlan and and second to connect to the standard network. It should be possible for a desktop in the standard network to connect to either nic by providing the correct ip address.use this server as our first virtualisation hosts server using Xen. I dont want traffic used to upload / download images to the server through nic1 to effect the users traffic on the standard network on nic2. However any attempt at routing (which Im not good at) has led to the tx traffic all going out the default route (users subnet).
Each time I setup the nics via yast2 lan I can get the standard lan nic working ok. but cannot get the management nic working correctly. The server can ping a workstation on another vlan, but the workstation cannot ping the management nic. The default route appears to be forcing all traffic on the host out through this route, which I presume is normal behaviour. Using tcpdump I can see the ping packets received by the server, the server then responds through the default gateway, which the workstation does not see.
However, this normal behaviour will result in extra traffic on the users network when image downloads are initiated from the management interface.If I use a 172.24.1.0 network routed through 172.24.1.1 router setup as our management vlan , and 200.200.1.0 with router 200.200.1.1 as our lan for general users. Where server ips are nic1 10.1.1.10 and nic2 200.200.1.10 My workstation would be 200.200.1.10. If I ping the server at 10.1.1.10 I get no response. If I ping the server at 200.200.1.20 no problem.
Basically I used the network setup recommended by vmware to manage a virtual server. I actually have 4 nics, I thought by just talking about 2 nics the problem would be easier to explain. vmware specify that two nics should be used for management and two for the Lan. This is what I am trying to achieve, but both subnets must operate independently.
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
I have a firewall between two different subnets. The reason for the second subnet within the internal network is because I have a mail server that I want to protect. However, we need to make sure that the mail server can communicate with the internal network as well.
Mail server is 192.168.100.100 Firewall is 192.168.100.1 and 10.110.101.5 (and its gateway is 10.110.101.1 to the router)
I go to another workstation and ping the mail server. I can't. It times out. I do the same from the mail server. It times out as well.
I have a 2-floor house, with a single ethernet cable from the ground floor to the 1st. Downstair there is my ADSL modem, which is connected to the router upstair through this one cable. Now, I would like to have some more ethernet ports on the ground floor, but there's no room left to run another cable between the floors, so here's the big question: can I run both the modem-router connection and my regular LAN (which are on different subnets) through that one cable, with a switch at both ends?
To make it a little more clear, here is my present configuration
I have two subnets which I am interested in connecting.
Some basic network details:
Subnet A:
Subnet B:
I am trying to think of any further relevant details, but that seems to be it to me. If I forgot anything, please tell me.
Ok the question. WHAT do I type? (Explicitly!) And WHERE do I type it? In order to reach ubuntu-01.tec.lan, or ubuntu-02.tec.lan from perpetrator.tec.lan or rapine.tec.lan?
I'm interested in using actuall ROUTES. I can already achieve results similair to this with either a NAT firewall, or with VPN.. but that's not what I am interested in.
From what I have found out so far, I should need something like the following:
I have an embedded device for which I've created an html configuration page. This page allows you to set static IPs, dhcp, and can scan for wireless devices.My problem is that in order to access the device it requires that it runs as a dhcp server otherwise people are not assigned an IP and so can not access the embedded devices static IP. (This config page is for the laymen and so they are not the type who are able to set up their own static IPs). One of the potential options is to have the device connect to the network on eth0 acting as a dhcp client. However this prevents me from running a dhcp server.One solution I can think of is running a dhcp server only if it doesn't detect another dhcp server running on the network.
I have a network routing problem that I need to fix using a PC with ubuntu installed.
Here are the details of my problem: - I have two networks. - The first network is an ADSL router with subnet 192.168.1.x. I do not have access to the router nor change any of its configuration. - The second network has a subnet 172.26.x.x and connect via a wireless access point. Some of the devices connected to the network require to have static IPs. - I have a PC with ubuntu installed and two ethernet cards: one connected to the first network and the other connected to the access point. - I need to share the internet connection between the two networks using ubuntu. I already tried before on windows and the sharing worked when both networks were configured to use the same subnet. Once I changed the subnet of the second network, internet sharing stopped working.
Im having a issue with routing internet traffic from my router two different subnets (vlans).
Theres my setup:-
Server:
Both eth0,1 are running dhcp (two scoopes) that works fine!
The output of route -n is:
I have ip_forwarding on aswell, but i can ping the ip on the server running that dhcp scoope ie ping 192.168.4.1 works great but i just cant get the internet on the clients.
I have some CISCO,Linux related problem with 2 Class C subnets:
192.168.64.0 -> PC5 192.168.65.0 -> PC6
Here's a picture of my situation: [URL]
HQ has to have 2 STATIC routes in order those 2 "PCs" mentioned above to have end to end connectivity with NETWORK A and NETWORK B. Now I try with
route0 -> network: 0.0.0.0, mask: 0.0.0.0, nexthop: Serial 0/0/0 route1 -> network: 0.0.0.0, mask: 0.0.0.0, nexthop: Serial 0/0/1
And it seems to work but I don't think it's proper! I feel it's kinda wrong ... but all my other attempts to set another couple of static routes ends in "Request timed out" and thus connection lost.
We have a network of 20 boxes and the router dealt with DHCP, but I'm planning to assign the DHCP task to the linux box. Any heads up? eth card configuration, network topology... etc.?
I have 2 Ethernet connections, one (eth0) for the internet which gets set with dhcp, and one (eth1) for my internal network on which I have dhcp3-server running. I set eth1 to use static IP in interfaces, but every time I reset the network, it is fine for a couple of minutes, and switches over do being served by my own dhcp server on the same machine. (the interfaces file clearly says "iface eth1 inet static")
I reinstalled Ubuntu server, now, as always I have to start off with 8.04 then upgrade to 10.04, and I've never had a problem with this before on this machine or any other for that matter. The problem is, this time I have installed and Ubuntu installer cannot see a DHCP, I go a head and install anyway and fire up Ubuntu and there is no internet access, I have two network cards plugged in, when I type in ifconfig it shows only lo and no network cards, and yet when I check lspci ot shows both network cards are there and when either are plugger in it shows connection on both the connector at the stack end and on the router.
i have a homework where i have to set up a dhcp server on linux. I am using ubuntu. I tried following: [URL] However after running "sudo apt-get install dhcp3-server" the file "/etc/default/dhcp3-server" does not appear.
This is probably an odd request, but figured I'd ask in case someone knew. We have a lab that has the IP range 172.10.0.0/16 (255.255.0.0). The lab gateway/DHCP assigns an IP in the range of 172.10.0.2-172.10.0.254. I want to set up my own DHCP server on a specific range, for example 172.10.10.1-172.10.10.254. I create a new host fine, but since it's set for DHCP, it uses the DHCP server at 172.10.0.1. Is there a way to force it to use a different DHCP server on the client side? I realize that I can work around this with exclusions on the 172.10.0.1 DHCP server, or use iptables to deny DHCP requests to specific MACs, but wanted to know if there was an (easier?) way to configure the client to use the 172.10.10.1 DHCP server instead of the 172.10.0.1 server?
I have a scenario where a Debian (in this case) device will be connected to an existing LAN.What I then want said box to do, is to query the LAN to see if there is an existing DHCP server present. If there isn't one - then simply use the Debian box as the DHCP server (which works fine atm).If there is an existing one - I need the Debian box to be able to turn off it's own internal one and get it's details from the existing server (ie. change from server to client).
These action will need to be sat in the background as well - just in case another DHCP server appears on the LAN after this box does. Don't shoot me for saying it - but I know Windoze server does this. Is there a 'script/util' that anyone knows of (I am trying to do this auto-magically)?
when the machine rebooted, eth0 has the ip address 192.168.24.234. But if executing 'dhclient', eth0 will get the ip address 10.200.34.208, which is my expected ip address. I'm not quite familiar with networking things. I don't know what's going on there. Why should I need to execute 'dhclient' to obtain the expected ip address? Is there any way to obtain the ip address 10.200.34.208 right after host boot?
