For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Russell_77729's avatar
Russell_77729
Icon for Nimbostratus rankNimbostratus
Apr 09, 2012

traceroute over a VLAN

I know I can use tcpdump -i VLAN_name and only see traffic on that VLAN. The MAN page for traceroute reference a -i option as the interface used to send packets, but I get the following error when I try to use traceroute -i internal_vlan_87 172.31.87.5.

 

 

 

setsockopt SO_BINDTODEVICE: No such device

 

 

Any help/guidance would be greatly appreciated.

 

 

basic
getting started
new to f5

3 Replies

  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Apr 14, 2012
    is vlan name really correct? 

    [root@ve1023:Active] config  b vlan internal list
vlan internal {
   tag 4093
   interfaces 1.2
}

[root@ve1023:Active] config  traceroute -i internal 200.200.200.101
traceroute to 200.200.200.101 (200.200.200.101), 30 hops max, 40 byte packets
 1  200.200.200.101 (200.200.200.101)  4.583 ms  4.547 ms  4.531 ms

[root@ve1023:Active] config  traceroute -i fake 200.200.200.101
traceroute to 200.200.200.101 (200.200.200.101), 30 hops max, 40 byte packets
setsockopt SO_BINDTODEVICE: No such device
  • Russell_77729's avatar
    Russell_77729
    Icon for Nimbostratus rankNimbostratus
    Apr 16, 2012
    thanks for the nudge in the right direction tmsh show /net vlan showed the name is actually internal_vlan~3
  • Hamish's avatar
    Hamish
    Icon for Cirrocumulus rankCirrocumulus
    Apr 17, 2012
    Mm... You may want to keep your vlan names shorter than 16 characters... That was an old one from way back 9.0.3 IIRC...

     

     

    H