netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Soltys <soltys@ziu.info>
To: Greg Scott <GregScott@Infrasupport.com>
Cc: David Lamparter <equinox@diac24.net>, netdev@vger.kernel.org
Subject: Re: ebtables on a stick
Date: Fri, 02 Dec 2011 16:40:13 +0100	[thread overview]
Message-ID: <4ED8F15D.8020909@ziu.info> (raw)
In-Reply-To: <925A849792280C4E80C5461017A4B8A2A048FA@mail733.InfraSupportEtc.com>

On 11-12-01 17:56, Greg Scott wrote:
>>  # ip -4 a l eth0; ip r l match 0.0.0.0; ip r l exact 10.255.255.1
>>  2: eth0:<BROADCAST,MULTICAST,UP,LOWER_UP>  mtu 1500 qdisc pfifo_fast
>>  state UNKNOWN qlen 1000
>>      inet 87.106.131.203/32 scope global eth0
>>  default via 10.255.255.1 dev eth0
>>  10.255.255.1 dev eth0  scope link

Aside from addresses, same config I had when I was on adsl.

>
> Wow, how does that even work?  Every time I think I know something, I
> get challenged.  I should make that a slogan.
>
> - Greg
>

BTW:

You should be able to avoid whole proxy thing altogether (on your 
router), by doing:

ip add add 1.2.115.157/32 dev eth0
ip ro del table local 192.168.99.5/32 dev eth0
ip route add 1.2.115.157/32 dev eth1

instead of:

ip neigh add proxy 1.2.115.157 dev eth0

The former will still expose the address, but it will be not routable 
inside the router, so will get passed to your internal host. (this 
assumes your kernel is compiled with advanced routing).

  reply	other threads:[~2011-12-02 15:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <925A849792280C4E80C5461017A4B8A2A04879@mail733.InfraSupportEtc.com>
2011-11-26  8:27 ` ebtables on a stick Greg Scott
2011-11-27 15:10   ` Greg Scott
2011-11-28 14:39     ` David Lamparter
2011-11-28 14:54       ` Greg Scott
2011-11-28 15:30         ` David Lamparter
2011-11-29 10:05           ` Greg Scott
2011-11-29 10:23             ` David Lamparter
2011-11-29 10:48               ` Greg Scott
2011-11-29 23:11       ` Michal Soltys
2011-12-01  5:46         ` Greg Scott
2011-12-01  7:14           ` David Lamparter
2011-12-01 14:10             ` Greg Scott
2011-12-01 14:39             ` Greg Scott
2011-12-01 14:47               ` David Lamparter
2011-12-01 15:29                 ` Greg Scott
2011-12-01 16:50                   ` David Lamparter
2011-12-01 16:56                     ` Greg Scott
2011-12-02 15:40                       ` Michal Soltys [this message]
2011-12-02 16:04                         ` David Lamparter
2011-12-02 16:09                           ` Greg Scott
2011-12-02 16:06                         ` Greg Scott
2011-12-02 16:16                           ` Michal Soltys
2011-12-02 16:20                             ` Greg Scott
2011-12-02 16:44                               ` Michal Soltys
2011-12-01 17:44           ` Michal Soltys
2011-12-01 17:51             ` Greg Scott

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4ED8F15D.8020909@ziu.info \
    --to=soltys@ziu.info \
    --cc=GregScott@Infrasupport.com \
    --cc=equinox@diac24.net \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).