router to router link for more routery goodness?

Permabanned
Joined
22 Aug 2004
Posts
9,204
Hi all. Just fitted some new buffalo kit to the hotel for a good range signal. the router and repeater are connected wirelessly via buffalos WDA service. What i want to know is ..

Can i connect my older netgear DG834 router modem to the buffalo router, via cable of course as another repeater station? In essence im asking, if i connect some crossover cable between router A (which is on the internet) and router B will a wireless connection to B be able to connect to the internet.
 
can u explain that a bit more? when you say it will act as an access point not a repeater. i dont follow thought they were the same?? lets put it into hypotheticity.

Router connected to broadband has SSID of "hotel" repeater unit in seperate building has SSID "annexe" then netger router now has SSID upper floor.

What i assume you mean to say is, if all these were set to "hotel" then people could move between them without reconfiguring their wireless yet you are not sure if this will work with the netgear as its config may be different to the buffalo stuff yeah?

Damn i can only fiind patch cable so cant test this out!
 
hit on a mini admin problem. I cant seem to access the netgears admin page any longer. its previous ip was 192.168.0.1 of course now it has also been assigned an ip by the main router that is acting as a DHCP which is 192.168.11.5 now how in the hell do i get to 192.168.0.1 through 192.168.11.5?!? lol
help
 
problem number 2....lol...xbox 360 wont connect to the netgear as the netgear refuses to assign it an IP address. This is because i disabled the DHCP server protocol on the netgear. What should i do? man this stuff is complex but its nice to learn it :D
 
null said:
Login to the main router and look around for a page to the DHCP leases. It should show you a list of all the devices that have got a lease from the main router. One of these should be the Netgear router. You may have to work it out by process of elimination if it's not clear. So just copy the IP and paste it into another browser tab/window.

Once you've got to the Netgear's panel you may consider giving it a static IP if you're confident with doing so, that way you won't have to look it up from the lease page next time.

Hope this helps, null :)

well buffalo reports its dhcp lease addy as 192.168.11.5 but if i type that in i get error connection refused
 
well this is interesting. assigned a static ip to the xbox. no joy cant confirm DNS. assigned gateway address as the address of the netgear assigned to it by the buffalo DHCP and now confirms DNS but fails MTU. wierd.
 
WOO! wicked sorted. had to assign the netgear as a DMZ and enable a box suspiciously labled "pass-through IP adressing" hmm

easy as cake, well rock cake. i now have a wireless network that god himself probably envies. Thanks for all your help null
 
still cant get the blooming netgear config up, tried it all! geuss if i unhook the wire and send the netgear back into isolation it should become available again then plug it back in and presto-matic fingers crossed
 
tolien said:
You shouldn't need to do any of that if you set it up properly - the wireless and wired segments are bridged by default.
You'll need to change the Netgear's IP...

pretty tough when i cant get into the config lol so you suggest i assign the netgear an ip then it should automatically have that ip through the buffalo therefore giving me access, despite the fact that neither its default ip nor the current dhcp assigned ip allows me access to the config?
 
null said:
Unless there's some setting that Ultra_Extreme has unknowingly changed somewhere though, I can't see that helping. Assuming he had the right IP from the lease table earlier it shouldn't make any differene whether it got it by DHCP or is static really? Unless the Netgear has a strange behaviour that blocks the webconfig when its IP is assigned by DHCP...

The other weird thing is, this:

I still can't understand why that was necessary, if it was just plugged into the main router from and to LAN ports, it should have acted just like a WAP attached to a switch in one box. I'm thinking there's something up with the way the router is configured :confused:

The DMZ bit was just for the xbox 360's benefit. I probably could have used static routing to assign it but i though that could lead to future conflicts. Basically the 360 could not get an IP assigned to it untill i changed those options. It was fine if i used the very weak signal from the buffalo, but when connected to the netgear it for some bizzare reason seemed to insist that the ip was assigned directly rather than from the remote dhcp :confused: im learning but not quick enuff i reckon lol
 
Phemo said:
Exactly what I'm thinking. At present I am using a Netscreen Firewall for my NAT/DHCP/etc stuff and my Netgear router simply as a switch and wireless AP and I've had to do nothing strange. I've left my Netgear with a static IP and I've turned off the DHCP server on it - that's it, works fine. So, it is possible that it could do some strange stuff when it's getting its IP via DHCP.

In fact checking the webconfig through the buffalo client monitor the netgear appears to have no IP at all now. It appears to be operating the same as the airstation repeater that is connected through WDA hmmm
 
huzzah. The problem seems to have been that the buffalo kit works on 192.168.11.xx and netgear works on 192.168.0.xx so their subnets or whatever were different.

Unhooked ethernet between routers. rebooted, had to assign manual ip cos forgot id turned off dhcp. assigned static ip of 192.168.11.10 (also set this as a reserved address in the buffalo DHCP settings) reconnected cable rebooted and now can access both (well all three!! lol) webconfigs. Networks are great when the errr work lol
 
null said:
Have you tried setting the Netgear with a static IP yet? If not, do so (in the same range as the main router), and while you're at it do a full factory reset (sounds like you're gonna have to anyway to access the panel).

Hope this helps, null :)

edit - Posted at same time lol! So I might have been onto something earlier when I mentioned subnets. Yay I'm learning too :cool: . And yeah you're right, networks are great when they work :D

Glad you fixed it, hopefully for a little longer than last time :p

lol yeah, well technically it wasnt broke just a bit bent :D now however i dont have to go anywhere to fiddle which is useful cos i wanna get security going asap (esp as i now have a silly coverage!)
 
Back
Top Bottom