Welcome, Guest. Please login or register.

Author Topic: hub (again), with two wifi routers problem  (Read 2182 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline orangeTopic starter

  • Hero Member
  • *****
  • Join Date: Dec 2003
  • Posts: 2799
  • Country: 00
    • Show only replies by orange
hub (again), with two wifi routers problem
« on: August 27, 2007, 04:24:23 PM »
I'm trying to connect Amiga to Internet using RS232,hub  and two wireless routers.
Just want to make sure if its actually a waste of time..

I have some results with these two configurations:

1)
hub RS232      IP=192.168.10.1/31 (Amiga=192.168.10.11)
hub LocalLan   IP=192.168.16.1/24

ruter2 LocalLan IP=192.168.16.2/24
ruter2 Wifi IP=10.0.1.200/24

ruter1 Wifi IP=10.0.1.1/24
ruter1->Internet

with such config I can ping ruter2 from Amiga(RS232), but not ruter1.
OTOH, computer connected to hub LAN cannot access net at all.






2)
hub RS232      IP=192.168.10.1/31 (Amiga=192.168.10.11)
hub LocalLan   IP=192.168.16.1/24
hub GlobalIP   IP=192.168.1.200/24

ruter2 LocalLan IP=192.168.1.1/24
ruter2 Wifi IP=10.0.1.200/24

ruter1 Wifi IP=10.0.1.1/24
ruter1->Internet


now I can't ping ruter2 from AmigaRS232, but computer connected to hub LAN
can ping Internet.


Is it 'mission impossible'?
“Giving up is always an option, but not always a failure.”
 

Offline adolescent

  • Hero Member
  • *****
  • Join Date: Sep 2003
  • Posts: 3056
    • Show only replies by adolescent
Re: hub (again), with two wifi routers problem
« Reply #1 on: August 27, 2007, 05:13:08 PM »
You need a route from 192.168.10.0 to 192.168.1.0.  I would just put the hub on 192.168.1.0 (same net as router 1).  Otherwise, you may be able to just add a route locally (on the Amiga), but I think your hub is actually a router/bridge so you may have to do it there.

Edit: saw your second configuration is what I'm talking about.  Not sure why the PC would work, but not the RS232.  Sounds like the gateway address is different from the LAN ports to the RS232.

Edit2: BTW, don't trust pings for tests.  Edge devices could have ICMP replies disabled.  
Time to move on.  Bye Amiga.org.  :(
 

Offline Shamus_

  • Jr. Member
  • **
  • Join Date: Aug 2007
  • Posts: 62
    • Show only replies by Shamus_
    • http://www.imgburn.com
Re: hub (again), with two wifi routers problem
« Reply #2 on: August 28, 2007, 03:11:13 AM »
Quote

orange wrote:
I'm trying to connect Amiga to Internet using RS232,hub  and two wireless routers.


Establish a connection between your Ami and your first router.

Use a LAN port and not a WAN port from the first router to connect to the second router. Change the address type of your first router from static to dynamic and also turn off the dhcp server.

Refresh the IP address of your Ami or set a static IP from the pool of your second router.

Using 2 routers is pretty pointless. By using a lan port to connect the 2 routers, you disable the routing functions of your first router and effectively turn it into a wireless switch. This allows both your Amiga and second router to meld seemlessly into the address pool of the router connected to the internet without screwing around with gateways.  
A500 - dead
A500 - pulse detected
A500/A570/A590 ROM Switcher/Action Replay Mk III
A1200/020 18megs RAM
A1200/020/10megs RAM/scsi/CD/ZIP/1x4gig+2x2gig HD
A4000/EC030 - Work in progress
A4000/040 x 2 - Work in progress
 

Offline orangeTopic starter

  • Hero Member
  • *****
  • Join Date: Dec 2003
  • Posts: 2799
  • Country: 00
    • Show only replies by orange
Re: hub (again), with two wifi routers problem
« Reply #3 on: August 28, 2007, 05:12:33 PM »
yes, I understand that using router2 (working in AP Client mode) as a switch would solve the problem, but it insists on having wifi and LAN on different subnets. And I'd like to avoid drilling hole in wall/window for wired connection.
“Giving up is always an option, but not always a failure.”
 

Offline Zac67

  • Hero Member
  • *****
  • Join Date: Nov 2004
  • Posts: 2890
    • Show only replies by Zac67
Re: hub (again), with two wifi routers problem
« Reply #4 on: August 28, 2007, 07:08:41 PM »
Oh dear...

>1)
>hub RS232      IP=192.168.10.1/31 (Amiga=192.168.10.11)
>hub LocalLan   IP=192.168.16.1/24

If it's a real hub with the RS232 bridged in (same segment/collision domain) this may be the first problem: you'll have to use the same network address / mask on all ports incl. RS232. 'IP=192.168.10.1/31 (Amiga=192.168.10.11)' is a contradiction in itself and a CIDR mask of /31 is absolutely senseless: there one bit left for the host part, but the host part must not be all 0s or all 1s, so there's nothing left... And a hub usually has no IP (only managed ones).

>ruter2 LocalLan IP=192.168.16.2/24
>ruter2 Wifi IP=10.0.1.200/24

OK.

>ruter1 Wifi IP=10.0.1.1/24
>ruter1->Internet

This looks OK, but all hosts/routers must be aware of the segments available. The Amiga should have a default gateway of 192.168.16.2 and the packets find their way out. But router1 doesn't know about the 192.168.16/24 segment and the answer packets can't find their way back. You'll have to add a static route for router1 192.168.16.0/24 -> 10.0.1.200 to enable traffic between it and the Amiga. Plus router2 has to have a default gateway -> 10.0.1.1. to reach the internet.

PS: just read up a bit on what's to be found for the EP-3506: it looks like the serial port is routed, so you'll have to add/modify the routes there, too. (And the segmenting you posted looks OK.)
 

Offline orangeTopic starter

  • Hero Member
  • *****
  • Join Date: Dec 2003
  • Posts: 2799
  • Country: 00
    • Show only replies by orange
Re: hub (again), with two wifi routers problem
« Reply #5 on: August 28, 2007, 08:58:44 PM »
sorry about that CDIR mistake, I'm not good with that notation, but those two IP addresses are correct and Amiga can always ping RS232.

I can set two values for RS232: VPN and ISP,
if VPN is used then its used to connect remotely identical hub with IPs: 192.168.10.0-192.168.10.255

The manual for hub specifically states that RS232 must be different domain than hub LocalIP(192.168.16.0).

of course, I have setup static routes on both ruters
including the one for 192.168.10.0 (should I delete that one?)

The RS232 port(s) are intended for connecting LocalLan to ISP with modem, could that be the problem?

unfortunately hub has no options for gateway or static route in web interface  :-(
“Giving up is always an option, but not always a failure.”
 

Offline Zac67

  • Hero Member
  • *****
  • Join Date: Nov 2004
  • Posts: 2890
    • Show only replies by Zac67
Re: hub (again), with two wifi routers problem
« Reply #6 on: August 29, 2007, 07:31:08 AM »
Well, the 'hub' seems to be a router after all. You need static routes to 192.168.10.0/24 on both wireless routers, that's fine. The problem might be that the 'hub' always uses the serial port as default gateway - it's supposed to point to the ISP - and if that can't be changed, you're screwed... Do you have the manual? Does it have another way of configuring (e.g. telnet)?
 

Offline orangeTopic starter

  • Hero Member
  • *****
  • Join Date: Dec 2003
  • Posts: 2799
  • Country: 00
    • Show only replies by orange
Re: hub (again), with two wifi routers problem
« Reply #7 on: August 29, 2007, 04:19:53 PM »
ok, thanks, I understand now.

yes, it has telnet option for configuring, haven't tried that.
Please have a look at hub manual (500Kb), I could not understand all of it
“Giving up is always an option, but not always a failure.”
 

Offline Zac67

  • Hero Member
  • *****
  • Join Date: Nov 2004
  • Posts: 2890
    • Show only replies by Zac67
Re: hub (again), with two wifi routers problem
« Reply #8 on: August 29, 2007, 09:46:03 PM »
The 'hub' is a narrowband router with NAT support.

I assume you've set up leased line operation, disabled NAT and configured Amy to connect via PPP.
As far as I can see there's no way to define the default gateway for the hub...
You might get around some problems when you configure your wireless routers to 'bridge LAN and WLAN' mode, most models support this option (under various names though).

The only solution I can currently see is to set up an HTTP proxy on one of the other machines that the Amiga can see/ping and configure that for outbound connections.