RE: problem with proxy-arp

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I actually prefer to use "ip addr add" as good practice for the reason that it makes rules alot easier to write so you don't have to worry about eth0:0 or was that eth0:1 ..etc..etc.. just eth0 with 2 IPs hanging off it.

This is the real way to bind multiple addresses to a NIC.. ie.

#ip addr show dev eth1
4: eth1: <BROADCAST,MULTICAST,PROMISC,UP> mtu 1500 qdisc pfifo_fast qlen 100
    link/ether 52:54:05:e3:08:9a brd ff:ff:ff:ff:ff:ff
    inet 10.2.1.1/30 brd 10.2.1.3 scope global eth1
    inet 203.111.79.114/28 scope global eth1

Thanks,
____________________________________________
George Vieira
Systems Manager
georgev@xxxxxxxxxxxxxxxxxxxxxx

Citadel Computer Systems Pty Ltd
http://www.citadelcomputer.com.au

-----Original Message-----
From: Jet (jchan@xxxxxxxxxxxxx) [mailto:yenjet.chan@xxxxxxxxxxxxxx]
Sent: Thursday, June 12, 2003 1:29 PM
To: Steven Mugassa
Cc: netfilter@xxxxxxxxxxxxxxx
Subject: Re: problem with proxy-arp


At router B, try this (instead of using the arp command)

ifconfig eth1:10 10.10.10.10 netmask 255.255.255.0 up

The idea is to create an alias interface (I'm using 10 but you can use any)
at interface eth1 of router B.


--
Jet (Security Analyst)
http://www.secure-ip.com



[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux