Router problems on Redhat 9.0 Linux 2.4.20-13.9.HOSTAP

[Yann Garcia]

-----Message d'origine-----
De : Pete Nesbitt [mailto:pete at linux1.ca] 
Envoyé : vendredi 16 avril 2004 15:30
À : yann.garcia at smartcom.com; General Red Hat Linux discussion list
Objet : Re: Router problems on Redhat 9.0 Linux 2.4.20-13.9.HOSTAP

Yann, please add to posts at end of message. It is easier to follow that

way.... (see below)

On April 16, 2004 12:18 am, Yann Garcia wrote:
> Hi Pete,
>
> Thank you for your help.
>
> If I use a range of address 10.1.0.1 to 10.1.0.50 using a net mask
> 255.255.255.0, is it ok?
>
> Cheers,
>
> Yann Garcia
>
> -----Message d'origine-----
> De : redhat-list-bounces at redhat.com
> [mailto:redhat-list-bounces at redhat.com] De la part de Pete Nesbitt
> Envoyé : vendredi 16 avril 2004 03:33
> À : yann.garcia at smartcom.com; General Red Hat Linux discussion list
> Objet : Re: Router problems on Redhat 9.0 Linux 2.4.20-13.9.HOSTAP
>
> On April 15, 2004 12:21 am, Yann Garcia wrote:
> > Hi,
> >
> > On my Linux box, I have two network interfaces: a LAN interface
(eth0)
>
> and
>
> > a WLAN (wlan0). I set ip forwarding in /etc/sysctl.conf. I start a
>
> sniffer
>
> > (tethereal) on both interfaces. When I make a ping from WLAN network
>
> to LAN
>
> > network, ping don’ cross my gateway. The networks infos are:
> > eth0: 10.0.1.37/16
> > wlan0: 10.0.10.1/24
> > The route tables are (netstat –rn):
> >          Destination     Passerelle      Genmask         Indic   MSS
> > Fenetre irtt Iface 10.0.10.0       0.0.0.0         255.255.255.0   U
> >
> >  0 0          0 wlan0 10.0.0.0        0.0.0.0         255.255.0.0
>
> U
>
> >     0 0          0 eth0 169.254.0.0     0.0.0.0         255.255.0.0
>
> U
>
> >       0 0          0 wlan0 127.0.0.0       0.0.0.0         255.0.0.0
> >
> > U         0 0          0 lo 0.0.0.0         10.0.0.1        0.0.0.0
> >
> > UG        0 0          0 eth0
> >
> > The iptables rules are (iptables –L –n –v):
> >          Chain INPUT (policy ACCEPT 17346 packets, 1205K bytes)
> >           pkts bytes target     prot opt in     out     source
> >
> >  destination
> >
> >          Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
> >           pkts bytes target     prot opt in     out     source
> >
> >  destination
> >
> >          Chain OUTPUT (policy ACCEPT 17144 packets, 1306K bytes)
> >           pkts bytes target     prot opt in     out     source
> >
> >  destination
> >
> > I’m sorry but I don’t understand why my gateway doesn’t work!
> >
> > Thank you very much for your assistance,
> >
> > Best regards,
> >
> > Yann Garcia
> > Software Engineer
> >
> > SmartCom
> > 400, Av Roumanille - BP 309
> > 06906 Sophia Antipolis Cedex
> > France
> >
> > Tel: +33 493 008 746
> > Fax: +33 493 001 101
> > Mail: yann.garcia at smartcom.com
> > Site: www.smartcom.com
>
> Hi,
> Your eth0's network contains of the wlan IP range.
> 10.0.1.37/16 is part of a network ip range of 10.0.0.1 to 10.0.255.254
> Your wlan range is inside that so no routing is performed.
>
> You want to use a class C range for the wlan, so instead of 10.0.10.0
> network,
> try using one of the 192.168. class C networks. It may make be best to
> use 2
> different 192.168 networks (say 192.168.0.0/24 for LAN and
> 192.168.1.0/24 for
> the WLAN).
>
> Class A 1.0.0.0 - 127.255.255.255
> Class B 128.0.0.0 - 191.255.255.255
> Class C  192.0.0.0 - 223.255.255.255
>
> Hope that helps.
> --
> Pete Nesbitt, rhce
>
>
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list

Hi Yann,
The 10.1 range should be fine. But again, the 192.168 is also a in the
private 
IP range, so it is a a good choice and less confusing. 

Pete
-- 
Pete Nesbitt, rhce

Hi Pete,

Sorry, I forgot to add the text to posts at end of the message.

My problem is that I work in a business center. The range 192.168.x.y is
already used: 'x' is affected for each company which rents offices in
the business center. 

Cheers,

Yann Garcia