1 ethernet port, multiple virtual interfaces, multiple DHCP servers. How to set up?

Posted on 2004-10-27
Medium Priority
Last Modified: 2013-12-23
I have a laptop running FreeBSD 4.10 which has one ethernet port (fxp0)

I have so far configured the ethernet port and kernel to support three vlan virtual interfaces with static IPs. (vlan0, vlan1, vlan2). So far, I have got this working.

What I want to do now is make each of my vlan interfaces connect to a DHCP server to get their own IP adresses on different networks, but here's the catch: each vlan interface needs to connect to a different DHCP server.

I figure that since there's only one default gateway on the machine, all DHCP requests are going to end up at one DHCP server, therefore making all 3 virtual vlan interfaces get an IP from the same network. I don't want this to happen.

I know that in FreeBSD, rc.conf can be edited so that an interface gets its IP from DHCP (for example, ifconfig_fxp0="DHCP"

Is there any way I can set up rc.conf to get each virtual interface to point to a different DHCP server? If not, is there some set of commands I can use to do this?

Question by:Neo-Rio
  • 2
LVL 62

Expert Comment

ID: 12427445
DHCP is for ethernet and not for vlan.
VLAN is fot those whose ethernet switches decode it.

Please describe your problem in understandable manner with commands you run and errors you get ...

Author Comment

ID: 12429583
Ok, here's a more concise question:

Can I, or can I not, set a virtual vlan interface to receive an IP from a specified DHCP server within FreeBSD?

I can set an ethernet interface to receive DHCP with ifconfig_fxp0="DHCP".
If I do ifconfig_vlan0="DHCP", then no IP address is taken for the interface, and the vlan interface remains with no IP address.
LVL 62

Accepted Solution

gheist earned 750 total points
ID: 12431248
This is impossible.
vlan is not intended to work with DHCP
no dhcp client works with two differently configured DHCP servers
vlan is specific sub-protocol for ethernet, where frames are tagged with specific vlan-id, and then most likely, by a ethernet switch with vlan support, further mapped to distinct ethernet ports. this, for example, makes firewall in middle of corporate network wuite easily -  it is simply capable of decode data from every port on the switch etc.
i will confirm that no DHCP providers support vlan for their clients and connecting cables of two providers is basically against their AUP or so.
please buy network card, and stop dreaming about impossible things.

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If you’re involved with your company’s wide area network (WAN), you’ve probably heard about SD-WANs. They’re the “boy wonder” of networking, ostensibly allowing companies to replace expensive MPLS lines with low-cost Internet access. But, are they …
How to fix a SonicWall Gateway Anti-Virus firewall blocking automatic updates to apps like Windows, Adobe, Symantec, etc.
NetCrunch network monitor is a highly extensive platform for network monitoring and alert generation. In this video you'll see a live demo of NetCrunch with most notable features explained in a walk-through manner. You'll also get to know the philos…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …

593 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question