Re: Policy-based routing for packets originating from local machine ('reinject' packets back into kernel?)
- From: m_wlist@xxxxxxxxxxxx
- Date: Mon, 23 Jul 2007 03:08:44 +0700 (NOVST)
On Sunday 22 July 2007, m_wlist@xxxxxxxxxxxx wrote:
At the moment I'm trying to get that working with netgraph's ngeth
interfaces. But they seem to behave in some really weird way.
Details:
# ifconfig ngeth0 10.42.42.1 netmask 255.255.255.250
Netmask 255.255.255.250 looks weird to me. Something like this is really
unusual. What does ifconfig ngeth0 show?
Oh. Yes, that was a typo in command that I've copypasted here.
Thank you for pointing to that.
# ngctl connect ngeth0: ngeth1: lower upper
# ngctl connect ngeth1: ngeth0: lower upper
('tcpdump -ni ngeth0' on other terminal for great justice)
# ping 10.42.42.2
(here after some delay I get 'host is down' messages with no output from
tcpdump).
# ping 10.42.42.5
(broadcast address, gives nothing from ping, and 'blal blah 10.42.42.1 >
10.42.42.5: ICMP echo request, blah' from tcpdump)
(here i change tcpdump from ngeth0 to ngeth1)
# ping 10.42.42.2 and # ping 10.42.42.3
give 'host is down' from ping and nothing from tcpdump
# ping 10.42.42.4
(LOL WUT!) still gives 'host is down' from ping, but tcpdump -ni ngeth1
gives 'arp who-has 10.42.42.4 tell 10.42.42.1'!
That raises two questins:
1) Wtf is going on?
2) How to make ngeth just send ip packet, avoiding that arp stuff (or is
there any other virtual interface devices available that do that)?
I can't comment on these question, but my recommendation would be to
choose
more usual mask - if it's not a typo, this could cause various interesting
errors.
Now It looks more sane -- arp messages appear on trying to ping every
(except first that belongs to ngeth0) ip in that subnet.
So the second question is still open.
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
- References:
- Prev by Date: Re: 6.2 mtu now limits size of incomming packet
- Next by Date: Re: Policy-based routing for packets originating from local machine ('reinject' packets back into kernel?)
- Previous by thread: Re: Policy-based routing for packets originating from local machine ('reinject' packets back into kernel?)
- Next by thread: Re: Policy-based routing for packets originating from local machine ('reinject' packets back into kernel?)
- Index(es):
Relevant Pages
- Re: dual-net problem
... >> tcpdump and ping to check that they work as expected. ... >You
are using 2 interfaces on the same subnet on this machine. ... (Fedora) - Re: Policy-based routing for packets originating from local machine (reinject packets back into
... interfaces. ... What does ifconfig ngeth0 show? ... ('tcpdump
-ni ngeth0' on other terminal for great justice) ... # ping 10.42.42.2 ... (freebsd-net) - troubles with ng_fec on -current
... connected to the ste0..4 interfaces. ... Problem is when I ping box4
from the other boxes. ... I then ran tcpdump on the 4 ste interfaces. ...
(freebsd-net) - Re: sent an invalid ICMP type 11, code 0 error to a broadcast: 0.0.0.0 on lo?
... rp_filter is activated on all interfaces. ... If you ping an IP address
on your eth0, ... You can verify it using tcpdump: ... send the line "unsubscribe
linux-kernel" in ... (Linux-Kernel) - Re: sis190
... > differently sized ping packets to cover the whole allowed range. ... Jun
14 15:24:02 local kernel: eth0: Enabling Auto-negotiation. ... tcpdump: verbose
output suppressed, use -v or -vv for full protocol decode ... (Linux-Kernel)