Generall: Carrier-Router without DHCP

I wan't to explain a situation we often have outside at our customers:

The Branchoffices have a SDSL-Line with a Router provided by the carrier. The Router provides an public IP Network (/29 or /30) on it's ethernet device, but NO DHCP. The carrier will not change the router configuration. For DHCP a second router is needed

Because i wan't to get rid of another spare router between ASG-RED a Provider-Router: Is there a solution to configure a fixed ip (dns and gateway) on the WAN interface of RED?

It would be very usefull for our deployment scenarios.

Parents

0 tom_01 over 15 years ago

If you know how to use confd-client ("cc"), you can edit the respective itfhw->red_server object to use static addressing:


127.0.0.1 OBJS > itfhw

127.0.0.1 OBJS itfhw > red_server

127.0.0.1 OBJS itfhw red_server >

MAIN                                                                 RAW                                                                  WIZARD

OBJS                                                                 REF_hZPMONnNkX[reds1 (Durlach Tom),itfhw,red_server]



127.0.0.1 OBJS itfhw red_server > REF_hZPMONnNkX[reds1 (Durlach Tom),itfhw,red_server]

Logged into object 'REF_hZPMONnNkX'. Use 'w' to write eventual changes.

{

          'split_networks' => [],

          'tunnel_id' => 1,

          'failover_direct' => 0,

          'manual_address' => '0.0.0.0',

          'unlock_code' => 'be1ebce5',

          'red_id' => 'A300000412EAC1E',

          'hardware' => 'reds1',

          'manual_netmask' => 24,

          'mac' => '31:af:9b[:D]6:4c:5e',

          'remote_cert' => 'REF_JXLJkFAKpS',

          'hub_hostname' => 'thekla.eurescom.eu',

          'manual_dns' => '0.0.0.0',

          'name' => 'reds1 (Durlach Tom)',

          'description' => 'Remote Ethernet Server Device',

          'comment' => '',

          'manual_defgw' => '0.0.0.0',

          'uplink_mode' => 'dhcp',

          'type' => 'red',

          'route_mode' => 'default'

        }

Set "uplink_mode" to "manual", and the "manual_*" options to your desired values.

You need to make sure that the device picks up the config, so you must boot it once in a DHCP-enabled environment (does not matter where that is).

/tom

Reply

0 tom_01 over 15 years ago

If you know how to use confd-client ("cc"), you can edit the respective itfhw->red_server object to use static addressing:


127.0.0.1 OBJS > itfhw

127.0.0.1 OBJS itfhw > red_server

127.0.0.1 OBJS itfhw red_server >

MAIN                                                                 RAW                                                                  WIZARD

OBJS                                                                 REF_hZPMONnNkX[reds1 (Durlach Tom),itfhw,red_server]



127.0.0.1 OBJS itfhw red_server > REF_hZPMONnNkX[reds1 (Durlach Tom),itfhw,red_server]

Logged into object 'REF_hZPMONnNkX'. Use 'w' to write eventual changes.

{

          'split_networks' => [],

          'tunnel_id' => 1,

          'failover_direct' => 0,

          'manual_address' => '0.0.0.0',

          'unlock_code' => 'be1ebce5',

          'red_id' => 'A300000412EAC1E',

          'hardware' => 'reds1',

          'manual_netmask' => 24,

          'mac' => '31:af:9b[:D]6:4c:5e',

          'remote_cert' => 'REF_JXLJkFAKpS',

          'hub_hostname' => 'thekla.eurescom.eu',

          'manual_dns' => '0.0.0.0',

          'name' => 'reds1 (Durlach Tom)',

          'description' => 'Remote Ethernet Server Device',

          'comment' => '',

          'manual_defgw' => '0.0.0.0',

          'uplink_mode' => 'dhcp',

          'type' => 'red',

          'route_mode' => 'default'

        }

Children

No Data