![]() ![]() ![]() |
|
First screenshot should be eth0/LAN1 if you're on UFB as you said in your original post (ptm0 is for VDSL)
LAN1 corresponds to the numbered port on the back which needs to be connected to the ONT.
yitz:
First screenshot should be eth0/LAN1 if you're on UFB as you said in your original post (ptm0 is for VDSL)
LAN1 corresponds to the numbered port on the back which needs to be connected to the ONT.
Is the WAN service you set up under eth0/LAN1 ppp0.1 or ppp1.1 ? The correct one needs to be selected for Default Gateway and DNS interfaces. If you don't know, then go into Advanced Setup -> WAN Service and remove both. Then recreate a WAN service on eth0/LAN1 again.
yitz:
Is the WAN service you set up under eth0/LAN1 ppp0.1 or ppp1.1 ? The correct one needs to be selected for Default Gateway and DNS interfaces. If you don't know, then go into Advanced Setup -> WAN Service and remove both. Then recreate a WAN service on eth0/LAN1 again.
Down the left hand side under Device Info --> WAN. Under WAN Info does the Status show Connected?
Is the cable between port LAN 1 on the NF17ACV and first port on the ONT physically connected?
The logical setup appears fine to me but I would double check the physical setup. LAN1 should be the port at the end of the row of 4 ports on the back, worst case there have been cases where other manufacturers have the labels the wrong way round.
yitz:
Down the left hand side under Device Info --> WAN. Under WAN Info does the Status show Connected?
Is the cable between port LAN 1 on the NF17ACV and first port on the ONT physically connected?
The logical setup appears fine to me but I would double check the physical setup. LAN1 should be the port at the end of the row of 4 ports on the back, worst case there have been cases where other manufacturers have the labels the wrong way round.
What if you plug the blue cable into the yellow port 1 on the back?
Perhaps the trick on this particular device is to update the firmware... is it that the blue WAN port can only be configured through the Basic Setup wizard which at least on the original firmware version does not support tagged WAN interfaces.
yitz:
What if you plug the blue cable into the yellow port 1 on the back?
Perhaps the trick on this particular device is to update the firmware... is it that the blue WAN port can only be configured through the Basic Setup wizard which at least on the original firmware version does not support tagged WAN interfaces.
OK it seems you will need to update the firmware on this device
http://support.netcommwireless.com/product/nf17acv#Firmware
Download the release notes and firmware file and perform the upgrade (instructions provided in release notes).
After upgrading, plug the blue cable into the blue port and run the Basic Setup wizard which will now also ask for Vlan ID details.
--
R5B019
New Features
Added custom VLAN tagging to the Basic Setup page for VDSL/ETH WAN interfaces
yitz:
OK it seems you will need to update the firmware on this device
http://support.netcommwireless.com/product/nf17acv#Firmware
Download the release notes and firmware file and perform the upgrade (instructions provided in release notes).
After upgrading, plug the blue cable into the blue port and run the Basic Setup wizard which will now also ask for Vlan ID details.
--
R5B019
New Features
Added custom VLAN tagging to the Basic Setup page for VDSL/ETH WAN interfaces
|
![]() ![]() ![]() |