Author | Message | Time |
---|---|---|
CupHead | My setup is as follows: [code] IDSL Modem/Router -> Wireless Access Point Router -> Computer systems (192.168.100.1) -> (192.168.1.1) -> (192.168.1.100 - 192.168.1.200) [/code] IDSL Modem: Motorola Vanguard 65 WAP: LinkSys BEFW11S4 The problem that I'm having is that I am unable to accept incoming connections. As soon as a packet hits the IDSL Modem, it doesn't have any idea what computer behind the wireless router the packet is supposed to go to and therefore it drops it. I have been into its settings to look for port forwarding/pass-through abilities and have had no luck with that. If anyone has ideas about how I can direct traffic through my network, please let me know. | August 4, 2003, 6:50 PM |
Skywing | [quote author=CupHead link=board=2;threadid=2200;start=0#msg17012 date=1060023053] My setup is as follows: [code] IDSL Modem/Router -> Wireless Access Point Router -> Computer systems (192.168.100.1) -> (192.168.1.1) -> (192.168.1.100 - 192.168.1.200) [/code] IDSL Modem: Motorola Vanguard 65 WAP: LinkSys BEFW11S4 The problem that I'm having is that I am unable to accept incoming connections. As soon as a packet hits the IDSL Modem, it doesn't have any idea what computer behind the wireless router the packet is supposed to go to and therefore it drops it. I have been into its settings to look for port forwarding/pass-through abilities and have had no luck with that. If anyone has ideas about how I can direct traffic through my network, please let me know. [/quote] I'm not familiar with your IDSL modem, but if you put two NICs in one of the computers (one going to the IDSL modem and one to the wireless access point) and used something like Win2k/Win2003 RRAS to do NAT, you ought to be able to control port forwarding nicely. Presumably you could do the same thing with Linux, but I have no experience with setting such a thing up under Linux. | August 4, 2003, 7:03 PM |
Raven | As far as I know, IDSL should be configured more like an ISDN line than a digital subscriber line. | August 4, 2003, 8:35 PM |
Thing | Your WAP has two interfaces, one to the IDSL router and one to the Wireless Network. These need to be on two different subnets. Make the WAN side the same as the IDSL router and the Wireless side something else. [code]IDSL(192.168.100.1)<->(192.168.100.2)WAP(192.168.1.100)<->(192.168.1.200)Computer[/code] <edit>If you can connect one computer directly to the IDSL you can set up an AdHoc network without using the WAP. | August 5, 2003, 2:55 AM |
CupHead | So I should give the wireless router a static WAN IP? If I do that, how is that going to allow me to run connections correctly? I really don't understand the reasoning behind setting the subnets. | August 5, 2003, 4:56 AM |
iago | 1. Tell windows XP to set up a home/small office network 2. Magic happens 3. Done! :-) | August 5, 2003, 6:56 AM |
Adron | Depending on the capabilities of your WAP and your IDSL router, pick one of these alternatives: #1: IDSL router internal IP 192.168.100.1 WAP router "external" IP 192.168.100.2 WAP router internal IP 192.168.1.1 Computers 192.168.1.X WAP router set to not do NAT IDSL router set to do NAT Static route for 192.168.1.0/24 through gateway 192.168.100.2 on IDSL router Port forwarding only set up on IDSL router, giving address mappings directly to the 192.168.1.X computers #2: IDSL router internal IP 192.168.100.1 WAP router "external" IP 192.168.100.2 WAP router internal IP 192.168.1.1 Computers 192.168.1.X WAP router set to do NAT IDSL router set to do NAT 192.168.100.2 set as DMZ host on IDSL router Port forwarding only set up on WAP router #3: IDSL router internal IP 192.168.100.1 WAP router "external" IP 192.168.100.2 WAP router internal IP 192.168.1.1 Computers 192.168.1.X WAP router set to do NAT IDSL router set to do NAT Port forwarding set up on both WAP router and IDSL router - on IDSL router mapping ports to 192.168.100.2 and on WAP router mapping them to individual computers #4: IDSL router internal IP 192.168.1.1 WAP bridge IP 192.168.1.2 Computers 192.168.1.X WAP router set to transparent bridge IDSL router set to do NAT Port forwarding only set up on IDSL router, giving address mappings directly to the 192.168.1.X computers | August 5, 2003, 11:50 AM |
CupHead | I am unsure of the capabilities of the IDSL router because the last time I was in its settings it didn't seem to have anything in the way of routing/forwarding capabilities (I also checked google for information on it), but maybe I wasn't looking hard enough. | August 5, 2003, 6:42 PM |
Adron | Perhaps it isn't a router at all? It could be running in bridge mode? | August 5, 2003, 8:04 PM |
CupHead | I don't know, maybe? | August 5, 2003, 8:07 PM |
Adron | If you didn't have any router behind it, would you plug in a computer and set the computer to use dhcp? Does it have a built-in hub/switch or only a single connector for a pc? | August 5, 2003, 8:59 PM |
CupHead | The IDSL router only has a single out to LAN slot. The WAP is set to obtain its WAN address automatically, so I would guess that the IDSL router has some sort of DHCP capability. | August 5, 2003, 9:15 PM |
Adron | That, or your ISP has dhcp going... What IP is your wap getting from dhcp? It's definitely wrong if you're getting 192.168.100.1/255.255.255.0 for the IDSL and 192.168.1.1/255.255.255.0 for the WAP on the same wire... | August 5, 2003, 10:08 PM |
CupHead | I have no way of seeing what the WAP's WAN IP address is. | August 5, 2003, 10:22 PM |
Adron | Really? Is there no web interface or something to do it? | August 6, 2003, 11:22 AM |
CupHead | There is, but it doesn't seem to display the web interface. Let me get a screenshot. [img]http://cuphead.valhallalegends.com/images/wlan.png[/img] | August 6, 2003, 5:00 PM |