Hawaiian tel fiber WAN 0.0.0.0
-
@stephenw10 Hi Steve
I am not sure if i ran it correctly, attached are the results
pcap.txt -
@ariban99 might be better to download and attach the pcap file.
-
Yes that or set the view level to full. That will show tags.
However I don't see any replies to the DHCP requests there. And this looks odd:
19:03:05.113339 ARP, Request who-has 192.168.1.1 tell 192.168.1.1, length 46 -
-
@stephenw10
see attached pcap downloaded file.
however somehow it just started working and i have no idea why. but i now have an IP. maybe the PCAP can say something in case it needs a reboot and i dont get an ip anymore? -
You can upload the file to me here:
https://nc.netgate.com/nextcloud/s/J93aALkntB6GQ4d -
@stephenw10 done
-
Unfortunately there's no DHCP traffic in that capture. It was only set to 100 packets (the default) so it only captured 1.2s.
Try setting it to, say, 5000 packets. And be sure to enable promiscuous mode.
Steve
-
@stephenw10 im sorry about that, i uploaded a second file, is that better?
-
@stephenw10 said in Hawaiian tel fiber WAN 0.0.0.0:
Unfortunately there's no DHCP traffic in that capture. It was only set to 100 packets (the default) so it only captured 1.2s.
Try setting it to, say, 5000 packets. And be sure to enable promiscuous mode. -
Hmm, still no DHCP traffic there. Which is odd since your first pcap had lots in it.
But there is a lot of successful TCP traffic. Are you sure it's still failing to pull a lease?
-
@stephenw10 “however somehow it just started working” mentioned 22 hrs ago
-
Ha, totally missed that!
Well looks fine then.
-
@stephenw10 lol yes it just started working by itself after 2 days plugged in!
For my knowledge, what would i have seen if there was a need to set a VLAN ID? would it have said VLAN ID in the packet capture or its called something else followed by the ID number? -
You can see it in a pcap with the view set to full. VLAN tagged traffic looks like:
13:53:08.514821 90:ec:77:1f:8c:3d > 00:90:7f:b6:30:01, ethertype 802.1Q (0x8100), length 102: vlan 229, p 0, ethertype IPv4, (tos 0x0, ttl 64, id 35682, offset 0, flags [none], proto ICMP (1), length 84, bad cksum 0 (->d968)!) 10.229.0.11 > 10.229.0.10: ICMP echo request, id 63834, seq 0, length 64There showing VLAN 229:
ethertype 802.1Q (0x8100), length 102: vlan 229, p 0If the ISP required a VLAN you would likely see some incoming packets tagged with it.
What I was looking for though was priority tagging which might look like:
ethertype 802.1Q (0x8100), length 102: vlan 0, p 5Some ISPs reply to DHCP requests with priority tagged replies and pfSense will drop those resulting in no lease. They still show in a pcap though.
Anyway neither of those things are happening here.
Steve
-
@stephenw10 Thank you for teaching me. if there was a priority tagged reply and pfsense drop those, is there a solution to make that work? or its not possible to use pfsense in that case?
-
There are two possible workarounds for ISPs who do that.
You can put a vlan capable switch in between the WAN and ONT/modem. The 1100/2100/3100 can do that using their on-board switch.
You can use a netgraph script to strip the vlan0 tags. That works with any NIC except igb currently.Just to be clear though you don't need either if those.
Steve
-
@stephenw10 correct i dont need any of these and my internet works. i just wanted to learn from you in case something like that happens here in Hawaii.
Thank you again for everything and for the knowledge you taught me in this case.
