Running Wireless and Wired eth connections at the same time

sam bedouglas at earthlink.net
Wed Oct 17 01:11:45 UTC 2007


Hi john, and all!!

Thanks for the replies to this....

What I really wound up doing to resolve this:

Setup:
    Laptop
      ath0 - 192.168.1.33 (sub1)
      eth0 - 192.168.2.33 (sub2)

    Internal Box
      eth0 - 192.168.2.99 (sub2)

This allows me to be able to have the laptop connect to both the wireless
network, and the internal box at the same time.

I also needed to modify the laptop/internal box:

 Laptop:
  -setup iptables for masquerade on ath0 port.
   this basically takes traffic on eth0 and forwards it to ath0
  -setup box for ip_forwarding (/etc/sysctl.conf)

 Internal Box
  -setup "route" to use the laptop eth0 as the gateway (route
   cmd)

To ensure traffic works, check the traffic on the laptop for both eth0/ath0
using iptraf, to see what is coming from the Internal box, and to ensure
that it gets to the wireless network...

It works as required....

Thanks!!


-----Original Message-----
From: fedora-list-bounces at redhat.com
[mailto:fedora-list-bounces at redhat.com]On Behalf Of John Summerfield
Sent: Tuesday, October 16, 2007 5:23 PM
To: For users of Fedora
Subject: Re: Running Wireless and Wired eth connections at the same time


Marko Vojinovic wrote:
> On Monday 15 October 2007 03:51, sam wrote:
>> here's what i have so far.
>>
>>                                    >>>>  dns
>>
>> internal box   <<<<  >>>laptop >>>+>>>   internet
>>   192.168.2.99   (eth0)     (ath0)
>>                 192.168.2.33  192.168.1.33
>>
>> the laptop can access both the internal box, and the internet
>> the internal box can only access the laptop...
>>
>> i'm trying to be able to allow the internal box to be able to access
>> everything that the laptop can...
>
> Maybe I am wrong, but I believe You need to setup eth0 as a bridged
network
> connection. There is a howto about it in www.tldp.org :-).

You are.

The laptop needs forwarding enabled:
10:13 [summer at numbat ~]$ grep ip_ /etc/sysctl.conf
net.ipv4.ip_forward = 0
08:19 [summer at numbat ~]$
Change that to 1. "man sysctl"

Hosts on each side need route set so the can find the other. "man route"

Use of tcpdump on the laptop can help sort out where packets are being
lost. "man tcpdump"
Something like this:
tcpdump -i any host a and host b
Hosts  a and be are on opposite sides of the laptop.



--

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu

Please do not reply off-list

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




More information about the users mailing list