search

sudomesh / sudowrt-firmware

Scripts to build the sudo mesh OpenWRT firmware.
Other
73 stars 19 forks source link

Connecting to Pico2 but not to internet #10

Closed TinajaLabs closed 9 years ago

TinajaLabs commented 10 years ago

Connected directly to Ethernet of Comcast cable modem. The connection to the wifi router is made, but connection to internet fails.

Settings when connected to peoplesopen.net: IPv4: 10.0.7.106, 255.255.255.0 Default Gateway: 10.42.10.10 DHCP: 10.0.7.1 DNS: 10.42.10.10

Settings when connected to private SSID: IPv4: 172.30.0.145, 255.255.255.0 Default Gateway: 172.30.0.1 DHCP: 172.30.0.1 DNS: 172.30.0.1

Please advise on further troubleshooting. chris@tinajalabs.com

Juul commented 10 years ago

Can you tell me what IP eth0 on the sudomesh node has? Maybe it's getting a 10.0.0.0/8 address from the comcast modem?

TinajaLabs commented 10 years ago

Running ifconfig, eth0 has no ip address.

br-openmesh has 10.0.7.1 priv0 has 172.30.0.1 lo has the typical 127.0.0.1

all the rest have no associated ip.

TinajaLabs commented 10 years ago

Comcast info:

Default Gateway: 24.130.120.1 DHCP: 24.130.120.132 DNS: 68.87.76.182

Juul commented 10 years ago

Hm. Could it be that comcast is using MAC filtering?

TinajaLabs commented 10 years ago

When connecting the Pico2 BEHIND the firewall, the pico2 connects to the internet as expected.

My laptop when connected to PeoplesOpen.net: getting +- 3.4 Mbps 199.175.49.22 10.0.7.106 255.0.0.0 Gateway: 10.42.10.10 DHCP: 10.0.7.1 DNS: 10.42.10.10

When connected to private ssid: getting +- 10-11 Mbps 172.30.0.145 255.255.255.0 Gateway: 172.30.0.1 DHCP: 172.30.0.1 DNS: 172.30.0.1

TinajaLabs commented 10 years ago

Word about Comcast connectivity.

So I'm trying to connect the Pico2 directly to the Comcast modem. I already have a firewall box connected to the modem, so by putting a simple switch between the modem and the firewall, I had hoped I could accomplish this configuration... But!

It seems most non-business Comcast accounts only allow one device and one IP. '( from this post: http://goo.gl/YYd5CT

"The DHCP address you are assigned by the Comcast system is associated with the MAC address of the device directly connected to the modem. So, every router you connect to test will get a diffferent IP, but if you swap out devices, and leave something disconnectd for a short period, it will normally (no guarantees) get the same IP address the next time you connect it. The IPs assigned by the Comcast DHCP servers are dynamic, however they actually change very seldom, unless Comcast re-distribute their public subnets.

That being said, you can't have multiple IPs assigned to your account. In reality, IPs are not assigned to individual accounts. What is configured at the account level is the number of devices that can be connected to the modem and receive an IP, and for residential accounts, that is one device."

wrought commented 10 years ago

I'm getting a similar issue, and also have comcast, see #11 for updates.

Parsing your issue, trying to figure out what info may apply to my situation..

Juul commented 9 years ago

No longer relevant. So much has changed.