Re: wireless/cat5 bridge

2003-07-16 Thread Damien Solley
I've set my bridge with wireless and wired interfaces just as you are
doing. In my setup, the bridge retrieves its IP via DHCP.
Mike has correctly pointed out the settings if only wired interfaces are
used, but one further step was necessary for wireless (using
linux-wlan-ng drivers).
My /etc/network/interfaces also contains the wireless arguments as
follows: 

auto br0
iface br0 inet dhcp
hostname bridge
#   address 192.168.0.2
#   network 192.168.0.0
#   netmask 255.255.255.0
#   broadcast 192.168.0.255
   bridge_ports wlan0 eth0  #can just say 'all'
   up \
   /sbin/iwconfig wlan0 essid partyshack && \
   /sbin/iwconfig wlan0 channel 6 && \
   /sbin/iwconfig wlan0 mode ad-hoc


On Wed, 2003-07-16 at 23:20, Todd Pytel wrote:
> On Wed, 16 Jul 2003 16:04:29 -0700
> Mike Fedyk <[EMAIL PROTECTED]> wrote:
>  
> > # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
> > 
> > #auto br0
> > iface br0 inet static
> > address 10.0.0.122
> > netmask 255.255.255.0
> > broadcast 10.0.0.0
> > gateway 10.0.0.1
> > bridge_ports all
> 
> OK, cool... bridges can be configured through interfaces, which saves me
> the fuss of writing an init script.  But a few more details would be
> helpful - mainly, do I really need an IP address for the bridge?  Also,
> I have the wireless configured in interfaces already in order to
> specify the ESSID and WEP key - it also uses DHCP to get an address. 
> When I switch to bridging, do I switch that to static or will
> removing the "auto" directive be enough?
> 
> Thanks,
> Todd
-- 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: wireless/cat5 bridge

2003-07-16 Thread Todd Pytel
Mike,

Great - thanks for the info.  I'll try it out tomorrow or Friday, and
report back if there are issues.

Cheers,
Todd

On Wed, 16 Jul 2003 16:34:13 -0700
Mike Fedyk <[EMAIL PROTECTED]> wrote:

> On Wed, Jul 16, 2003 at 06:20:02PM -0500, Todd Pytel wrote:
> > On Wed, 16 Jul 2003 16:04:29 -0700
> > Mike Fedyk <[EMAIL PROTECTED]> wrote:
> >  
> > > # /etc/network/interfaces -- configuration file for ifup(8),
> > > # ifdown(8)
> > > 
> > > #auto br0
> > > iface br0 inet static
> > > address 10.0.0.122
> > > netmask 255.255.255.0
> > > broadcast 10.0.0.0
> > > gateway 10.0.0.1
> > > bridge_ports all
> > 
> 
> apt-get -u install bridge-utils
> 
> > OK, cool... bridges can be configured through interfaces, which
> > saves me the fuss of writing an init script.  But a few more details
> > would be helpful - mainly, do I really need an IP address for the
> > bridge?  Also,
> 
> Probably not, but it is useful.
> 
> > I have the wireless configured in interfaces already in order to
> > specify the ESSID and WEP key - it also uses DHCP to get an address.
> > 
> > When I switch to bridging, do I switch that to static or will
> > removing the "auto" directive be enough?
> 
> This works too:
> 
> auto br0
> iface br0 inet dhcp
> bridge_ports all
> 
> I haven't used bridging with wireless, but I have assigned an ip
> address to individual interfaces and it worked.  YMMV.
> 
> Mike
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
> with a subject of "unsubscribe". Trouble? Contact
> [EMAIL PROTECTED]
> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: wireless/cat5 bridge

2003-07-16 Thread Mike Fedyk
On Wed, Jul 16, 2003 at 06:20:02PM -0500, Todd Pytel wrote:
> On Wed, 16 Jul 2003 16:04:29 -0700
> Mike Fedyk <[EMAIL PROTECTED]> wrote:
>  
> > # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
> > 
> > #auto br0
> > iface br0 inet static
> > address 10.0.0.122
> > netmask 255.255.255.0
> > broadcast 10.0.0.0
> > gateway 10.0.0.1
> > bridge_ports all
> 

apt-get -u install bridge-utils

> OK, cool... bridges can be configured through interfaces, which saves me
> the fuss of writing an init script.  But a few more details would be
> helpful - mainly, do I really need an IP address for the bridge?  Also,

Probably not, but it is useful.

> I have the wireless configured in interfaces already in order to
> specify the ESSID and WEP key - it also uses DHCP to get an address. 
> When I switch to bridging, do I switch that to static or will
> removing the "auto" directive be enough?

This works too:

auto br0
iface br0 inet dhcp
bridge_ports all

I haven't used bridging with wireless, but I have assigned an ip address to
individual interfaces and it worked.  YMMV.

Mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: wireless/cat5 bridge

2003-07-16 Thread Todd Pytel
On Wed, 16 Jul 2003 16:04:29 -0700
Mike Fedyk <[EMAIL PROTECTED]> wrote:
 
> # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
> 
> #auto br0
> iface br0 inet static
> address 10.0.0.122
> netmask 255.255.255.0
> broadcast 10.0.0.0
> gateway 10.0.0.1
> bridge_ports all

OK, cool... bridges can be configured through interfaces, which saves me
the fuss of writing an init script.  But a few more details would be
helpful - mainly, do I really need an IP address for the bridge?  Also,
I have the wireless configured in interfaces already in order to
specify the ESSID and WEP key - it also uses DHCP to get an address. 
When I switch to bridging, do I switch that to static or will
removing the "auto" directive be enough?

Thanks,
Todd


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: wireless/cat5 bridge

2003-07-16 Thread Mike Fedyk
On Wed, Jul 16, 2003 at 05:28:52PM -0500, Todd Pytel wrote:
> I'm looking to set up a transparent wireless/cat5 in the uncommon
> direction - i.e. the network and rest of the world are on the wireless
> side and the LAN is on the cat5 side.  At some point, I'll probably go
> with a hardware solution, but for the moment Debian is what I've got.  I
> don't need firewalling, filtering, routing, or NAT - just a transparent
> bridge.  So what is the "Debian proper" way to do this?  From what I've
> read online, I need to ultimately do...
> 
> brctl addbr br0
> brctl addif br0 eth0
> brctl addif br0 eth1
> ifconfig eth0 0.0.0.0
> ifconfig eth1 0.0.0.0
> ifconfig br0 netmask 255.255.240.0 broadcast 10.36.127.255
> 
> Is the last line correct (assuming my numbers are right)?  That is, I
> don't assign an IP address to br0 because it's transparent?  For the
> same reason, I shouldn't be doing any routing, correct?  Also, do I need
> entries in interfaces for eth0 or eth1?  Or should I just write
> everything I need into a script, dump that into init.d, and create
> links appropriately?
> 

# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)

#auto br0
iface br0 inet static
address 10.0.0.122
netmask 255.255.255.0
broadcast 10.0.0.0
gateway 10.0.0.1
bridge_ports all


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



wireless/cat5 bridge

2003-07-16 Thread Todd Pytel
I'm looking to set up a transparent wireless/cat5 in the uncommon
direction - i.e. the network and rest of the world are on the wireless
side and the LAN is on the cat5 side.  At some point, I'll probably go
with a hardware solution, but for the moment Debian is what I've got.  I
don't need firewalling, filtering, routing, or NAT - just a transparent
bridge.  So what is the "Debian proper" way to do this?  From what I've
read online, I need to ultimately do...

brctl addbr br0
brctl addif br0 eth0
brctl addif br0 eth1
ifconfig eth0 0.0.0.0
ifconfig eth1 0.0.0.0
ifconfig br0 netmask 255.255.240.0 broadcast 10.36.127.255

Is the last line correct (assuming my numbers are right)?  That is, I
don't assign an IP address to br0 because it's transparent?  For the
same reason, I shouldn't be doing any routing, correct?  Also, do I need
entries in interfaces for eth0 or eth1?  Or should I just write
everything I need into a script, dump that into init.d, and create
links appropriately?

Thanks for any assistance,
Todd


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]