Hidden option? dhcp-client to provide blank identifier?

Good evening,

I have a requirement at a client site running RouterOS 5.11 where in order to be provided an IP via DHCP by the ISP, they require the following:

    • Router’s WAN port to have a particular (provided) MAC address (supported in RouterOS)
  • Router’s WAN port to operate on VLAN 35 (supported in RouterOS)
  • Router’s DHCP client running on VLAN 35 (supported in RouterOS)
  • Router’s DHCP client must NOT provide a client identifier (impossible in RouterOS???)

Note: The above requirements are also discussed by others here: http://www.digitalhome.ca/forum/showthread.php?t=134496)

My main issue is that RouterOS insists in providing the DHCP server with a host name even if I set it to blank. As documented in the RouterOS Wiki, the DHCP Client will provide the client’s system identity if the host-name parameter is not set.

host-name (string; Default: ) > Host name of the client sent to a DHCP server. If not specified, client’s system identity will be used.

Using a basic Linux box, I’m able to get an IP from the client’s ISP no problem by using the following config:

ifconfig ethX hw ether 00:00:00:00:00:00 #replace with the MAC address provided by the ISP
ifconfig ethX up #bring up the WAN port
vconfig add ethX 35 #bring up VLAN 35 on the WAN port
vconfig set_flag ethX.35 1 1 #required to get the ISP's DHCP server to talk to you
dhcpcd -d -t 60 -R ethX.35 #acquire an IP address

Now, here are my questions:

  1. Is there a way to instruct the DHCP client to NOT provide a client identifier?
  2. What is the equivalent code in RouterOS to this piece of Linux code?
vconfig set_flag ethX.35 1 1

Any help is much appreciated.

Thanks,

Shaun

BUMP

has anyone been able to figure this out? i am testing my FiberOP connect from BELL as well and i cant get a IP from DHCP.

Ether1 → Used for WLAN Port
Mac:A8:39:44:9A:57:D2

VLAN3
MTU: 1500
ARP: Enabled
VLANID: 35
Interface: ether1
Use Service Tag: checked

DHCP Client:
Interface: Ether1(not sure if i should should use ether1 or vlan3???)
use Peer DNS: checked
Use Peer NTP: checked
Add Default Route: Yes
Default Route Dist: 0

Routes:
nothing set here for VLAN or Ether1 yet(do i need anything?)

Ok i was able to get it working with Bell Aliant FibreOP:

VLAN3
MTU: 1500
ARP: Enabled
VLANID: 35
Interface: ether1
Use Service Tag: unchecked

DHCP Client:
Interface: vlan3
use Peer DNS: checked
Use Peer NTP: checked
Add Default Route: Yes
Default Route Dist: 0

Hello, can you send us your config for FibreOP?

yes, the complete configuration is required as the presented information doesn’t explain all.
First of all there is no requirement for this VLAN3, not sure why this is here in that it clouds the issue.
I too have bell aliant fibre OP and the only requirement for internet is VLAN35.
One doesn’t have to clone any mac address either.

For my zyxel router its basically like cable setup initially with a few differences.

  1. setup WANX ethernet interface
  2. instead of assigned automatically, the DHCP client is set as STATIC with address of 0.0.0.0 and mask of 0.0.0.0
  3. Associate VLAN35 to WANX
    Then connect to the ISP and the VLAN being the client will pull an IP address after the handshaking.

I am trying to set this up on a HEX with no luck so far but just found this thread so will try some of the options delineated below.
The main issue I am having is NOT being able to assign the 0.0.0.0/0 and 0.0.0.0 in the hex settings be it IP address or DHCP client (for WAN).
I keep getting an error message saying improper address.

Finalement j’ai fini par trouver la manière de faire pour la configurations chez BELL

1 Set 2 VLAN sur l’interface WAN
vlan35 pour le pppoe
vlan36 pour le IPTV DHCP avec no default route.
2 Configurations du pppoe sur le vlan35.
3 Download multicast package et l’installer
4 Voir code

/routing igmp-proxy
set quick-leave=yes
/routing igmp-proxy interface
add interface=bridge-LAN-DATA
add alternative-subnets=239.0.0.0/8,10.0.0.0/8 interface=vlan36_IPTV upstream=yes

5 Ajouter une route 10.0.0.0/8 vers le gw recu du DHCP vlan36

J’espere de ne rien oublier.

Merci mon cher Botter,

je n’utilise pas la television. Seulement jai besoin du internet!

Pardon mon franglaise.

By the way, the IGMP proxy is very very important if one is to setup the router for The TV side of Bell Fibre OP. They use VLAN34 for this.
The important part is that its a separate IP negotiated on VLAN34, but the handshake includes IGMP traffic (wireshark).
The Zyxel USG series (older 40 etc) that I have added the IGMP proxy capability and they implemented EVERYWHERE in the routing process (except for the initial handshake).
So I couldnt use it for TV, which is a good thing as they are too expensive and dealing with streaming TV now anyway.