Netgate 1100 not getting IP address from WAN
-
When I plug my laptop directly into the port of my Arris S33 modem my laptop gets an IPv4 address and I can ping google.com and other addresses. I also validated that from a different internet connection I can ping the IPv4 address of the laptop as given to it by the S33. Further more I used Wireshark and was able to see the ICMP ping packets into and out of the laptop. So it works as I would expect.
But when I plug the S33 into the WAN port of the 1100 and the laptop into the LAN port of the 1100 I cannot ping addresses on the internet from the laptop.
If I go to "Interfaces -> WAN" in the web interface from the laptop I see title="Interfaces / WAN (mvnet0.4090)" (url=192.168.1.1/interfaces.php?if=wan). There I see the
IPv4 Configuration Type: DHCP.I then click on the "related status" button on the right and I end up at "Status / interfaces" (url=192.168.1.1/status_interfaces.php). There, in the WAN interface section at the top I see:
Status: up DHCP: up MAC Address: f0:... IPv4 Address: 0.0.0.0 Subnet mask: 255.0.0.0 ...IPv4 Address 0.0.0.0 doesn't feel correct.
Maybe the Arris S33 on Xfinity should have a configuration other than
DHCP, but as I mentioned my laptop seems to be working fine and I assume the address is assigned viaDHCP.Any suggestions?
-
@winksaville Have you tried rebooting the Arris? Cable modems often lock onto a MAC address.
-
@steveits, great idea, power cycling worked! Well the 1100 now has an addresses, DNS servers, .... but I still can't reach the internet :(
The route on the laptop when using the 1100 -> Arris S33 -> Xifinity doesn't look right on the laptop:
$ ip route 192.168.1.0/24 dev enp0s13f0u3 proto kernel scope link src 192.168.1.222 metric 100Where as when I plug the laptop into my other network using an Asus RT-AX86U router -> ATT modem -> ATT fiber I get:
$ ip route default via 192.168.1.1 dev enp0s13f0u3 proto dhcp src 192.168.1.105 metric 100 192.168.1.0/24 dev enp0s13f0u3 proto kernel scope link src 192.168.1.105 metric 100So I conclude the route is wrong, so that's where I'll focus tomorrow. TYVM for the power tip!!
Any suggestions on the possible "route" issue?
-
J jimp moved this topic from Problems Installing or Upgrading pfSense Software on
-
Well, today my laptop was able to get a proper route and is able to use the internet as would be expected. I have no idea what is different from today as compared to yesterday. "I changed nothing" except that I unplugged the power from both the Netgate 1100 and the Arris S33 router overnight. I powered them up this morning, first the S33 and let it power up completely. I then powered up the 1100 waiting until the Console Menu popped up and then plugged in the S33 to the WAN port of the 1100.
The final steps were to plug in my usb to ethernet adapter into the laptop, I then started Wireshark and started capturing packets. No packets were being captured, as expected as the there was not cable connected between the laptop and the 1100. The final step was plugging in the cable to the 1100 LAN port.
Wireshark started capturing packets and shortly I had an address and a "proper" looking route:
$ ip a show dev enp0s13f0u3 6: enp0s13f0u3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 00:05:1b:b0:6f:f0 brd ff:ff:ff:ff:ff:ff inet 192.168.1.105/24 brd 192.168.1.255 scope global dynamic noprefixroute enp0s13f0u3 valid_lft 6386sec preferred_lft 6386sec inet6 2601:647:cb00:470a::2000/128 scope global dynamic noprefixroute valid_lft 6388sec preferred_lft 3688sec inet6 2601:647:cb00:470a:37d:3b80:545c:c086/64 scope global dynamic noprefixroute valid_lft 86396sec preferred_lft 14396sec inet6 fe80::faff:5f36:799d:482d/64 scope link noprefixroute valid_lft forever preferred_lft forever $ ip r show dev enp0s13f0u3 default via 192.168.1.1 proto dhcp src 192.168.1.105 metric 100 192.168.1.0/24 proto kernel scope link src 192.168.1.105 metric 100And I could
ping ucsc.edu:$ ping ucsc.edu PING ucsc.edu (128.114.119.88) 56(84) bytes of data. 64 bytes from resnet.ucsc.edu (128.114.119.88): icmp_seq=1 ttl=53 time=12.1 ms 64 bytes from resnet.ucsc.edu (128.114.119.88): icmp_seq=2 ttl=53 time=15.0 ms 64 bytes from webops-vip88.ucsc.edu (128.114.119.88): icmp_seq=3 ttl=53 time=11.9 ms 64 bytes from webops-vip88.ucsc.edu (128.114.119.88): icmp_seq=4 ttl=53 time=11.4 ms 64 bytes from resnet.ucsc.edu (128.114.119.88): icmp_seq=5 ttl=53 time=11.1 ms 64 bytes from webops-vip88.ucsc.edu (128.114.119.88): icmp_seq=6 ttl=53 time=11.1 ms ^C --- ucsc.edu ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 5008ms rtt min/avg/max/mdev = 11.053/12.102/15.016/1.361 msNot sure what I learned, I suspect I did something wrong, but for now I'll chalk it up to "be patient" and "never give up" :)
Thanks @SteveITS