0

My hosting provider routes an IP block to my eth0 interface. Until today I've been adding the block using IP alias via ifconfig, unknown to me that it was an old solution.

I've now learnt that there are at least two other options: VLANs, and MAC VLAns.

I couldnt make MAC VLANs work, but I succeeded in pinging correctly a VLAN. Anyhow it broke my iptables (check this question).

What is the best option and why?

Which solution allows me to use traffic control on the interface? which allow me to use iptables on the interface instead of filtering by IP destination?

Community
  • 1
Mascarpone
  • 872
  • 3
  • 9
  • 28
  • 1
    What do you mean by "broke your iptables"? The same issue as not being able to use interface names or your current configuration stopped working? – DarkLighting Dec 30 '14 at 21:11
  • The configuration stopped working. Forwarding by selecting destionation ip didnt work anymore, nor interface forwarding – Mascarpone Dec 30 '14 at 21:40
  • 2
    I would just use `ip a add 1.2.3.4/32 dev eth0` to add an extra address to the interface. Note that you could even add them to the `lo` interface, linux by default will respond to arp requests on all interfaces. – wurtel Dec 31 '14 at 11:30

0 Answers0