1

DHCP server for different VLANs [closed]

view story
linux-howto

http://serverfault.com – Possible Duplicate: How do I dynamically obtain IP addresses for VLAN interfaces? I am setting up a dhcp server to supply ip address for different VLANs of different subnet.(192.168.1.x for VLAN100, 192.168.2.x for VLAN200 and likewise for VLAN300)I have created VLANs 100,200,300 on eth0 on the ubuntu machine on which the dhcp server runs.I have configured the dhcp server to hear on all the virtual interfaces eth0.100 eth0.200 eth0.200.But when i run the dhclient for the interface eth0.100 ,how the server will recognize that this packet is from that particular interface? Will the dh ()

u85500's picture
Submitted by u85500 on 08/02/2012

Stories similar to DHCP server for different VLANs [closed]

I want to configure my eth0 interface using an external DHCP server (resident in my subnet), so I edited /etc/network/configure with the lines

auto eth0 iface eth0 inet dhcp

but I also want to use avahi autoconfiguration when the DHCP server is down.

So I tried ifup eth0 when the server is down, and after a certain amount of time it fails, but the interface eth0:avahi is correctly configured

I use Ubuntu, and I have many interfaces.

My first post here.

Relevant info:

Host OS: Windows 7 Home Premium 64-bits with VMware Workstation 8 Two VMs: Ubuntu Server 12.04 and Ubuntu Desktop 12.04

VMware NAT settings: Use local DHCP service is DISABLED Subnet IP: 192.168.2.0 Subnet mask: 255.255.255.0 Gateway IP: 192.168.2.2

On Ubuntu Server I have a DHCP server: isc-dhcp-server DHCP is working OK.

As the question title states, I wan't to classify my clients based on the interface their requests are coming from.

I use dhcp in /etc/network/interfaces: auto eth0 iface eth0 inet dhcp No network-manager installed.

This makes the dhclient run with option "-1":dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases -1 eth0 dhclient manpage: The -1 flag will cause dhclient to try once to get a lease.

I can't find answer about how linux processes incoming packets from different VLANs, that do not belong to a subnet assigned to a VLAN.

Imagine this situation. On Linux machine with the following configuration: eth0.100 - assigned address from 192.168.100.0/24 subnet (eg. 192.168.100.2) eth0.150 - assigned address from 192.168.150.0/24 subnet (eg.

I just did a recent install of Ubuntu Server 12.10 (no GUI, command line only) on a new system. I noticed that upon booting the server does not obtain an IP address from my router. However, once I log into the machine locally the server shows up on my list of DCHP clients and I can connect remotely without issue.

linux vlan routing 1 year 9 weeks ago

I've got this network topology:

network 192.168.100.0/24 vlan 100 network 192.168.200.0/24 vlan 200

one ubuntu server(2 vlans on 1 ether) eth0.100 (ip:192.168.100.10/24) eth0.200 (ip: 192.168.200.20/24 def gw 192.168.200.254)

Situation is next:

eth0.200 is up eth0.100 us down. connection from subnet 192.168.100.0/24 is ok to 192.168.200.20.

When i make eth0.100 up:

cannot access 192.168

Fedora 16 eth0 issues 31 weeks 3 days ago

Hi,

I'm currently going to school in a computer technician program and I'm in need of a some help to complete a lab. I currently have one f16 server and one f16 client running. They both have 2 interfaces.

eth0 = dhcp eth1 = static (private college network)

The issue I'm having is that my eth0 interface on my server isn't receiving any IPV4 address. My client is working fine.