![]() That is, I temporarily bring up the second IP on my Linode, ping it (thus caching the MAC IP relationship in Linode's routers, I suppose), and then bring it back down, and then bring back up the tunnel. What seems to work, although I don't know how to persist this setting, is if I use my first Linode/first IP to do proxy ARP for the second IP. However, at this point, it seems like the Linode routers just discard the response (maybe because they don't like the MAC address?) The client then responds with its tap0 MAC address (which I guess is just generated randomly). If I try to connect to my Linode IP externally, I see an arp who-has (public IP), which gets forwarded over the OpenVPN tunnel to the client. ![]() Then I configure the client's tap0 as my second Linode IP. My client machine connects over OpenVPN to my Linode with bridging. Okay, I've gotten this somewhat working, but I've still hit another snag. TX packets:0 errors:0 dropped:20 overruns:0 carrier:0 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 ![]() Tap0 Link encap:Ethernet HWaddr 00:FF:6B:4B:80:97 TX packets:68 errors:0 dropped:0 overruns:0 carrier:0 RX packets:68 errors:0 dropped:0 overruns:0 frame:0 TX packets:1673 errors:0 dropped:0 overruns:0 carrier:0 RX packets:2713 errors:0 dropped:0 overruns:0 frame:0 ![]() UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 TX packets:27 errors:0 dropped:0 overruns:0 carrier:0 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Bridge name bridge id STP enabled interfacesīr0 8000.00ff6b4b8097 no ~]$ ifconfig | moreīr0 Link encap:Ethernet HWaddr 00:FF:6B:4B:80:97 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |