ROBIN -  Open Source Mesh Network Forum Index ROBIN - Open Source Mesh Network
users community forum
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Node won't connect as Gateway

 
Post new topic   Reply to topic    ROBIN - Open Source Mesh Network Forum Index -> Absolute Beginner Talk
View previous topic :: View next topic  
Author Message
Ads






Posted: Tue Sep 26, 2017 11:33 am    Post subject: Ads

Back to top
harry_the_face
Power User
Power User


Joined: 24 Aug 2009
Posts: 254

PostPosted: Mon Mar 07, 2011 5:05 am    Post subject: Node won't connect as Gateway Reply with quote

I have: Dsl Modem> Belkin Router > Eugenius 2611P.

I flashed the node and connected it to my router at home and the node connected as a gateway and stayed connected all night. I unplugged it brought it to the location that I wanted to set it up and Plugged it in (Config above) and it WILL NOT connect as a gateway! I put this 2611P in the place of an OM1P so I know that the DSL, and Router work. Is it a problem with the node, or the router?

I got the Logread off the node and it did say this:

Mar 7 03:20:15 "Network Name" daemon.warn dnsmasq[2770]: no address range available for DHCP request via br-lan
Back to top
View user's profile Send private message
bconverse
Moderator
Moderator


Joined: 07 Mar 2008
Posts: 848
Location: Little Rock, AR (USA)

PostPosted: Mon Mar 07, 2011 12:53 pm    Post subject: Reply with quote

Post full logread from boot
Back to top
View user's profile Send private message
harry_the_face
Power User
Power User


Joined: 24 Aug 2009
Posts: 254

PostPosted: Mon Mar 07, 2011 6:59 pm    Post subject: Reply with quote

I rebooted the node and then ran logread and this is what I got. It means nothing to me so hope it helps:

Dec 31 16:01:07 WideOpenWireless40A user.info : ### adding option 0x35
Dec 31 16:01:07 WideOpenWireless40A user.info : ### adding option 0x3d
Dec 31 16:01:07 WideOpenWireless40A user.info : ### adding option 0x3c
Dec 31 16:01:07 WideOpenWireless40A user.info : ### adding option 0x39
Dec 31 16:01:07 WideOpenWireless40A user.info : Sending discover...
Dec 31 16:01:07 WideOpenWireless40A user.info : ### adapter index 2
Dec 31 16:01:07 WideOpenWireless40A user.info : ### adapter hardware address 00:02:6f:98:88:2c
Dec 31 16:01:08 WideOpenWireless40A user.info : ### Waiting on select...
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x35
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x3d
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x3c
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x39
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adapter index 2
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adapter hardware address 00:02:XX:XX:XX:XX
Dec 31 16:01:08 WideOpenWireless40A user.info : ### Waiting on select...
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x35
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x3d
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x3c
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x39
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adapter index 2
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adapter hardware address 00:02XX:XX:XX:XX
Dec 31 16:01:08 WideOpenWireless40A user.info : ### Waiting on select...
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x35
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x3d
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x3c
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x39
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adapter index 2
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adapter hardware address 00:02:XX:XX:XX:XX
Dec 31 16:01:08 WideOpenWireless40A user.info : ### Waiting on select...
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x35
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x3d
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x3c
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x39
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adapter index 2
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adapter hardware address 00:02:XX:XX:XX:XX
Dec 31 16:01:08 WideOpenWireless40A user.info : ### Waiting on select...
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x35
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x3d
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x3c
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x39
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adapter index 2
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adapter hardware address 00:02:XX:XX:XX:XX
Dec 31 16:01:08 WideOpenWireless40A user.info : ### Waiting on select...
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x35
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x3d
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x3c
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x39
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adapter index 2
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adapter hardware address 00:02:XX:XX:XX:XX
Dec 31 16:01:08 WideOpenWireless40A user.info : ### Waiting on select...
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x35
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x3d
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x3c
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adding option 0x39
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adapter index 2
Dec 31 16:01:08 WideOpenWireless40A user.info : ### adapter hardware address 00:02:XX:XX:XX:XX
Dec 31 16:01:08 WideOpenWireless40A user.info : ### Waiting on select...
Dec 31 16:01:08 WideOpenWireless40A user.info : ### vfork'ing and execle'ing /usr/share/udhcpc/robin.script
Dec 31 16:01:08 WideOpenWireless40A user.info : No lease, failing
Dec 31 16:01:08 WideOpenWireless40A user.info : killall: udhcpc: no process killed
Dec 31 16:01:08 WideOpenWireless40A user.info : processing UCI file: mesh, part 1
Dec 31 16:01:08 WideOpenWireless40A user.info : processing UCI file: mesh, part 2
Dec 31 16:01:09 WideOpenWireless40A user.info : processing UCI file: general
Dec 31 16:01:09 WideOpenWireless40A user.info : processing UCI file: acl
Dec 31 16:01:09 WideOpenWireless40A user.info : processing UCI file: iprules
Dec 31 16:01:10 WideOpenWireless40A user.info : processing UCI file: madwifi
Dec 31 16:01:10 WideOpenWireless40A user.info : processing UCI file: management
Dec 31 16:01:12 WideOpenWireless40A user.info : processing UCI file: node
Dec 31 16:01:12 WideOpenWireless40A user.info : processing UCI file: radio
Dec 31 16:01:12 WideOpenWireless40A user.info : processing UCI file: ra_switch
Dec 31 16:01:12 WideOpenWireless40A user.info : processing UCI file: cp_switch
Dec 31 16:01:12 WideOpenWireless40A user.info : processing UCI file: chilli
Dec 31 16:01:24 WideOpenWireless40A user.info : brctl: invalid argument '0' to 'timespec'
Dec 31 16:01:24 WideOpenWireless40A user.info kernel: device ath1 entered promiscuous mode
Dec 31 16:01:24 WideOpenWireless40A user.info kernel: br-lan: port 1(ath1) entering learning state
Dec 31 16:01:31 WideOpenWireless40A authpriv.info dropbear[1724]: Running in background
Dec 31 16:01:33 WideOpenWireless40A user.info kernel: br-lan: port 1(ath1) entering disabled state
Dec 31 16:01:33 WideOpenWireless40A user.info kernel: device ath1 left promiscuous mode
Dec 31 16:01:33 WideOpenWireless40A user.info kernel: br-lan: port 1(ath1) entering disabled state
Dec 31 16:01:43 WideOpenWireless40A user.info kernel: device eth0 entered promiscuous mode
Dec 31 16:01:43 WideOpenWireless40A user.info kernel: br-lan: port 1(eth0) entering learning state
Dec 31 16:01:58 WideOpenWireless40A user.info kernel: br-lan: topology change detected, propagating
Dec 31 16:01:58 WideOpenWireless40A user.info kernel: br-lan: port 1(eth0) entering forwarding state
Dec 31 16:01:58 WideOpenWireless40A user.info kernel: device ath1 entered promiscuous mode
Dec 31 16:01:58 WideOpenWireless40A user.info kernel: br-lan: port 2(ath1) entering learning state
Dec 31 16:01:59 WideOpenWireless40A user.info kernel: device ath1 left promiscuous mode
Dec 31 16:01:59 WideOpenWireless40A user.info kernel: br-lan: port 2(ath1) entering disabled state
Dec 31 16:02:04 WideOpenWireless40A user.info kernel: device ath1 entered promiscuous mode
Dec 31 16:02:04 WideOpenWireless40A user.info kernel: br-lan: port 2(ath1) entering learning state
Dec 31 16:02:05 WideOpenWireless40A user.info : ath0
Dec 31 16:02:09 WideOpenWireless40A user.info : using gpio pin 4
Dec 31 16:02:09 WideOpenWireless40A user.info : using gpio pin 6
Dec 31 16:02:09 WideOpenWireless40A user.info : using gpio pin 7
Dec 31 16:02:09 WideOpenWireless40A user.info : Parsing file: "/etc/olsrd.conf"
Dec 31 16:02:09 WideOpenWireless40A daemon.info olsrd[2724]: Writing "0" to /proc/sys/net/ipv4/conf/all/send_redirects
Dec 31 16:02:09 WideOpenWireless40A daemon.info olsrd[2724]: Writing "0" to /proc/sys/net/ipv4/conf/ath0/rp_filter
Dec 31 16:02:09 WideOpenWireless40A daemon.info olsrd[2724]: Writing "0" to /proc/sys/net/ipv4/conf/ath0/send_redirects
Dec 31 16:02:09 WideOpenWireless40A daemon.info olsrd[2724]: Adding interface ath0
Dec 31 16:02:09 WideOpenWireless40A daemon.info olsrd[2724]: New main address: 5.1xx.1xx.xx
Dec 31 16:02:10 WideOpenWireless40A daemon.info olsrd[2724]: olsr.org - 0.5.6-r8 successfully started
Dec 31 16:02:20 WideOpenWireless40A user.info kernel: br-lan: topology change detected, propagating
Dec 31 16:02:20 WideOpenWireless40A user.info kernel: br-lan: port 2(ath1) entering forwarding state
Dec 31 16:02:41 WideOpenWireless40A user.info : uci: Entry not found
Dec 31 16:02:42 WideOpenWireless40A daemon.info dnsmasq[2775]: started, version 2.47 cachesize 150
Dec 31 16:02:42 WideOpenWireless40A daemon.info dnsmasq[2775]: compile time options: IPv6 GNU-getopt no-DBus no-I18N TFTP
Dec 31 16:02:42 WideOpenWireless40A daemon.info dnsmasq[2775]: DHCP, IP range 102.1xx.xx.10 -- 102.1xx.xx.250, lease time 2h
Dec 31 16:02:42 WideOpenWireless40A daemon.info dnsmasq[2775]: reading /etc/resolv.conf
Dec 31 16:02:42 WideOpenWireless40A daemon.warn dnsmasq[2775]: ignoring nameserver 127.0.0.1 - local interface
Dec 31 16:02:42 WideOpenWireless40A daemon.info dnsmasq[2775]: using nameserver 208.xx.xxx.220#53
Dec 31 16:02:42 WideOpenWireless40A daemon.info dnsmasq[2775]: using nameserver 208.xx.xxx.222#53
Dec 31 16:02:42 WideOpenWireless40A daemon.info dnsmasq[2775]: read /etc/hosts - 2 addresses
Dec 31 16:02:44 WideOpenWireless40A user.info : flushing ipfilter rules...
Dec 31 16:02:45 WideOpenWireless40A user.info : starting preUp script: chilli
Jan 1 00:02:47 WideOpenWireless40A user.info : chilli: Starting...
Jan 1 00:02:47 WideOpenWireless40A user.notice chilli: Starting...
Jan 1 00:02:48 WideOpenWireless40A local6.info coova-chilli[2977]: CoovaChilli(ChilliSpot) 1.0.13. Copyright 2002-2005 Mondru AB. Licensed under GPL. Copyright 2006-2008 David Bird <dbird@acm.org>. Licensed under GPL. See
Only registered users can see links on this forum!
Register or Login on forum!

for details.
Jan 1 00:02:48 WideOpenWireless40A user.info : chilli: started
Jan 1 00:02:48 WideOpenWireless40A local6.notice coova-chilli[2977]: tun.c: 515: TX queue length set to 100
Jan 1 00:02:48 WideOpenWireless40A user.notice chilli: started
Jan 1 00:02:50 WideOpenWireless40A user.info : iprules.sh: public-AP iface is tun0
Jan 1 00:02:50 WideOpenWireless40A user.notice iprules.sh: public-AP iface is tun0
Jan 1 00:02:50 WideOpenWireless40A authpriv.info dropbear[3046]: Child connection from 5.xxx.xxx.xxx:37274
Jan 1 00:02:51 WideOpenWireless40A user.notice iprules.sh: applying input rules...
Jan 1 00:02:51 WideOpenWireless40A user.info : iprules.sh: applying input rules...
Jan 1 00:02:52 WideOpenWireless40A user.info : iprules.sh: applying AP isolation...
Jan 1 00:02:52 WideOpenWireless40A user.notice iprules.sh: applying AP isolation...
Jan 1 00:02:52 WideOpenWireless40A user.info : iprules.sh: set MTU to auto
Jan 1 00:02:52 WideOpenWireless40A user.notice iprules.sh: set MTU to auto
Jan 1 00:02:52 WideOpenWireless40A user.info : iprules.sh: postrouting and masquerading...
Jan 1 00:02:52 WideOpenWireless40A user.notice iprules.sh: postrouting and masquerading...
Jan 1 00:02:54 WideOpenWireless40A user.info : rc.httpd: started
Jan 1 00:02:54 WideOpenWireless40A user.notice rc.httpd: started
Jan 1 00:02:54 WideOpenWireless40A user.info : iwpriv-mesh.sh: set ath0 mcast_rate to 5500
Jan 1 00:02:54 WideOpenWireless40A user.notice iwpriv-mesh.sh: set ath0 mcast_rate to 5500
Jan 1 00:02:54 WideOpenWireless40A user.notice iwpriv-mesh.sh: set abolt=0 and doth=0 for ath1 ath2
Jan 1 00:02:54 WideOpenWireless40A user.info : iwpriv-mesh.sh: set abolt=0 and doth=0 for ath1 ath2
Jan 1 00:02:54 WideOpenWireless40A user.info : iwpriv-mesh.sh: set abolt=0 and doth=0 for ath1
Jan 1 00:02:54 WideOpenWireless40A user.notice iwpriv-mesh.sh: set abolt=0 and doth=0 for ath1
Jan 1 00:02:54 WideOpenWireless40A user.info : iwpriv-mesh.sh: set abolt=0 and doth=0 for ath2
Jan 1 00:02:54 WideOpenWireless40A user.notice iwpriv-mesh.sh: set abolt=0 and doth=0 for ath2
Jan 1 00:02:54 WideOpenWireless40A user.notice iwpriv-mesh.sh: set ath1 bintval to 100
Jan 1 00:02:54 WideOpenWireless40A user.info : iwpriv-mesh.sh: set ath1 bintval to 100
Mar 7 17:47:55 WideOpenWireless40A local6.err coova-chilli[2977]: options.c: 821: Rereading configuration file and doing DNS lookup
Mar 7 17:47:57 WideOpenWireless40A user.info : kernel.panic_on_oops = 1
Mar 7 17:47:57 WideOpenWireless40A user.notice speed-test: current bandwidth [] 0 Kbps
Mar 7 17:47:57 WideOpenWireless40A user.info : speed-test: current bandwidth [] 0 Kbps
Mar 7 17:47:59 WideOpenWireless40A authpriv.info dropbear[3046]: exit before auth: Timeout before auth
Mar 7 17:48:11 WideOpenWireless40A authpriv.info dropbear[3214]: Child connection from 5.xxx.xxx.xxx:37275
Mar 7 17:48:20 WideOpenWireless40A authpriv.notice dropbear[3214]: password auth succeeded for 'root' from 5.xxx.xxx.xxx:37275
--
Back to top
View user's profile Send private message
bconverse
Moderator
Moderator


Joined: 07 Mar 2008
Posts: 848
Location: Little Rock, AR (USA)

PostPosted: Mon Mar 07, 2011 7:05 pm    Post subject: Reply with quote

It appears to not get a lease from the router

Quote:
Dec 31 16:01:08 WideOpenWireless40A user.info : No lease, failing
Back to top
View user's profile Send private message
harry_the_face
Power User
Power User


Joined: 24 Aug 2009
Posts: 254

PostPosted: Tue Mar 08, 2011 12:23 am    Post subject: Reply with quote

That is what I thought because I took it down and brought it back to my house and connected it to the router here and it connects as a gateway first time.

Any idea why the OM1p has no problem on the router and the 2611P does have a problem?
Back to top
View user's profile Send private message
ispyisail
Site Admin
Site Admin


Joined: 12 Sep 2008
Posts: 4604
Location: New Zealand

PostPosted: Tue Mar 08, 2011 6:34 am    Post subject: Reply with quote

update the firmware on the Belkin Router?

_________________
ROBIN-Mesh Wiki:

Only registered users can see links on this forum!
Register or Login on forum!

Test Network:
Only registered users can see links on this forum!
Register or Login on forum!



Please donate to ROBIN by paypal:

Only registered users can see links on this forum!
Register or Login on forum!

!
Back to top
View user's profile Send private message
harry_the_face
Power User
Power User


Joined: 24 Aug 2009
Posts: 254

PostPosted: Wed Mar 09, 2011 4:17 am    Post subject: Reply with quote

I just updated the firmware like a month ago. This problem is intermittent with this router and only this router. I am beginning to think that it is going bad. I bought a replacement.
Back to top
View user's profile Send private message
harry_the_face
Power User
Power User


Joined: 24 Aug 2009
Posts: 254

PostPosted: Sat Mar 12, 2011 3:53 am    Post subject: Reply with quote

Replaced the router and still have the problems. It is up and down as a Gateway. Is there a way to SSH into the node and KNOW for sure if a node is in Gateway mode, or force Gateway mode?
I am thinking maybe it is a dashboard problem? Maybe saying that it is down when it isn't?

This is driving me crazy!
Back to top
View user's profile Send private message
harry_the_face
Power User
Power User


Joined: 24 Aug 2009
Posts: 254

PostPosted: Mon Mar 14, 2011 6:24 am    Post subject: Reply with quote

Ican SSH into the node but I am not sure what command to run to mae it stay as a gateway or even what command tells if it is in gateway mode currently.
Back to top
View user's profile Send private message
ispyisail
Site Admin
Site Admin


Joined: 12 Sep 2008
Posts: 4604
Location: New Zealand

PostPosted: Mon Mar 14, 2011 10:04 am    Post subject: Reply with quote

My post was rubbish so I have deleted it. I re-read the original post

_________________
ROBIN-Mesh Wiki:

Only registered users can see links on this forum!
Register or Login on forum!

Test Network:
Only registered users can see links on this forum!
Register or Login on forum!



Please donate to ROBIN by paypal:

Only registered users can see links on this forum!
Register or Login on forum!

!
Back to top
View user's profile Send private message
Antonio (isleman)
Site Admin
Site Admin


Joined: 10 Feb 2008
Posts: 2323
Location: Toscana, Italy

PostPosted: Mon Mar 14, 2011 11:03 am    Post subject: Reply with quote

you can force the 2611P to act as a statically-configured-gateway but that doesn't fix the cause...
Back to top
View user's profile Send private message Send e-mail Visit poster's website
harry_the_face
Power User
Power User


Joined: 24 Aug 2009
Posts: 254

PostPosted: Sun Mar 20, 2011 6:15 am    Post subject: Reply with quote

Any idea what the cause is? Is this an Engenius issue or something with my setup. I have similar issues with my Pico2HPs but they are up as gateways more than they are down.
Back to top
View user's profile Send private message
harry_the_face
Power User
Power User


Joined: 24 Aug 2009
Posts: 254

PostPosted: Tue Mar 29, 2011 6:18 am    Post subject: Reply with quote

Still have nodes that won'y connect as gateways despite being connected to the DSL modem by a router. I have tested the cable and it worked fine with OM1P.

What is the problem?!!!
Back to top
View user's profile Send private message
harry_the_face
Power User
Power User


Joined: 24 Aug 2009
Posts: 254

PostPosted: Thu May 12, 2011 3:17 am    Post subject: Reply with quote

So now the only node I can get to connect as a gateway is the OM1P. None of my Pico2HP's or 2611p's will recognize that they are connected to the internet.

I used the following steps to change the "Stay as Gateway" (SAG) time and it did not change. As far as I can tell it doesn't even come up as a gateway. I have one Pico2HP on r3690 and the rest on r2695.


Gateway Nodes
1. To check the “Stay as Gateway” (SAG) time

cat /etc/config/management

Look for the line for SAG and change the time in seconds to a large number ( 3600 = 1 hour)

option 'sag_mode_interval' '3600'

2. To change use, enter the number of seconds you want the node to wait until it changes to a repeater:

vi /etc/config/management


This stops the node changing to a repeater if the etho loses the internet for 1 hour .
Back to top
View user's profile Send private message
brecklandit
Ultimate User
Ultimate User


Joined: 23 Mar 2010
Posts: 717

PostPosted: Thu May 12, 2011 8:39 am    Post subject: Reply with quote

You clearly have an issue with either the DSL routers or cables etc.

2611P works flawlessly with Robin, I have at least 200 in the field, as does MTLowes so they are well tested.

Does the LAN light on the 2611p come on and stay on as the units boot? If not, try connecting the 2611P via a switch (unmanaged) and see if that helps. Have you tried different DSL routers?

_________________
Please support the Robin Mesh project by donating via paypal to:

Only registered users can see links on this forum!
Register or Login on forum!

.
Back to top
View user's profile Send private message
harry_the_face
Power User
Power User


Joined: 24 Aug 2009
Posts: 254

PostPosted: Thu May 12, 2011 3:55 pm    Post subject: Reply with quote

I have two separate cable connections and one DSL connection al using different modems but similar Belkin routers. I would think it was the cord but I can plug an OM1P into the same cord with no problems so unless the other nodes use a wire for connection to the internet that is different than the OM1P it isn't the wire. I will make a few more cords and test it out. I just can't figure why it would have changed suddenly.

Is there a command in SSH that I can run to know what role the node is in? The best way I can tell is to run "update" and if it shows a connection speed after "getting node status" then it is a repeater, otherwise it is a gateway.
Back to top
View user's profile Send private message
robgmann
Ultimate User
Ultimate User


Joined: 06 May 2009
Posts: 512
Location: Monterey, California USA

PostPosted: Thu May 12, 2011 4:21 pm    Post subject: Reply with quote

Well, we're all guessing now, so here's my guess (you're buying beers for whomever figures it out, right?)

1) Are you using the stock POE injector that came with the OM1P? You mentioned plugging the 2611 into the same cord as the OM1P. Make sure you use the correct POE for Engenius.

2) Could be that the modem/ISP's configuration requires you to clone the MAC, for example not allowing the MACs behind that router? Would it help to clone the 2611p MAC address on that Belkin? Maybe for some strange reason, that ISP recognizes the OM1P as a valid router (based on its hardware ID), but for some reason blocks unknown MACs from routing.
(This is a wild-ass guess).

Finally, can you confirm that the OM1P stays as a gateway over several updates? Maybe send the logread from the OM1P.
Back to top
View user's profile Send private message
reverged
Skilled User
Skilled User


Joined: 29 Jul 2009
Posts: 169
Location: Los Angeles, CA

PostPosted: Fri May 13, 2011 5:09 am    Post subject: Reply with quote

As long as we are guessing.....

If you plug your laptop into the router, do you get an IP address and can browse?

Does the router work with ANY OM1P or just the one you have been testing with?

Is the lease pool on the router exhausted?
Does the router have a status page where you can check the dhcp config and lease status?
Back to top
View user's profile Send private message
harry_the_face
Power User
Power User


Joined: 24 Aug 2009
Posts: 254

PostPosted: Mon May 16, 2011 5:36 am    Post subject: Reply with quote

Yes I have a desktop plugged into the same router and it connects at full speed no problem.

It seems to work with any OM1P because all three of my internet connections have OM1P's that are feeding Other nodes with stronger radios (Pico2HP, E-2611P) on the same pole.

I am not sure if the lease pool is exhausted because I am not sure how to look at that. The Belkin does of a web-based interface. I will look to see if there is a way to look at the lease pool.

Could the RJ-45 configuration make a difference? Should I be using the T568-A, or the T568b (AT&T) configuration? I have always made sure that both ends where configured the same but didn't pay much attention to what color went where.

Could it be a POE problem? A few days ago I set up a Pico2HP,( that I had pulled down because it stopped acting as a gateway) on the desk in my office connected to the same router as an OM1P (working as a gateway), and a Pico2HP (That is not working as a gateway). The only difference I could see is the length of cable. The desk not more than 3 feet, the Other Pico more like 15 feet of cable because it is on the roof.

And yes nI will buy a KEG of beer for anyone that can help me figure this out.
Back to top
View user's profile Send private message
reverged
Skilled User
Skilled User


Joined: 29 Jul 2009
Posts: 169
Location: Los Angeles, CA

PostPosted: Mon May 16, 2011 7:21 am    Post subject: Reply with quote

Quote:

Could the RJ-45 configuration make a difference? Should I be using the T568-A, or the T568b (AT&T) configuration? I have always made sure that both ends where configured the same but didn't pay much attention to what color went where.


Absolutely. I don't want to read too much into the statement above, but are you using either T568A or B? You aren't just randomly aligning the wires, are you? I'm hoping the answer is "No". I feel a bit silly asking the question.

In theory it doesn't matter what color pair goes where as long as you maintain pairs correctly pinned out throughout the cabling. Twisted pairs on the data signals are essential.

That being said, for the sake of the poor guy who has to re-terminate a cable in your network down the road, adhering to T568A or B will make life easy for him.


Only registered users can see links on this forum!
Register or Login on forum!

Back to top
View user's profile Send private message
harry_the_face
Power User
Power User


Joined: 24 Aug 2009
Posts: 254

PostPosted: Mon May 16, 2011 3:27 pm    Post subject: Reply with quote

I am a bit embarrassed to say that I have not been using the T568A or B standard because when I started making cables e years ago did know what they were. I did keep the pairs together my standard has been Blue, Blue/white, green, green/white, orange, orange/white, brown, brown white. It made sense to me that as long as both end were the same it should work fine, and it has for 2 years.

I started thinking about it a few days ago and remembered that the T568 standards both have one pair split on the plug at slot 3 and 6. I thought if the power wire are running to close to the LAN wires it might cause enough interference prevent the node from connecting to the internet. The OM1P uses a very weak POE injector, like 4.5v (don't have one close so it may be higher) were the Pico2HP uses a 15v and the 2611P uses a 24 or 48v injector. That would cause the OM1P to work and not the others. It may use a different pair of wires for power or connection to the internet that would make the difference too. Does anyone know the slots on the plug that are used for each thing?

I am going to retip the ends of my pluggs and see if it makes the difference. I will report back.
Back to top
View user's profile Send private message
brecklandit
Ultimate User
Ultimate User


Joined: 23 Mar 2010
Posts: 717

PostPosted: Mon May 16, 2011 4:12 pm    Post subject: Reply with quote

I use the following for all my cables: from left to right and have never had any problems.

Orange/White
Orange
Green/White
Blue
Blue/White
Green
Brown/White
Brown

Thats looking at the plug gold connections on top

_________________
Please support the Robin Mesh project by donating via paypal to:

Only registered users can see links on this forum!
Register or Login on forum!

.
Back to top
View user's profile Send private message
reverged
Skilled User
Skilled User


Joined: 29 Jul 2009
Posts: 169
Location: Los Angeles, CA

PostPosted: Mon May 16, 2011 4:51 pm    Post subject: Reply with quote

Yikes, I'm surprised it worked at all, but if cable runs were short and not a lot of external noise, it could. I have seen some crazy stuff that worked....sort of. Usually there is high packet loss.

The biggest problem with not having a twisted pair is usually crosstalk from TX to RX and vice versa. Since the cables run in a tight bundle for relatively long distances and signals are fast switching, magnetic fields couple from one wire to the other. In a twisted pair, the coupling is more or less equal on each wire in the pair, so the coupling cancels itself out. The same holds true for external noise sources. This is why ethernet and other high speed signals use balanced lines of twisted pair cabling.

The pinout is:

1 TX+
2 TX-
3 RX+
4 V+ (PoE except Engenious)
5 V+ (PoE except Engenious)
6 RX-
7 V- (PoE except Engenious)
8 V- (PoE except Engenious)

Yes, 3 and 6 form a pair.
Most everything today is auto detect, so crossover cables are not required. Crossover cables swap TX and RX pairs in the cable.

Engenious reverses V+ and V- in their power injector (oddly). So it only works with their device or a reversed cable. It usually won't damage another device as there is a blocking diode to protect. But I don't recommend testing another person's design in the field.

The OM1P will run on as little as 5V, but the PS in the box is 12V.
Pico's should run on 12V. Better to check the spec. They ship with 15V.
Engenious probably will not run on 12V, since they are expecting 24V.


Good luck!
Back to top
View user's profile Send private message
brecklandit
Ultimate User
Ultimate User


Joined: 23 Mar 2010
Posts: 717

PostPosted: Mon May 16, 2011 5:03 pm    Post subject: Reply with quote

reverged wrote:

Engenious probably will not run on 12V, since they are expecting 24V.

Good luck!


2610/2611P run fine on 12v - we have loads of battery powered packs in the field using a single 12v battery, plus all our survey kit runs them on 12v as well. Not saying its suggested, just that it works albeit probablly with a lower output than normal.

_________________
Please support the Robin Mesh project by donating via paypal to:

Only registered users can see links on this forum!
Register or Login on forum!

.
Back to top
View user's profile Send private message
harry_the_face
Power User
Power User


Joined: 24 Aug 2009
Posts: 254

PostPosted: Tue May 17, 2011 6:16 am    Post subject: Reply with quote

You will NEVER guess what happened today when I cut the tips off my cables and rewired them to T568b (AT&T) (the one that brecklandit noted above)! Yeah! Everything work as a Gateway!

I am revealed and pissed at the same time because I have had off and on problems with dropped packets for 2 years. I thought it was just environmental because it was not uniform through out my network.

Thank you all so much for your help.

SO who do I owe beer to. Smile
Back to top
View user's profile Send private message
reverged
Skilled User
Skilled User


Joined: 29 Jul 2009
Posts: 169
Location: Los Angeles, CA

PostPosted: Tue May 17, 2011 7:48 am    Post subject: Reply with quote

Can we agree that you roll that keg into the next Robin user's meeting?!?

I am truly glad you got it sorted out.
Back to top
View user's profile Send private message
brecklandit
Ultimate User
Ultimate User


Joined: 23 Mar 2010
Posts: 717

PostPosted: Tue May 17, 2011 8:27 am    Post subject: Reply with quote

@reverged - Well done on some amazing troubleshooting - i wan't you in my corner next time I have problems!

Glad the problem is sorted.

_________________
Please support the Robin Mesh project by donating via paypal to:

Only registered users can see links on this forum!
Register or Login on forum!

.
Back to top
View user's profile Send private message
harry_the_face
Power User
Power User


Joined: 24 Aug 2009
Posts: 254

PostPosted: Tue May 17, 2011 6:54 pm    Post subject: Reply with quote

I didn't know there was Robin users meetings! When and where? I thought I was getting the hang of this but obviously I still have a lot to learn. I like the idea of getting together with other robin users. Are there any in the Pacific NW? Maybe Portland, or Seattle?

If so I will gladly bring a keg for the after party. And it will be the good stuff from a local Micro brew.
Back to top
View user's profile Send private message
robgmann
Ultimate User
Ultimate User


Joined: 06 May 2009
Posts: 512
Location: Monterey, California USA

PostPosted: Tue May 17, 2011 7:30 pm    Post subject: Reply with quote

The Anaptyx crew has offered to organize.
Add to your location in your forum profile. I'm hoping that we might find an obvious quadrant of the planet for a meet up.
Between New Zealand and the West Coast, USA we seem to have good representation. Now if only that Pacific Ocean were a little smaller...
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    ROBIN - Open Source Mesh Network Forum Index -> Absolute Beginner Talk All times are GMT + 1 Hour
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
c d
e



Powered by phpBB © 2001, 2005 phpBB Group

Abuse - Report Abuse - TOS & Privacy.
Powered by forumup.it free forum, create your free forum! Created by Hyarbor & Qooqoa
Confirmed

Page generation time: 4.342