Inability to get DHCP ? No Carrier – SOLVED.
-
LED on the ASUS WAN is green (10mbps… my connection speed is 6mbps.
WOW!!! 6 millibit/s!!!
Actually, it shouldn't show green for 10 Mb, unless the other end is only a 10 Mb interface. The light has nothing to do with the actual bandwidth. For example, the modem interface could be capable of 1 Gb, yet still only provide 6 Mb, as limited by ADSL.
-
Seems the SG3100 is affected by this as well: https://redmine.pfsense.org/issues/7532
That would severely suck for me… as that's going on 6mo with no movement. Is there any way I can actually see what my connection is ? based on 6Mbps, it very well could be 10FD.@JKnott:
LED on the ASUS WAN is green (10mbps… my connection speed is 6mbps.
WOW!!! 6 millibit/s!!!
Actually, it shouldn't show green for 10 Mb, unless the other end is only a 10 Mb interface. The light has nothing to do with the actual bandwidth. For example, the modem interface could be capable of 1 Gb, yet still only provide 6 Mb, as limited by ADSL.
Haha thank you for pointing out the error of my ways. The light is a very definitive green, as compared to the yellow of the connection coming out of the switched ports. There is 100Mbps internet coming into this area though, which leads me to believe the line is faster than 10baseF. The light would also be green with a 100Mbps negotiated link too, correct ? Is there a way for me to determine what protocol the line is running 10 or 100 or 1000baseF ?
I have also submitted a ticket to NetGate for assistance. They want me to test putting an unmanaged switch between the SG3100 and the wall socket, which I'll grab tomorrow.
-
Connect a laptop into the SG-3100 port. What happens?
Connect a laptop to the wall jack. What happens?
If you have no idea why you spoofed the MAC address, why did you do that? Do you know this ISP requires it?
Did you try a crossover cable?
Have you called the ISP to see what they see from their side?
-
Is there a way for me to determine what protocol the line is running 10 or 100 or 1000baseF ?
Unfortunately, the LED status lights are not universal, have to consult the manuals for exact meaning if they are not clearly labeled nearby. Generally, yes light Good, all dark No-Good.
SG3100… amazing these days and age still dealing with negotiation issue.
1000baseF as in FIBER? Once you have RJ45, the "fiber" component is gone. Everything inside your place is baseT, as in Twisted Pairs CAT cablings and jacks. Anywhoo, think we are zero-ing the NICs speed/duplex negotiation component. Got a CROSSOVER ethernet cable laying around?
-
SG3100… amazing these days and age still dealing with negotiation issue.
There have been a couple of things with the built-in switch but that is a new beast and they have been corrected (a couple of bits not flipped quite right in the early releases).
This is the first i have heard of any issues with the other two discrete ports. And I remain unconvinced it is not something to do with settings or the ISP port itself.
I recently got a dumb switch that simply would not establish link with a Mac. The Mac worked with everything else. The switch worked with everything else. Whose fault is that? Who the hell knows. Still happens.
-
The light would also be green with a 100Mbps negotiated link too, correct ? Is there a way for me to determine what protocol the line is running 10 or 100 or 1000baseF ?
You'll have to check the manual to see what the light colour means. As for connection bandwidth, you need some way to check the bandwidth status. I'm not familiar with that equipment, so I can't say. On pfSense, you can see on the Status/Interfaces tab.
-
BREAK BREAK BREAK
SOLVED
So after 5 calls to the ISP and talking to the techs there (it's a small local company with only a few techs who are happy to nerd out about this stuff. One of them was like "you had me at pfsense, brother")
They forced my connection to 100FD, over 1000FD. Apparently they had a contractor come out and dig/install the fiber, and they stole some of the pairs for TV/phone rather than running separate lines.
For some reason, the SG3100 was unable to negotiate a link with the combined internet, tv, phone combo (even though I only have the internet portion). As soon as he forced it to 100FD, it immediately went link status "up" and DHCP "up". It did negotiate a new public IP (in the first couple octets at least) than usual, but who cares. I have internet, and all shall behold the power of this fully operational… SG3100.
Again thank you all for your insight, and all of y'alls instincts about link negotiation were spot. freaking. on. and instrumental to isolating the problem/figuring this out.
Respectfully,
IDThank you all for your help and I will pass this info along to NetGate via the open ticket I have with them and this issue.
 -
Yup, cutting corners without a full CAT cable will cause this. Netgate will be glad to know not a SG box problem. :)
-
They forced my connection to 100FD, over 1000FD. Apparently they had a contractor come out and dig/install the fiber, and they stole some of the pairs for TV/phone rather than running separate lines.
It's obvious someone doesn't know what they're doing. Ethernet auto-negotiation takes place at 10 Mb, over 2 pairs. It will then switch to the best common speed, which the NICs think is 1 Gb. However, GB requires all 4 pairs and so will fail. By locking the modem at 100 Mb, it now only needs 2 pairs.
-
It's obvious someone doesn't know what they're doing.
Nah, I wager is one of those just doing enough the get by. Contractor didn't want the hassle to run a new cable, so use old one with 1/2 pairs. this puppy is gonna come up again at upgrade time, hope the cable is outside of DMARC (ISP responsibility) 'cuz if it's inside, customer's expense to fix/upgrade.
-
A speed/duplex hard-set there is not the end of the world.
-
A speed/duplex hard-set there is not the end of the world.
Not at all. If I had 1Gbps speeds, it would be a different situation. But right now I pay ~30/mo for 6Mbps (I know, sacrilege) or the other option is $120/mo for 100mbps…
Half of me thinks it's 4x the cost for ~15x the speeds, mathematically it makes sense.
The other half of me goes that's $90/mo, 1080/yr that could go towards other things.They forced my connection to 100FD, over 1000FD. Apparently they had a contractor come out and dig/install the fiber, and they stole some of the pairs for TV/phone rather than running separate lines.
It's obvious someone doesn't know what they're doing. Ethernet auto-negotiation takes place at 10 Mb, over 2 pairs. It will then switch to the best common speed, which the NICs think is 1 Gb. However, GB requires all 4 pairs and so will fail. By locking the modem at 100 Mb, it now only needs 2 pairs.
Who doesn't know what they're doing ? The contractor ? Or the ISP ? Or me ? Because definitely me, in addition to whoever else is to blame. There's quite a steep learning curve with this stuff, but it's all very worthwhile. Things we use on a daily basis even with basic router/switch/802.11 radio combo "wireless router"
Yup, cutting corners without a full CAT cable will cause this. Netgate will be glad to know not a SG box problem. :)
Yeah… ISP isn't happy and needed a bunch of info from me as to when exactly I had it installed and other things to (I'm assuming) bring up to the contractor. Since it's a known issue, it makes me think it's in the works to be fixed (small town (50k people live within a 100mi radius) so small companies and limited options. Usually things are resolved peacefully and without litigation.
-
It's obvious someone doesn't know what they're doing.
Nah, I wager is one of those just doing enough the get by. Contractor didn't want the hassle to run a new cable, so use old one with 1/2 pairs. this puppy is gonna come up again at upgrade time, hope the cable is outside of DMARC (ISP responsibility) 'cuz if it's inside, customer's expense to fix/upgrade.
The problem is these days Internet connections often exceed 100 Mb. Mine now offers up to 1 Gb. If the contractor takes pairs for phones, then that connection will never exceed 100 Mb, even though you may be paying for more. It's just a bad idea. Incidentally, other than for Gb, there is not a technical problem with having phone and Ethernet in the same cable. The original spec for what became 10baseT (StarLAN) was designed to work over 3 pair CAT3 cable, with one pair used for the phone and 2 pairs for Ethernet. However, these days it is considered bad practice.
I have also seen contractors do lousy work. One for my sister's cable TV company stapled the black coax right down the middle of the living room wall! On the other hand, when I had a cable modem installed, about 20 years ago, the first guy that showed up wanted to run the coax along the baseboards & around doors etc.. I refused. They then sent 2 men, who took 3 hours to fish the cable from one end of my condo to the other. I also had them pull in a couple of runs of CAT5, so I could have network connections at the other end of my unit. They did a very nice, neat job!
