I previously set up an older version of the rolling release, but something happened my connection was getting disrupted so I started over… but apparently the commands I used the first time aren’t sufficient.
configure
set interfaces ethernet eth1 address 10.32.0.1/24
set interfaces ethernet eth1 description LAN
commit
save
set service dhcp-server shared-network-name LAN subnet 10.10.10.0/24 range 0 start 10.32.0.50
set service dhcp-server shared-network-name LAN subnet 10.10.10.0/24 range 0 stop 10.32.0.250
set service dhcp-server shared-network-name LAN subnet 10.32.0.0/24 name-server 10.32.0.1 # previously [name-server] was [dns-server]
set service dhcp-server shared-network-name LAN subnet 10.32.0.0/24 default-router 10.32.0.1
commit
save
at this point I’m stuck with the following error message:
No DHCP address range or active static-mapping configured within shared-network "LAN, 10.32.0.0/24"!
I don’t know where to go from here, any help would be appreciated
are you sure that you want to use 10.10.10.0/24 as network but then assigning range with different network?
Probably the best would be :
set service dhcp-server shared-network-name LAN subnet 10.32.0.0/24 range 0 start 10.32.0.50
set service dhcp-server shared-network-name LAN subnet 10.32.0.0/24 range 0 stop 10.32.0.250
ok, so maybe I didn’t copy the commands precisely from my original setup…
does this make sense?
configure
set interfaces ethernet eth1 address 10.10.10.10/24
set interfaces ethernet eth1 description LAN
commit
save
set service dhcp-server shared-network-name LAN subnet 10.10.10.0/24 range 0 start 10.10.10.50
set service dhcp-server shared-network-name LAN subnet 10.10.10.0/24 range 0 stop 10.10.10.250
set service dhcp-server shared-network-name LAN subnet 10.10.10.0/24 name-server 10.10.10.10
set service dhcp-server shared-network-name LAN subnet 10.10.10.0/24 default-router 10.10.10.10
commit save
set service ssh port 22
commit
save
You can check at os layer via cli, for example, with the command
ip a
From that you can see also the mac address of the two interfaces, then with wireshark with your laptop you can try to connect to one of the interfaces of the VyOS system and check the capture to identify the mac of the box.
Or in a more simple way, if not yet tested, just try to invert the cable. So connect the laptop to the interface that before was attached to the ISP and then analyze if something different is happening.
Then in a normal situation it would start to work. If no other strange issue are in … like physical problem on the interfaces or something like that