On 13/02/14 05:20, Mark Hatch wrote:
Wow! I think I got it to work.
I did some stuff that I'm not totally sure is correct, but it appears
to have worked!!!
bitbake -c clean virtual/kernel
bitbake -c -f virtual/kernel
this gave uImage and modules.tgz, where modules is lib/ folder
//Make copy of old image
root@beaglebone cp /boot/uImage /boot/uImage.old
//Copy new image
host# scp uImage root@192.168.1.3:/boot/uImage
//Copy modules
host# scp lib root@192.168.1.3:/ -r
//Install modules a
root@beaglebone depmod -a
root@beaglebone reboot
Now I was able to run my iptable command and it seems to have worked!
(It went through, before I'd get an error message)
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
So the rootfs and the uImage are completely separated? Cause it
doesn't appear that a rootfs was built and I didn't change it? I'm
still a noob at this linux stuff...
The kernel image and root files system are separate items. You can
upgrade the kernel and copy it to the existing root files system. If you
upgrade the kernel it is usual to to upgrade the device modules as well.
Should my process have even worked???
On Wednesday, February 12, 2014 11:58:07 AM UTC-5, Mark Hatch wrote:
Thanks a lot for clearing some of this up!
So I'm trying to get a mesh network running for a university
project using AHCPD/Babel.
The goal would be for a Ethernet connected node (beaglebone) to
use DHCP to acquire an IP address, and then it would share it's
internet connection over ad-hoc wlan with it's peers (also
beaglebones).
If I can't get AHCPD/Babel to run properly, I'll probably just use
a regular ad-hoc network with static IPs. ('m severely
time-constrained as this project is due by the end of the
semester... and this is only a part of it!)
Yes I have got my wifi module working, I was already able to ping
google.com <http://google.com> from wireless ad-hoc beaglebones
over my laptop's eth0 which was awesome!
Now I just want to replicate this with only beaglebones, which is
why I need the kernel changes for NAT.
I do have a microSD card for testing. I ran into some
complications last night trying to format the card properly
because the mkcard.sh script was not working for me.
I followed some of the instructions here
http://derekmolloy.ie/custom-kernel-and-angstrom-distribution-recipe/
<http://derekmolloy.ie/custom-kernel-and-angstrom-distribution-recipe/>.
Do you know of any good guides for testing the kernel? I didn't
know you could test it before flashing it.
I'm also still trying to work through bitbake and just building
the custom kernel. It's been difficult to distinguish how the
images get built, since there are lots of defconfigs
(ti-linux-psp-3.2 vs. linux-mainline-3.8.0) and I'm unsure how
they all get tied together.
Thanks again,
Mark
On Wednesday, February 12, 2014 9:39:59 AM UTC-5,
rchrd...@gmail.com wrote:
Some further comments:
You don't need to rebuild MLO/u-boot.img
You don't need a serial cable. It can be helpful for
debugging, but thats all.
Have you got the wifi device working correctly on your BBB?
I would recommend you get an micro SD card for testing
your new kernel, before you copy it to eMMC.
Regards ...
On Tuesday, February 11, 2014 6:45:31 AM UTC+11, Mark Hatch
wrote:
Hi friends,
Total newbie here, so forgive me.
I
<http://www.meadios.com/2012/01/building-angstrom-using-bitbake-and-openembedded/>'m
trying to add functionality to iptables so I can use the
BBB as a ad-hoc "router", sharing it's Ethernet connection
with others.
From what I've gleamed so far I need to add that
functionality by recompiling the kernel.
So following the links at
http://www.angstrom-distribution.org/
<http://www.angstrom-distribution.org/> i cloned the
setup-scripts.
|MACHINE=beaglebone ./oebb.sh config beaglebone|
|MACHINE=beagleboard ./oebb.sh update|
|. environment-angstrom-v2013.06
|
|bitbake -c menuconfig virtual/kernel|
I then change the options I need, but when I built it made
a zImage file... Which confuses me.
Now what I don't understand is that the image I want
should be based off the regular systemd image.
*
bitbake systemd-image
How do I update the kernel configuration from the systemd
image without just building the regular image?
A step-by-step explanation would be awesome, cause I've
never customized/built the linux kernel before.
I also do not have a serial cable yet. Is this necessary
for running a custom kernel? Do options in u-boot need to
be changed?
I'm sure I'm asking all the wrong questions, but would
really appreciate some help!
Here are the options that I need:
Networking ---->
Networking options ---->
Network packet filtering framework (Netfilter)--->
Core Netfilter Configuration ---->
<*> Netfilter connection tracking support
<*> Netfilter Xtables support (required for ip_tables)
<*> "NFLOG" target support
<*> "conntrack" connection tracking match support
<*> "state" match support
IP: Netfilter Configuration --->
<*> IPv4 connection tracking support (required for NAT)
<*> IP tables support (required for filtering/masq/NAT)
<*> Packet Filtering
<*> REJECT target support
<*> Full NAT
<*> MASQUERADE target support
<*> Packet mangling
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
