I'll continue this monologue with another update just in case anyone
else is reading...
The problem is now fully fixed! The fix was simple (and I'm kicking
myself for not having tried it earlier). I simply built the latest trunk
release via the ADK and it all worked perfectly. I imagine there's some
issue with dhcp in the if.post-up scripts for bridged connections in 1.03.
Anyway, the final (and very simple) config is:
# Loopback
auto lo
iface lo inet loopback
# LAN ports
auto eth0.0
iface eth0.0 inet manual
switch-ports 0 1 2 3 5*
# WAN port
auto eth0.1
iface eth0.1 inet manual
switch-ports 4 5
# Bridge
auto br0
iface br0 inet dhcp
bridge-ifaces eth0.0 eth0.1
broadcast +
Sam Crawford wrote:
> For anyone interested I've managed to partially solve this by splitting
> the VLANs further still. My config now looks like:
>
> # Loopback
> auto lo
> iface lo inet loopback
>
> # LAN ports
> auto eth0.0
> iface eth0.0 inet manual
> switch-ports 0 1 2 5*
>
> # WAN port
> auto eth0.1
> iface eth0.1 inet manual
> switch-ports 4 5
>
> # Management port
> auto eth0.2
> iface eth0.2 inet dhcp
> switch-ports 3 5
> broadcast +
>
> # Bridge
> auto br0
> iface br0 inet static
> bridge-ifaces eth0.0 eth0.1
> address 10.0.10.1
> netmask 255.255.255.0
> broadcast +
>
>
> Ultimately this means I now have to run two cables to the upstream
> router (one for WAN, one for management). Not ideal, but it does the job
> at least. This gives me the ability to have an application sitting on
> the unit monitoring traffic on eth0.1 and have it report data back via
> the management interface.
>
> If anyone has a better configuration suggestion I'm all ears!
>
> Thanks,
>
> Sam
>
>
> Sam Crawford wrote:
>> Afternoon,
>>
>> I'm trying to bridge two VLANs and want the bridge to acquire it's IP
>> configuration via DHCP. I attempted to use the following config but the
>> device didn't pick up a lease and was unreachable...
>>
>> # Loopback
>> auto lo
>> iface lo inet loopback
>>
>> # LAN ports
>> auto eth0.0
>> iface eth0.0 inet manual
>> switch-ports 0 1 2 3 5*
>>
>> # WAN port
>> auto eth0.1
>> iface eth0.1 inet manual
>> switch-ports 4 5
>>
>> # Bridge
>> auto br0
>> iface br0 inet dhcp
>> bridge-ifaces eth0.0 eth0.1
>> broadcast +
>>
>> I would have expected the above to work. As soon as I change the config
>> for br0 to use a static IP config it all works perfectly.
>>
>> You might ask why I don't just put all the switch ports in one VLAN and
>> get that to acquire a DHCP lease. Well, that works just fine, but it
>> means that all of the traffic is switched and does not pass through the
>> bridge. I need traffic to/from the WAN to pass through the bridge so
>> that I can capture it with tcpdump. Trying tcpdump on setup with just a
>> single VLAN containing all ports yields no traffic (except for traffic
>> destined to the router itself).
>>
>> I'm running a WRT54GL with freewrt 1.03 built via the web image builder.
>>
>> Any bright ideas?
>>
>> Thanks!
>>
>> Sam
>> _______________________________________________
>> freewrt-users mailing list
>> freewrt-users@freewrt.org
>> https://www.freewrt.org/lists/listinfo/freewrt-users
> _______________________________________________
> freewrt-users mailing list
> freewrt-users@freewrt.org
> https://www.freewrt.org/lists/listinfo/freewrt-users
_______________________________________________
freewrt-users mailing list
freewrt-users@freewrt.org
https://www.freewrt.org/lists/listinfo/freewrt-users
