Hello all, first of all i want to thank the community for all the great manuals and documentation about the bubba devices! Its great what one can do with them

What i want:
Bubba2 as a bridge acting as a hardware firewall isolating a network segment (LAN) by only enabling communication to certain hosts on the other segment (WAN). Its not about much traffic, but about reachability. Currently my idea is based on usage of iptables with NAT on the bubba2 between the segments. Probably another solution exists without NAT just mirrorring traffic of one port to the otherone, but for the main topic i would like to stick getting NAT working in the current configuration.

What i have:
I installed b2-install-1.2.zip on the bubba2 and followed the guide on viewtopic.php?f=11&t=2518#p11869 to reach a debian squeeze system, which i then upgraded to wheezy and now jessie currently with sources.list:

Do note that when using deb sources for the kernel the kernel Makefile will not contain the correct subversion. Use uname to find the exact version for your kernel and edit the variables at the top of Makefile to reflect that version ID. The kernel will not load the module if the version ID does not match.

Also, if your application doesn't specifically require Debian, you might try the Gentoo live USB for the B2, it has the necessary iptables kernel modules precompiled (config here). You can run it without harming any existing Debian install on your B2's HDD.
Best, sakaki

I am still unsure about the step using arch/powerpc/configs/bubbatwo_defconfig as .config but compiling of make modules is currently running right now and looks promising

Will keep the Gentoo live USB idea in the back and will try it if i dont success here on the kernel way!
Also had the idea today to try an older kernel, since i fount /lib/modules/2.6.32.13/kernel/net/ipv4/netfilter/iptable_nat.ko.
But i did not investigate yet how to downgrade via aptitude using the bubba specific kernels, and if 2.6.32.13 kernel will work with jessie and for example the new systemd.

Will have further look into this two other ideas tomorrow and keep you all updated about make modules result

Do note that EXTRAVERSION must contain all separator characters. There's no rule that says it has to start with a hyphen although I think it may assume so if the first character is a number. For clarity you should set value "-1" (including the quotation).

But I guess you'll find out when you run `make modules_install` and it creates an incorrectly named folder in /lib/modules

But in which module(s) .ko files do those two files land on compilage?
I guess its a module which already exists but is not compiled with the missing symbol on the running kernel, and which i did not yet copy over from the new modules (im afraid using just make modules_install to move all modules over, since i removed some flags in the .config to compile faster or skip some errors). Yes, that was not very clean...

I have changed to configs and I will compile a new kernel for the B2 which will include the missing NAT modules tonight. It will also be upgraded to latest 3.18.27 (the b3 will also get an upgrade). Hopefully it will be uploaded on the repository tomorrow.

Sorry about that it shouldn't have happened. If you are in a hurry I can provide the deb package directly (the cross compiled versions I use for testing), let me know.