Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

wireless - wired routing -- eth0 - wlan0 traffic setup

Status
Not open for further replies.

bletey

Programmer
Feb 26, 2001
5
GB
Hi there

I have a solution like the above working using the parprouted software and was working well, but now seems to have fallen over, so I want to route between the eth0 (wired) NIC and the wlan0 (wireless) NIC as simply as possible.

They are 192.168.1.3/255.255.255.0 and 192.168.1.141/255.255.255.0 respectively, ip_forward is turned on but no traffic passes between them, not sure where I am going wrong. I can ping an outside address from the box and I can arping both NICS in the wireless router from the main LAN.

Q. Do i still need to parprouted to get traffic flowing or should the "normal" kernel routing do what I want.

Thanks in advance

Pete
 
Can you ping each interface from an IP on that interface's network?
 
Hi there and thanks for the response.

OK I hope this makes sense.

And pleased dont laugh at the IP addressing, I probably should have done some
subnetting but this is a work in progress since 1997, rip and replace sounds good but i have never been brave enough


Test Lan
--------

PC1 - IP 192.168.1.7/24
GW 192.168.1.1
eth0 ---> 10Mb Hub (3Com)

WR1 (WirelessRouter)

eth0 IP 192.168.1.3/24
wlan0 IP 192.168.1.140/24
GW 192.168.1.1
eth0 ---> 10Mb Hub (3Com)
wlan0 ---> WAP11

Wireless Lan
------------

WAP11 v2.2
IP 192.168.1.5/24
GW 192.168.1.1
eth0 ---> 100Mb Hub (netgear)

Main Lan
--------

ADSL Modem/Router IP 192.168.1.1/24 (original eh)
1 of 4 eth ports ---> 100Mb Hub (netgear)
2 of 4 eth ports ---> eth0 of DNS Cache/Squid

DNS Cache/Squid
IP 192.168.1.2/24
GW 192.168.1.1

All other PC's are DHCP's of the ADSL Modem Router with it as the GW
PC2 blah
PC3 blah
PC4 blah

Now from any of the PC2-xxx machines i can ping the WLAN0 if of WR1.

I can also arping the eth0 if of WR1, so echo 1 > /proc/sys/net/ipv4/ip_forward is doing its job

But how come i cant ping from PC1 out through WR1....hmmm

with the other box i just built parprouted form source and did a parprouted eth0 wlan0 adn thats that,
but since I went on holiday i can only connect through the 192.168.1.2:3128 squid to the outside world, its like it half broke on me.

anyway hope it makes sense, and answers your q

kind regards Pete
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top