apu2c4

it doesn´t find the networkcards.

\Robban

in this version it works but i rather run smallwall.
you see the differens between the names of the network interfaces.


*** This is t1n1wall, version 1.10.2b102
built on Thu Mar 24 22:54:35 GMT 2016 for generic-pc-serial
Copyright (C) 2015 by Andrew White. All rights reserved.
Visit www.t1n1wall.com for updates.


LAN IP address: 192.168.1.1
WAN IP address: (unknown)

Port configuration:
LAN -> igb0
WAN -> igb1

t1n1wall console setup
**********************
1) Interfaces: assign network ports
2) Set up LAN IP address
3) Reset webGUI password
4) Reset to factory defaults
5) Reboot system
6) Ping IPv4 host
7) Ping IPv6 host

Enter a number:

\Robban

Hmmm would it be possible to go from SmallWall to T1n1wall via the System: Firmware: Upload route? Then using Diagnostics: Backup the updated configuration under T1n1wall before setting up the APU2c4 with T1n1wall? And then finally Diagnostics: restore this configuration file to the APU2c4 T1n1wall box? Or just setup T1n1wall on the new APU2c4 box and Diagnostics: restore the 1.8.4b11 built on Thu Jun 23 17:11:56 CDT 2016 configuration file to reduce the number of rules and configuration I would have to do manually....

So I finally managed, after an arduous process, to get t1n1wall running on the APU2c4. Only one tiny problem so far, besides cosmetics (icon beside DHCP leases to add to reservations is missing, tho the link works). Here's the only major problem today for 2.11.1b140 built on Sat Feb 18 18:30:49 GMT 2017:

Can't enable IP6 - doing so locks up t1n1wall and I have to reset everything via the console and restore saved configuration. I've tried straight from initial configuration with no configurations other than out of box and still no go.

Enable IPv6 support
After enabling IPv6 support, configure IPv6 addresses on your LAN and WAN interfaces, then add IPv6 firewall rules.
Note: you must set an IPv6 address on the LAN interface for the IPv6 support to work.

Of course I had IP6 enabled on SmallWall 1.8.4b11 built on Thu Jun 23 17:11:56 CDT 2016 without problem. Here's t1n1wall 2.11.1b140 built on Sat Feb 18 18:30:49 GMT 2017 status.php - interfaces section:

igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=6403fb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,POLLING,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
ether 00:0d:b9:46:3d:a8
inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255
inet6 fe80::20d:b9ff:fe46:3da8%igb0 prefixlen 64 scopeid 0x1
nd6 options=61<PERFORMNUD,AUTO_LINKLOCAL,NO_RADR>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
igb1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=6403fb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,POLLING,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
ether 00:0d:b9:46:3d:a9
inet6 fe80::20d:b9ff:fe46:3da9%igb1 prefixlen 64 scopeid 0x2
inet x.x.x.x netmask 0xfffffe00 broadcast 255.255.255.255
nd6 options=61<PERFORMNUD,AUTO_LINKLOCAL,NO_RADR>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
igb2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=6403fb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,POLLING,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
ether 00:0d:b9:46:3d:aa
inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255
inet6 fe80::20d:b9ff:fe46:3daa%igb2 prefixlen 64 scopeid 0x3
nd6 options=61<PERFORMNUD,AUTO_LINKLOCAL,NO_RADR>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
enc0: flags=41<UP,RUNNING> metric 0 mtu 1536
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
groups: enc
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
groups: lo
pflog0: flags=100<PROMISC> metric 0 mtu 33184
groups: pflog


Would have posted on t1n1wall forum, but registering to post there doesn't seem to be working atm...so here I am. Need to be pointed in the right direction to help diagnose/enable IP6.

Thanks to your previous help I've gotten this far...just about there.

Thanks Lee for crossposting for me...ta.

Well I finally figured out a workaround - went to the console after enabling IP6, and disabled pf duh. Finished the configuration for IP6 and restarted. All good now. But something's up, not sure what. Ask for diagnostic additional information and I'll try to trouble shoot, as it seems there's still something amiss...just not sure how to tell for sure, as all seems to be running fine now.

Thanks Lee for posting, I think I need to find a new forum home , their FIREWALL was blocking email ?! ...

t1n1wall 2.x is based on pf, not ipfilter (too many issues in freeBSD 11 with ipfilter 5), which is a significant change, hence the jump to 2.x.x versions. Under the hood there are significant changes to move to pf, so probably a bug.

I'll update here when I fix it