General TC > Tiny Core on Virtual Machines
Installed TC on VMWARE 6.7 with open-vm-tools but tools are not running
LeonStraathof:
Yeah stateless is great when you have a task for a machine it just has to do until the end of times. Build once and after that just use. Since VMware dropped support of Linux network drivers which everybody dislikes but for VMware's point of view is understandable. I got the idea to just let the network interfaces live in it's own habitat with a real Linux kernel. So for the the question if routing is the same as bridging the answer is no it is not the same. When you bridge 2 interfaces both ends connect 2 networks 2 become 1 subnet. So if on one side of your bridge you have a dhcp server it can serve ip addresses to machines at the other side of the bridge. Most used home user scenario is when you put your isp's modem in bridge and putting your own router behind it. The wan port of your own router will get public internet ip address. The static configured ip of the bridge machine itself can still be used to connect to the bridge machine for configuration if needed. I don't think i will need configuration trough network though as i plan to build everything preconfigured in a stateless machine.
On Debian i build something by doing these easy steps:
--- Code: ---apt install bridge-utils
Edit: /etc/network/interfaces
auto lo br0
iface lo inet loopback
iface eth0 inet manual
iface eth1 inet manual
iface br0 inet static
bridge_ports eth0 eth1
address 192.168.111.1
netmask 255.255.255.0
gateway 192.168.111.3
--- End code ---
In this example the address for connecting to the Debian machine trough ssh to configure something is 192.168.111.1 it is not the address you direct other traffic to. All the traffic in the subnet 192.168.111.1/24 is transparent as far as the bridge is concerned. You also see that although the bridge has 2 interfaces they only have 1 ip adress for the whole bridge.
Still reading documentation though trying to find how to configure network interfaces in TC.
On Debian you can verify the bridge status with brctl show
did a tce-load net-bridging-5.4.3-tinycore but that does not seem to have brctl in it but it looks like the core items for bridging are in there.
Yeah i am on 32bit, have no preference yet for 32 vs 64 bit. Probably build both if i get things running and choose which i am going to use after some performance testing.
[EDIT]: Added code tags. Rich
Rich:
Hi LeonStraathof
Please use Code Tags when posting commands and responses seen in a terminal. To use Code Tags click on the # icon
above the reply box and paste your text between the Code Tags as shown in this example:
--- Quote ---[code][ 36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[ 36.176536] pcm512x 1-004d: Failed to get supplies: -517
[ 36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517[/code]
--- End quote ---
It will appear like this in your post:
--- Code: ---[ 36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[ 36.176536] pcm512x 1-004d: Failed to get supplies: -517
[ 36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517
--- End code ---
Code Tags serve as visual markers between what you are trying to say and the information you are posting. They also preserve
spacing so column aligned data displays properly.
Rich:
Hi LeonStraathof
--- Quote from: LeonStraathof on October 27, 2020, 02:44:03 PM --- ... Still reading documentation though trying to find how to configure network interfaces in TC. ...
--- End quote ---
This is one way of doing it:
--- Code: ---tc@E310:~$ cat /opt/eth0.sh
#!/bin/sh
pkill udhcpc
ifconfig eth0 192.168.1.35 netmask 255.255.255.0 broadcast 192.168.1.255 up
route add default gw 192.168.1.1
echo nameserver 192.168.1.1 > /etc/resolv.conf
echo nameserver 68.237.161.12 >> /etc/resolv.conf
tc@E310:~$
--- End code ---
/opt/eth0.sh gets called from /opt/bootlocal.sh.
--- Quote --- ... did a tce-load net-bridging-5.4.3-tinycore but that does not seem to have brctl in it but it looks like the core items for bridging are in there. ...
--- End quote ---
Those are kernel modules. I don't see any extensions in the repository that depend on them yet.
Juanito:
There’s bridge-utils in the x86_64 repo.
LeonStraathof:
Thanks Rich for pointing out how to configure network settings.
Juanito, thanks for mentioning that it is in the 64 bit build. guess i will be switching to that instead of the 32bit build. Any reason why there is so many differentiation between all repository folders of all builds? Or is it just because of development capacity and what was asked to be build first?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version