Ticket #212 (new Feature Request)

Opened 14 years ago

Last modified 7 years ago

Enable gatewayinterface for all interfaces in a non-bridged router setup

Reported by: berry [dot] groenendijk [at] gmail [dot] com Owned by:
Priority: high Milestone:
Component: Gateway Version: Gateway SVN
Keywords: gatewayinterface Cc:

Description

If you are using Mesh routing software, like OLSR, on a router it is necessary to split the Lan and Wifi interfaces from each other. And for other reasons it can also be necessary to split the Lan and Wifi interface from each other.

You can setup Wifidog to watch only one interface at a time. So, in a non-bridged router setup you need to choose between the Lan interface or the Wifi interface.

Proposal: make it possible for Wifidog to capture the traffic for more than one interface at a time. Technically it must be possible, nocatsplash for example can do this. nocatsplash is however not a viable replacement for Wifidog. At least not for me.

I am part of a business that is creating wifi communities. To make our business model a success this functionality needs to work. So, I would like this functionality to be present in WifiDog as soon as possible ;-)

Change History

  Changed 14 years ago by benoitg

  • version set to Gateway SVN

  Changed 14 years ago by dana

I second this request. NYCwireless would really like to see this work so that we can deploy solutions that create multiple distinct networks.

For example, it should be possible to create wireless VLANs that offer the same portal page, but for security reasons don't have bridged interfaces (for example, an open hotspot and a protected WPA encrypted, 802.1X hotspot). This would also make it easier to merely create two totally distinct wireless networks using 2 radios, but managed as the same node in wifidog.

  Changed 13 years ago by Berry

Is there a chance that this request will be implemented in Wifidog?

  Changed 12 years ago by wichert

Ticket #466 has a slightly different approach: it makes it possible to run multiple wifidog instances on a single machine. I am succesfully using that to manage 3 different networks on a single gateway device.

Is there a reason why this approach would not work for you?

follow-up: ↓ 6   Changed 11 years ago by dana

Yes, your approach in ticket #466 wouldn't work because it requires setting up 3 different "hotspots" on the server, for each wifidog instance. We would want a single "hotspot" instance on the server to be made available across a few different local network devices.

in reply to: ↑ 5   Changed 7 years ago by anonymous

Replying to dana:

Yes, your approach in ticket #466 wouldn't work because it requires setting up 3 different "hotspots" on the server, for each wifidog instance. We would want a single "hotspot" instance on the server to be made available across a few different local network devices.

Hi there, I was wondering if you guys were able to this to work. Thanks for your help, much appreciated.

Note: See TracTickets for help on using tickets.