WiFi AP

[SMOKEU]

At work we have a Cisco ADSL modem/router, which I don't know how to configure so I'm not going to fuck with it. That's the device that is serving as our modem/NAT/firewall etc. We also have an Innbox V50-U ADSL modem/router with WiFi capability which we are currently using just as a switch, so I've daisy chained the 2 together.

What I'd like to do is to turn the Innbox device into a WiFi AP. I've looked in the configuration of the Innbox device and I can't find any way to change the IP address, and it's on a different subnet from the Cisco device. Is there any way around this? I can't afford to fuck anything up on the Cisco device so I'm not going to try that.

[nodrog]

I thought McDonald's already had free Wi-Fi?

[BigAl]

have you check net for configuration software?

Set notebook on same ip range and subnet then connect to switch with patch lead and run up configurator.

If that fails do some skids :-)

[Trade_nancy]

At work we have a Cisco ADSL modem/router, which I don't know how to configure so I'm not going to fuck with it. That's the device that is serving as our modem/NAT/firewall etc. We also have an Innbox V50-U ADSL modem/router with WiFi capability which we are currently using just as a switch, so I've daisy chained the 2 together.

What I'd like to do is to turn the Innbox device into a WiFi AP. I've looked in the configuration of the Innbox device and I can't find any way to change the IP address, and it's on a different subnet from the Cisco device. Is there any way around this? I can't afford to fuck anything up on the Cisco device so I'm not going to try that.

Well that configuration is valid and i have it working for a client. Similar setup - but different brand gear. I have the primary router accessing internet and using 192.168.1.1 (Dynalink RTA1330).
They also have a wireless D-LINK router - so I set that to 192.168.10.1 and connected the two sets by LAN cable - using LAN port on the Dynalink and into the WAN port on the D-LINK. It works and that choice of IP sub-range was on the suggestion of D-LINK help desk. The wireless router is only used for a user who comes in with a laptop periodically. All other people connect by cable to the Dynalink.
All that will change on Monday however when they convert to Ultra-fast and SPARK will dump new gear on us to work through.
Some further details on your device here may help: http://www.worldnet.co.nz/support/dsl/?menu=configadslrouter_InnBoxV50u

[Gremlin]

With respect to Cisco and Innbox on different subnets, as long as there is routing between the two, it's no problem. The Innbox might be configured to GW to the Cisco etc.

You connect to Wifi on Innbox, Innbox connects to Cisco, Cisco connects to Internet. Your only potential problem is whether or not the Cisco knows to returns Wifi traffic to the Innbox.

Cisco can range from Linksys basic devices through to hardcore routers and switches.... massive difference in functionality, but generally, the basic model gear is more plug and play doing things for you, vs the higher range stuff where everything has to be explicit.

[Gremlin]

All that will change on Monday however when they convert to Ultra-fast and SPARK will dump new gear on us to work through.
I haven't used Spark UFB (we supply our own) but generally all you need is to setup a PPPoE client.

[TheDemonLord]

Cisco can range from Linksys basic devices through to hardcore routers and switches.... massive difference in functionality, but generally, the basic model gear is more plug and play doing things for you, vs the higher range stuff where everything has to be explicit.

en
Conf -t
Hostname Demon
!
boot-start-marker
boot-end-marker
!
logging buffered 4096
enable secret 5 DemonRouter123
!
no aaa new-model
!
etc.

[avgas]

en....#killall.....etc.
Lol he didn't mean that bad - more that you can run an NMS on it.

In regards to the op's question - see what you can find.
Half the freebee routers out there are locked down in regards to making them bridge clients. They look like they work but in reality they never find a AP to bridge.

If all you want to do is make them both AP running through copper - should be no reason for it not to work. Most stuff has connection at:

192.168.0.1
172.192.0.1
10.0.0.1

But as others have mentioned shove a copper up its arse, the other end into your computer - set DHCP on and see if it gives you an address. If not - check what wireshark picks up. You generally can spot the router as the guy going "if you find jimbo - tell 10.0.0.1". If you still can't see it. Turn everything off - then only turn the router you want to talk to and watch wireshark - should show you something about it.

All this advice is very crude - but you would be supprised how crude stuff gets you to the right place.
You can spot the most advancedly secured Cisco networks via their spanning tree protocol :killingme

[Gremlin]

en
Conf -t
Hostname Demon
!
*snip*
huh? :scratch:

Jeez, ok, I wasn't saying that. More that the basic stuff will give you a wizard which will sort most of it or a very easy GUI. On the higher range stuff, you have to tell it to NAT, bridge etc.

We stopped buying Cisco when the distributor said we had to be Cisco certified to purchase. I wanted an 8 port unmanaged switch :wacko: Actually, on that note, we never bought Fortinet for the same reason :D

[jonbuoy]

At work we have a Cisco ADSL modem/router, which I don't know how to configure so I'm not going to fuck with it. That's the device that is serving as our modem/NAT/firewall etc. We also have an Innbox V50-U ADSL modem/router with WiFi capability which we are currently using just as a switch, so I've daisy chained the 2 together.

What I'd like to do is to turn the Innbox device into a WiFi AP. I've looked in the configuration of the Innbox device and I can't find any way to change the IP address, and it's on a different subnet from the Cisco device. Is there any way around this? I can't afford to fuck anything up on the Cisco device so I'm not going to try that.

Must be a LAN setup page for it somewhere - unless its been locked down. If it has a WAP mode you will be OK but I have had issues in the past using routers as access points connected on the LAN side only. Sometimes they look like they work OK but won't pass DHCP requests or other odd isssues.

[TheDemonLord]

huh? :scratch:

Jeez, ok, I wasn't saying that. More that the basic stuff will give you a wizard which will sort most of it or a very easy GUI. On the higher range stuff, you have to tell it to NAT, bridge etc.

We stopped buying Cisco when the distributor said we had to be Cisco certified to purchase. I wanted an 8 port unmanaged switch :wacko: Actually, on that note, we never bought Fortinet for the same reason :D

Really? we aren't Cisco or Fortinet certified - yet we use both.

[neels]

I had the same setup at my last house, ADSL modem/router with wireless router connected.

Wireless router wouldn't configure as both were defaulted to 192.168.1.1, changed the modem to 192.168.2.1 and they decided to play nice, then tweaked it from there.

Had no issues with router connected to router, only connection from the modem LAN was to the router WAN, everything else downstream was on the wireless router LAN via switches.

[Gremlin]

Really? we aren't Cisco or Fortinet certified - yet we use both.
Hmmm, maybe they changed the rules, or someone at the bare minimum does all the buying. :D

It would be a few years ago now actually, circa 2010/11. Stopped using Juniper Netscreens, Fortinet was coming the scene without the licensing crap of Juniper (the only reason we ever rang them), but they wanted to put us on courses before we could buy.

Cisco, I told my account manager to pass it up the chain, they were losing sales due to their stupid rules. Don't think we've bought Cisco since. Now HP has the lovely ProCurve range available from anything 8-24+ ports, nice and easy :wings: