Timeline for Firewall incoming packets are dropped with VLAN configuration
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 23 at 11:56 | comment | added | Karma Yogi |
Got it, Thanks. In the board 229.255.41.90 was considered as destination IP. But in my testing using scapy, passed this IP as source IP, hence it was not working.
|
|
| Jan 23 at 11:54 | comment | added | Paul |
Yes, multicast can be the destination if the recipient is listening for it. However, your example had src='229.255.41.90' which implies it is the source IP
|
|
| Jan 23 at 8:32 | comment | added | Karma Yogi |
My board ip is 160.48.219.91. And when i check iproute it daisplays 229.255.41.90 dev eth0.61 scope link src 160.48.249.97. So as per this destination ip is 229.255.41.90 and multicast ip can be destination ip, right ?
|
|
| Jan 23 at 7:41 | comment | added | Paul | You can't use a multicast address as source address. | |
| Jan 23 at 5:40 | history | asked | Karma Yogi | CC BY-SA 4.0 |