A networking issue to induce suicide.
CommunistWithAGun
Local Propaganda Guy Join Date: 2003-04-30 Member: 15953Members
Local Propaganda Guy Join Date: 2003-04-30 Member: 15953Members
in Off-Topic
Okay, I'm going to try and make this as simple (lol) as possible.
I am staying at my parents for a while. They have Verizon DSL (yuck). When I used to live with them they also had it. When we first had it, we were given a, at the time, rather nice westell versalink 327w router/gateway/WAP.
Fast forward 4 years to now. I kept the router for myself, they now have a new tiny little modem. Apparently this thing while only having one RJ-45 is DHCP capable.
My brother and I both wanted to access the internet at the same time. So I took the versalink router, disabled its DSL WAN port, and set Ethernet 1 port to the WAN port. I then plugged the modem into the router. No joy. I reset the Versalink's configuration file, while leaving everything else plugged in, magically, it worked. It stayed working until the connection just died over night, then it ceased working. I repeated the same thing. Joy, worked again. Tonight the connection died again, and I'm back to ground zero, except the whole router-resetting ceased working. It's PPPoE, but will work as a routed bridge. I am totally lost.
Oh yeah, one last thing, the reason I'm just not using the versalink is, Even with the PPPOE user name and password inserted, it refuses to work. It will detect the DSL and sync, but not give actual connectivity.
I am staying at my parents for a while. They have Verizon DSL (yuck). When I used to live with them they also had it. When we first had it, we were given a, at the time, rather nice westell versalink 327w router/gateway/WAP.
Fast forward 4 years to now. I kept the router for myself, they now have a new tiny little modem. Apparently this thing while only having one RJ-45 is DHCP capable.
My brother and I both wanted to access the internet at the same time. So I took the versalink router, disabled its DSL WAN port, and set Ethernet 1 port to the WAN port. I then plugged the modem into the router. No joy. I reset the Versalink's configuration file, while leaving everything else plugged in, magically, it worked. It stayed working until the connection just died over night, then it ceased working. I repeated the same thing. Joy, worked again. Tonight the connection died again, and I'm back to ground zero, except the whole router-resetting ceased working. It's PPPoE, but will work as a routed bridge. I am totally lost.
Oh yeah, one last thing, the reason I'm just not using the versalink is, Even with the PPPOE user name and password inserted, it refuses to work. It will detect the DSL and sync, but not give actual connectivity.
Comments
Step #2 Profit.
Oh, but that won't be good enough.... so....
Step #1: This 'Modem' is it an IP capable device itself? I.E Do you gateway to it? If so, it's basically a 2 port router (or a Bridge if you want to get picky, but whatever) or is it actually Modem, and it's just an attachment to an existing device, and all it can do is dialup?
I'm going to presume the former. Work your way up the OSI stack as usual, if so. Get connectivity to the router, ensuring you have it as a default gateway. Connect modem, configure modem IP (and you'll need to have 2 distinct IP subnets, because you're performing proper routing now dawg.) and ensure the Router can default gateway to it. I suppose my general advice is; don't try to do everything at once. Work 'upwards' in complexity, especially when troubleshooting. I also tend to Visio network diagram even the most basic setups, because it makes the whole process of tracing things simpler mentally.
Personally, I'd either try and solve the whole "good router doesn't work w/ modem" thing, which is probably due to some retarded Verizon MAC address locking or something. And failing that, turn off DHCP on R2 and just use its built-in switch to hook everything up.
Does this mean that it is trying to sync and just does not succeed?
What exactly do you mean by: It syncs, but does not give actual connectivity?
Every modem only knows certain modulations and thusly an old modem might not work with a new ADSL2+ line. Sometimes a firmware update can help.
On another note: Bringing multiple routers in the same home net is always a bad idea, cause those suckers usually dont immediately accept their set state. So even if you disable everything except the modem capabilities for one of the routers it will still boot up, fully capable of acting like a router, before it then disabled its own router functionality.
<b>
The following should work:
Hook the modem to be router up the splitter or directly into the telephone jack. Wait 5 minutes so the damn thing stops pretending to be a router. Now plug the router to be router into the modem to be router and enjoy. THis however might horribly fail if for some reason the modem to be router resets and then shortly starts acting as a router again.
</b>
So yeah, consumer level hardware is cheap and it will work, but only if you either have a single jack of all trades or if you buy a specialist for every single task.
I am staying at my parents for a while. They have Verizon DSL (yuck). When I used to live with them they also had it. When we first had it, we were given a, at the time, rather nice westell versalink 327w router/gateway/WAP.
Fast forward 4 years to now. I kept the router for myself, they now have a new tiny little modem. Apparently this thing while only having one RJ-45 is DHCP capable.
My brother and I both wanted to access the internet at the same time. So I took the versalink router, disabled its DSL WAN port, and set Ethernet 1 port to the WAN port. I then plugged the modem into the router. No joy. I reset the Versalink's configuration file, while leaving everything else plugged in, magically, it worked. It stayed working until the connection just died over night, then it ceased working. I repeated the same thing. Joy, worked again. Tonight the connection died again, and I'm back to ground zero, except the whole router-resetting ceased working. It's PPPoE, but will work as a routed bridge. I am totally lost.
Oh yeah, one last thing, the reason I'm just not using the versalink is, Even with the PPPOE user name and password inserted, it refuses to work. It will detect the DSL and sync, but not give actual connectivity.<!--QuoteEnd--></div><!--QuoteEEnd-->
hiya.
I actually worked for verizon dsl tech support up in ontario (the largest center in North america and am very fimilar with the 327W so I can more than likely help you out (yay!)
shame I don't work there anymore (moved to a different town) so I can't do everything I could before but I'd be happy to take a shot <img src="style_emoticons/<#EMO_DIR#>/smile-fix.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile-fix.gif" />
just to make sure I understand the issue.
you brought back the 327w to your parents place and then disabled some things and hooked it up to the other modem right?
also what kind of modem is that other device? for example 2100 2200 etc? did you get it from verizon?
and also just to verify your a PPPoE customer or DHCP?
I figured I could just reassign the 327w to use Eth1 as a WAN uplink and plug the 6100 into it but it does not communicate. Sometimes It would but only my brother's computer could get internet. Mine wouldn't.
They used to be DHCP when we had the 327, but now with the 6100 Its PPPoE. I have verified the password to be correct, I've tried just about everything and just can't get them working.
When you said "you brought back the 327w to your parents place and then disabled some things and hooked it up to the other modem right?" that is correct.
Just curious now (coming from a UK ISP, we use PPPoA over here, because British Telecom's core is built on ATM - Note, I'm not in any way suggesting it's better!) but why are these mutually exclusive to you guys?
Update: From what I understand now having browsed a bit of documentation, you mean IPoE, but apparently the US market refers to it as DHCP because that's used primarily in the negotiation. D'oh. It just seemed to be a very odd mismatching of terms.
I figured I could just reassign the 327w to use Eth1 as a WAN uplink and plug the 6100 into it but it does not communicate. Sometimes It would but only my brother's computer could get internet. Mine wouldn't.
They used to be DHCP when we had the 327, but now with the 6100 Its PPPoE. I have verified the password to be correct, I've tried just about everything and just can't get them working.
When you said "you brought back the 327w to your parents place and then disabled some things and hooked it up to the other modem right?" that is correct.<!--QuoteEnd--></div><!--QuoteEEnd-->
ok the best thing you can do is simply hook up just the 327w. I would suggest resetting it (the small pin hole in teh back holding it down for minimum of 30 seconds) assuming you or someone in the house knows the username and password of your internet account (you may be actually a Open PPPOE customer which is like a combination of both in which case it would not matter what you put in either field)
so the default ip address will be 192.168.1.1 and the username and password for modem access with me admin and password.
then depending on the version of the modem (if it has a black and red background it's the latest firmware, if it's anything with blue it is not)
if it's black and red then there will more than likely be an auto setup
if not you can (if you know your way around and feel comfortable with it) do it yourself or call verizon frontline tech support and they will be more than capable of helping you with basic setup. I could help you but if you reset the modem you won't be able to get online so we would not be able to communicate XD
best of luck mate hope this helps
so you still have it hooked up to the 6100 modem?
Its possible you'll need to use a crossover cable between the "modem" and router.