Skip to main content
formatting
Source Link
Jawa
  • 3.7k
  • 13
  • 32
  • 38

I'd suggest "permanently" editing the routing table. This way you can still use youyour DHCP configuration unaltered, while adding a routing option for your attached laptop without messing up its configuration:

route -p ADD <the IP of the laptop> mask 255.255.255.255 <your PC's IP> <some metric value> <your PC IP>

route -p ADD <the IP of the laptop> mask 255.255.255.255 <your PC's IP> <some metric value> <your PC IP>

Of course, if you so desire, you may opt for a subnet routing instead of a host route.

Hope it helps.

I'd suggest "permanently" editing the routing table. This way you can still use you DHCP configuration unaltered, while adding a routing option for your attached laptop without messing up its configuration:

route -p ADD <the IP of the laptop> mask 255.255.255.255 <your PC's IP> <some metric value> <your PC IP>

Of course, if you so desire, you may opt for a subnet routing instead of a host route.

Hope it helps.

I'd suggest "permanently" editing the routing table. This way you can still use your DHCP configuration unaltered, while adding a routing option for your attached laptop without messing up its configuration:

route -p ADD <the IP of the laptop> mask 255.255.255.255 <your PC's IP> <some metric value> <your PC IP>

Of course, if you so desire, you may opt for a subnet routing instead of a host route.

Source Link

I'd suggest "permanently" editing the routing table. This way you can still use you DHCP configuration unaltered, while adding a routing option for your attached laptop without messing up its configuration:

route -p ADD <the IP of the laptop> mask 255.255.255.255 <your PC's IP> <some metric value> <your PC IP>

Of course, if you so desire, you may opt for a subnet routing instead of a host route.

Hope it helps.