Not receiving WAN

[Doorenism]

Hiya!

 

I'm a university student, and switched dorms this year. I've been using my neighbours WiFi as I can't get mine to work. Sadly this neighbour isn't around, so I don't have WiFi.
I could connect my pc to the wall ethernet port, but my cable is too short. I have a router that worked on the previous dorm, but somehow it doesn't work here. It's a Belkin N900. WAN, Subnet mask etc is all NULL. 

Now, I'm not sure if it has to do with brand or something, because everyone around me seems to be using TP-Link or Sitecom...

 

Any help is appreciated (I'm not very tech savvy though, keep that in mind.)

The logs show this:

 

Spoiler

Jan 1 00:00:19		Lease of 10.9.211.216 obtained, lease time 86400
Jan 1 00:00:19		version 1.4 started
Jan 1 00:00:15		started, version 2.60 cachesize 150
Jan 1 00:00:19		overflow: 4 log entries lost
Jan 1 00:00:19		started, version 2.60 cachesize 150
Jan 1 00:00:19		compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack
Jan 1 00:00:19		read /etc/hosts - 3 addresses
Jan 1 00:00:19		using nameserver 8.8.8.8#53
Jan 1 00:00:19		using nameserver 10.2.205.63#53
Jan 1 00:00:19		using nameserver 10.2.205.62#53
Jan 1 00:00:21		Warn: The origin for route 239.255.255.250 changed from 192.168.2.1 to 192.168.169.1
Jan 1 00:00:22		Warn: The origin for route 239.255.255.250 changed from 192.168.169.1 to 192.168.1.254
Jan 1 00:00:23		Warn: The origin for route 239.255.255.250 changed from 192.168.1.254 to 10.9.211.3
Jan 1 00:00:24		Warn: The origin for route 239.255.255.250 changed from 10.9.211.3 to 192.168.1.5
Jan 1 00:00:25		Warn: The origin for route 239.255.255.250 changed from 192.168.1.5 to 10.9.211.106
Jan 1 00:00:27		Warn: The origin for route 239.255.255.250 changed from 10.9.211.106 to 192.168.1.1
Jan 1 00:00:27		Warn: The origin for route 239.255.255.250 changed from 192.168.1.1 to 10.9.211.52
Jan 1 00:00:33		Warn: The origin for route 239.255.255.250 changed from 10.9.211.52 to 10.9.209.118
Jan 1 00:00:44		Warn: The origin for route 239.255.255.250 changed from 10.9.209.118 to 10.9.210.112
Jan 1 00:00:45		192.168.2.2 login success
Jan 1 00:00:47		Warn: The origin for route 239.255.255.250 changed from 10.9.210.112 to 10.9.211.52
Jan 1 00:00:51		Warn: The origin for route 239.255.255.250 changed from 10.9.211.52 to 10.9.210.204

[Electronics Wizardy]

2 minutes ago, Doorenism said:

I could connect my pc to the wall ethernet port, but my cable is too short

Get a longer cable, this feels like the simple solution.

[Oshino Shinobu]

If you're in a dorm, I'd assume you're using a shared network rather than everyone having their own connection to the ISP, so you shouldn't need a router. 

 

Connect your PC to the ethernet port to see if it works. If it does, buy a longer cable. If you want WiFi as well, buy a switch and an access point. 

 

EDIT: On the router, does it have a WAN port? If so, don't use it, use one of the LAN ports and enable access point mode if it has one. If not, disable DHCP and NAT. 

[Levisallanon]

4 minutes ago, Doorenism said:

Hiya!

 

I'm a university student, and switched dorms this year. I've been using my neighbours WiFi as I can't get mine to work. Sadly this neighbour isn't around, so I don't have WiFi.
I could connect my pc to the wall ethernet port, but my cable is too short. I have a router that worked on the previous dorm, but somehow it doesn't work here. It's a Belkin N900. WAN, Subnet mask etc is all NULL. 

Now, I'm not sure if it has to do with brand or something, because everyone around me seems to be using TP-Link or Sitecom...

 

Any help is appreciated (I'm not very tech savvy though, keep that in mind.)

The logs show this:

 

  Reveal hidden contents

Jan 1 00:00:19		Lease of 10.9.211.216 obtained, lease time 86400
Jan 1 00:00:19		version 1.4 started
Jan 1 00:00:15		started, version 2.60 cachesize 150
Jan 1 00:00:19		overflow: 4 log entries lost
Jan 1 00:00:19		started, version 2.60 cachesize 150
Jan 1 00:00:19		compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack
Jan 1 00:00:19		read /etc/hosts - 3 addresses
Jan 1 00:00:19		using nameserver 8.8.8.8#53
Jan 1 00:00:19		using nameserver 10.2.205.63#53
Jan 1 00:00:19		using nameserver 10.2.205.62#53
Jan 1 00:00:21		Warn: The origin for route 239.255.255.250 changed from 192.168.2.1 to 192.168.169.1
Jan 1 00:00:22		Warn: The origin for route 239.255.255.250 changed from 192.168.169.1 to 192.168.1.254
Jan 1 00:00:23		Warn: The origin for route 239.255.255.250 changed from 192.168.1.254 to 10.9.211.3
Jan 1 00:00:24		Warn: The origin for route 239.255.255.250 changed from 10.9.211.3 to 192.168.1.5
Jan 1 00:00:25		Warn: The origin for route 239.255.255.250 changed from 192.168.1.5 to 10.9.211.106
Jan 1 00:00:27		Warn: The origin for route 239.255.255.250 changed from 10.9.211.106 to 192.168.1.1
Jan 1 00:00:27		Warn: The origin for route 239.255.255.250 changed from 192.168.1.1 to 10.9.211.52
Jan 1 00:00:33		Warn: The origin for route 239.255.255.250 changed from 10.9.211.52 to 10.9.209.118
Jan 1 00:00:44		Warn: The origin for route 239.255.255.250 changed from 10.9.209.118 to 10.9.210.112
Jan 1 00:00:45		192.168.2.2 login success
Jan 1 00:00:47		Warn: The origin for route 239.255.255.250 changed from 10.9.210.112 to 10.9.211.52
Jan 1 00:00:51		Warn: The origin for route 239.255.255.250 changed from 10.9.211.52 to 10.9.210.204

it seems it doesn't get any info from DHCP. How did you set it up (bridge mode or something else etc).
You only want to use if for wireless?
Could it be there is a mac filter on the devices and you first need to register it?

[Windows7ge]

It's possible to setup managed switches to stop switches/routers from being plugged into them. The campus may do this for security reasons. (Though based on the errors this doesn't look like the issue) It's looks like a routing issue.

 

For now your best option is to just go to your local store and buy a longer Ethernet cable.

[Doorenism]

7 minutes ago, Electronics Wizardy said:

Get a longer cable, this feels like the simple solution.

 

4 minutes ago, Oshino Shinobu said:

If you're in a dorm, I'd assume you're using a shared network rather than everyone having their own connection to the ISP, so you shouldn't need a router. 

 

Connect your PC to the ethernet port to see if it works. If it does, buy a longer cable. If you want WiFi as well, buy a switch and an access point. 

 

EDIT: On the router, does it have a WAN port? If so, don't use it, use one of the LAN ports and enable access point mode if it has one. If not, disable DHCP and NAT. 

 

1 minute ago, Windows7ge said:

It's possible to setup managed switches to stop switches/routers from being plugged into them. The campus may do this for security reasons. (Though based on the errors this doesn't look like the issue) It's looks like a routing issue.

 

For now your best option is to just go to your local store and buy a longer Ethernet cable.

I enjoy having wifi on my phone when I'm in my room. Decided to drag my pc around for experimenting, plugged it in... No internet. Ran problemsolver and it states: " The external apparatus or external source does not accept the connection ". Also, my router does have an access point option. And I was using the wan port before.

[Windows7ge]

4 minutes ago, Doorenism said:

 

 

I enjoy having wifi on my phone when I'm in my room. Decided to drag my pc around for experimenting, plugged it in... No internet. Ran problemsolver and it states: " The external apparatus or external source does not accept the connection ". Also, my router does have an access point option. And I was using the wan port before.

If you're saying plugging your computer into the wall is giving you nothing now then you need to take that up with the college.

 

Or if you're adventurous you can check the internals of the RJ-45 wall jack and see if it has any broken wires. I know kids aren't the most gentle. If it looks broken re-terminate it (will require tools).

[Doorenism]

1 minute ago, Windows7ge said:

If you're saying plugging your computer into the wall is giving you nothing now then you need to take that up with the college.

 

Or if you're adventurous you can check the internals of the RJ-45 wall jack and see if it has any broken wires. I know kids aren't the most gentle. If it looks broken re-terminate it (will require tools).

Judging how every port except 80 and 443 are blocked should tell you something about the quality of our IT department. They're a bunch of incompetent idiots who block everything to limit data usage. Anyhow, I'll go complain tomorrow.

[Windows7ge]

9 minutes ago, Doorenism said:

Judging how every port except 80 and 443 are blocked should tell you something about the quality of our IT department. They're a bunch of incompetent idiots who block everything to limit data usage. Anyhow, I'll go complain tomorrow.

Unfortunately it's not incompetence it's all about control. They don't want you using much bandwidth like you stated. Even so installing your own router should work unless the switches are configured to block them. If plugging directly into the wall doesn't work then yeah that's a IT dept issue they need to resolve.

 

Sometimes though it's because the campus is on a domain that you have to login to and register your device under your account. That's what my college does to keep track of users. (Though they don't do a very good job. Many holes in the security but I won't go into it.) Now that's incompetence.