Mdthbs

Why commonly or frequently used fonts sizes are even numbers like 10px, 12px, 16px, 24px, or 32px?

Wiring a 4 channel relay - is this possible?

Why are goodwill impairments on the statement of cash-flows of GE?

APFS - how do I enable transparent compression

c++ conditional uni-directional iterator

What metal is most suitable for a ladder submerged in an underground water tank?

​Cuban​ ​Primes

Testing if os.path.exists with ArcPy?

Will the volt, ampere, ohm or other electrical units change on May 20th, 2019?

What is the status of the Lannisters after Season 8 Episode 5, "The Bells"?

tikz drawing rectangle discretized with triangle lattices and its centroids

Why when I add jam to my tea it stops producing thin "membrane" on top?

Why is Drogon so much better in battle than Rhaegal and Viserion?

Developers demotivated due to working on same project for more than 2 years

How does Ctrl+c and Ctrl+v work?

Is there any deeper thematic meaning to the white horse that Arya finds in The Bells (S08E05)?

God-Pharaoh's Statue and Finale Of Promise

UUID type for NEWID()

Is my test coverage up to snuff?

In season 17 does LoN buff work against season journey set rewards?

Can anyone give me examples of the relative-determinative 'which'?

Can a tourist shoot a gun in the USA?

Are there microwaves to heat baby food at Brussels airport?

How do I know which cipher suites can be disabled?

Invalid multicast interface

Invalid greeting from server802.3ad on FreeBSD and Linux using crossover cables?FreeBSD reboots during install and leaves invalid installpf out interface?FreeBSD complains “invalid partition table”—still bootsFreeBSD Multicast Ethernet AddressCannot mount USB on FreeBSD: Invalid argumentInvalid time on FreeBSDSSH connection timeout after a couple of seconds when my second interface is upping6: sendmsg: No buffer space available

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}

1

I am trying to use ping with specified interface with a command

ping -I re3 192.168.1.1

I know re3 exists from ifconfig

re3: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500

        options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>

        ether e8:de:27:01:7f:e7

        inet6 fe80::eade:27ff:fe01:7fe7%re3 prefixlen 64 scopeid 0x4

        inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255

        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

        media: Ethernet autoselect (100baseTX <full-duplex>)

        status: active

Unfortunately I can't ping it's gateway:

$/root: ping -I re3 192.168.1.1

ping: invalid multicast interface: `re3'

What that mean?

UPDATE

$arp 192.168.1.1

? (192.168.1.1) at (incomplete) on re3 expired [ethernet]

freebsd pfsense

share|improve this question

edited Jan 31 '17 at 21:45

Dims

asked Jan 31 '17 at 21:38

DimsDims

4821934

add a comment | 

1

I am trying to use ping with specified interface with a command

ping -I re3 192.168.1.1

I know re3 exists from ifconfig

re3: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500

        options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>

        ether e8:de:27:01:7f:e7

        inet6 fe80::eade:27ff:fe01:7fe7%re3 prefixlen 64 scopeid 0x4

        inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255

        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

        media: Ethernet autoselect (100baseTX <full-duplex>)

        status: active

Unfortunately I can't ping it's gateway:

$/root: ping -I re3 192.168.1.1

ping: invalid multicast interface: `re3'

What that mean?

UPDATE

$arp 192.168.1.1

? (192.168.1.1) at (incomplete) on re3 expired [ethernet]

freebsd pfsense

share|improve this question

edited Jan 31 '17 at 21:45

Dims

asked Jan 31 '17 at 21:38

DimsDims

4821934

add a comment | 

I am trying to use ping with specified interface with a command

ping -I re3 192.168.1.1

I know re3 exists from ifconfig

re3: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500

        options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>

        ether e8:de:27:01:7f:e7

        inet6 fe80::eade:27ff:fe01:7fe7%re3 prefixlen 64 scopeid 0x4

        inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255

        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

        media: Ethernet autoselect (100baseTX <full-duplex>)

        status: active

Unfortunately I can't ping it's gateway:

$/root: ping -I re3 192.168.1.1

ping: invalid multicast interface: `re3'

What that mean?

UPDATE

$arp 192.168.1.1

? (192.168.1.1) at (incomplete) on re3 expired [ethernet]

freebsd pfsense

share|improve this question

edited Jan 31 '17 at 21:45

Dims

asked Jan 31 '17 at 21:38

DimsDims

4821934

ping -I re3 192.168.1.1

re3: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500

        options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>

        ether e8:de:27:01:7f:e7

        inet6 fe80::eade:27ff:fe01:7fe7%re3 prefixlen 64 scopeid 0x4

        inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255

        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

        media: Ethernet autoselect (100baseTX <full-duplex>)

        status: active

$/root: ping -I re3 192.168.1.1

ping: invalid multicast interface: `re3'

$arp 192.168.1.1

? (192.168.1.1) at (incomplete) on re3 expired [ethernet]

share|improve this question

edited Jan 31 '17 at 21:45

Dims

asked Jan 31 '17 at 21:38

DimsDims

4821934

share|improve this question

edited Jan 31 '17 at 21:45

Dims

asked Jan 31 '17 at 21:38

DimsDims

4821934

asked Jan 31 '17 at 21:38

DimsDims

4821934

asked Jan 31 '17 at 21:38

DimsDims

4821934

2 Answers
2

active

oldest

votes

3

Not much experience in freebsd system, as far as i know for ping try:

ping -S 192.168.1.2 192.168.1.1

As for arp

• If arp cant fetch mac address of your gateway then freebsd server
  lost it's connectivity with the gateway.


• Check whether gateway of your server is UP/RUNNING, and also check
  the physical connectivty of both.

share|improve this answer

answered Feb 2 '17 at 4:34

Rakesh.NRakesh.N

594414

add a comment | 

1

On FreeBSD and macos the -I flag does not behave as one would expect from Linux. If you check the man page carefully, you'll see:

 -I iface

        Source multicast packets with the given interface **address**.

[emphasis mine]

So the -I flag actually expects an address, not an interface. You can confirm with something like:

$ ping -I 192.168.1.2 192.168.1.1

But unless your target IP address is a multicast address this will still fail.

To get the behaviour we all know and expect from traceroute and Linux, use the -S flag instead and specify the IP address of the interface you want to use:

$ ping -S 192.168.1.2 192.168.1.1

PING 192.168.1.1 (192.168.1.1) from 192.168.1.20: 56 data bytes

64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=5.956 ms

share|improve this answer

answered 2 hours ago

Heath RafteryHeath Raftery

27519

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f341590%2finvalid-multicast-interface%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

3

Not much experience in freebsd system, as far as i know for ping try:

ping -S 192.168.1.2 192.168.1.1

As for arp

• If arp cant fetch mac address of your gateway then freebsd server
  lost it's connectivity with the gateway.


• Check whether gateway of your server is UP/RUNNING, and also check
  the physical connectivty of both.

share|improve this answer

answered Feb 2 '17 at 4:34

Rakesh.NRakesh.N

594414

add a comment | 

3

Not much experience in freebsd system, as far as i know for ping try:

ping -S 192.168.1.2 192.168.1.1

As for arp

• If arp cant fetch mac address of your gateway then freebsd server
  lost it's connectivity with the gateway.


• Check whether gateway of your server is UP/RUNNING, and also check
  the physical connectivty of both.

share|improve this answer

answered Feb 2 '17 at 4:34

Rakesh.NRakesh.N

594414

add a comment | 

Not much experience in freebsd system, as far as i know for ping try:

ping -S 192.168.1.2 192.168.1.1

As for arp

• If arp cant fetch mac address of your gateway then freebsd server
  lost it's connectivity with the gateway.


• Check whether gateway of your server is UP/RUNNING, and also check
  the physical connectivty of both.

share|improve this answer

answered Feb 2 '17 at 4:34

Rakesh.NRakesh.N

594414

ping -S 192.168.1.2 192.168.1.1

share|improve this answer

answered Feb 2 '17 at 4:34

Rakesh.NRakesh.N

594414

answered Feb 2 '17 at 4:34

Rakesh.NRakesh.N

594414

answered Feb 2 '17 at 4:34

Rakesh.NRakesh.N

594414

1

On FreeBSD and macos the -I flag does not behave as one would expect from Linux. If you check the man page carefully, you'll see:

 -I iface

        Source multicast packets with the given interface **address**.

[emphasis mine]

So the -I flag actually expects an address, not an interface. You can confirm with something like:

$ ping -I 192.168.1.2 192.168.1.1

But unless your target IP address is a multicast address this will still fail.

To get the behaviour we all know and expect from traceroute and Linux, use the -S flag instead and specify the IP address of the interface you want to use:

$ ping -S 192.168.1.2 192.168.1.1

PING 192.168.1.1 (192.168.1.1) from 192.168.1.20: 56 data bytes

64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=5.956 ms

share|improve this answer

answered 2 hours ago

Heath RafteryHeath Raftery

27519

add a comment | 

1

On FreeBSD and macos the -I flag does not behave as one would expect from Linux. If you check the man page carefully, you'll see:

 -I iface

        Source multicast packets with the given interface **address**.

[emphasis mine]

So the -I flag actually expects an address, not an interface. You can confirm with something like:

$ ping -I 192.168.1.2 192.168.1.1

But unless your target IP address is a multicast address this will still fail.

To get the behaviour we all know and expect from traceroute and Linux, use the -S flag instead and specify the IP address of the interface you want to use:

$ ping -S 192.168.1.2 192.168.1.1

PING 192.168.1.1 (192.168.1.1) from 192.168.1.20: 56 data bytes

64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=5.956 ms

share|improve this answer

answered 2 hours ago

Heath RafteryHeath Raftery

27519

add a comment | 

On FreeBSD and macos the -I flag does not behave as one would expect from Linux. If you check the man page carefully, you'll see:

 -I iface

        Source multicast packets with the given interface **address**.

[emphasis mine]

So the -I flag actually expects an address, not an interface. You can confirm with something like:

$ ping -I 192.168.1.2 192.168.1.1

But unless your target IP address is a multicast address this will still fail.

To get the behaviour we all know and expect from traceroute and Linux, use the -S flag instead and specify the IP address of the interface you want to use:

$ ping -S 192.168.1.2 192.168.1.1

PING 192.168.1.1 (192.168.1.1) from 192.168.1.20: 56 data bytes

64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=5.956 ms

share|improve this answer

answered 2 hours ago

Heath RafteryHeath Raftery

27519

$ ping -I 192.168.1.2 192.168.1.1

$ ping -S 192.168.1.2 192.168.1.1

PING 192.168.1.1 (192.168.1.1) from 192.168.1.20: 56 data bytes

64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=5.956 ms

share|improve this answer

answered 2 hours ago

Heath RafteryHeath Raftery

27519

answered 2 hours ago

Heath RafteryHeath Raftery

27519

answered 2 hours ago

Heath RafteryHeath Raftery

27519