Comments
Having multiple interfaces with the same IP address was always the standard configuration of a terminal server with multiple PPP and SLIP links. The default configuration of Portslave always had a single IP address for the local end of all PPP/SLIP connections and there was no documentation on how to do otherwise. A few years ago when such things were common there didn't seem to be any problems doing it. Of course things may have changed since then.
#1 Russell Coker (Homepage) on 2010-02-05 13:20
That works nicely for me for *years* now.
#2 Joerg Jaspert on 2010-02-05 14:19
I think "setting up a listening socket at only one of these interfaces" is the historical reason why it's not commonly done. It also breaks SNMP, which uses the IP address as the primary key in the ipAddressTable. In general, the localip could also be an RFC1918 address if you wanted to conserve routeable addresses, but this might conflict with your peer's setup.
#3 GyrosGeier on 2010-02-05 14:24
Rather than some custom SSH-tunnel-based VPN, do yourself the favour and use OpenVPN instead. It supports tap interfaces, which means that you don't have to have any internal addresses, but it can manage tun interfaces too, either with a separate pool each, or out of one large common pool.
#4 martin f. krafft (Homepage) on 2010-02-05 20:58
Ask on debian-user mailing list. (i.e don't turn debian-planet into a support "mailing list").
#5 Franklin Piat on 2010-02-05 22:59
Add Comment

E-Mail addresses will not be displayed and will only be used for E-Mail notifications.

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.
CAPTCHA
 
Submitted comments will be subject to moderation before being displayed.