[CUWiN-Dev] multiple HSLS networks, different SSIDs
David Young
dyoung at pobox.com
Thu Aug 25 17:40:43 CDT 2005
On Thu, Aug 25, 2005 at 04:17:38PM -0500, Bill Comisky wrote:
>
> In the course of testing I ended up with 2, two node networks in the lab
> with different SSIDs. The first time up, both had a gateway plugged into
> the same LAN. Unexpectedly, there were routing entries for the the nodes
> of the other network, but routed through the LAN gateway address of the
> other network (see routing table at bottom). I couldn't connect from
> nodes on one to nodes on the other though.. which makes sense since 10/8
> is NAT'd through the wired interface.
There is a bug, but we may disagree what the bug is. :-) The SSID is a
layer-2 property that the layer-3 routing should be blissfully unaware of.
I believe the networks should merge when you plug them into the same
switch. The bug is that they don't merge. Well, they do, but the NAT
firewalls get in the way. The fix I prefer is to patch up the firewall
rules so that packets to 10/8 from 10/8 are not translated.
That said, I acknowledge the desirability of separating routing on the
same media into two different "domains." The quick way to do it is
by using different HSLS ports on the two networks. The default port
is 9191. You could use 9393. It SHOULD only be necessary to change
the port number in /etc/services.
It would be nice if the HSLS port and other properties were command-line
options for mkstaboot.
Dave
> I powered everything down and powered up again with one network's gateway
> plugged into a separate LAN. No cross-network routing entries this time.
> However, I did notice that when both networks were up, I was getting a
> bunch (100's in a couple minutes) of these:
>
> ieee80211_ibss_merge: merge failed, capabilities mismatch
>
> This is mostly just an interesting observation of an edge case, but it
> didn't seem like those cross-network routing entries should be showing up.
>
> Bill
>
> --
> Bill Comisky
> bcomisky at pobox.com
>
> [ 2 two-node networks with distinct SSID's plugged into same LAN]
> Routing tables
>
> Internet:
> Destination Gateway Flags Refs Use Mtu
> Interface
> default 192.168.2.1 UGS 0 7 - sip0
> 10.0.134.27 192.168.2.140 UGH1 0 0 - sip0
> 10.0.146.77 192.168.2.140 UGH1 0 0 - sip0
> 10.0.146.80 169.254.160.244 UGH1 1 944 - ath0
> 10.0.151.111/32 link#1 UC 0 0 - ath0
> 10.190.80/24 192.168.2.140 UG1 0 0 - sip0
> 10.190.80.254 192.168.2.140 UGH1 0 0 - sip0
> 10.190.81/24 192.168.2.140 UG1 0 0 - sip0
> 10.190.81.254 192.168.2.140 UGH1 0 0 - sip0
> 10.213.204/24 link#3 UC 0 0 - sip1
> 10.213.205/24 link#2 UC 0 0 - sip0
> 10.213.208/24 192.168.2.140 UG1 0 0 - sip0
> 10.213.208.254 192.168.2.140 UGH1 0 0 - sip0
> 10.213.209/24 192.168.2.140 UG1 0 0 - sip0
> 10.213.209.254 192.168.2.140 UGH1 0 0 - sip0
> 10.214.132/24 169.254.160.244 UG1 0 0 - ath0
> 10.214.132.254 169.254.160.244 UGH1 0 0 - ath0
> 10.214.133/24 169.254.160.244 UG1 0 0 - ath0
> 10.214.133.254 169.254.160.244 UGH1 0 0 - ath0
> 127/8 127.0.0.1 UGRS 0 0 33192 lo0
> 127.0.0.1 127.0.0.1 UH 5 0 33192 lo0
> 169.254/16 link#1 UC 1 0 - ath0
> 169.254.160.244 00:02:6f:21:fd:73 UHLc 5 0 - ath0
> 192.168.2/24 link#2 UC 3 0 - sip0
> 192.168.2.1 00:0f:66:8e:39:bb UHLc 1 0 - sip0
> 192.168.2.4 00:12:79:5c:44:2d UHLc 1 5668 - sip0
> 192.168.2.140 00:00:24:c0:9a:90 UHLc 10 0 - sip0
> 192.168.2.150 127.0.0.1 UGHS 0 0 33192 lo0
> 224.0.0.5 127.0.0.1 UGH1 0 0 33192 lo0
> 224.0.0.6 127.0.0.1 UGH1 0 0 33192 lo0
> 224.0.0.9 127.0.0.1 UGH1 0 0 33192 lo0
> _______________________________________________
> CU-Wireless-Dev mailing list
> CU-Wireless-Dev at lists.cuwireless.net
> http://lists.chambana.net/cgi-bin/listinfo/cu-wireless-dev
--
David Young OJC Technologies
dyoung at ojctech.com Urbana, IL * (217) 278-3933
More information about the CU-Wireless-Dev
mailing list