WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Any guesses why Google Compute Engine req manual route configuration?  (Read 926 times)

Offline as

  • WikiUser
  • *
  • Posts: 29
I have a tinycore image that I have booted on various clouds and xen VMs. Networking comes up OK except for on Google compute engine, where I have to add the following to bootlocal.sh:

sudo route add -net 10.240.0.0 netmask 255.255.0.0 dev eth0
sudo route add default gw 10.240.0.1 eth0

With the above entries the networking comes up fine. Obviously it would be better if explicit configuration wasn't required and instead it just worked from DHCP. DHCP must be working to some extent because the Tinycore instance is getting an IP address.

Can anyone suggest why it might be necessary to add the above lines to make the network come up?

thanks!

Offline hiro

  • Hero Member
  • *****
  • Posts: 1071
Re: Any guesses why Google Compute Engine req manual route configuration?
« Reply #1 on: October 25, 2015, 04:51:57 AM »
show me your "ip address" output, does the ip have a /16 or rather a /32 netmask ?

deeper investigation would be possible by runnuing tcpdump -i br0 -vvv -s 1500 port 67 or port 68

br0 being your interface
« Last Edit: October 25, 2015, 04:54:25 AM by hiro »