As an aside, if you have more than 1 computer at home and they run a version of Linux from the past 8 years or so, or run Windows Vista or later, or run MacOS from within that same time period, you can test out IPv6 on your LAN, as it is likely already up and running. The link local IP addresses (starts with fe80:) are kind of like the 169.254 range of IPv4, so even if no formal IPv6 infrastructure is detected your machines will still autoconfigure this address and broadcast it out with the neighbour discovery protocol built into the IPv6 stack. This will work with Samba, SSH, Apache and any IPv6 aware protocols/applications.
On Sun, Mar 29, 2015 at 12:12 PM, Gustin Johnson <gus...@meganerd.ca> wrote: > You could create virtual or dummy interfaces (I don't usually recommend > virtual interfaces since you can usually assign more than one IP to the > physical interface or you have a sophisticated bridging toolset, neither of > which is going to help you in this particular case). > > Basically I imagine something like this: > "sudo /sbin/ip li add dummy0 type dummy" and then again for a dummy1 > interface. > Bring up the fake interface with "sudo ip link set dummy0 up" and assign > an IP to it with "sudo ip addr add 192.168.1.1/24 dev dummy0" and then a > different IP from a different subnet on the other dummy interface. From > here you set up a NAT with the dummy interfaces acting like the external > interface and the real ones connected to the cameras as the "internal" > interface. All the usual NAT things like forwarding will need to be > enabled. > > Hopefully this is not for a production environment. Ideally you would > need to be able to change the IP addresses of the cameras to play nice on > their respective networks, since what I have outlined will be a pain to > maintain. > > You might get lucky and these cameras might support IPv6; "sudo ip neigh > is kind of like arp but will also show IPv6 addresses (this is the short > short description of "ip neigh", the reality is a little more complicated > under the hood). If you are lucky you will see link local IPv6 addresses > that are listed as "REACHABLE". You might then be able to connect via the > IPv6 address that starts with fe80. > > Hth, > __ > Gustin > > > > On Sun, Mar 29, 2015 at 11:30 AM, Zander Robertson < > zandervanrobert...@gmail.com> wrote: > >> Hi there, I'm wondering if the issue is because you have two network >> cards on the same subnet. >> >> Alex >> Hi all, >> I'm working with some Sony WiFi attached cameras, and would like to use >> multiple at the same time.... however they are the 'AP' end of the link >> and they both issue the same IP's, so I end up with a screwed up network >> and can only talk to the last one to connect. >> >> As you can see from the attached log, I am using multiple network cards, >> and they both get issued '10.0.1.1' (with the cameras both at '10.0.0.1'). >> >> Is there any 'network-voodoo' (iptables or the like) I can do to create a >> 'fake IP' which would be routed to the cameras? >> >> Thanks, >> Simon. >> >> PS. There are some cameras (QX30 for example) which can connect to a >> remote router, which might be a better choice. However I don't have any of >> those. >> >> PPS. https://github.com/Bloodevil/sony_camera_api/ >> >> _______________________________________________ >> clug-talk mailing list >> clug-talk@clug.ca >> http://clug.ca/mailman/listinfo/clug-talk_clug.ca >> Mailing List Guidelines (http://clug.ca/ml_guidelines.php) >> **Please remove these lines when replying >> >> _______________________________________________ >> clug-talk mailing list >> clug-talk@clug.ca >> http://clug.ca/mailman/listinfo/clug-talk_clug.ca >> Mailing List Guidelines (http://clug.ca/ml_guidelines.php) >> **Please remove these lines when replying >> > >
_______________________________________________ clug-talk mailing list clug-talk@clug.ca http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
