Broadband-Hamnet™ Forum
Welcome Guest   [Register]  [Login]
«StartPrev271272273274275276277278279280NextEnd»
 Subject :Re:VPN / GRE tunneling.. 2013-12-21- 04:52:31 
EB5JEQ
Member
Joined: 2013-09-21- 14:11:41
Posts: 8
Location: Elche Alicante Spain
 
Forum : Sweden/Finland
Topic : VPN / GRE tunneling

Waldek, excelent HSMM installation .

Johan: I make the basic mods in my router for establish the vpn links. I send to you and email for answer for the parameters of the link config. I wait your answer.

I have other doubt : 

For config my dsl router ( ports 47&1723 ), my problem is that this home router, don't permit two ips in diferent subnets.


My local lan is in the segment 192.168.0.x , and the lan ip of the mesh node is 172.27.0.1.


I can change the ip of the mesh node to the 192.168.0.x segment ?

73's



IP Logged
 Subject :Re:SSH login problems.. 2013-12-21- 04:42:35 
EB5JEQ
Member
Joined: 2013-09-21- 14:11:41
Posts: 8
Location: Elche Alicante Spain
 
Forum : General
Topic : SSH login problems

ok, Bob it works OK!!!

IP Logged
 Subject :Re:HSMM-Mesh and AmprNet.. 2013-12-21- 00:44:46 
sp2ong
Member
Joined: 2013-10-30- 10:57:25
Posts: 72
Location
Forum : How we used HSMM-MESH™
Topic : HSMM-Mesh and AmprNet

Ok I have working setup with my WRT54 which is connected to my local AmprNet GW and now any

local Mesh Node can connect to AmprNet hosts

Script setup tunnel where 44.165.3.254 and IP WAN 192.168.1.5 is my WRT54 and 44.165.3.1 is IP interface tun0 on my AMprNet GW server

# AmprNet tunnel
ip tunnel add tun0 mode ipip remote 192.168.1.2 local 192.168.1.5 ttl 255
ifconfig tun0 44.165.3.254 pointopoint 44.165.3.1 mtu 1480 up
route add -net 44.0.0.0/8 gw 44.165.3.1
iptables -t nat -A POSTROUTING -s 10.0.0.0/8 -o tun0 -j MASQUERADE

I have add on my WRT54 which is AMprNet GW now for Mesh nodes information about default routing 44/8 network via this Mesh Node. In /etc/config.mesh/olsrd.conf I have add in:

Hna4
{
44.0.0.0 255.0.0.0
}

73 Waldek


IP Logged
 Subject :Re:HSMM-Mesh and AmprNet.. 2013-12-20- 21:51:27 
sp2ong
Member
Joined: 2013-10-30- 10:57:25
Posts: 72
Location
Forum : How we used HSMM-MESH™
Topic : HSMM-Mesh and AmprNet

Hi,

I have try setup IPIP on WRT54 with HSMM v1.0 but it is look that busybox in our firmware is very old

BusyBox v1.4.2 (2008-08-04 21:28:11 CDT) multi-call binary

it is look that in this version "ip rouet" is not full support.

I have try follow:

ip addr add 44.165.3.254/32 dev tunl0
ip link set dev tunl0 up
ifconfig tunl0 mtu 1500

iptables -t nat -A POSTROUTING -s 10.0.0.0/8 -o tunl0 -j MASQUERADE
ip rule add to 44.0.0.0/8 table 44 priority 44
ip route add 44.0.0.0/8 dev tunl0 via 192.168.1.2 onlink table 44

but last command don't work

How to upgrade busybox on our firmware ???

IP Logged
 Subject :Interesting scripts for GL routers... 2013-12-20- 21:24:17 
W7REA
Member
Joined: 2013-03-05- 21:13:59
Posts: 11
Location: Gillette Wy - DN74gg
 
Forum : General
Topic : Interesting scripts for GL routers.

Wasn't sure where to start this thread...

Would it be possible to get a collection of the interesting or helpful scripts that people have come up with?

Example: Someone came up with using the link light on the front of the routers to indicate whether or not they were in range of another mesh node, someone else had the idea that either that light or another flashed out his call sign.

In one way it kind of takes the fun out of experimenting and finding them out, but for those of us that aren't Linux gurus it'd make life a lot simpler.

I use the 'range indicator' script on mine, but would like to add the call sign flasher as well.


Thanks!

Robert, W7REA

IP Logged
 Subject :Re:OLSR Switch on Windows works to connect directly to the mesh... 2013-12-20- 15:18:18 
kv4pc
Member
Joined: 2013-09-30- 20:06:03
Posts: 47
Location: Madison, AL
 
Forum : Applications
Topic : OLSR Switch on Windows works to connect directly to the mesh.

Your settings are same as mine. There arent any errors in your Output window. I dont know what else to say or try.

Im posting my Nodes tab so you can see what it looks like with a connected mesh. The 172.30.1.2 address is my end of a GRE tunnel connecting the two 10.x.x.x nodes.

I have also post my Default.olsr file so you can see what is in it FWIW.

73;

Bob KV4PC



#

# Configuration file for solsr.org - pre-0.5.6-r3

# automatically generated by olsrd-cnf parser v. 0.1.2

#

 

# Debug level(0-9)

# If set to 0 the daemon runs in the background

 

DebugLevel 0

 

# IP version to use (4 or 6)

 

IpVersion 4

 

# FIBMetric ("flat", "correct", or "approx")

 

FIBMetric "flat"

 

# HNA IPv4 routes

# syntax: netaddr/prefix

 

Hna4 {

}

 

# Should olsrd keep on running even if there are

# no interfaces available? This is a good idea

# for a PCMCIA/USB hotswap environment.

# "yes" OR "no"

 

AllowNoInt yes

 

# TOS(type of service) to use. Default is 16

 

TosValue 16

 

# Policy Routing Table to use. Default is 254

 

RtTable 254

 

# Policy Routing Table to use for the default Route. Default is 0 (Take the same table as specified by RtTable)

 

RtTableDefault 0

 

# The fixed willingness to use(0-7)

# If not set willingness will be calculated

# dynammically based on battery/power status

 

#Willingness 4

 

# Allow processes like the GUI front-end

# to connect to the daemon.

 

IpcConnect {

MaxConnections 1

Host 127.0.0.1

Net 10.0.0.0/8

Net 192.168.1.0/24

}

 

# Hysteresis adds more robustness to the

# link sensing.

# Used by default. 'yes' or 'no'

 

UseHysteresis no

 

# Hysteresis parameters

# Do not alter these unless you know

# what you are doing!

# Set to auto by default. Allowed

# values are floating point values

# in the interval 0,1

# THR_LOW must always be lower than

# THR_HIGH!!

 

#HystScaling 0.50

#HystThrHigh 0.80

#HystThrLow 0.30

 

# Polling rate in seconds(float).

# Auto uses default value 0.05 sec

 

Pollrate 0.05

# Interval to poll network interfaces for configuration

# changes. Defaults to 2.5 seconds

NicChgsPollInt 2.50

# TC redundancy

# Specifies how much neighbor info should

# be sent in TC messages

# Possible values are:

# 0 - only send MPR selectors

# 1 - send MPR selectors and MPRs

# 2 - send all neighbors

#

# defaults to 0

 

TcRedundancy 2

 

# MPR coverage

# Specifies how many MPRs a node should

# try select to reach every 2 hop neighbor

# Can be set to any integer >0

# defaults to 1

 

MprCoverage 7

 

# Link quality level

# 0 = do not use link quality

# 1 = use link quality for MPR selection

# 2 = use link quality for MPR selection and routing

 

LinkQualityLevel 2

 

# Fish Eye algorithm

# 0 = do not use fish eye

# 1 = use fish eye

 

LinkQualityFishEye 1

 

# Link quality algorithm (if LinkQualityLevel > 0)

# etx_fpm (hello loss, fixed point math)

# etx_float (hello loss, floating point)

# etx_ff (packet loss for freifunk compat)

 

LinkQualityAlgorithm "etx_ff"

 

# Link quality aging factor

 

LinkQualityAging 0.100000

 

# NAT threshold

 

NatThreshold 1.000000

 

# Clear screen when printing debug output?

 

ClearScreen no

 

# Olsrd plugins to load

# This must be the absolute path to the file

# or the loader will use the following scheme:

# - Try the paths in the LD_LIBRARY_PATH

# environment variable.

# - The list of libraries cached in /etc/ld.so.cache

# - /lib, followed by /usr/lib

 

LoadPlugin "olsrd_txtinfo.dll" {

PlParam "Accept" "127.0.0.1"

}

LoadPlugin "olsrd_dot_draw.dll" {

PlParam "Accept" "127.0.0.1"

}

LoadPlugin "olsrd_httpinfo.dll" {

PlParam "port" "8080"

PlParam "Host" "127.0.0.1"

PlParam "Net" "10.0.0.0 255.0.0.0"

PlParam "Net" "192.168.0.0 255.255.0.0"

}

 

# Interfaces

# Multiple interfaces with the same configuration

# can shar the same config block. Just list the

# interfaces(e.g. Interface "eth0" "eth2"

 

Interface "IF35" {

 

# IPv4 broadcast address to use. The

# one usefull example would be 255.255.255.255

# If not defined the broadcastaddress

# every card is configured with is used

 

#Ip4Broadcast 255.255.255.255

 

# IPv6 address scope to use.

# Must be 'site-local' or 'global'

 

Ip6AddrType global

 

# IPv6 multicast address to use when

# using site-local addresses.

# If not defined, ff05::15 is used

Ip6MulticastSite ff05::15

 

# IPv6 multicast address to use when

# using global addresses

# If not defined, ff0e::1 is used

Ip6MulticastGlobal ff0e::1

 

# Olsrd can autodetect changes in

# interface configurations. Enabled by default

# turn off to save CPU.

AutoDetectChanges: yes

# Emission and validity intervals.

# If not defined, RFC proposed values will

# in most cases be used.

 

HelloInterval 5.00

HelloValidityTime 125.00

TcInterval 3.00

TcValidityTime 375.00

MidInterval 25.00

MidValidityTime 375.00

HnaInterval 25.00

HnaValidityTime 375.00

#LinkQualityMult default 1.0

# When multiple links exist between hosts

# the weight of interface is used to determine

# the link to use. Normally the weight is

# automatically calculated by olsrd based

# on the characteristics of the interface,

# but here you can specify a fixed value.

# Olsrd will choose links with the lowest value.

# Note:

# Interface weight is used only when LinkQualityLevel is 0.

# For any other value of LinkQualityLevel, the interface ETX

# value is used instead.

 

#Weight 0

 

}

 

 

# END AUTOGENERATED CONFIG

IP Logged
 Subject :Re:OLSR Switch on Windows works to connect directly to the mesh... 2013-12-20- 06:03:20 
W5LMM
Member
Joined: 2012-02-13- 18:18:04
Posts: 126
Location: Albuquerque, NM
 
Forum : Applications
Topic : OLSR Switch on Windows works to connect directly to the mesh.

Hi Bob!


Opened 698 UDP/TCP in windows firewall, also I do run OLSR Switch as admin too.


Here's some scrapes of the various tabs in Switch.  Thanks!



IP Logged
 Subject :Re:Lost password??.. 2013-12-20- 05:26:22 
k2vjk
Member
Joined: 2013-11-25- 10:55:46
Posts: 15
Location
Forum : General
Topic : Lost password??

Thanks for the help. My biggest problem was finding where to set the IP address for the adapter in Win7 (it was so much easier in the old days with NT4).
IP Logged
 Subject :Re:OLSR Switch on Windows works to connect directly to the mesh... 2013-12-20- 01:48:08 
kv4pc
Member
Joined: 2013-09-30- 20:06:03
Posts: 47
Location: Madison, AL
 
Forum : Applications
Topic : OLSR Switch on Windows works to connect directly to the mesh.

Another thought... if you have local firewall service running on your host you might need to punch a hole for the olsr protocol. Port 698 has to be passed through and may not be by defaut.
IP Logged
 Subject :Re:OLSR Switch on Windows works to connect directly to the mesh... 2013-12-20- 01:38:16 
kv4pc
Member
Joined: 2013-09-30- 20:06:03
Posts: 47
Location: Madison, AL
 
Forum : Applications
Topic : OLSR Switch on Windows works to connect directly to the mesh.

I would also like to see what is on your "Settings" tab and "Output" tabs.

It all looks good except the default gateway entry.

I left mine blank for the interface I connected to the mesh with and instead added persistent routes (IPv4) with high metric numbers (4 digits) for each way I reach the internet(mesh or AP or wired ethernet - I routinely use my laptop several different ways). On the mesh I usually get a 0.0.0.0 and a 10.0.0.0 route automatically with a low metric (3 digits or less) when I fire things up but if I dont it all still works anyway.

Less important, I set my nearest "HNA" router advertising the internet exit as the "first DNS" and 8.8.8.8 and 8.8.4.4 (google) as the second and third. DNS has never worked right for me, and the windows version of OLSRd lacks the DNS plug-in, but that configuration has given me the best results wrt the external internet.

I also just noticed I have set up OLSR Switch to run as Administrator. I cant remember why I decided to do that but it could be a factor.

Im glad adhoc is working for you! But it has always been very fragile for me if I try to roam or if events are causing topology changes on the mesh. Or even if I have two overlapping nodes at about the same signal strength at my location. If OLSR Switch is working, any streams or connections I may have running tend to survive topology changes. Straight adhoc doesnt.

It is also very handy to look on the nodes tab and see everything on the mesh. Mine lists every node including my GRE tunnels and the nodes on the other side.

73;

Bob KV4PC

IP Logged
Last Edited On: 2013-12-20- 01:40:36 By kv4pc for the Reason
 Subject :Re:OLSR Switch on Windows works to connect directly to the mesh... 2013-12-19- 21:49:01 
W5LMM
Member
Joined: 2012-02-13- 18:18:04
Posts: 126
Location: Albuquerque, NM
 
Forum : Applications
Topic : OLSR Switch on Windows works to connect directly to the mesh.

Yeah, quick reply mangled it. I am usig the mesh at this moment, and am able to connect to both nodes. I am also able to connect to shares etc on the local network (since one node is gateway.
IP Logged
 Subject :Re:OLSR Switch on Windows works to connect directly to the mesh... 2013-12-19- 21:45:04 
W5LMM
Member
Joined: 2012-02-13- 18:18:04
Posts: 126
Location: Albuquerque, NM
 
Forum : Applications
Topic : OLSR Switch on Windows works to connect directly to the mesh.

C:\Users\W5LMM>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : W5LMM-HMMWV-PC
Primary Dns Suffix  . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 00-19-C1-EA-8A-E5
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix  . : maiseldata.com
Description . . . . . . . . . . . : Marvell Yukon 88E8055 PCI-E Gigabit Ether
net Controller
Physical Address. . . . . . . . . : 00-0B-97-50-EF-91
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter TB Wifi:

Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : Intel(R) Wireless WiFi Link 4965AG
Physical Address. . . . . . . . . : 00-1D-E0-07-AE-15
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.7.174.21(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.143.7.121
DNS Servers . . . . . . . . . . . : 8.8.8.8
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.maiseldata.com:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fd:24ad:2b0c:f5f8:51ea(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::24ad:2b0c:f5f8:51ea%12(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{57A0507A-576B-4C41-9FFD-79F47E67F1C7}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{A99A3B0D-5C80-4F08-A744-5CB511866893}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

C:\Users\W5LMM>

IP Logged
 Subject :Re:OLSR Switch on Windows works to connect directly to the mesh... 2013-12-19- 21:41:24 
W5LMM
Member
Joined: 2012-02-13- 18:18:04
Posts: 126
Location: Albuquerque, NM
 
Forum : Applications
Topic : OLSR Switch on Windows works to connect directly to the mesh.


C:\Users\W5LMM>route print
===========================================================================
Interface List
14...00 19 c1 ea 8a e5 ......Bluetooth Device (Personal Area Network)
11...00 0b 97 50 ef 91 ......Marvell Yukon 88E8055 PCI-E Gigabit Ethernet Cont
oller
10...00 1d e0 07 ae 15 ......Intel(R) Wireless WiFi Link 4965AG
1...........................Software Loopback Interface 1
19...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
12...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
15...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
20...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
0.0.0.0          0.0.0.0     10.143.7.121      10.7.174.21     25
10.7.174.0    255.255.255.0         On-link       10.7.174.21    281
10.7.174.21  255.255.255.255         On-link       10.7.174.21    281
10.7.174.255  255.255.255.255         On-link       10.7.174.21    281
127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
224.0.0.0        240.0.0.0         On-link       10.7.174.21    281
255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
255.255.255.255  255.255.255.255         On-link       10.7.174.21    281
===========================================================================
Persistent Routes:
None

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination      Gateway
12     58 ::/0                     On-link
1    306 ::1/128                  On-link
12     58 2001::/32                On-link
12    306 2001:0:5ef5:79fd:24ad:2b0c:f5f8:51ea/128
On-link
12    306 fe80::/64                On-link
12    306 fe80::24ad:2b0c:f5f8:51ea/128
On-link
1    306 ff00::/8                 On-link
12    306 ff00::/8                 On-link
===========================================================================
Persistent Routes:
None

C:\Users\W5LMM>

IP Logged
 Subject :Re:OLSR Switch on Windows works to connect directly to the mesh... 2013-12-19- 20:52:40 
kv4pc
Member
Joined: 2013-09-30- 20:06:03
Posts: 47
Location: Madison, AL
 
Forum : Applications
Topic : OLSR Switch on Windows works to connect directly to the mesh.

It looks like QuickReply scrogged your columns. Im sorry but I cant make head or tails of this.Try a regular post.

73;

Bob KV4PC

IP Logged
 Subject :Re:Dayton Hamvention 2014.. 2013-12-19- 20:03:06 
WA2ZE
Member
Joined: 2013-07-16- 11:48:15
Posts: 2
Location: New Jersey
Forum : General
Topic : Dayton Hamvention 2014

I will have a node of some sort out in the parking lot of the vacant car dealership across the street from Hara Arena.

IP Logged
Last Edited On: 2013-12-19- 20:05:43 By WA2ZE for the Reason grammar
 Subject :Re:OLSR Switch on Windows works to connect directly to the mesh... 2013-12-19- 18:55:37 
W5LMM
Member
Joined: 2012-02-13- 18:18:04
Posts: 126
Location: Albuquerque, NM
 
Forum : Applications
Topic : OLSR Switch on Windows works to connect directly to the mesh.

C:\Users\W5LMM>route print =========================================================================== Interface List 14...00 19 c1 ea 8a e5 ......Bluetooth Device (Personal Area Network) 11...00 0b 97 50 ef 91 ......Marvell Yukon 88E8055 PCI-E Gigabit Ethernet Contr oller 10...00 1d e0 07 ae 15 ......Intel(R) Wireless WiFi Link 4965AG 1...........................Software Loopback Interface 1 19...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 12...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface 15...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2 20...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3 =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 10.143.7.121 10.7.174.21 25 10.7.174.0 255.255.255.0 On-link 10.7.174.21 281 10.7.174.21 255.255.255.255 On-link 10.7.174.21 281 10.7.174.255 255.255.255.255 On-link 10.7.174.21 281 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 10.7.174.21 281 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 10.7.174.21 281 =========================================================================== Persistent Routes: None IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 12 58 ::/0 On-link 1 306 ::1/128 On-link 12 58 2001::/32 On-link 12 306 2001:0:5ef5:79fd:c89:3946:f5f8:51ea/128 On-link 12 306 fe80::/64 On-link 12 306 fe80::c89:3946:f5f8:51ea/128 On-link 1 306 ff00::/8 On-link 12 306 ff00::/8 On-link =========================================================================== Persistent Routes: None C:\Users\W5LMM>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : W5LMM-HMMWV-PC Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : Yes WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Bluetooth Network Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network) Physical Address. . . . . . . . . : 00-19-C1-EA-8A-E5 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Ethernet adapter Local Area Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : maiseldata.com Description . . . . . . . . . . . : Marvell Yukon 88E8055 PCI-E Gigabit Ether net Controller Physical Address. . . . . . . . . : 00-0B-97-50-EF-91 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Wireless LAN adapter TB Wifi: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) Wireless WiFi Link 4965AG Physical Address. . . . . . . . . : 00-1D-E0-07-AE-15 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 10.7.174.21(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 10.143.7.121 DNS Servers . . . . . . . . . . . : 8.8.8.8 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.maiseldata.com: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 11: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fd:c89:3946:f5f8:51ea(Prefe rred) Link-local IPv6 Address . . . . . : fe80::c89:3946:f5f8:51ea%12(Preferred) Default Gateway . . . . . . . . . : :: NetBIOS over Tcpip. . . . . . . . : Disabled Tunnel adapter isatap.{57A0507A-576B-4C41-9FFD-79F47E67F1C7}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter isatap.{A99A3B0D-5C80-4F08-A744-5CB511866893}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes C:\Users\W5LMM> Interesting.......



Methinks OLSR Switch doth nothing here. 

IP Logged
Last Edited On: 2013-12-19- 19:15:33 By W5LMM for the Reason
 Subject :WA5210G with HSMM ?.. 2013-12-19- 18:47:43 
sp2ong
Member
Joined: 2013-10-30- 10:57:25
Posts: 72
Location
Forum : Hardware
Topic : WA5210G with HSMM ?

Hi,

I have found very nice wifi router  TL-WA5210G

http://www.tp-link.com/en/products/details/?model=TL-WA5210G

it will be nice to have firmware HSMM for this router. It is ready hardware to put outdoor and use.

73 Waldek sp2ong



IP Logged
 Subject :Re:SSH login problems.. 2013-12-19- 10:02:41 
kv4pc
Member
Joined: 2013-09-30- 20:06:03
Posts: 47
Location: Madison, AL
 
Forum : General
Topic : SSH login problems

Miguel:

If this is HSMM or BBHN node and you havent modified the setup then the ssh port should be "2222" instead of the standard "22". Give that a try.

73;

Bob KV4PC

IP Logged
Last Edited On: 2013-12-19- 10:03:14 By kv4pc for the Reason
 Subject :SSH login problems.. 2013-12-19- 07:13:54 
EB5JEQ
Member
Joined: 2013-09-21- 14:11:41
Posts: 8
Location: Elche Alicante Spain
 
Forum : General
Topic : SSH login problems

Hi, I need access in a ssh session in to my mesh node, for config a vpn tunnel.

But I can't gain access to the router.

I create in ubuntu a pair of ssh keys  with

ssh-keygen -t rsa
later I make 
ssh-copy-id remote_host ( ip of the mes node )
the result is : ssh: connect to host 172.27.0.1 port 22: Connection refused
I try to download the key in the mesh node, thru the web interface , the file keyxx.pub. The mesh node accepts this key.
But, if I try login ssh 172.27.0.1
 connect to host 172.27.0.1 port 22: Connection refusedsh 172.27.0.1
I have the same result. I tried with putty ( in windows ), but I don't know, what I am making bad. 
Please Help.

73s. Miguel

IP Logged
 Subject :Re:SSH Access with Putty.. 2013-12-19- 05:20:43 
VA3RRZ
Member
Joined: 2013-08-26- 06:54:56
Posts: 15
Location: L'Orignal, Ontario, Canada
Forum : Applications
Topic : SSH Access with Putty

Eric, I tired both instructions for login in without a password.  Didn't work.  Found a way that works.  Here's how.  Upload public key file to etc/dropbear directory and rename file to authorized_key or if the file already exists, append public key to to it by copying and pasting.  Chmod 600.  Run Pageant: upload private key; enter passphrase; close window.

In Putty, enter login name in Connection>Data: Auto-login username.   In Session: choose SSH; port 2222.  Save configuration.  Login without typing username or password.  This now works with WinSCP using SSH as well. 

*** Note: There was already an authorized_key on my mesh with a public key inside.  Not sure why. Do the mesh routers need SSH to talk to each other?  I would check before replacing the file with your public key.  Just append your public key to this file for now. 73 de ron

IP Logged
Last Edited On: 2013-12-19- 09:44:56 By VA3RRZ for the Reason
Page #  «StartPrev271272273274275276277278279280NextEnd»


Powered by ccBoard


SPONSORED AD: