ip masquerading/subnets

[bruce]

hi mike...

not sure who mikkel is... but if you have emails from him, that i've missed,
send them my way!!

i've thought of the bridge issue, but very preleminary research has
indicated that bridging has issues when dealing with ath0/eth0 setups...

i've seen information related to dropouts/locking up...

but if you have detailed information detailing how the bridging should be
setup to work, i'm game to try!

thanks


-----Original Message-----
From: fedora-list-bounces at redhat.com
[mailto:fedora-list-bounces at redhat.com]On Behalf Of Mike Wright
Sent: Monday, November 26, 2007 4:03 PM
To: For users of Fedora
Subject: Re: ip masquerading/subnets


bruce wrote:
> craig...
>
> if you look at the diagram again.. box2 has ath0 which is on the 192.168.1
> sub (it's 1.5). box2/eth0 is on a different sub, because as i understand
it,
> you can't have multiple nics on the same box, on the same subnet....

Sure you can!  Mikkel's advice is perfect here.  Create a bridge, remove
the IPs from ath0 and eth0, add the former IP of ath0 to the bridge,
then add the two devices to the bridge.

Everything is now on the same subnet, including box3.

>
> the issue is what has to be setup on box2 regarding iptables/route cmds to
> allow this to all work.
>
> thanks
>
>
> -----Original Message-----
> From: fedora-list-bounces at redhat.com
> [mailto:fedora-list-bounces at redhat.com]On Behalf Of Craig White
> Sent: Monday, November 26, 2007 3:40 PM
> To: For users of Fedora
> Subject: RE: ip masquerading/subnets
>
>
> On Mon, 2007-11-26 at 15:43 -0800, bruce wrote:
>
>>Hi mike..
>>
>>
>>here's my system:
>>
>> internet
>>
>>
>>    dsl box
>>       V
>>       V
>>     dlink router (192.168.1.100)
>>         V
>>         V
>>       switch  ->>>>>>>>>>>>>>+
>>         ^                    V
>>         ^                    V
>>         ^                    V
>>        box1           wireless access point (192.168.1.200)
>>          (eth0)               |
>>                               |(ath0)
>>                              box2
>>                               |(eth0)
>>                               |
>>                                            box3 (future) (192.168.2.13)
>>
>>    so:
>> router - 192.168.1.100 (gateway)
>> wireless access point - 192.168.1.200
>> box1 (eth0) 192.168.1.3
>>
>> box2
>>    ath0 - 102.168.1.5
>>    eth0 - 102.168.2.5
>>
>> box3
>>    eth0 - 102.168.2.6
>>
>>box1 connects to the switch, which is connected to the access point via
>
> the
>
>>lan (eth) connection.
>>
>>so, everything is on the 192.168.1 subnet, except the eth0 nic of box2,
>
> and
>
>>the box3 that'll be added to interface with box2/eth0...
>>
>>box2 has ip_forwarding set.
>>
>>so my basic questions:
>> -what do i need to do on box2 to allow a user to
>>  be able to do a "ping 192.168.2.5"
>> -what do i need to do on box2 to allow a user on
>>  box1 to be able to "ping 192.168.2.5" and have a
>>  successful reply.
>>
>>bear with me !!
>
> ----
> box 2 and 3 should be on same subnet as box 1 ( 192.168.1.0/24 ) because
> wireless access point is not the same thing as a router.
>
> Craig
>
> --
> fedora-list mailing list
> fedora-list at redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>

--
fedora-list mailing list
fedora-list at redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list