Urgent.News

What's breaking now, across hundreds of outlets.

Tech

Testing DHCP on tagged VLANs from a Raspberry Pi

A trunk port can look fine and still hand the wrong VLAN a DHCP lease. The usual check is to re-cable a laptop and add a temporary VLAN interface. A Raspberry Pi on the bench is a better test client: small, wired, and easy to leave on the switch port while you watch the offer. This post uses PathProbe, a command-line DHCP and VLAN tester we build, on Raspberry Pi OS 64-bit. The Free tier covers…

When connecting a network device to a trunk port, it may still assign a DHCP lease to the wrong VLAN, even if the port appears correct. To test this, a Raspberry Pi can serve as an easy and reliable client. The PathProbe tool, built by the author, is used for this purpose. Two main tests are performed: the first checks if an untagged client receives a lease from the expected VLAN, and the second verifies if a client sending a VLAN tag gets a lease from that specific VLAN.

If the first test succeeds but the second fails, there might be an issue with the port, trunk, or DHCP helper. To set up the test, install the PathProbe package on the Raspberry Pi, connect it to the switch port being tested, and run the appropriate PathProbe command. The first test uses an untagged interface, while the second uses a single-tagged interface with a specific VLAN ID.

If the tests yield different results, the issue lies with the port, trunk, or DHCP configuration. Remember to test only networks you have permission to test and not publish any sensitive information from the captures.

Rewritten by urgent.news; may contain errors — check the original.

Read the original at dev.to →

Report a problem with this story

More in Tech

Scripting network console sessions with a local API

A lot of network work still happens on a console: a USB-serial cable for the first SSH key, a Telnet jump on a lab switch, then a normal SSH session once the box is up.

  • JackedIN provides API for scripting network console sessions
  • Supports Junos, Cisco IOS/NX-OS, Arista, Nokia, MikroTik devices
  • Offers 72-hour free trial without registration

GRH proof's geometry is `fun _ _ _ => True`, in 24 files

GRH proof's geometry is fun _ _ _ => True , in 24 files Yesterday the Lean and Mathlib communities certified Alpöge's 17.4-million-line GRH proof as correct. Today a paper says the certification proves nothing — because the geometry predicate the proof runs on is defined as fun _ _ _ => True . I opened the source.

  • Geometry predicate defined as fun = True in Alpöge's proof
  • Author found actual geometry predicate named geoOf in source code
  • anyGeometry used in 24 files, geoOf in 12 files

More from Sunday 22 November →