Revised New Build
-
The Viking card interface must be in the same subnet as the router part of the Viking card.
I thought you said you had set it to 192.168.0.1?
It doesn't matter as long as it's in a different subnet to the pfSense LAN interface.So if the Viking modem/router is at 192.168.1.1 the you could set the viking interface as 192.168.1.10 and have the pfSense LAN as 192.168.0.100.
Don't set it as the default gateway. Only traffic to the modem webgui will use it.
Steve
-
My Viking card is in bridge mode and is still at the default 192.168.1.1 address. I tried your latest suggestion, but the "one moment please . . ."
arrow just keeps spinning when I click save, sort of like Ezekiel and the Wheel. -
I just did another hour of experimenting. The only way that I can access my Viking modem is via telnet, and the only way I can telnet to it is if I disable its PPPoE WAN interface in PfSense.
-
Ah well it may be that the Viking card doesn't provide a web gui in bridge mode.
Where are you telneting from? Can you ping it?
Are you seeing anything in the firewall logs? You shouldn't be but worth checking.Steve
-
I have to telnet the Viking card in my PfSense box (via IPMI from one of my networked computers). I dropped an e-mail to the manufacturer's tech support group about the matter to see if there is a telnet command that activates an access override on the web interface.
-
If it is responding to telnet then you should be able to telnet to it from a LAN machine if you have NAT setup correctly.
Steve
-
But I can only telnet to it when the WAN port is deactivated. :(
-
Well like I said not all modems offer a webgui in bridge mode. :(
I'm surprised though. Can you ping it?Steve
-
I can ping the card, but, again, only when the WAN port is deactivated. I'm still waiting to hear from the manufacturer as I know there are more telnet commands of which I am not aware.
-
Steve:
I finally figured out how to access the Viking card through pfSense–see the new thread I created earlier today under the "Firewall" forum.
